[State Audit] Validate corrected Base checkpoint for #287 (evidence only)

[VirtualAdam]

Outcome

Produce fresh native dark-factory validation evidence for the existing Base implementation tracked by #287. Do not rebuild, refactor, or modify the implementation.

Immutable input: contrib/287-manifest-checkpoint at 8f31c8860ca7673cf2fe13223a993adb18e6060e. This checkpoint adds two clean-checkout portability corrections to the previously published implementation: LF migration checksums and a deterministic registry-artifact checkout rule.

The original #287 mission and both cancelled runs remain historical failures. This is a separate, explicitly tracked validation-only task for the corrected input, not a replay, accounting reset, accepted implementation, or replacement of the original human gate.

Acceptance criteria

• Execute the existing migration, compatibility, formatting, Clippy, web, Base unit, ignored PostgreSQL/gateway/admin/paging, and pinned registry checks against this exact input.
• Execute the real long worker/gateway/Anvil restart, reorg, and finality case. Retain fresh complete logs, exit status, duration, and source identity. The 60-second automatic verifier does not independently rerun this approximately five-minute case.
• Run the full ordinary workspace suite and report its real result. The two unchanged Git2.55 runner-fixture failures tracked in Native GitHub setup: empty core.hooksPath is incompatible with Git 2.55 #289 remain failures, not a full-suite pass. An excluding-runner run is a separate result. Any other failure blocks the report.
• Keep product source identical to the input. The sole permitted deliverable is docs/evidence/issue287-base-validation.md, containing actual results and precise limitations.
• Retain native mission/task/run identity, automatic verifier outcomes, and raw execution evidence. Prior local qualification is background, never a substitute for fresh execution.
• Request genuine owner/admin outcome review after automated checks. A green report does not approve the Base implementation, close [State Audit V2] Optional Base anchoring with admin configuration and explicit enablement #287, or authorize publication, merge, spending, or deployment.

Dependencies

The immutable input already includes the #283 foundation at c19cdfdbc5893c4655f6d58bd00f57668879d4a4; its merge is not required for local validation. #287 remains the feature issue and #281 the umbrella. #289 is a separately tracked runner prerequisite, not a source change permitted here.

Execution contract

Use the existing native github-copilot adapter and a factory-provisioned managed worktree. First execute the trusted host launcher, without repository rediscovery:

& (Join-Path $env:USERPROFILE 'Projects\TaskRabbit\ecorp-contributor\output\issue287-validation\run-validation.ps1')

The launcher uses repository commands, captures compact summaries plus complete host-side logs, and creates the evidence document. Wait for its actual completion; use long waits rather than repeated short polling. Inspect a failed command only if needed, and do not attempt product corrections in this task. Do not substitute a narrative, fabricate receipts, or claim an unexecuted case passed.

Use only operator-owned loopback PostgreSQL on55473, the canonical-LF admin database issue287_admin_lf, and pinned disposable Anvil fixtures on18545/18546. Never use the retained contributor database on54329, live contributor binaries/target, customer data, public chains, or real KMS signing. Keep frozen lockfile integrity and TLS enabled.

One task attempt, at most500000 additional recorded tokens, and a10000000microusd recorded cost ceiling. The original stopped work consumed940915 tokens; combined recorded usage must remain below1500000, with no concurrent resumed spending from that lineage. No budget reset, native state patch, automatic review approval, publishing credentials, GitHub writes, PR creation, issue closure, or deployment from the producer.

Planning authority is All-The-Vibes Project #5. Only this validation task may be selected; the broad watcher remains disabled. Any future feature PR must link #287 and this evidence task, reference #281 without closing it, and retain the #283 stack while that foundation is unmerged. Publication and human review remain separate gates.

[VirtualAdam]

Native execution update: run 147d86b4-b8ef-416d-91d0-196c3196c0b1 on pinned source 8f31c8860ca7673cf2fe13223a993adb18e6060e actually executed the migration checker successfully (49 migrations). The frozen host harness then failed with a PowerShell missing-property error (exit); failure receipt 58b29d82-49f6-4d09-8e5a-cdd00705667d is preserved. No remaining qualification groups, long-worker acceptance, report, native artifact, or outcome approval exist. This is a harness failure, not established product failure or a successful factory qualification. Further agent activity is being stopped; factory:ready is removed. A versioned minimal harness correction is under investigation, without altering frozen helpers or failed receipts and without authorizing an automatic retry. Original #287 history and accounting remain intact; no PR has been opened.

[VirtualAdam]

Root cause isolated and a versioned host-only correction prepared: two CopyToAsync/GetResult calls leaked VoidTaskResult objects into PowerShell output, making Invoke-Captured return three values rather than one command result. The correction suppresses those values and serializes the cache-use flag as a Boolean. Five actual tiny child-process cases plus exception/source guards pass; these are harness regressions, NOT product qualification. Original frozen helpers/policy/failed receipts/claim remain unchanged. Native run147d86b4 is now cancelled and retained, with107802 tokens; combined recorded usage across the original #287 lineage and this task is1048717 tokens. No new native retry has run. The documented factory verification-recovery endpoint returns400: exactly one failed task is required, found0 (this task is cancelled). No state reset, guard bypass or replacement mission has been used for the correction. Temporary owned fixtures are stopped with data retained; contributor UI/API remain running. The feature implementation and existing local evidence remain intact. Native acceptance and draft publication are still blocked.

[VirtualAdam]

Supported continuation found and admitted without resetting state: this task never entered verification, its verification status was pending, and the factory item remained running. The separate generic same-session resume path therefore applies, unlike the verification-recovery route. Native contract revision 007bd3cd-5724-4066-b59e-638d62415252 now binds BOTH producer and all12 verifiers to the corrected, versioned helper bundle. Check kinds/selections/timeouts, source8f31c88, scope, existing300000-token budget and genuine owner/admin manual gate remain unchanged. Native resume returned run 7dce410f-4953-4f62-9d6d-99fde53899b2, retaining the same provider session/worktree and task attempt; prior107802 tokens and failed receipt remain counted. No new mission, attempt reset, budget increase, DB patch, weakening, or human acceptance occurred. This continuation is now running; results are not yet available.

[VirtualAdam]

Native qualification update for #287: the same-session continuation 7dce410f-4953-4f62-9d6d-99fde53899b2 executed against unchanged 8f31c8860ca7673cf2fe13223a993adb18e6060e. Migration/compatibility/format, Clippy, web build/lint and Base unit groups passed. The full workspace suite executed and retained exactly the two inherited #289 runner failures; it is not green.

The batch then failed before database setup because Windows command discovery returned both docker.exe and extensionless docker as one executable. Receipt 4403eb75-448c-48b0-aefe-014805726737 and command logs are retained. Database, registry and the actual long-worker case have not yet executed in this native task. The run was explicitly interrupted; no report artifact or human outcome approval exists.

A second isolated, versioned host-harness correction selects one application in existing PATH order for Docker/Git/Cargo/Node. Real command-resolution and prior capture/guard regressions passed; those are helper tests, not product qualification. The bundle has not yet been bound or run natively.

Continuation is waiting for ECorp's authoritative preserved-workspace event. The runner is still making measurable progress fingerprinting the complete retained worktree, including ignored Cargo build files. We are not deleting that cache, overriding checkpoint state, or equating an existing directory with a valid checkpoint. Once preservation completes, the intended path is another narrow native contract revision and same-session resume, with all twelve verifier selections/timeouts and the genuine owner/admin gate unchanged.

Accounting remains intact: this task used 222433/300000 recorded tokens, leaving 77567; combined original #287 and #292 usage is 1163348. No new attempt, budget reset, source change, PR, deployment, or automated human approval is claimed.

[VirtualAdam]

Blocked: native token circuit breaker stopped qualification. Source remains 8f31c8860ca7673cf2fe13223a993adb18e6060e; no product changes were made for the harness corrections.

After ECorp confirmed the previous checkpoint, native contract revision df972963-21bf-43da-a96e-217a0ebd4bae (version3) admitted same-session run 9e2cc872-da2a-4ecc-8b35-9ff0c1cbfc20, preserving source, attempt count, budgets, twelve check selections/timeouts and the owner/admin outcome gate. The second harness correction got past the Docker ambiguity.

Fresh actual results: migrations, compatibility, formatting, Clippy, web build/lint, Base units, store and both gateway groups passed. The full workspace suite failed with exactly the two inherited #289 runner failures. Admin HTTP began but has no completion/exit receipt. Paging, registry and the actual long-worker acceptance case did not run. Partial logs are retained under e0ebcd17-0baf-4ea4-95a4-a7c496a826a6; there is no final receipt or generated report.

Native event1115 triggered stop at86639/77567 run tokens; event1119 records cancellation at2026-09-16T03:37:20UTC. This task totals309072/300000 recorded tokens (9072 over, no remaining allowance). Combined original #287 and #292 usage is1249987 recorded tokens. Reported cost0microusd is not a claim about actual billing. No accounting reset or observer-initiated interruption occurred in this continuation.

The source is physically retained, but event1118 explicitly reports no checkpoint proof after hard-boundary capture timed out; fingerprint is null. A preserved disposition alone is not usable recovery proof. No native artifact, verification result, human outcome approval or PR exists. Further execution is blocked pending explicit authorization through a supported recovery path; no replacement task, budget reset, checkpoint-state override or manual qualification around the stop is being used. Earlier claims, receipts and source worktrees remain intact.

[VirtualAdam]

Linked to draft PR #293 under explicit contributor authorization to publish existing code and retained local evidence while marking factory qualification incomplete. This evidence task remains incomplete/open: no final native report, artifact, verifier outcome or human acceptance was created. The stopped run, consumed budget, partial receipts and absent checkpoint proof are unchanged; no recovery or reset was performed. GitHub-only tracking is confirmed for this GitHub contribution. #293

[VirtualAdam]

PR closeout source advanced to 3ff5e62 in draft #293 after operator-local corrections and explicit foundation merges. The native evidence task remains pinned to its original 8f31c88 input and is NOT complete. Operator-local results recorded in the PR are not a replacement native report, verifier outcome or human acceptance. Native token stop, 309072/300000 task usage, 1249987 combined recorded tokens, and missing latest checkpoint proof are preserved; no resume, replacement mission, budget/reset or state override occurred. This issue remains open.