docs: record contract campaign review and verification progress

[lidge-jun]

Summary

Record the latest contract campaign checkpoint: thirteen issues are closed, resolver parent #5171 has landed, and #5114/#5117/#5118 remain open. Update the remaining owner split and preserve the exact review and hosted-verification history, including the macOS diagnostic run and outstanding metrics/preview acceptance.

Verification

• Independent publication review passed for the six changed Markdown files: status, chronology, ownership, privacy and completion claims agree.
• git diff --cached --check passed; copied source documents match the publication checkout.
• No local tests, typecheck, builds or runtime execution were run, per the campaign restriction. Applicable hosted documentation controls remain required.

Checklist

• Scope stays focused and avoids unrelated cleanup.
• Docs or release notes were updated when needed.
• Security-sensitive changes were reviewed for secrets, auth, and unsafe defaults. This documentation checkpoint excludes private security working notes and changes no runtime behavior.

Summary by CodeRabbit

• Documentation

  • Updated implementation ownership records and delivery responsibilities.
  • Refreshed campaign status, acceptance tracking, and review history for resolver, metrics, and preview work.
  • Added verification notes covering hosted CI results, regression findings, preview requirements, and dashboard evidence.
  • Clarified outstanding issues and conditions required before related work can be merged or closed.

• Product Impact

  • No user-facing product behavior changes are included in this update.

[github-actions]

✅ Deterministic PR hygiene checks passed.

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-09-19T17:28:47.250887Z	110bb43	PR opened

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Repository: lidge-jun/opencodex/.coderabbit.yaml

Review profile: ASSERTIVE

Plan: Advanced

Run ID: 758c9985-132f-4d52-9302-7e9c5cbf1692

📥 Commits

Reviewing files that changed from the base of the PR and between efb55e7 and 110bb43.

📒 Files selected for processing (6)

• devlog/_plan/260919_contract_resolution/000_plan.md
• devlog/_plan/260919_contract_resolution/001_status.md
• devlog/_plan/260919_contract_resolution/035_static_policy_resolver.md
• devlog/_plan/260919_contract_resolution/037_acceptance_ledger.md
• devlog/_plan/260919_contract_resolution/038_metrics_review.md
• devlog/_plan/260919_contract_resolution/040_preview_review.md

Included review availability: Your plan provides up to 10 included reviews per hour; 6 remain after this review.

---

📝 Walkthrough

Walkthrough

The PR updates campaign documentation for ownership, resolver integration, metrics verification, acceptance tracking, and preview implementation status. It records current open issues, hosted verification results, correction commits, and remaining evidence requirements.

Changes

Contract Resolution Campaign

Layer / File(s)	Summary
Ownership and campaign status devlog/_plan/260919_contract_resolution/000_plan.md:19-25, devlog/_plan/260919_contract_resolution/000_plan.md:54-55, devlog/_plan/260919_contract_resolution/001_status.md:3-12, devlog/_plan/260919_contract_resolution/001_status.md:137-138, devlog/_plan/260919_contract_resolution/037_acceptance_ledger.md:12-16, devlog/_plan/260919_contract_resolution/037_acceptance_ledger.md:31-32	The records split #5118 ownership between runtime server work and policy dashboard work. They report thirteen closed issues and three open issues. They update resolver, metrics, and preview acceptance evidence.
Resolver integration history devlog/_plan/260919_contract_resolution/035_static_policy_resolver.md:48-53, devlog/_plan/260919_contract_resolution/035_static_policy_resolver.md:55-59, devlog/_plan/260919_contract_resolution/035_static_policy_resolver.md:61-63, devlog/_plan/260919_contract_resolution/035_static_policy_resolver.md:65-67, devlog/_plan/260919_contract_resolution/035_static_policy_resolver.md:69-73, devlog/_plan/260919_contract_resolution/035_static_policy_resolver.md:75-85, devlog/_plan/260919_contract_resolution/035_static_policy_resolver.md:87-91	The resolver log records two consumer contract regressions, their corrections, parent integration, added precedence coverage, Linux verification, and a macOS timeout that keeps the merge held.
Metrics cancellation and upgrade review devlog/_plan/260919_contract_resolution/038_metrics_review.md:36-43, devlog/_plan/260919_contract_resolution/038_metrics_review.md:44-53, devlog/_plan/260919_contract_resolution/038_metrics_review.md:54-61, devlog/_plan/260919_contract_resolution/038_metrics_review.md:62-73	The metrics log records fixture-harness changes, cancellation verification, successful WebSocket 101 classification, live-upgrade fixture corrections, and request-local finalization. The acquisition-cancellation and timeout branch remains without actual-route regression activation.
Preview implementation status devlog/_plan/260919_contract_resolution/040_preview_review.md:8-19	The preview note records read-only and profile preview work, restore and publication corrections, filesystem regression coverage, and remaining hosted, roster, profile, restore, and dashboard evidence requirements.

Priority: ⬇️ Low

Estimated code review effort: 2 (Simple) | ~12 minutes

Change: Other

Merge Risk: ⚪ Minimal · up to 110bb

This documentation-only update has consistent ownership, issue-status, and verification records, with no actionable merge risk remaining.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and concisely describes the changes. The pull request records contract campaign review and verification progress across the updated Markdown documents.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Commit to this branch
• Create a new PR

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[lidge-jun]

Maintainer integration into dev under MAINTAINERS.md, bound to head 110bb438ff6351e3231d1421254fe2ef66f8c9cb.

Applicable hosted controls and aggregate passed in run 35458046177, with target/hygiene controls also successful. Runtime, build and test jobs were change-inapplicable and skipped; no execution pass is claimed for them. Independent publication review passed, and no unresolved public review thread or maintainer objection was found.

The candidate union with dev 0c45969a846e38bbd89f892af5118712da4f65d8 is d0fb88aaef9b1a4484d75d26a456169b60597bf9: only the six reviewed documentation files change, with their contents identical to this head and current runtime source retained. Native stack membership is absent. This is an ongoing evidence checkpoint, not completion of the remaining three issues.