docs: triage Codex review threads before landing - #869

Scope

Codex cloud review remains in use, but the landing procedure has no per-thread disposition step. This adds that step to the existing Landing section: read every connector thread and comment, retain a fixed/replied/not-applicable disposition and evidence, and re-read the exact head and all conversations before declaring readiness.

• Base commit: 64a8cda01700d5e823c18e4b989e856de2ee2241
• Lane: lane:foundation
• Owned paths: docs/command-center.md; its evidence hash is refreshed in the last registry-only commit.

SOTA sources

• Official OpenAI Codex GitHub review, fetched 2026-10-08: supported cloud review remains the native route.
• cli/cli v2.102.0, installed native client, and gh api manual: GraphQL pagination requires an end cursor and pageInfo for the connection being paged.
• GitHub GraphQL pagination and native conversation resolution, fetched/reviewed 2026-10-08. Live native schema and thread returns distinguish outdated, resolved, author and original-commit state.

Evidence-class table

Local commands run

gh --version
gh version 2.102.0

gh api graphql --paginate --slurp -f query=<retained query>
exit 0: PR #854 returned 4 connector review threads; all pageInfo.hasNextPage fields false

python3 scripts/validate.py
exit 0: repository integrity/scope passed

git diff --check
exit 0

The full native query/output is retained privately with its actual post-exec argv. A CLI option-validation failure before the request was retained and corrected; it is not a provider failure. Metadata reads do not prove semantic triage or future enforcement. No low-impact document test was added.

Modified test files: none. Declared modified-test failing set: empty.

Decision record

The new docs/command-center.md#codex-cloud-review-thread-triage subsection is the source-reviewed B3 procedure. It explicitly covers resolved/outdated threads and nested comments, both connector login spellings, current-head evidence, justified resolution, zero-thread proof and invalidation after a push, thread or comment. A reply, outdated flag or green CI cannot justify resolving a valid outstanding finding.

PR #859 was independently confirmed MERGED first at 64a8cda01700d5e823c18e4b989e856de2ee2241; its landed map blob matches the retained SHA256. The inverse for B3 is to revert the documentation and its final registry hash coherently.

Host evidence

No host installation, platform status, client configuration or credential change.

Checklist

• No workflow, ruleset, frozen input or always-loaded instruction surface changed.
• No credential value or private host state is published.
• No paid service or billing surface introduced.
• Peer-owned worktrees and private landing code preserved.
• Evidence registry is the final commit.
• Landing remains with 5f under the standing cue when required-green and zero threads.