Refuse conflicting Claude identity during startup - #1090

Independent Fable review

Reviewed commit: aa3227f162a92a3b5f857808b0327eff12befe78

Reviewer: Claude, configured model fable, reasoning effort high. The coordinator publishes the retained independent review; no new review call was made.

Verdict: PASS. Both accepted requirements are covered; all three observations below are nonblocking.

The workflow rejected only the summary length: 1,270 characters against a 1,200-character limit. Taras explicitly accepted this exact review unchanged as a one-time exception. The shared schema remains unchanged.

Summary

Signed merge aa3227f preserves the seven owned #1088 paths byte-for-byte from 8485a70, and its patch relative to main bddf524 equals the original base-to-feedback patch (same SHA-256). The vendored Claude tarball matches MANIFEST (195823 bytes, sha256 6490fb5d...), both embedded base64 payloads decode to the committed tarballs, and the vendor pin equals the manifest. Extracting old and new tarballs shows only dist/acp-agent.js and its .d.ts.map differ, and that dist delta is exactly the upstream patch: the reader stores the identity-refusal Error before throwing (iterator return would otherwise reject the held getContextUsage lookup, which readResumedLiveModel swallows), and publication rechecks queryFailure and disposal after the last await with no intervening await before insertion or response. Public declarations, acceptance, checkpoint and the joined setup-catch reader are unchanged. The permanent production-artifact case gates on the real get_context_usage request and holds it until Query closure, so ordering is deterministic without sleeps; retained receipts bind the failing run to main's snapshot bytes (failure undefined at line 555 after the gate assertion passed) and the passing run to the committed snapshot. Both acceptance clauses hold.

Accepted requirements

• refuse-contradictory-startup
• preserve-native-checkpoint-acceptance

Nonblocking observations

1. The added this.disposed recheck before publication (packaged dist/acp-agent.js:5139) closes a real parallel gap (dispose() during optional setup ends the reader cleanly without a queryFailure, so the session would otherwise be inserted into a disposed agent), but no retained test exercises that branch. It mirrors the existing post-initialization check and is harmless; worth a focused upstream case when that path is next touched.
2. Issue #1086 (held-helper disposal ordering) failed once on the integrated candidate in attempt 0003 (observed dispose-start, dispose-return, backend-close) and passed on the single authorized identical-input rerun in attempt 0004. It is unrelated to this repair and remains unresolved/intermittent; Root owns the flake issue and the Node22/CI delivery gates. No local Node22 evidence exists (local runs are Node 26.5.1).
3. MANIFEST patchedCommit bea799c8 is a scratch upstream commit reproducible only through the retained upstream-final-source.patch and build receipts, the same convention the prior pin 54df80cb used; PROVENANCE.md states this. The pullRequest link to upstream PR 1047 is unchanged and does not carry this delta.

Retained original response SHA-256: 7efdc62f92df8bcc331a9e8aa72f7c2e2e8bc86ac2ab20b4558c24d1b67bc3d4.