Skip to content

docs(rfc-008): mark P5 DONE, OpenCode plugin merged (#424/#425)#426

Merged
lantiscooperdev merged 1 commit into
mainfrom
docs/rfc-008-p5-done
Jun 27, 2026
Merged

docs(rfc-008): mark P5 DONE, OpenCode plugin merged (#424/#425)#426
lantiscooperdev merged 1 commit into
mainfrom
docs/rfc-008-p5-done

Conversation

@lantisprime

Copy link
Copy Markdown
Owner

What

Rule 10 doc-sync follow-up. P5 (OpenCode enforcement plugin) merged via #424 (f5dbaef) + doc fix #425 (a7f66c9), but the per-phase status still read queued in three places. This flips them, mirroring #423's P4-DONE sync.

Changes

  • docs/rfcs/RFC-008/README.md phase matrix: the shared P5-P7 row now reads P5 DONE; P6 / P7 queued (Codex, Pi Agent still pending).
  • docs/rfcs/RFC-008-decouple-enforcement-from-substrate.md phase-index stub (:1220): same split.
  • docs/rfcs/RFC-008/P5-P7-tool-plugins.md status line: P5 DONE, P6/P7 queued.

P6/P7 stay queued because they share the row and the slice file with P5.

Not changed (intentional)

docs/rfcs/_index.json and docs/rfcs/README.md track RFC-level status only. RFC-008 stays accepted (P6-P9 not shipped), so those are untouched. em-rfc-validate.mjs passes: 8 RFCs in _index.json, 8 canonical files, 8 README rows.

No code change.

🤖 Generated with Claude Code

P5 (OpenCode enforcement plugin) merged via #424 (`f5dbaef`) + doc fix
#425 (`a7f66c9`). Flip the stale `queued` P5 status in the three places
that track it, mirroring #423's P4-DONE sync:

- RFC-008/README.md phase matrix: the shared P5-P7 row now reads
  P5 DONE; P6 / P7 queued (Codex, Pi Agent still pending).
- RFC body phase-index stub (:1220): same split.
- P5-P7-tool-plugins.md status line: P5 DONE, P6/P7 queued.

P6/P7 stay queued (shared row/file). RFC-008 remains `accepted` at the
registry level (not all phases shipped), so docs/rfcs/_index.json +
README.md are unchanged; em-rfc-validate passes (8/8/8 consistent).
Rule 10 doc-sync; no code change.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

@lantiscooperdev lantiscooperdev left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Bot review (lantiscooperdev)

Reviewed the diff against the Rule 10 doc-sync intent. Verdict: ACCEPT (user approves + merges).

Verified

  • Completeness: grep for P5.*queued across docs/rfcs/ returns only the three intentional edits; no stale queued P5 marker remains. The three files are exactly the ones #423 touched for P4, adjusted for the shared P5-P7 row.
  • Correctness of the split: P5-P7 share one matrix row and one slice file, so flipping the whole row to DONE would have falsely marked P6 (Codex) and P7 (Pi Agent) done. The diff correctly reads "P5 DONE; P6 / P7 queued" in all three places.
  • Registry scope: _index.json + docs/rfcs/README.md left unchanged is correct — RFC-008 stays accepted until P6-P9 ship. node scripts/em-rfc-validate.mjs = "RFC registry consistent: 8 / 8 / 8".
  • Citations: PR/commit refs (#424 f5dbaef, #425 a7f66c9) match the merged history.
  • Style: no em/en dash introduced in added text (the P5–P7 row label en dash is pre-existing).

Notes (non-blocking)

  • The body manifest table row (:1188) has no status column, so it correctly needs no edit; status lives only in the three edited locations. Confirmed not an omission.

No code paths touched. Nothing to defer.

@lantiscooperdev lantiscooperdev merged commit 81bf1f0 into main Jun 27, 2026
4 checks passed
@lantisprime lantisprime deleted the docs/rfc-008-p5-done branch June 27, 2026 06:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants