docs: record contract campaign review and verification progress

devlog/_plan/260919_contract_resolution/000_plan.md

@@ -16,13 +16,13 @@ Evidence lives in this unit; previous implementation specifications remain in `d
 
 ## Ownership and dependencies
 
-| Lane | Sole issue ownership | File domains and sequence |
+| Lane | Issue and layer ownership | File domains and sequence |
 | --- | --- | --- |
-| Runtime | #5109 #5110 #5111 #5113 #5115 #5118 #5122 #5123 #5124 | Raw transport contract, custom input consistency, send accounting, journal ownership and continuation policy. Stack null-body/coding only if a real shared helper dependency exists; upload can stay independent. Keep stream and state changes separate. |
-| Policy and operator | #5112 #5114 #5116 #5117 #5119 #5120 #5121 | Schema reports before reject-lossy policy, static merge parity before consolidation, identity hints separate from availability, authority-map/tooling, optional metrics and pure preview, documentation alignment. Stack by these dependencies; independent docs can land separately. |
+| Runtime | #5109 #5110 #5111 #5113 #5115 #5118 (server) #5122 #5123 #5124 | Raw transport contract, custom input consistency, send accounting, journal ownership and continuation policy. Stack null-body/coding only if a real shared helper dependency exists; upload can stay independent. Keep stream and state changes separate. |
+| Policy and operator | #5112 #5114 #5116 #5117 #5118 (dashboard) #5119 #5120 #5121 | Schema reports before reject-lossy policy, static merge parity before consolidation, identity hints separate from availability, authority-map/tooling, optional metrics and pure preview, documentation alignment. Stack by these dependencies; independent docs can land separately. |
 | Coordinator | Review, CI, base/merge judgment and issue closure | Workers never merge or close issues. Cross-lane shared test-layout/structure changes are serialized at integration, with no cap increases or dropped regressions. |
 
-The user chose two different main-task models and a specific subagent model. Runtime/model selection provenance stays in task records rather than public repository artifacts. Workers may use unlimited useful subagent rounds; concurrent workers have disjoint writes and never perform branch-level git operations in parallel on one checkout.
+Workers may use unlimited useful subagent rounds; concurrent workers have disjoint writes and never perform branch-level git operations in parallel on one checkout.
 
 ## Integration policy
 
@@ -51,3 +51,5 @@ Ownership amendment: #5115 moved to the runtime owner after the policy owner con
 Independent preparation audit accepted the #5115 ownership amendment: `knownModelIdsForProvider` is byte-identical across #5174, the registry entry type is unchanged by that layer, and the new helper has no static-policy dependency. Expected later overlap is import ordering and line movement; integration must retain both independent changes and obtain new-head hosted proof.
 
 Second ownership amendment: #5118 transferred to the existing runtime owner after confirmation that no implementation writer, branch or commit existed. Server and dashboard delivery remain required, with the prior private pre-build audit incorporated before implementation. Metrics-to-preview shared-route integration is serialized; preparation can proceed in disjoint files. Dashboard evidence must satisfy the actual file-based screenshot gate using hosted artifacts under the no-local-build restriction. No third implementation owner was created.
+
+Ownership refinement for #5118: the runtime owner retains server/writer/routes/backend tests and documentation; the existing policy owner takes the dashboard and its tests after explicit release of the untouched layer. Delivery remains server parent #5185 followed by a manually chained dashboard child, with independent reviews, each required hosted gate and actual screenshot evidence. No acceptance criterion or execution restriction changes.

devlog/_plan/260919_contract_resolution/001_status.md

@@ -1,15 +1,15 @@
 # Campaign status
 
-Status: ACTIVE. Thirteen of the sixteen original issues are resolved and closed. Remaining: #5114, #5117, #5118. Supplementary sideband recovery #5161 and send-assertion follow-up #5170 are merged. Runtime ownership #5157 is merged. Strict-policy child #5167 is merged. Static-policy resolver/consumer stack #5171/#5174 and metrics #5183 remain under review and hosted verification; preview #5185 is a draft. Integration snapshot at 2026-09-19T15:27:51Z: #5167 at `96a6de86b71cf8a8f78959e0bf626dac642510a7`.
+Status: ACTIVE. Thirteen of the sixteen original issues are resolved and closed. Remaining: #5114, #5117, #5118. Resolver parent #5171 landed at `efb55e71e547ac83563e1d45dd60fb0b646e6cf7`; consumer #5174 remains open after a macOS job timeout, with a diagnostic rerun active at the same head. Metrics #5183 has further regression coverage pending after its latest correction. Preview #5185 remains a draft; server and dashboard work continue in separate existing owner checkouts. No additional issue closure is claimed.
 
 ## Owners
 
 | Lane | State | Issues |
 | --- | --- | --- |
-| Runtime | Active in an isolated worktree | #5109 #5110 #5111 #5113 #5115 #5118 #5122 #5123 #5124 |
-| Policy and operator | Active in an isolated worktree | #5112 #5114 #5116 #5117 #5119 #5120 #5121 |
+| Runtime | Active in an isolated worktree | Remaining: #5118 server, writer, routes, backend tests and documentation |
+| Policy and operator | Active in an isolated worktree | Remaining: #5114, #5117 and #5118 dashboard with its tests |
 
-Private orchestration records retain the actual task handles, model-selection evidence and wake cursors. The current coordinator heartbeat is ACTIVE at a 20-minute interval. It follows the two existing implementation owners; it must not duplicate them. The coordinator owns integration and issue closure.
+Private orchestration records retain the actual task handles and wake cursors. The current coordinator heartbeat is ACTIVE at a 20-minute interval. It follows the two existing implementation owners; it must not duplicate them. The coordinator owns integration and issue closure.
 
 ## Current evidence
 
@@ -134,3 +134,5 @@ Second ownership amendment: #5118 transferred to the existing runtime owner afte
 #5177 is integrated and #5115 closed after complete acceptance verification. Current progress is12/16; remaining issues are #5112/#5114/#5117/#5118. The independent decode-hint change landed before policy migration after a recorded source-based sequencing amendment.
 
 The current-task heartbeat was updated and read back ACTIVE with the existing twenty-minute cadence. It now reflects twelve closed issues, runtime ownership of #5118, policy ownership of #5112/#5114/#5117, and the remaining publication/visual verification duties. Other task monitors were not modified.
+
+Current verified ledger remains thirteen closed issues and three open (#5114/#5117/#5118). The policy owner now owns only the dashboard child layer of #5118 in addition to #5114/#5117; the runtime owner retains its server, writer, routes, backend tests and documentation. The runtime handoff confirmed no dashboard writer, branch or commit existed. The two-owner limit, manual parent-child delivery and actual screenshot requirement remain unchanged.

devlog/_plan/260919_contract_resolution/035_static_policy_resolver.md

@@ -45,3 +45,47 @@ Parent6892 narrow review found one cross-source provenance mismatch: a registry
 Parent `844cea4e0f11b5fa78fb5b1352a6949f4ab19035` adds merged winning-key provenance; the consumer stack is published on it at `304648706a360a737cad4d6473b9d164869e4c45`. Narrow parent re-review and exact-head hosted checks are pending. Running checks are not recorded as passing execution evidence.
 
 Independent review accepted winning-key provenance at `844cea4e0f11b5fa78fb5b1352a6949f4ab19035`, including cross-source exact/family precedence and explicit false. Source and provenance now share the same key-selection order. Current parent/child hosted proof remains in progress.
+
+Refreshed consumer head3046487 reached later existing cases and exposed two further contract regressions: inbound protocol is lost during Responses replay for Chat/Anthropic, and an explicit provider-level service-tier false is not retained by the catalog. Completed hosted job logs were sent to the owner and an independent boundary review; existing expectations remain authoritative. Earlier fixes are not proof of complete migration.
+
+Independent review localized the remaining consumer regressions to final-route inbound recapture, preserving captured configured intent for Fast eligibility, and explicit-empty default-map semantics during gather enrichment. Owner received exact source boundaries and must retain the original assertions. Captured dynamic eligibility remains distinct from shared static merge authority; a generic static value must not override an explicit disabled result.
+
+Remaining parent public review points to a documentation precision fix: the observed-limit projection may fill an absent static cap; it remains unknown only when both inputs are absent. Main confirmed source behavior and requested a call-local wording correction that preserves the immutable static policy. No runtime change is needed for that comment.
+
+Parent844 hosted run35451826594 ended with one macOS timing assertion: an unchanged stalled-stdout case took256ms against its250ms bound; 13,652 cases passed and22 skipped in that shard. Its test and adapter files are byte-unchanged against current dev. This is a timing-jitter candidate, not a proven resolver defect or a pass. Owner was told not to widen/skip the assertion and to use the next already-required documentation head for fresh CI rather than repeatedly rerun the superseded head.
+
+Consumer correction124e34f778 is under narrow review for all initial/fallback route recaptures, captured Fast eligibility and explicit-empty default-map semantics. Parent documentation correction7896b715 was inspected and preserves source behavior while clarifying call-local observed-limit filling. New-head hosted evidence remains required.
+
+Independent review passed `124e34f778913f8adcc1ff1fde66f7d5379d9e7a`: all route-selection paths recapture inbound protocol before adapter consumption; captured Fast intent is authoritative for publication; an explicit empty reasoning-default map retains its established fallback. All three original regression files are unchanged. Current-head hosted proof is still required.
+
+Child67bc1488 is a descendant of corrected parent7896b715; its source/tests match the independently reviewed consumer fix. A small catalog-document merge artifact retains parent-only migration wording and a duplicate fragment. Owner was asked to make that paragraph describe the final migrated contract without changing implementation. New-head CI and final public review remain required.
+
+Child documentation cleanupf5df7cb049 removes only the obsolete parent-only migration sentence and duplicate fragment. Main verified the final catalog contract remains consistent with the migrated implementation and frozen gather behavior. Current-head hosted verification remains required.
+
+Resolver parent #5171 merged as `efb55e71e547ac83563e1d45dd60fb0b646e6cf7` at2026-09-19T16:10:55Z. Head7896b715 passed every applicable hosted check and aggregate [35453258484](https://github.com/lidge-jun/opencodex/actions/runs/35453258484); macOS logs show36 parity cases executing. Independent reviews and public threads are complete. Current merge preserves reviewed core/test blobs and current integration documentation/layout. Actual dev ancestry verified. #5114 remains OPEN until child#5174 is restacked, verified and integrated; parent branch retained.
+
+Post-parent cascade `20ac21d4a650399870c397de8c8fad608f43488c` passed independent union review: reviewed consumer changes and decoded-identity helper remain, and current schema/ownership/policy documentation and layout inventories coexist. No cap change or semantic cascade regression was found. Current-head hosted checks remain running.
+
+Current post-parent child20ac reached an unchanged source-oracle assertion expecting the former terminal-repair helper call. The implementation intentionally consumes captured static policy instead. Owner received the exact assertion anchor to update while retaining all platform/relay invariant checks; no runtime fallback or removed assertion was requested.
+
+Independent oracle-fix review passed head6878d8b24: the source assertion now names captured terminal policy while preserving every platform, bounded relay, native WebSocket and failure invariant. Hosted CI at that head remains required.
+
+Child6878d8b24 reached green applicable hosted CI. Final public review requested two bounded end-to-end precedence cases: API-key provider lower/higher configured limits through capture into catalog, and a family-specific context limit competing with a provider-wide default. These correspond to the issue's explicit consumer-parity acceptance. Owner was asked for focused coverage only; an independent lookup checks for existing equivalent tests before duplication. No current source defect was asserted by these comments. Merge remains held until disposition and fresh head evidence.
+
+Independent existing-test lookup confirmed the two requested coverage cases are not duplicates: lower/higher limits are tested separately in routing and augmentation, but not through capture-to-catalog; existing family-context tests omit the competing provider-wide fallback. Owner was asked for only the minimal three cases, retaining existing tests and file-size constraints.
+
+Coverage commit `3b731ac5d95eec4b4f430abf80c571924a1d09c3` adds the minimal capture-to-catalog lower/higher limit and family-versus-provider context cases. Independent test review checks activation and fixed expected values; production source is unchanged in this delta. Fresh exact-head hosted verification is required.
+
+Review of3b731ac5 found the API capture test incomplete: it covers only configured-lower context/output values, while the requested positive-cap contract applies to context and max input and also requires an above-registry case. Owner received the exact two-row correction; the Anthropic family-versus-provider/observed test passed review. No production change is requested.
+
+Corrected coverage head `bc9e61aed886252a4bbb33cef340ae8dc91ac557` is published with the requested lower/higher context and max-input cases. Independent review is scoped to that test correction; the previously accepted family-context case is retained. New-head hosted proof remains required.
+
+Independent test re-review passed bc9e61aed8: configured lower and higher context/max-input values are checked against fixed expected caps in both captured maps and emitted catalog rows; the family-precedence conflict remains covered. Current-head hosted verification and final public-thread disposition remain the only known gates for this test delta.
+
+Final source integration review passed at bc9e61aed886252a4bbb33cef340ae8dc91ac557 against dev efb55e71e547ac83563e1d45dd60fb0b646e6cf7. The conflict-free merge tree139eebbab0cefb4a9113a16a26e6cd4bc6eeb34e equals the reviewed head tree. Production consumers are unchanged from6878d8b24a; later edits add only the accepted precedence cases. Parent policy, schema and ownership contracts and registry identity hints remain present. No public review thread is unresolved. Hosted run35456151926 still has macOS shard1 running; no merge or issue closure is claimed.
+
+Hosted execution evidence for the four consumer regressions was read directly from run35456151926 Linux shard4 job105931863842: frozen capture with late credential replacement, virtual wire identity replacement, lower/higher API context/input caps, and family context precedence all passed. The macOS shard1 handle105931863680 was independently confirmed in progress in its Test step. No completed-job failure was observed and no rerun or cancellation was started.
+
+Run35456151926 attempt1 ended with macOS shard1 cancellation and aggregate failure. GitHub annotation confirms the20-minute job limit; the last file group was tests/clients/client-connect.test.ts, with no subsequent result. Head bc9e61 is unchanged. One targeted diagnostic rerun of job105931863680 was accepted as attempt2 and read back queued. This measures recurrence; it is not a fix or environmental attribution. Source investigation is active, with no timeout increase, skipped case or local execution. Merge remains held.
+
+Source diagnosis narrowed the missing observation to file startup, not a proven environmental cause: top-level imports, synchronous warm-up scanning and child startup remain distinct hypotheses. Earlier green-head blob identity is not causal proof. If the diagnostic run repeats without phase evidence, add bounded phase markers before changing harness behavior. Attempt2 job105935450017 was read back in progress on the same head.

devlog/_plan/260919_contract_resolution/037_acceptance_ledger.md

@@ -9,11 +9,11 @@ This checkpoint does not declare the campaign complete. Current disposition: thi
 | #5111 | Closed; landed through #5126 | [`af4f744c75`](022_pr_5126.md); closure at 2026-09-19T10:01:05Z. |
 | #5112 | Closed; parent #5162 and child #5167 landed | [`96a6de86b7`](034_strict_schema_policy.md); current closure verified after both ancestries. |
 | #5113 | Closed; landed through #5129 | [`bb2fa5ab25`](024_pr_5129.md); closure at 2026-09-19T10:04:15Z. |
-| #5114 | Open; incomplete | Resolver #5171 passed hosted CI but has unresolved review findings; consumer #5174 has hosted failures under repair. Both layers must land. [Record](035_static_policy_resolver.md). |
+| #5114 | Open; incomplete | Resolver #5171 landed at efb55e71e5; consumer #5174 has an unresolved macOS startup timeout under diagnosis. Its current-head verification and landing remain required. [Record](035_static_policy_resolver.md). |
 | #5115 | Closed; landed through #5177 | [`838af40f1b`](039_decode_hint_review.md); closure at 2026-09-19T15:01:16Z. |
 | #5116 | Closed; landed through #5155 | [`6d42723387`](030_pr_5155.md); closure at 2026-09-19T11:07:05Z. |
-| #5117 | Open; incomplete | Opt-in metadata-only exporter is being implemented; full privacy/auth/counting/lifecycle acceptance remains unverified. [Record](000_plan.md). |
-| #5118 | Open; incomplete | Server-owned read-only preview, fingerprint validation and dialog integration still required. [Record](000_plan.md). |
+| #5117 | Open; incomplete | Metrics #5183 is implemented with reviewed terminal-path corrections; acquisition regression coverage and current-head hosted verification remain required. [Record](038_metrics_review.md). |
+| #5118 | Open; incomplete | Draft server #5185 and its dashboard child remain incomplete; source acceptance, hosted execution and actual visual evidence are required. [Record](040_preview_review.md). |
 | #5119 | Closed; landed through #5153 | [`f117c20d12`](029_pr_5153.md); closure at 2026-09-19T10:21:08Z. |
 | #5120 | Closed; landed through #5134 | [`1b54f2940b`](026_pr_5134.md); closure at 2026-09-19T09:02:10Z. |
 | #5121 | Closed; landed through #5138 | [`5ce51cb554`](027_pr_5138.md); closure at 2026-09-19T10:08:29Z. |
@@ -28,3 +28,5 @@ Publication review checkpoint: independent re-review accepted the corrected Engl
 Public checkpoint #5175 landed as `57b1df792ef7e66e17b0110727eefdd5387e164d` at 2026-09-19T14:13:30Z after reviewed head `128a47ea9db9b93ffc80fc2d42a2f4cddcc8f8c0` passed all applicable hosted checks and public review. Runtime checks were change-inapplicable, not executed. The original coordinator checkout staging was retained. Future implementation outcomes still require ledger updates and independent completion proof.
 
 At the #5123 checkpoint, the total was eleven closed and five open; this earlier checkpoint remains historical evidence.
+
+Second public checkpoint #5187 landed as `00ac9b6a6c0707b8e315b88f334c396162909b17` at2026-09-19T15:45:45Z after applicable hosted CI and all publication findings were resolved. It records thirteen completed issues and three open issues; later working updates remain pending publication.