docs: mark every RFC accepted and link its implementing PR - #19
Merged
Conversation
All thirteen are implemented and merged, so the index and each header now say so and link the PR that did it. RFC-0002, 0003, 0004 and 0011 also name the follow-up PRs that materially changed them, since a reader chasing why the shipped behaviour differs from the proposal should not have to find that by bisecting. The folder is now a design record rather than a to-do list, and the README says which it is. The gap analysis is left in the present tense of when it was written — the reasoning is the point, and rewriting it into the past would lose why that ordering was chosen. RFC-0013's references to #17 are replaced: that PR was superseded by #18, which carries its commits, so the links pointed at a closed PR. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
All thirteen RFCs are implemented and merged. This closes the loop on the design record.
docs/rfc/README.mdset the convention up front — "An RFC isDraftuntil someone implements it; the implementing PR flips it toAcceptedand links itself" — and the implementing PRs didn't do it. This does.What changed
Every RFC header now carries its implementing PR:
keyverbThe four with follow-ups name them deliberately: a reader wondering why the shipped behaviour differs from the proposal shouldn't have to find that by bisecting. #16 fixed seven defects in console/net that only surfaced after merge; #18 changed MCP's bind coverage and how recording's
--scaleis verified.Two editorial decisions
The gap analysis stays in the present tense of when it was written. It says "the CLI can click and type, but cannot press a key" — no longer true, and deliberately left. The reasoning is the point of keeping these; rewriting it into the past would lose why that ordering was chosen. The README now says the folder is a design record rather than a to-do list, so nobody reads it as a plan.
RFC-0013's
#17references are replaced. That PR was superseded by #18, which carries its commits, so four links pointed at a closed PR. RFC-0013 also gets a line in the README explaining that it wasn't part of the original set — it came out of a failure this work itself caused, and the reproduction contradicted the first diagnosis, which is why it's written up rather than just fixed.Docs only — no code changes.