Skip to content

Record QEP-2 as Accepted - #10

Merged
mmcky merged 1 commit into
mainfrom
qep-0002-accepted
Aug 8, 2026
Merged

Record QEP-2 as Accepted#10
mmcky merged 1 commit into
mainfrom
qep-0002-accepted

Conversation

@mmcky

@mmcky mmcky commented Aug 8, 2026

Copy link
Copy Markdown
Contributor

QEP-2 merged in #2 while its status still read Draft, so main currently holds an in-effect standard that its own record describes as a draft. This PR completes step 5 of QEP-1's decision process, which was skipped at merge time.

The flip is applied in the three places AGENTS.md keeps in sync: the YAML frontmatter, the in-document header table, and the README index row. CI parity passed before this PR only because all three agreed on the wrong value.

No version bump. A newly accepted QEP carries no version — implicitly v0 until first substantively amended — so the README Version column stays at the em dash. QEP-4 will be the thing that moves QEP-2 to v1, when its acceptance PR re-applies the registry hooks it parked per the convention in #9.

The decision itself is not reopened here: @jstac approved the label set and the labelling policy on #2, and @mmcky confirmed the merge. Only the bookkeeping is outstanding.

Changes

Location Was Now
qeps/qep-0002-standard-github-labels.md frontmatter status: Draft status: Accepted
qeps/qep-0002-standard-github-labels.md header table Draft Accepted
README.md index row Draft Accepted

Nothing else changes — no normative content is touched, so this is an editorial commit under AGENTS.md's substantive/editorial split.

Downstream

Merging this changes the README row QEP-3 (#7) and QEP-4 (#8) must carry. Both branches are already stale against main (they predate QEP-1 v2 and QEP-2's merge, and neither has the QEP-2 row at all), so each will be brought up to date in its own revision round.

🤖 Generated with Claude Code

QEP-2 merged in #2 while its status still read Draft, so `main` holds an
in-effect standard that the record describes as a draft. This completes step 5
of QEP-1's decision process — flip Draft -> Accepted in the three places kept in
sync per AGENTS.md: the frontmatter, the in-document header table, and the
README index row.

The decision itself is not in doubt: @jstac signed off on the label set and the
labelling policy, and @mmcky confirmed the merge. Only the record step was
skipped, and it was skipped after the fact rather than reversed, so nothing here
reopens the substance.

No version bump. A newly accepted QEP carries no `version` — it is implicitly v0
until first substantively amended (QEP-1, Versioning), so the README Version
column stays at the em dash.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Copilot AI lite review requested due to automatic review settings August 8, 2026 04:19

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Pull request overview

This PR corrects the repository’s QEP registry bookkeeping by recording QEP-2 as Accepted (instead of Draft) across the three synced locations (frontmatter, in-document header table, and README index), aligning the public record with the already-merged decision.

Changes:

  • Update QEP-2 frontmatter status from DraftAccepted.
  • Update QEP-2 in-document header table Status from DraftAccepted.
  • Update README index row for QEP-2 Status from DraftAccepted (leaving Version as ).

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File Description
README.md Updates the QEP index row so QEP-2 is shown as Accepted.
qeps/qep-0002-standard-github-labels.md Updates QEP-2’s status in both frontmatter and header table to Accepted.

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

@mmcky
mmcky merged commit cfbc00e into main Aug 8, 2026
2 checks passed
@mmcky
mmcky deleted the qep-0002-accepted branch August 8, 2026 04:21
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