docs: add post-178-remediation-plan.md — resolve dangling CHANGELOG reference#206
Merged
Conversation
…OT reference) PR #205's CHANGELOG entry cites `docs/pending-updates/post-178-remediation-plan.md` as the remediation SSOT, but the file was only ever in the local working tree (authored before the isolated worktree was set up) and never committed — so the reference dangled on `main` after #205 merged. This adds the plan doc to the repo (alongside the other docs/pending-updates/ planning records like Banker-Merge-Risk.md) so the CHANGELOG reference resolves. Header status updated DRAFT → EXECUTED (shipped in #205). Docs-only. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
…about as-shipped Audit of PR #206 found the committed plan (marked EXECUTED) self-contradicted and overstated fidelity to what PR #205 actually shipped: - §5 "Out of scope" still listed "wire claude_qa_dimension_score" + "export kgBreaker" as out-of-scope, contradicting the locked decisions (§2 D1=wire, D2=export). Removed. - Added §8 "Execution divergences" recording what shipped vs. planned: the Dim13ScoreLow→BankerCertifierReject retarget (no dim_13 key), 9 artifacts not 8, and the review-time scope expansion (schema-evolve/PB1, cross-skill sweep, §4.1 48-agent table, CHANGELOG) not in the original plan. - Sequencing note: D3 chose one omnibus branch, not 4 PRs. Docs-only. Co-Authored-By: Claude Opus 4.8 (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.
Summary
Follow-up to PR #205. That PR's CHANGELOG entry cites
docs/pending-updates/post-178-remediation-plan.mdas the remediation SSOT, but the file was only ever in the local working tree (authored before the isolated worktree was set up) and never committed — so the reference dangled onmainafter #205 merged.This PR adds the plan doc to the repo so the CHANGELOG reference resolves.
Why
docs/pending-updates/docs (e.g.Banker-Merge-Risk.md).Changes
super-legal-mcp-refactored/docs/pending-updates/post-178-remediation-plan.md(the full remediation plan: context, decisions, workstreams, 4-tier verification).DRAFT — awaiting approval→EXECUTED — shipped in PR #205.Docs-only. No code, schema, or runtime change.
Verification
git show origin/main:…/post-178-remediation-plan.mdcurrently → not found (the dangling ref); after merge it resolves.🤖 Generated with Claude Code