Historical evidence; no provider qualification or policy activation. This page preserves the conclusions and limits of unfinished Claude and Codex audit work. The source manifest identifies exact historical documents by SHA-256. Original bytes and private source locations are retained separately; no historical receipt, policy pin or audit signature is rewritten.
Claude: reporting passed, completeness did not
The Claude CLI 2.1.283 audit branch ended at e3a1d04ccd698b5a64dd8e8c9dcfb30c50a6ca43. Its partial audit records an earlier owner decision to trust named built-in components under specified conditions. That historical decision is not new authority to enable a transport or import the branch's revision-6 runtime policy.
The later completeness assembly covers twelve report families. Astra round 7 accepted the accuracy of that static reporting. The machine record still states:
complete: falseandsigned: false.retries.bounded: false.- 25 open and 36 unknown route rows after cross-family reconciliation.
Open concerns include ambient instructions and configuration, cross-session input, file attachments, post-snapshot tool availability and internal retries. A process stopped after an init event may already have contacted the provider; detection is not prevention. No finite request bound was demonstrated. Proposed remedies, owner decisions and observation drills remain unfulfilled gates.
The completeness JSON's historical hash is f61a54b16f453e38b18d84638e37a14d73cf9ec4a172599179edecd03a7106f0. Recovery rechecked all twelve report hashes and twelve evidence-index hashes. That checks preservation integrity, not every route conclusion or present-day binary behaviour. The historical review's wider extract checks remain attributed to that review.
A separate revision-6 source review recorded PASS with filesystem-dependent tests still blocked: 211 passed and 31 failed during sandbox setup without exercising their assertions. It established no live qualification. Revision 6, the inventory probe, process-attribution machinery and allowlist changes are not recovered into runtime by this documentation work. Its proposed preflight also failed to bind the signed field; a structural completeness check must not be described as authenticated owner approval.
A separate source-only recovery extracts the credential-shaped process-name screen from c7f259b4c4c9bfa5c120d11613a88b31f1ff25ea. It replaces recognised names with unrecognised and retains their numeric rows. Independent source review found that different hidden names could otherwise compare equal. Such surviving PID/group comparisons now remain unknown unless definite new rows are seen; those rows remain observed with a stated comparison limit and a count of definite new rows only. Additive evidence records independent source review and offline checks; neither establishes live qualification. No inventory probe, attribution exemption or revision-6 policy is imported. Historical audit and qualification bytes remain unchanged.
Claude subscriptions are unavailable under the current commission. These audit records neither reopen them nor qualify another route in their place.
Codex: partial source draft, missing receipt
The uncommitted Codex CLI 0.159.1 source-audit draft has hash 5438ce0335c408f70b2959a86c810b6221946c10e3ad2bf3ff2c7946161319aa. It labels itself incomplete, not independently reviewed and not owner-signed. Its conclusions concern a particular proposed producer configuration and historical source snapshot, not this agent's current capabilities.
The draft claims a docs/codex-cli-audit-receipt.json binds its cited sources and binaries. That receipt is missing from both the draft worktree and the recovery baseline. The claim is therefore unsupported. Recovery preserves the original document and this correction; it creates no replacement historical receipt or invented collection evidence.
The draft leaves ambient inputs, authentication boundaries, the remote catalogue, request counts and source-to-binary correspondence unresolved. A dedicated home, sign-in and configuration remain proposals requiring their own authority and qualification. Source inspection cannot establish runtime isolation or a tool-free transport.
Producer source-pin draft: preserve the omitted change honestly
Commit f6eb4e267e0f10d7e66aa5a21e271c2ea45b05c7 adds only the historical producers-source-pin-draft.json. Its text says adapter byte pins were moved out of the adoption test, but the commit message records that the test edit was refused and omitted. The recovery baseline still checks both adapter files and both historical qualification receipts byte for byte in test/producer-adoption.test.ts.
The two recorded adapter hashes match this baseline. That does not make the claimed test change implemented or establish acceptance. The unchanged draft is kept under the source ID producer-source-pin; it is not installed as a new current receipt. No test is relaxed, no source is repinned and no old qualification receipt is replaced. Any future source change needs a new, truthful evidence record and independent review.
The cloud and owner-presence proposals retain their own decisions and qualification gates. Saving any of these documents starts no task, provider call, account operation or scheduled continuation.
