test(integration): validate combined draft stack [DO NOT MERGE]

[zzwong]

Integration validation only. DO NOT MERGE.

This draft exists to run the repository's existing hosted CI against one exact combined open-PR source stack. Separate component checks do not establish combined behavior. Keep the component PRs separate; this is not a merge or rollout proposal.

Base: main at 999e59ddfc74a67ffeef3c4b4a78a8528365afe6.
Exact proposed source tree: 7fd8e55a2b263b912b9103a3ab213c46b929a59b.
Scope: 449 source files; 88 changed paths against main (40 added, 48 modified, no deletions).

The combined source has an independent source-only review with no blocking integration finding. Every file, executable mode and source hash was checked, and the full patch reconstructs the exact proposed tree. This draft's own hosted CI has now passed all 12 jobs on this exact tree. See the observed results below.

Exact input heads

The validation snapshot contains these 14 intended public inputs:

• fix(pi): honor settled runs and sum usage [#638] #641: 8797d43863628badb8ba1293ddacf77c9ee3ad23
• test(pi): gate the installed Pi 1.0.0 RPC runtime [#639] #646: e9d463ee16231f1a7d9759bf6ef1ddf3de87c844
• fix(pi): isolate RPC prompts from ambient instructions #656: 73bf803c51fdb5ee75bf3b0add13ed96d6410818
• ci: add repeated ledger migration race checks #658: 1abe5d6707b744e1d65d1e11511f136d2107fdee
• test(claude): isolate background polling timeout fixture #660: 39313d560e6e32e20acca9182f018afa192d1301
• fix(claude): retain scratch until background cleanup completes #665: 3cb2f1e0d3b63909b4d2ca6e2cb3b5b5a59b3c6f
• fix(review): isolate thread analysis failures #661: 9aee7e338448907adc428efcc2ce46688793d7d4
• feat(review): replay a PR without its existing discussion #627: 2a2dc5e9fcb1439f996d9474496adaf47085eb33
• feat(benchmark): isolate pinned reviews from saved sessions #663: b83a5c471143df15a9f4f883ff644d236e254718
• feat(llm): persist bounded Pi reviewer execution evidence #662: 982341589d5c3db76ac260626faa325df4ff0dc1
• test(review): cover reapproval after superseded verdicts #664: a4fef48d48edbba262187167ed45671e828eb196
• fix(openai): retain cache-write usage telemetry #666: 29edd5c6877be9cda7341ee6f5b11b0acdcff5fb
• feat(catalog): add strict request pricing bindings #667: 8320ef841b6661be56fe94a5017e2626c12d3c72
• feat(llm): collect bounded request-cost evidence #668: 4c1d9887e3d88fac17b749630936ed5e0ebefd77

These are source-composition inputs, not a claim that the validation commit has all 14 commits as Git ancestors. #666's two-file cache-write parser prerequisite is carried in #668. The changes from #654 are already in the main baseline and are not an extra input.

The composition retains the reviewed #641/#662 integration repair: reviewer trace completeness is determined after terminal result/error classification and requires successful settlement plus an uncanceled task. It also retains #668's S7 sidecar/binding-authority correction, detached response/evidence copies, retry and cache histories, and catalog legacy-pricing rejection.

Expected hosted CI scope

The existing CI workflow in this exact tree declares 12 jobs after expansion:

• Linux, macOS and Windows builds, plus the aggregate build check
• Standard tests
• Ledger/dbmig race checks, repeated 25 times with bounded scheduling
• No-1Password opt-out tests
• CGO-disabled static smoke tests
• Installed Pi 1.0.0 RPC gate using Node 22.22.3 and scripted local-provider fixtures
• Lint
• Packaging identity validation
• PR-title validation

The workflow and Makefile are the already-reviewed versions in this input stack; this draft adds no further workflow changes. The Pi and race jobs are part of the combined stack and must be observed independently. Go is selected from the existing go 1.26 module requirement; actual runner/tool versions, skips and failures must be recorded from this run.

CI checks out a synthetic PR merge commit. Its tree must be verified against 7fd8e55a2b263b912b9103a3ab213c46b929a59b before results are attributed to this candidate. If main or an input changes, that is a different source identity requiring a new check.

Observed combined hosted result

CI run 37764216368, attempt 1, completed successfully for head 50b56b2ca487812b1888e299aac24c912bdd4b97. Its synthetic checkout c1e137e2c249779348bb1acba1b1184d5044d16a was independently verified to contain exact tree 7fd8e55a2b263b912b9103a3ab213c46b929a59b.

All 12 jobs passed, including lint with 0 issues, the three platform builds, standard/opt-out/static tests, targeted ledger/dbmig race checks and the installed Pi gate.

• Each of the three general test profiles passed all 43 request-cost declarations (73 selected pass events) and all six settlement-integration cases. No selected case failed or skipped; no cached package-result lines appeared.
• Standard and static-smoke logs each contain 4,030 pass and 22 skip events. Opt-out contains 4,014 pass and 35 skip events. These are test/subtest events; unrelated conditional skips are retained.
• The separate installed Pi 1.0.0 gate passed eight selected declarations and 24 events with zero skips. It used Node 22.22.3 and scripted local-provider fixtures.
• Ledger/dbmig passed the declared targeted -race -count=25 job. This does not establish full-repository or request-cost race coverage.
• Retrieved Linux test/lint logs report Go 1.26.8 and the verified synthetic checkout. Historical-defect controls and paid/live-provider validation remain NOT RUN.

These are this combined draft's own results. The original local attempt remains UNKNOWN, and no merge, issue closure or estimator activation is authorized by this result.

Existing evidence and limits

Current #667 and #668 each have their own successful 10-job hosted runs. Those runs cover their standalone trees and profiles only. They provide no combined test, lint, build, race or installed-runtime credit here. This draft has no inherited combined passes.

The earlier local attempt on combined tree 98e4444f340fc078f4ec9090be77dea1106fd17c remains UNKNOWN after its original deadline. No outcome is inferred, recovered or transferred, and this hosted validation does not resume or restart that operation.

#549 and #659 are not included; no private/runtime artifacts from other projects are included; no estimator activation; no inherited or recovered local combined result.

#665 is included only for cleanup ordering. Orphan ownership and complete descendant cleanup remain unqualified. Request-cost collection still has incomplete-history semantics and makes no invoice-completeness or lossless crash/power-loss claim. Hosted CI does not replace the separately planned historical-defect controls or establish live-provider behavior.

No component draft is modified by this validation snapshot. Do not merge this draft, close linked issues, deploy, release or activate an estimator on the basis of it. Record the exact combined results and remaining blockers first.