# Core Architecture v2 CI Alignment Campaign

**Campaign:** PR #64, branch core-architecture-v2
**Normative target:** CORE_ARCHITECTURE_V2.md (unchanged)
**Baseline local/PR HEAD:** bbe2bc6624d2b1a51f001f6dec566786590b1296
**Baseline GitHub Actions run:** https://github.com/JamesMorales04/agentic-engineering-harness/actions/runs/36782724704
**Most recent fully verified checkpoint before this status-record reconciliation:** `963cc3010dc5b372a282da4f37859a8ce6a27796`
**Campaign state:** status-doc candidate `963cc3010dc5b372a282da4f37859a8ce6a27796` passed all 13 required jobs in run [36832161124](https://github.com/JamesMorales04/agentic-engineering-harness/actions/runs/36832161124), after fresh independent review (Round 16). S10 re-acceptance remains a separate open architecture merge gate. The exact required-check result for each checkpoint is attached to its PR SHA; no merge claim is made in this record.
**Pre-amendment evidence snapshot (2026-10-01):** checkpoint `325605ebf842d098aa0fdbe556c433c3aac9cc0b` remains historical. At this snapshot, PR #64 head was `48276ea842fa3af475eb32632d995b18f755f17c`; GitHub run [36817138377](https://github.com/JamesMorales04/agentic-engineering-harness/actions/runs/36817138377) passed 12 of 13 jobs. Rootless isolation passed its real hosted campaign 3/3; packaged-consumer failed only at the final `aeh intent` smoke because the clean consumer had no session-scoped Paseo Semantic Assessor SDK/provider. A typed deterministic INTENT-fixture repair passed the direct built-CLI smoke locally. As of this snapshot, that repair was the next checkpoint candidate and had no hosted result. Fresh independent review and a new hosted run remain required; the campaign is not accepted.

**Intermediate hosted snapshot (2026-10-01):** PR #64 head `ff2b9f279fcf6c974f626875dc99248881613a79`; run 36822314115 checked PR merge SHA `64e3f963f7bf70e287da13f0f9aefb13e26c0450` for this head and completed 12/13 jobs. Packaged-consumer and rootless-isolation passed; test/release failed only at F5, the 5,000ms capability-detection timeout. The focused F5 fixture repair passed locally 10/10 in 417ms and was then pending hosted validation; run 36824682741 below verifies it on d21d6b5, the last green implementation checkpoint before this documentation-only amendment.

This document records CI evidence, not architecture certification. A green local suite does not replace the current PR checks. The TARGET remains authoritative; this campaign changes only the implementation, test, workflow, and evidence layers.

## Lead WorkGraph

| Node | Work | Status |
| --- | --- | --- |
| W0 | Reconstruct Git, PR, failed workflow, tests, production code, and target contracts. | COMPLETE |
| W1 | Record every baseline failure and owning-layer hypothesis. | COMPLETE |
| W2 | Reproduce provider-absent cases and capture lifecycle/fixture evidence. | COMPLETE |
| W3 | Repair owning fixtures and provider lanes. | Complete. Run 36824682741 on the last green implementation checkpoint d21d6b5 confirms all 13 jobs pass, including packaged-consumer, rootless-isolation, and test/release after the F5 fixture repair. |
| W4 | Separate deterministic, integration, rootless, provider, full-stack, supply-chain, and packaged lanes without coverage loss. | COMPLETE LOCALLY |
| W5 | Run repaired focused tests, deterministic/reliability suites, and every locally supported owner lane. | Hosted run 36824682741 on implementation checkpoint d21d6b5 completed all 13/13 jobs successfully; run 36822314115 remains the historical F5 failure that prompted the final fixture repair. The later status-doc candidate 963cc passed 13/13 in run 36832161124. The exact-SHA check result for each subsequent evidence snapshot is attached to its PR Actions run. |
| W6 | Update status, conformance, and ledger; hand off exact diff for fresh review. | Updated the four durable CI evidence documents and reconciled STATUS/CONFORMANCE/LEDGER to accepted closure evidence. Run 36824682741 passed 13/13 on implementation checkpoint d21d6b5; the later status-doc candidate 963cc passed 13/13 in run 36832161124 and was independently reviewed. Exact-SHA check results are recorded by GitHub Actions. |

## Reconstructed baseline

- Local core-architecture-v2, origin/core-architecture-v2, and PR #64 head were bbe2bc6624d2b1a51f001f6dec566786590b1296; local branch divergence from main was 0 18.
- PR #64 was OPEN against main. The failing baseline jobs were test, adversarial-system, human-e2e, system reliability campaign, full-stack-contract, and supply-chain.
- Baseline passing jobs were scenario-matrix, provider-contracts, validation provider contracts, real Pact provider verification, and OCI integration environment contract.
- npm test/release:check originally ran all Vitest-discovered files, including host/provider-dependent tests and a Node node:test file. Rootless isolation was in the generic suite without an installed bwrap provider. Provider-dependent Spec Manager tests had no pinned OpenSpec in their owner lane.
- The reconstruction and complete initial test-level inventory are preserved below. New failures exposed while running repaired aggregate lanes are included as separate rows.
- The baseline had 6 failing jobs and 33 unique failure records: 30 Vitest assertions in the generic test job, one Vitest file-discovery failure for the Node node:test file, one strict full-stack fixture failure, and one supply-chain job failure. Human, adversarial, and system-reliability job appearances repeat tests from the generic test job and are not counted again. A3, A4, C3, F3, F4, P1, and E2 were discovered during later validation and are separate from the original count.

## Checkpoint history and latest repair-round findings

The Campaign Director's sole checkpoint was `325605ebf842d098aa0fdbe556c433c3aac9cc0b`. PR run [36803071091](https://github.com/JamesMorales04/agentic-engineering-harness/actions/runs/36803071091) completed with 11 passing jobs and two failing jobs. Passing: test/release, scenario-matrix, system reliability, adversarial-system, human-e2e, provider-contracts, validation provider contracts, Pact provider verification, full-stack-contract, supply-chain, and OCI integration. Failing: packaged-consumer and rootless-isolation.

| ID | Job / exact observation | Reproduction and classification | Owning-layer repair / evidence boundary |
| --- | --- | --- | --- |
| P1 | Historical packaged-consumer failure on checkpoint SHA 325605: npm pack --silent captured prepare/build output with the archive filename; npm install exited 254/ENOENT. | The checkpoint hosted log and initial local replay established lifecycle-output contamination. CI_WORKFLOW_DEFECT. | The workflow builds explicitly, packs into RUNNER_TEMP with scripts/ci/packCandidate.mjs, and derives the archive from verified package metadata. It installs/verifies Podman. Pre-amendment run 368171 on SHA 48276 passed archive identity, clean install, CLI/MCP, init, toolchain compile, Podman setup, and policy sync before the separate P3 intent failure. P1 is verified repaired by that run. |
| P2 | Local packaged-consumer replay: packaged human CLI deterministic start saw empty captured stdout where it expected sessionBoundary=deterministic-fake-paseo-sdk; init succeeded with no stderr. | Reproduced only in the restarted managed shell, where Node-child execFile output was empty while an equivalent shell child was captured. ENVIRONMENT_COUPLED_TEST for the local observation. The pre-amendment GitHub run 368171 on SHA 48276 passed the packaged tarball journey 1/1. | Keep the stdout and session-boundary assertions. Record the managed-shell observation as local environment coupling; pre-amendment hosted evidence passed the packaged journey. |
| P3 | Pre-amendment run [36817138377](https://github.com/JamesMorales04/agentic-engineering-harness/actions/runs/36817138377), SHA 48276ea842fa3af475eb32632d995b18f755f17c: packaged-consumer final aeh intent smoke failed with SEMANTIC_ASSESSMENT_UNAVAILABLE. The clean consumer had no paseo executable and could not resolve @getpaseo/client; the configured session-scoped opencode Semantic Assessor correctly refused CLI fallback because dropping the launch environment could change native identity or permissions. | Exact hosted job log. TEST_HARNESS_DEFECT: the clean-consumer smoke invoked semantic INTENT without the deterministic runtime's typed response fixture. Production correctly fails closed when its required assessor cannot run. | The typed-fixture repair supplies the existing semantic-assessment:INTENT response and scopes AEH_DETERMINISTIC_PASEO_RUNTIME=1 AEH_PASEO_FORCE_CLI=0 to the unchanged intent call. It preserves the ^AUDIT assertion and adds no production fallback or provider optionality. Direct built-CLI smoke passed locally. The current run 36824682741 on PR head d21d6b5 passes packaged-consumer, including the consumer install/CLI smoke, confirming the typed fixture repair in hosted CI; the earlier no-hosted-result statement is historical to the 48276/368171 snapshot. |
| F4 | Packaged-consumer setup initially reported missingSystem=podman on a local host without Podman; the default toolchain correctly requires Podman. | Reproduced locally without Podman; unchanged setup and policy-sync assertions pass with real Podman 6.1.2. PROVIDER_PROVISIONING_DEFECT. Pre-amendment run 368171 installed/verified Podman 4.9.3 and passed setup/policy sync. | Podman is explicitly installed and version-checked in the packaged-consumer lane; the default toolchain and setup assertions remain. F4 is verified repaired by the pre-amendment hosted run. |
| E2 | rootless-isolation / tests/system/aehIsolationCampaign.test.ts: on checkpoint 325605, Ubuntu 24.04/bwrap 0.9.0 failed namespace execution and the validator returned FAIL; the old hosted logs lacked stderr. | The Ubuntu 24.04 AppArmor capability restriction was the best-supported cause. Pre-amendment run 368171 on Ubuntu 22.04 with bwrap 0.6.1 records CapEff=0000000000000000, NoNewPrivs=1, namespace smoke PASS, and the full real namespace/mutation/validator/egress suite 3/3 PASS. CI_ENVIRONMENT_DEFECT, verified repaired for hosted CI. | The required unprivileged provider and every original assertion remain. The Ubuntu 22.04 pin is temporary; migrate before its scheduled 2027-04-17 full unsupported date (official runner-image schedule: https://github.com/actions/runner-images/issues/14254). Local restricted-shell NETLINK_ROUTE failure does not override the hosted pass. |
| E3 | rootless-isolation / home-masking subassertions in tests/system/aehIsolationCampaign.test.ts. | Fresh review found the prior synthetic HOME beneath /tmp did not independently prove host-home masking (TEST_HARNESS_DEFECT). The fixture creates HOME under the checkout, proves .ssh and sentinel preconditions, and checks no visible/toolchain read-only path overlaps HOME. | Pre-amendment run 368171 on SHA 48276 passed all three tests, including actual home/namespace isolation, mutation denial, validator execution, and egress blocking. HOME is restored and its fixture removed in finally; E3 is exercised by the passing real lane. |

## Failure inventory and final local disposition

Rows cover each unique baseline failure family; duplicate appearances in test, system reliability, and dedicated lanes are recorded in the job column. New failures found during repair validation are explicitly marked.

| ID | Job / exact failing test | Observed failure and owning contract | Reproduction and evidence | Classification | Owning-layer repair and result |
| --- | --- | --- | --- | --- | --- |
| A | human-e2e, system reliability, test / tests/system/aehHumanBlackBox.test.ts: H01, H02, HJ-01 through HJ-12, five-turn continuation, informational follow-up, and packaged tarball journey (17 daemon-dependent assertions). | aeh start --deterministic received exit 0 and {} from paseo daemon status --json; production correctly classified this as unknown and failed closed. TARGET §§3/10. | Reproduced before repair. After changing only the deterministic boundary response to {localDaemon:"running",connectedDaemon:"not_probed"}, complete human lane passes 19/19; complete system campaign passes 67/67. observePaseoDaemonStatus() is unchanged. | STALE_TEST_FIXTURE | Repaired fixture to emit a supported explicit healthy status. No arbitrary exit-code or unknown-state relaxation. Pre-amendment GitHub run 36817138377 on SHA 48276 passed human-e2e and system reliability. |
| A2 | Same jobs / “routes natural-language informational, audit, and change prompts through the built CLI”. | Empty stdout and SEMANTIC_ASSESSMENT_UNAVAILABLE: a deterministic CLI contract case called the real MODEL/HYBRID semantic assessment without a scripted provider response. TARGET §2. | Reproduced after A isolated the daemon issue. Typed scripted INTENT/ROUTE assessments preserve the actual output schema and route assertions; complete human lane passes. | TEST_HARNESS_DEFECT | Added deterministic typed provider responses at the test boundary. No keyword-based product routing. |
| A3 | Human lane / “preserves structured context referents and constraints across five multi-turn continuations”. | Isolated execution measured 5.136s against Vitest’s 5s default; final complete human run measured 5.107s. | Reproduced over the bound; complete human/system reruns pass with a per-test 15s bound. | FLAKE_CONFIRMED | Replaced the inadequate default bound with 15s, based on measured five-process latency. No sleep or retry. |
| A4 (found during repair) | System reliability / “runs the packaged tarball through init, deterministic start, and a completed user turn”. | Failed at 30.016s under aggregate system-suite contention; the same package journey measured 29.098s alone. | After changing only the measured per-test bound, aggregate system run passes this case in 29.145s; packaged-consumer lane passes it in 29.112s; full human lane passes all 19. | FLAKE_CONFIRMED | Set a measured 45s bound. The test remains in complete human/system coverage and also has an explicit packaged-consumer owner run. |
| B | adversarial-system, system reliability, test / “does not allow a terminal operation to re-enter active execution”; “records completion callback failure without changing terminal truth”. | Synthetic RUNNING→SUCCEEDED fixtures lacked objective-completion and current AcceptanceOracle evidence; assertSuccessTerminalEvidence() correctly rejected them with OBJECTIVE_COMPLETION_REQUIRED. TARGET §12. | Reproduced locally before repair. Migrated fixtures now create CandidateRevision, current oracle result, persisted oracle artifact, and objective-completion evidence through canonical helpers. Focused and complete adversarial lane pass 28/28; full system run passes. | STALE_TEST_FIXTURE | Preserved both original adversarial assertions and the production terminal gate. |
| C | supply-chain / “Generate and verify the production-path evidence chain”. | Workflow omitted normalized provenance.artifact and generated evidence for supply-chain-fixture.txt, failing the strict artifact contract. TARGET §15. | Final evidence-collection run used disposable worktree /tmp/aeh-ci-runner-temp/aeh-supply-chain-evidence-final2; retained bundle /tmp/aeh-ci-runner-temp/supply-evidence-final2. Artifact SHA-256 a4fd36bf4b64a4f016f471159b9114ae67d249c05fc621bd44b7a9e527ed3321; CandidateRevision digest b8e48021741e0a6d523ab4f012e19841ee7abd2a8be00a998d1016f7ae285924; 54-component SBOM; summary SHA-256 ddc4de859cf97b33edf74fd27e94720a437876674b76789de9b3d7e4e65ecf30. The machine-readable summary contains digests for the original tarball, SBOM, manifest, in-toto statement, SLSA predicate, signature bundle, and public key. The copied bundle and summary sidecar were verified; privateKeyIncluded=false; pre-tamper strict verification PASS; tampering the original tarball is rejected. | CI_WORKFLOW_DEFECT | Workflow packs the real candidate in a temporary Git worktree, creates controller-owned candidate evidence, generates and verifies artifact-bound SBOM/provenance/signature, copies the exact .tgz, SBOM, manifest, statement, predicate, bundle, public key, and digest summary to RUNNER_TEMP, uploads them before tampering, then rejects tampering against the original tarball. Pre-amendment GitHub run 36817138377 on SHA 48276 passed supply-chain. |
| C3 | supply-chain / SBOM generation for packed artifact. | Trivy 0.70.0 fs --format cyclonedx <file.tgz> exits 0 but reports zero components for this npm archive. | Final pinned-tool run produced 54 components and all 10 direct runtime dependencies; product component/version and SHA-256 match the exact .tgz; SLSA sbomArtifactSha256 matches the same digest. | CI_WORKFLOW_DEFECT | Added scripts/ci/generatePackedArtifactSbom.mjs; it validates archive paths, packaged identity/version, matching lockfile identity, non-empty runtime dependency inventory, package component, and tarball SHA-256 before provenance signing/verification. |
| D | full-stack-contract / “runs the deterministic full-stack production-path fixture”. | Baseline fixture fabricated a COMPLETED run and directly called buildEffectivePrompt, bypassing controller identity, authority, read lease, and authorized retrieval. TARGET §7 and reversible context recovery. | Migrated to a disposable controller-owned AUDIT operation and actual participant identity/binding/retrieval path. Strict local run initially showed pretty JSON line-sampled to 202 tokens before Headroom, so compression did not beat that projection. The fixture now stores the same verified ValidationReport value in compact JSON and asserts canonical digest equality. Its persisted AuditReport is explicitly DEGRADED and productionSafe=false because this fixture does not run production audit aggregation. Strict run passes 8/8 with pinned Engram, Headroom, Graphify, Serena and Trivy. Retained report: .aeh-test-results/full-stack-contract.json, SHA-256 356826b038d1a22332919ff2693d44d15466a327a3c578585a59dc202502dbf4; all 14 check IDs, details, and the non-certifying audit scope are in the uploaded JSON. Latest evidence: operation AUDIT-20261001T012426Z-f83a6fe7; participant participant:7adf1c26f6831829; read lease lease:AUDIT-20261001T012426Z-f83a6fe7:request:AUDIT-20261001T012426Z-f83a6fe7:participant:7adf1c26f6831829:read:review; binding 7ba1e5cec97c1a04ad1095c5cdd565150c618356e25c68b7f1f83a7974396fb7; session deterministic:dec4eb8d-8ce1-4b8a-ad62-cf604988799e; receipt receipt:participant:7adf1c26f6831829:2026-10-01T01:24:28.509Z; validation-evidence source/recovered digest both 3e5f8880adc2e9a9db103bb7ce45ff4dbc1804d314057df6e7f2ddb1bc496118; recovery handle aeh-context://AUDIT-20261001T012426Z-f83a6fe7/validation-evidence/3e5f8880adc2e9a9db103bb7ce45ff4dbc1804d314057df6e7f2ddb1bc496118; one fragment compressed. Persisted audit-scope check asserts DEGRADED/productionSafe=false and actual dirty paths. | STALE_TEST_FIXTURE | Strict fixture traverses actual controller-issued authority and exact-byte authorized retrieval, and exercises reversible Headroom compression against the unchanged verified report value. Test asserts lease, binding, receipt, source/recovered digest, handle, compressed count, and the non-certifying AuditReport scope. GitHub strict job uploads this machine-readable evidence before fixture cleanup. |
| E | system reliability, test / tests/system/aehIsolationCampaign.test.ts real rootless isolation campaign: provider, namespaces, home/workspace scope, mutation, validator, and egress. | Checkpoint 325605 on Ubuntu 24.04/bwrap 0.9.0 failed namespace execution and validator returned FAIL. AppArmor capability restrictions are the best-supported cause; the local managed shell independently reports NETLINK_ROUTE: Operation not permitted. | Pre-amendment hosted run 368171 on Ubuntu 22.04/bwrap 0.6.1 passed preflight (CapEff=0, NoNewPrivs=1) and all three real tests. The separate local failure is environment-bound. | CI_ENVIRONMENT_DEFECT | The unprivileged rootless provider lane and all required assertions remain; see E2 for hosted environment repair and E3 for home-mask fixture repair. No skip or sandbox weakening. |
| E2 | rootless isolation CI runner/provider environment (Ubuntu 24.04 versus Ubuntu 22.04). | Ubuntu 24.04's default AppArmor profile allows user-namespace creation but denies subsequent capabilities; Ubuntu's 22.04 security matrix does not list that restriction. This was the supported diagnosis for checkpoint failure. | Pre-amendment GitHub run 368171 records bwrap 0.6.1, CapEff=0000000000000000, NoNewPrivs=1, namespace smoke PASS, and the actual namespace/mutation/validator/egress campaign 3/3 PASS. | CI_ENVIRONMENT_DEFECT | The lane is temporarily pinned to Ubuntu 22.04 with required provider setup and assertions. Migrate before the scheduled 2027-04-17 full unsupported date (official schedule: https://github.com/actions/runner-images/issues/14254); local restricted-shell NETLINK_ROUTE failure does not override the hosted result. |
| E3 | tests/system/aehIsolationCampaign.test.ts host-home masking proof. | The previous synthetic HOME lived below the /tmp overlay, so .ssh/sentinel absence could be caused by the overlay rather than host-home masking. TEST_HARNESS_DEFECT. | The fixture now creates HOME under the checkout, proves .ssh and a sentinel exist beforehand, and checks no visible/toolchain read-only path overlaps HOME. Pre-amendment run 368171's real rootless lane passed all 3 tests, including home/namespace isolation, mutation denial, validator execution, and egress blocking. | TEST_HARNESS_DEFECT | HOME is restored and the fixture removed in finally. All home/scope and sandbox assertions remain enabled and passed in the hosted real-provider lane. |
| F | Generic test / release:check suite topology. | npm test originally discovered hermetic tests, system journeys, missing-host-provider tests, rootless isolation, provider-dependent tests, build/package tests, and a Node node:test file. | In the pre-restart unrestricted shell, release:check passed typecheck/build, deterministic Vitest 200 files (1 skipped; 1,368 passed, 7 skipped), Node test 3/3, and npm pack --dry-run. The later post-restart managed-shell run failed during the deterministic stage as recorded below; this earlier pass is not evidence for that environment or for current hosted CI. Every excluded file has an explicit workflow/script owner below. | CI_WORKFLOW_DEFECT | Created deterministic/unit, system, human, scenario, adversarial, provider, rootless, full-stack, supply-chain and packaged-consumer ownership. No required suite is silently skipped; Playwright provider contract remains in its real provider lane. |
| F1 | test / tests/packed/s13GovernedCampaignPolicy.test.mjs. | Vitest reports “No test suite found”; the file uses node:test. | release:check runs it with node --test; all 3 pass. | TEST_HARNESS_DEFECT | Run with owning Node test runner and exclude that file from Vitest discovery. |
| F2 | test / tests/validation/failClosedProviders.test.ts, “blocks a required OCI integration environment when no container runtime is available”. | 5s timeout because containerRuntime probed live host podman/docker and could consume its 10s timeout; the test incorrectly assumed provider absence. Required OCI absence must still fail closed. | Controlled-empty-PATH reproduction passes; focused provider suite 12/12. Real OCI provider remains in integration-environment. | ENVIRONMENT_COUPLED_TEST | Test supplies an empty executable PATH to its no-provider assertion; production REQUIRED behavior untouched. OCI job command remains an actual Docker run. |
| F3 (local validation boundary) | integration-environment / actual Docker smoke: docker run --rm --network none alpine:3.20 sh -c ... | Local docker CLI could not connect to /home/james/.docker/desktop/docker.sock. This is a local provider absence, not a baseline GitHub Actions failure; baseline hosted OCI job passed. | Reproduced locally by docker info and the exact workflow docker run; both fail before container creation because no local daemon exists. | CI_ENVIRONMENT_DEFECT | Keep the real Docker command in its dedicated GitHub lane. Do not skip or mock the provider. The owning OCI integration job passed in pre-amendment GitHub run 36817138377 on SHA 48276. |
| F5 (discovered in run 36822314115) | test / tests/security/isolation.test.ts:113, “detects provider capabilities deterministically and reports missing providers”. | On Ubuntu 24.04.5 the generic runner image includes Podman 4.9.3 and Buildah 1.33.7. The test called detectIsolationCapabilities(root) with ambient PATH; production resolution reaches the live `podman info` probe (20s process bound), while Vitest enforces 5s. The hosted log confirms the timeout at the detection call but does not identify which subprocess remained active; this is environment coupling in the test fixture, not evidence of a product regression. | `npx vitest run tests/security/isolation.test.ts --reporter=dot` passes 1 file / 10 tests in 417ms after using a unique temp root and empty executable PATH. The test asserts `provider=none`, unavailable, and missing bwrap/podman/buildah details, and marks the suite sequential, restores PATH/cache in `finally`, and removes the temp root. Run 36824682741 on PR head d21d6b5 passes test/release; the hosted rerun validates the repair, though the job summary does not expose this individual test count. | ENVIRONMENT_COUPLED_TEST | Isolate the missing-provider contract test from host executables; leave production capability discovery and required-provider fail-closed behavior unchanged. Official runner package inventory: https://github.com/actions/runner-images/blob/ubuntu24/20260920.314/images/ubuntu/Ubuntu2404-Readme.md. |
| G | test / tests/contextArchitectureClose.test.ts, “keeps coordinator context forbidden while optional workers receive an explicit fallback”. | Noncanonical test role coordinator caused a live required Serena readiness check. | With Serena absent from PATH, original fixture fails; changing only role to canonical Operation Supervisor yields 9/9 pass without Serena. | STALE_TEST_FIXTURE | Canonical role fixture restored; production static capability resolution/live readiness boundary unchanged. |
| H | test / tests/specManagerCanonicality.test.ts: Planner escalation to FORMAL_SDD; rejection of noncanonical READY content before persistence (2 tests). | Baseline first assertion expected FORMAL_SDD but received DELEGATED; the second reached OPENSPEC_UNAVAILABLE because openspec was absent from CI PATH and provider-contracts did not install it. A stale global local openspec 1.3.1 was supplemental local evidence, not the observed GitHub cause. | Pinned OpenSpec 1.13.2 advertises required authoring flags; full local provider command including H passes. No route assertions changed. | PROVIDER_PROVISIONING_DEFECT | Pin and install OpenSpec 1.13.2 in provider-contracts. Invalid READY content still fails before persistence. |
| I | test / tests/changePlanRequirementTraceability.test.ts, “seals the routed contract before planning and the planner references its frozen requirement ids”. | Missing contract-authoring stage was downstream of absent Serena: UNSUPPORTED_CAPABILITY in discovery; terminal FAILED at triage, route DELEGATED, TaskContract/Planner absent, policy fresh, script cursor consumed route and supervisor only. | Diagnostic is attached to assertion. Full provider command with pinned Serena/OpenSpec passes. | PROVIDER_PROVISIONING_DEFECT | Test remains in provisioned provider-contracts lane; no stage assertion removed. |
| J | test / tests/changeControllerOwnedDecision.test.ts, “reaches HUMAN_REQUIRED through the real controller, then pauses, resumes, and cancels”. | No-OpenSpec reproduction terminalized FAILED at environment preflight with OPENSPEC_UNAVAILABLE; FORMAL_SDD route, last completed stage triage, and no TaskContract/Spec Manager/DecisionRequest/continuation. Controller record/events were readable. | First 90s wait emits durable snapshot with terminal/error/stage/route/contract/participant/session/decision/policy/cursor/read-path details. Pinned provider command passes. | PROVIDER_PROVISIONING_DEFECT | OpenSpec 1.13.2 is installed in provider-contracts; 90s lifecycle bound and all HUMAN_REQUIRED assertions remain unchanged. |
| K | test / tests/buildHygiene.test.ts, “keeps dist/main.js available while a real build is running”. | CI fixed 30s sampling/SIGKILL raced with real 18–22s builds under generic-suite contention; child was killed (exit null). | Baseline isolated passes: 21.94s, 19.26s, 18.30s. Repaired focused passes: 17.94s, 17.82s; packaged-consumer build-hygiene pass: 17.364s. | FLAKE_CONFIRMED | Replaced wall-clock sampling and kill with .build.lock observation, rename/change handling for lock/entrypoint, real CLI probes while lock is held, and child-close synchronization. Build/package tests have an explicit owner lane. |

## CI ownership after migration

| Lane | Test ownership | Local evidence |
| --- | --- | --- |
| test / release:check | Typecheck, build, deterministic unit/contract Vitest, Node node:test, npm pack dry-run. | Pass: 200 Vitest files / 1 skipped, 1,368 passed / 7 skipped; Node 3/3; build and pack pass. |
| scenario-matrix | Scenario state/action matrix. | 8/8 pass. |
| adversarial-system | Core terminalization and adversarial system tests. | 28/28 pass. |
| human-e2e | Full human CLI and deterministic provider journeys. | 19/19 pass. |
| system-reliability | All system suites except separately owned rootless file; complete reliability report. | 5 files / 67 tests; report PASS. |
| rootless-isolation | Actual bubblewrap namespace/mutation/network/validator isolation. | Pre-amendment GitHub run 368171 on SHA 48276: bwrap 0.6.1; `CapEff=0`, `NoNewPrivs=1`, namespace preflight PASS; real campaign 3/3 PASS. The restricted local shell still fails network namespace setup with `NETLINK_ROUTE: Operation not permitted`; hosted evidence owns the CI disposition. |
| packaged-consumer | Six build/hygiene tests, packaged human CLI journey, clean-consumer smoke. | In pre-amendment run 368171 on SHA 48276, build/hygiene 6/6, packaged journey 1/1, and consumer pack/install/CLI/MCP/init/toolchain/Podman setup/policy sync passed; final intent command failed because its deterministic Semantic Assessor response fixture was absent. At the 2026-10-01 snapshot, the typed-fixture repair was the next checkpoint candidate; its direct built-CLI smoke passed locally, and it had no hosted result. |
| provider-contracts | Pinned Headroom, Graphify, Engram, Serena MCP, OpenSpec, Trivy, OpenGrep, Playwright and H/I/J tests. | 17/17 with pinned tools and local Engram server; Chromium installed under temp HOME. |
| full-stack-contract | Strict disposable controller/authority/reversible recovery path with required providers. | 8/8; .aeh-test-results/full-stack-contract.json is mandatory upload with all check details. |
| supply-chain | Exact packed candidate, artifact-bound SBOM/provenance/signature/verification/tamper rejection. | Strict end-to-end pass; supply-chain-evidence artifact retains the exact package, SBOM, manifest, statements, bundle, public key and digest summary before tampering. |
| validation-contracts, Pact, OCI integration | Real validation provider and integration owners. | Validation provider suite 7/7; Pact CLI 0.10.8 installed under isolated CARGO_INSTALL_ROOT and actual verifier suite 5/5. Local Docker CLI has no daemon socket; pre-amendment GitHub run 36817138377 on SHA 48276 passed the validation provider, Pact, and OCI integration jobs. |

## Intermediate GitHub Actions snapshot — run 36822314115 (2026-10-01)

PR #64 is OPEN at head `ff2b9f279fcf6c974f626875dc99248881613a79`. Run [36822314115](https://github.com/JamesMorales04/agentic-engineering-harness/actions/runs/36822314115) checked PR merge SHA `64e3f963f7bf70e287da13f0f9aefb13e26c0450` for this head and completed with 12 of 13 jobs passing. P3 packaged-consumer and rootless-isolation are now green; the only failure is test/release at F5. The F5 repair below is local and unpushed, so it has no hosted result. Runs 368030 and 368171 remain historical snapshots.

| Job | Run 36822314115 status |
| --- | --- |
| test / release:check | FAIL — F5 timeout in `tests/security/isolation.test.ts` during live provider detection. |
| scenario-matrix | PASS |
| adversarial-system | PASS |
| human-e2e | PASS |
| system reliability campaign | PASS |
| rootless-isolation | PASS — real namespace/mutation/validator/egress campaign. |
| packaged-consumer | PASS — pack, clean consumer, Podman-backed setup and intent smoke. |
| provider-contracts | PASS |
| full-stack-contract | PASS |
| supply-chain | PASS |
| validation provider contracts | PASS |
| real Pact provider verification | PASS |
| OCI integration environment contract | PASS |

The workflow log reports 199 Vitest files passed, 1 skipped, and 1 failed; 1,366 tests passed, 8 skipped, and the F5 test timed out at the default 5,000ms. This intermediate run was not a green required-check set.

## Hosted CI checkpoint history (2026-10-01)

Run [36824682741](https://github.com/JamesMorales04/agentic-engineering-harness/actions/runs/36824682741) completed all 13 jobs successfully on implementation/workflow checkpoint `d21d6b5db6b36b8387af7687d9488c4f95229de1`. All required provider lanes ran, including real rootless isolation, strict full-stack, packaged-consumer, supply-chain, Pact, and OCI integration. The exact matrix for that historical checkpoint is:

| Required job | Run 36824682741 on d21d6b5 |
| --- | --- |
| test / release:check | PASS |
| scenario-matrix | PASS |
| system reliability campaign | PASS |
| adversarial-system | PASS |
| human-e2e | PASS |
| provider-contracts | PASS |
| validation provider contracts | PASS |
| real Pact provider verification | PASS |
| full-stack-contract | PASS |
| supply-chain | PASS |
| OCI integration environment contract | PASS |
| packaged-consumer | PASS |
| rootless-isolation | PASS |

This hosted result verifies the F5 deterministic test fixture repair, P3 packaged-consumer typed INTENT fixture, provider provisioning, and rootless environment repair on implementation/workflow checkpoint d21d6b5. The later status-doc candidate 963cc passed 13/13 in run 36832161124 and received fresh independent review. Runs 368030, 368171, and 368223 remain historical records. Exact-SHA check results are attached to each PR checkpoint; no merge claim is made here.

## Pre-amendment GitHub Actions snapshot — 2026-10-01

The first checkpoint run 36803071091 on `325605ebf842d098aa0fdbe556c433c3aac9cc0b` remains historical: 11 jobs passed and packaged-consumer/rootless-isolation failed. At the pre-amendment snapshot on 2026-10-01, PR #64 head was `48276ea842fa3af475eb32632d995b18f755f17c`; run [36817138377](https://github.com/JamesMorales04/agentic-engineering-harness/actions/runs/36817138377) completed with 12/13 jobs passing. Rootless-isolation passed 3/3 on Ubuntu 22.04/bwrap 0.6.1; packaged-consumer alone failed at P3's semantic INTENT call. The hosted log confirms the missing `paseo` executable and unresolved `@getpaseo/client` caused the session-scoped Semantic Assessor to refuse an identity-dropping CLI fallback. At this snapshot, the typed deterministic P3 fixture repair was the next checkpoint candidate and had no hosted result.

| Job | Historical run 368030 on SHA 325605 | Pre-amendment run 368171 on SHA 48276 |
| --- | --- | --- |
| test/release | PASS | PASS |
| scenario-matrix | PASS | PASS |
| system reliability campaign | PASS | PASS |
| adversarial-system | PASS | PASS |
| human-e2e | PASS | PASS |
| provider-contracts | PASS | PASS |
| validation provider contracts | PASS | PASS |
| real Pact provider verification | PASS | PASS |
| full-stack-contract | PASS | PASS |
| supply-chain | PASS | PASS |
| OCI integration environment contract | PASS | PASS |
| packaged-consumer | FAIL at pack-output capture (P1) | FAIL at final INTENT smoke (P3); typed fixture repair was the next checkpoint candidate, with no hosted result as of snapshot |
| rootless-isolation | FAIL at namespace + validator execution on Ubuntu 24.04 / bwrap 0.9.0 | PASS; real campaign 3/3 on Ubuntu 22.04 / bwrap 0.6.1 |

At the pre-amendment snapshot, the full required matrix was not green: P3 failed on SHA 48276. Direct built-CLI evidence for the typed-fixture checkpoint candidate does not substitute for hosted checks on the amended SHA.

## Validation record

- Pre-restart unrestricted-shell `npm run release:check` — final PASS after all code edits: typecheck/build; deterministic Vitest 200 files / 1 skipped, 1,368 passed / 7 skipped; Node suite 3/3; npm pack dry-run. Build releases include release-1790816218616-1827864-c955910a and release-1790816261719-1844232-bb244f71.
- npm run test:scenario — 8/8.
- npm run test:adversarial — 28/28.
- npm run test:human-e2e — 19/19; packaged user turn 29.098s in the earlier full run. npm run test:system-all after measured 45s bound passed 5 files / 67 tests and reliability report PASS; packed user turn 29.145s.
- Repeated build-hygiene test and packaged consumer: repaired focused runs 17.94s and 17.82s; npm run test:packaged-consumer passed build/hygiene 6/6 (17.364s) and packaged CLI 1/1 (29.112s).
- Repair-round packaged intent smoke: `npm run typecheck` and `npm run build` passed; `node dist/main.js intent ...` in an initialized temporary project with the same typed `semantic-assessment:INTENT` fixture and `AEH_DETERMINISTIC_PASEO_RUNTIME=1 AEH_PASEO_FORCE_CLI=0` passed the unchanged `^AUDIT` assertion. `npm run test:packaged-consumer` passed `tests/buildHygiene.test.ts` 6/6, then the pre-existing packaged `start` stdout assertion failed because the managed shell's `execFile` returned empty stdout; the new intent call was not reached in that test. `scripts/ci/packCandidate.mjs` generated the expected `agentic-engineering-harness-0.8.4.tgz`; clean consumer `npm install` failed against read-only `/home/james/.npm`, and a retry with a fresh `/tmp` cache remained silent for over 75 seconds before interruption, so no local clean-install result is claimed.
- Earlier unrestricted-shell `npm run test:rootless-isolation` — 3/3 with real local bwrap 0.13.0. Current post-restart restricted-shell replay — provider detection 1/1; both sandbox executions fail at `NETLINK_ROUTE: Operation not permitted`. At the 2026-10-01 pre-amendment snapshot, hosted run 368171 confirms the hosted Ubuntu 22.04/bwrap 0.6.1 lane passes the namespace preflight and all 3 real tests; the local failure is a separate host limitation.
- Controlled missing-provider suites: contextArchitectureClose 9/9 with Serena absent; failClosedProviders 12/12; OpenSpec/Serena provider command 17/17.
- Full provider-equivalent command: AEH_RUN_REAL_PROVIDERS=1 HOME=/tmp/aeh-ci-runner-temp/engram-home PATH="$PROVIDER_PATH:$PATH" npx vitest run tests/providerContracts.test.ts tests/specManagerCanonicality.test.ts tests/changePlanRequirementTraceability.test.ts tests/changeControllerOwnedDecision.test.ts --reporter=dot — 4 files / 17 tests passed after pinned Chromium install. PROVIDER_PATH contains mise’s pinned provider-contract tools; Engram ran from isolated temp HOME.
- Earlier unrestricted-shell `npm run test:packaged-consumer` — build hygiene 6/6 (including build-lock contention 17.154s) and packaged human CLI 1/1 (28.867s). The separate exact workflow smoke packed through `scripts/ci/packCandidate.mjs` to `/tmp/aeh-pack-candidate-smoke.zBoNQ6/agentic-engineering-harness-0.8.4.tgz` (SHA-256 `07547051210ba19345e9639baa346746ce85b66eeddd16b1198e0c8f25492b35`); clean consumer install/init, CLI/MCP, toolchain compile, `setup --dry-run`, and policy sync all passed with real Podman 6.1.2 from an isolated package extraction. This is earlier unrestricted-shell evidence, not a post-restart managed-shell or current hosted result.
- Pre-amendment GitHub run 368171 on SHA 48276 — 12/13 jobs passed; rootless-isolation passed the explicit non-root namespace preflight (`CapEff=0`, `NoNewPrivs=1`, smoke PASS) and all 3 real tests with bwrap 0.6.1. Packaged-consumer passed pack identity, clean install, CLI/MCP, init, toolchain compile, Podman-backed setup, and policy sync; it failed only at `aeh intent` with `SEMANTIC_ASSESSMENT_UNAVAILABLE` because `paseo` and `@getpaseo/client` were absent for the session-scoped Semantic Assessor. The provider correctly refused an identity-dropping CLI fallback. At the 2026-10-01 snapshot, the typed-fixture repair was the next checkpoint candidate; its direct built-CLI `^AUDIT` smoke passed locally, and it had no hosted result.
- Post-restart `npm run test:packaged-consumer` — partial local replay: build hygiene 6/6; the packaged CLI journey hit empty captured child stdout in this managed shell. The hosted packaged journey passed 1/1 on pre-amendment SHA 48276, and pre-amendment run 368171's clean-consumer smoke passed archive/install/setup through policy sync with Podman. Its final intent call failed at P3 because the deterministic semantic response fixture was absent; the typed fixture repair was the next checkpoint candidate and had no hosted result as of that snapshot; it requires a hosted run on its amended SHA.
- Current repair-round `npm run test:rootless-isolation -- --reporter=dot` — provider detection 1/1; 2 real sandbox execution tests fail because local bwrap 0.13.0 reports `bwrap: loopback: Failed to create NETLINK_ROUTE socket: Operation not permitted`. Before the provider call, the checkout-home fixture is created, `.ssh` and sentinel host preconditions pass, and the test verifies no `toolchainReadOnlyPaths` entry overlaps the synthetic HOME while retaining the Node and repository `node_modules/.bin` binds. Pre-amendment GitHub run 36817138377 on SHA 48276 passed the direct non-root namespace preflight and all 3 Ubuntu 22.04 hosted isolation tests; the restricted-shell NETLINK_ROUTE failure remains local host evidence.
- Post-restart `npm run release:check` — typecheck/build PASS (release `release-1790827040663-71-f30b97d1`); deterministic test stage is not a valid pass in the managed shell: 19 files failed / 181 passed / 1 skipped, 49 failures / 2 errors. The observed environment blockers include `listen EPERM: operation not permitted 127.0.0.1` in Control Center HTTP/SSE tests and `spawnSync ... EPERM` or empty captured Node-child output in CLI/direct-process tests. The test/assertion contracts were not changed to accommodate this runner; the current workflow test job must provide the authoritative hosted result.
- Pre-restart unrestricted-shell repair-round `npm run release:check` — PASS, exit 0; typecheck, build, deterministic Vitest/Node tests, and npm pack dry-run completed. Build release `release-1790821290230-2016254-d498851f`. Workflow YAML parsed with 13 jobs.
- Strict full-stack command: AEH_STRICT_FULL_STACK=1 HOME=/tmp/aeh-ci-runner-temp/engram-home PATH="$PROVIDER_PATH:$PATH" npx vitest run tests/architectureClosureIntegration.test.ts --reporter=dot — 8/8. The test emits/asserts complete identity/lease/binding/receipt/recovery evidence.
- Final full-stack evidence run used isolated source worktree /tmp/aeh-ci-runner-temp/aeh-full-stack-evidence-final. Retained report /tmp/aeh-ci-runner-temp/full-stack-contract-evidence.json SHA-256 356826b038d1a22332919ff2693d44d15466a327a3c578585a59dc202502dbf4; report status PASS, all 14 check IDs present, exact authority/lease/binding/receipt/recovery evidence asserted, audit scope DEGRADED/productionSafe=false.
- Final supply-chain evidence-collection run used Trivy 0.70.0 and Cosign 2.6.5 in disposable source worktree /tmp/aeh-ci-runner-temp/aeh-supply-chain-evidence-final2. The local upload-equivalent bundle /tmp/aeh-ci-runner-temp/supply-evidence-final2 summary has SHA-256 ddc4de859cf97b33edf74fd27e94720a437876674b76789de9b3d7e4e65ecf30 and binds artifact SHA-256 a4fd36bf4b64a4f016f471159b9114ae67d249c05fc621bd44b7a9e527ed3321 to CandidateRevision b8e48021741e0a6d523ab4f012e19841ee7abd2a8be00a998d1016f7ae285924 and 54 SBOM components. All retained file digests/summary sidecar and copied Cosign verification pass; privateKeyIncluded=false; tampering the original tarball is rejected.
- npx vitest run tests/validationProviders.test.ts tests/maturityEvidence.test.ts --reporter=dot — 7/7. PATH=/tmp/aeh-ci-runner-temp/pact-tools/bin:$PATH npx vitest run tests/validationProviders.test.ts --reporter=dot — 5/5 including the official Pact verifier. The local Docker-based OCI command cannot use the absent Docker Desktop socket (/home/james/.docker/desktop/docker.sock); the real hosted OCI integration job passed in pre-amendment run 368171.
- Final npm run test:system-all — 5 files / 67 tests passed; .aeh-test-results/coverage-report.json status PASS, human floor 12/12 and multi-turn floor 5/5; packaged tarball user-turn test 29.163s within its 45s bound.
- Workflow YAML parses with 13 jobs. actionlint is not installed locally. git diff --check and normative target equality check must be rerun after documentation is finalized.

## Preserved gates and review boundary

- Managed RUN/CHANGE success still requires current objective-completion and AcceptanceOracle evidence.
- Ambiguous Paseo daemon status stays unknown/fail-closed; fake status now describes a supported deterministic healthy boundary explicitly.
- Required providers remain fail-closed; rootless isolation and provider tests have explicit jobs that run real providers.
- Reversible compression still requires a controller-issued authority, authorized retrieval, exact raw-artifact recovery, and recovery handle.
- Strict supply-chain policy still requires the exact packed artifact, meaningful SBOM, provenance, signature, configured public-key verification, and tamper rejection.
- No continue-on-error, blanket skip, deleted assertion, relaxed schema, retry inflation, or compatibility branch was added. CORE_ARCHITECTURE_V2.md was not modified.
- At the pre-amendment snapshot on 2026-10-01, PR #64 head was `48276ea842fa3af475eb32632d995b18f755f17c`; run 36817138377 passed 12 jobs and failed packaged-consumer at the P3 intent smoke. The typed-fixture repair was the next checkpoint candidate and had no hosted result as of that snapshot. The earlier checkpoint 325605/run 368030 history remains above.
- Historical review/check states above are scoped to their dated snapshots. The status-doc candidate `963cc3010dc5b372a282da4f37859a8ce6a27796` passed all 13 required jobs in run 36832161124 and received fresh independent review. Subsequent checkpoint results are attached to the exact PR SHA. PR merge-readiness still requires resolution of the separate S10 re-acceptance gate.
