feat: consolidate the owner-led acceptance workflow

[YuzeJ21]

Summary

• make the public-PR path and deliberately constructed demo prominent while moving optional alpha feedback under research and historical options;
• state that Stage 1 is closed as not pursued and feedback is not required for owner-led Stage 2;
• make criteria confirmation an explicit apply-and-confirm action and keep analysis locked before a committed normalized snapshot;
• put decision progress and unresolved criterion cards before CI and secondary evidence detail, with direct navigation from the queue and summary;
• keep implementation/test candidates, observed CI, external runtime verification, and human decisions visibly separate;
• preserve constructed-demo tagging and segregation from genuine review claims;
• refresh the official-source GitHub Copilot, CodeRabbit, Qodo, and Graphite comparison as positioning research, not validation;
• add a documentation map that separates current operating guidance from historical evidence snapshots;
• record the dated post-PR feat: add exact-head informational check lifecycle #196 resulting-main evidence and keep v0.2.3 publication separate from unreleased 0.2.4.dev0 work.

Verified evidence

• resulting main after PR feat: add exact-head informational check lifecycle #196: merge 8387156fd6f6e90eef7caf58881b0cc5bb62b111; exact head 5a6a25a6dff23cdfa8dcb4023b83144078620610; hosted CI run 32093041685 succeeded;
• Ruff lint passed and repository diff checks are clean;
• 2,378 tests passed with 2 intentional browser-marker skips;
• combined coverage: 95.19%;
• 123 repository contracts passed;
• deterministic acceptance benchmark: 12 cases / 13 criteria, zero mismatches, zero must-have False Ready outcomes;
• comparison benchmark: 2 cases, zero mismatches;
• installed-wheel Chromium regression passed at 1280×720 and 390×844 with zero external requests, console errors, or page errors; the regression covers the revised flow, all export controls, an inspected Markdown download, automatic save, and validated reopen;
• two wheel builds were byte-identical: fd541c3b2cccb364b9d57f3c07a70b27697a84cf51bbe4802e6e7b139b443163;
• clean wheel installation, dependency validation, both CLIs, both installed benchmarks, source/installed version equality, and loopback health passed;
• clean installed lanes passed on CPython 3.11.15, 3.12.0, and 3.13.14.

Evidence boundaries

ScopeProof remains an evidence assistant, not a correctness oracle. It never executes target-repository code. Static candidates are not runtime verification. Criteria confirmation remains mandatory. Persisted and exported objects remain validated, and gate behavior remains deterministic and fail closed.

This PR is owner-led Stage 2 engineering evidence only. It does not establish customer or market validation, accessibility conformance, real screen-reader operation, a Windows or Linux desktop workflow, or non-Chromium support. Reviewer identity remains asserted rather than authenticated. The GitHub Action remains opt-in and informational.

Stage 1 remains closed as not pursued at 0/5 qualifying reviews, 0/3 independent practitioners, 0/3 public repositories, 0/3 independently observed under-ten-minute completions, and 0/2 reuse-intent signals.

Do not merge, release, tag, publish, deploy, conduct outreach, start Stage 3/4, retune R-002, or generate R-003 without a separate owner decision.

[YuzeJ21]

@codex review

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: bab61d2c73

ℹ️ 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".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 950679635e

ℹ️ 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".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[YuzeJ21]

@codex review

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 766e0f8b95

ℹ️ 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".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[YuzeJ21]

@codex review

[chatgpt-codex-connector]

Codex Review: Didn't find any major issues. Hooray!

Reviewed commit: 5a69af4e92

ℹ️ 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".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".