Fill the RFC-007 Phase 2 ledger provenance from git, not a placeholder#605
Merged
Conversation
PR #604 deliberately left PR #XXX (<pending-merge-sha>) in the Phase 2 row and the Implementation ledger row, to be resolved from git after merge per the #582 defect class. Derived from git log --oneline --follow -- scripts/em-graph.mjs, which gives df93920, the main-merge commit carrying (#604) in its subject, not a feature-branch tip. Also corrects the CI anchor in the same ledger row: the new suite step is at .github/workflows/tests.yml:404-405, not :403-404 as written. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
lantiscooperdev
approved these changes
Jul 25, 2026
This was referenced Jul 25, 2026
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
2 participants
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.
Follow-up to #604, which deliberately shipped
PR #XXX ()in two places because the merge SHA does not exist until merge. Resolving them now.Provenance
Derived from
git log --oneline --follow -- scripts/em-graph.mjs, against the file the ledger row claims to have changed:df93920carries(#604)in its subject, so it is the main-merge commit and not a feature-branch tip. That distinction is the whole point of #582, which tracks two pre-existing rows (RFC-008 P0, RFC-012 P1) that cite branch tips instead. Not copied from an adjacent row and not taken from a workplan note.Also fixed in the same row
The ledger claimed the new suite is CI-wired at
.github/workflows/tests.yml:403-404. It is at:404-405:Off by one, same accuracy discipline, so corrected here rather than filed.
Verified
node scripts/em-rfc-validate.mjs— 14 RFCs consistentnode tests/test-em-graph-nodes.mjs— 28 passed, 0 failed (includest_rfc_rows_flippedandt_rfc_states_no_name_policy, which assert on this file)grep -n "<LINE>\|XXX\|pending-merge\|TODO" docs/rfcs/RFC-007-graph-projection.md— no output, so no placeholder survivesem-graph.mjs:227is theruleById.has(id)branch,:231isrfcById.has(id)Docs only, two lines changed.