docs: track promoted provenance record for issue #576 - #577
Merged
Conversation
`potential_to_issue` wrote this promoted record when issue #576 was filed for the second defect in issue #545 — TaskMaster's root build files are absent from `shared_surfaces` in `config/blast-radius.json`, so two items that both edit `coverage.config`, `Directory.Build.targets`, or `TaskMaster.sln` report `conflict=False` and can be scheduled into the same parallel cohort. The record is the provenance artifact linking #576 back to its potential entry and carries the reproduction evidence gathered on `a01bdbb0`, including the negative control that distinguishes a real fix from one that simply reports `conflict=False` for every pair. Committing it so the audit trail survives; an untracked file under `docs/features/potential/promoted/` is lost to any tree clean. No code, configuration, or test is changed by this commit. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_016LdWAA7aMkzJ27NUW7WzaT
Uh oh!
There was an error while loading. Please reload this page.
5 tasks
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 freeto 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.
docs: track promoted provenance record for issue #576
Summary
potential_to_issuewrote when issue Bug: blast-radius-shared-surfaces-missing-root-build-files #576 was filed, so the audit trail linking that issue to its potential entry survives a tree clean.docs/features/potential/promoted/. No code, configuration, test, or workflow is touched.a01bdbb0, including the negative control that distinguishes a real fix from one that merely reportsconflict=Falsefor every pair.Why
Issue #545 reported two defects in
config/blast-radius.json. PR #575 fixed the first (the unfit module map). The second — TaskMaster's root build files being absent fromshared_surfaces— is not fixed, and #545's own text predicted that fixing the module map alone would convert it into a reported false negative. That is now the observed behavior, so the defect was split out to #576 rather than closed with #545.The promotion tooling left its provenance record untracked. An untracked file under
docs/features/potential/promoted/is lost to any tree clean, which would break the link from #576 back to the potential entry and discard the recorded evidence. Committing it closes that gap.What Changed
docs/features/potential/promoted/2026-08-21-blast-radius-shared-surfaces-missing-root-build-files.mdVerification
Completed
.mdonly, underdocs/— no code, config, test, or workflow path in the diffartifacts/is gitignored so the PR-body artifact does not enter the difforigin/mainata01bdbb0; merge-base equals base, so the PR is a single-commit fast-forward candidateNot applicable
The C# toolchain (CSharpier, analyzers, nullable, MSTest) is not exercised by this change: the diff contains no
*.cs,*.csproj,*.props,*.targets,*.config, or workflow file. CI runs regardless and is the gate for merge.Backward Compatibility / Migration Notes
None. Adding a Markdown record under
docs/changes no public surface, build input, or runtime behavior.Risks and Mitigations
Rollback is
git revertof the single commit, with no build or data implications.Review Guide
Single file, single commit. Read the record's Actual Behavior and Logs / Screenshots sections — they carry the reproduction output and the control case that together establish the defect is real and is a false negative rather than a missing feature.
Follow-ups
shared_surfaces(candidates includecoverage.config,Directory.Build.targets,TaskMaster.sln,.editorconfig,.globalconfig,dotnet-tools.json,.csharpierignore) plus ashared_surface_globsentry for.github/workflows/**, verifying each path exists before adding it..claude/rules/parallel-orchestration.mdstill narrates the reference repository's seven subsystem modules, which do not describe the shipped TaskMaster config. Noted in Bug: blast-radius-shared-surfaces-missing-root-build-files #576 as a related documentation defect.GitHub Auto-close
This pull request does not fix#576; it only commits that issue's provenance record. The context bundle detects
#576as a referenced issue, not as an autoclose target, and no autoclose list was supplied. Emitting a closing keyword here would wrongly close an open, confirmed bug.