Skip to content

docs: post-remediation documentation sweep - #198

Merged
TheCraftyMaker merged 1 commit into
mainfrom
docs/post-remediation-sweep
Jul 28, 2026
Merged

TheCraftyMaker merged 1 commit into
mainfrom
docs/post-remediation-sweep

Conversation

@TheCraftyMaker

Copy link
Copy Markdown
Owner

Summary

Lands Task F21 of the remediation plan (docs/superpowers/plans/2026-07-07-review-findings-remediation.md). Docs-only, no source/test changes.

Landed on main:

  • F12's PR link (#196) added to its table row and status note.
  • F19's "done, report-only close" status, which previously existed only on the unmerged test/remediation-regression branch.
  • F21 itself, added and marked done.

Fact-check findings (verified against git history / GitHub this session, not copied from any prior session):

Investigated and corrected, not filed as a new follow-up: the task brief described an open "regression" where dependabot silently reverted F14's bounded NuGet dependency ranges. Re-verifying via gh pr view --json files and git log -p -- Directory.Packages.props shows the three named dependabot PRs (#162/#165/#166) only ever touched demo/Directory.Packages.props; the root file's brackets were removed by a deliberate, already-merged, already-changelogged decision (#177), which also already carries its own accurate FOLLOWUPS.md entry. Corrected the framing in the plan doc (R7, F19's status, F21's scope) instead of propagating the incorrect claim or filing a redundant follow-up.

Humanizer pass: ran the humanizer skill over every Tier-1 doc touched here (README, CONTRIBUTING, SECURITY, CHANGELOG, the plan doc), and a style-only pass (dash/quote cleanup, no content changes) over the other dated design/discovery docs under docs/superpowers/plans/.

Test plan

  • Confirmed no non-.md files are in the diff.
  • Spot-checked several files' diffs to confirm only punctuation/prose style changed, no facts/numbers/decisions altered.
  • Re-verified every Tier-1 factual correction against git log, gh pr view, or the current source before applying it.

🤖 Generated with Claude Code

Lands F21 of the review-findings-remediation plan: corrects stale
factual claims across the repo's docs and lands F12/F19's status on
main, which had only existed on an unmerged branch.

Fact-check findings:
- README.md still advertised "pre-release (0.1.0-beta.7)" and named
  WolverineFx 6.9.x, though the package has shipped 1.0.0 since
  2026-07-06 and WolverineFx moved to 6.21.0. Also dropped an
  unverifiable "MongoDB.Driver 2.x also supported" claim.
- CONTRIBUTING.md called MongoDbUnitOfWork "a planned follow-up
  enhancement" though it shipped in PR #50.
- SECURITY.md's supported-versions table still listed 0.1.x.
- CHANGELOG.md's Unreleased section was missing entries for F16
  (dedup refactor, PR #187) and F18 (demo CustomerFeedback entity,
  PR #194).

Investigated, not fixed as new: this session's brief described a
"regression" where dependabot silently reverted F14's bounded NuGet
dependency ranges. Re-verifying against gh pr view and git log shows
the three named dependabot PRs only touched demo/Directory.Packages.
props; the root file's ranges were removed by a deliberate, already
merged, already changelogged decision (PR #177). Corrected the framing
in the plan doc rather than filing a redundant follow-up.

Ran the humanizer skill over every Tier-1 doc touched here, and a
style-only pass (dash removal, no content changes) over the other
dated design/discovery docs under docs/superpowers/plans/.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
@TheCraftyMaker
TheCraftyMaker force-pushed the docs/post-remediation-sweep branch from 0e6bdb6 to cbada15 Compare July 28, 2026 06:58
@TheCraftyMaker
TheCraftyMaker merged commit b9a8fb0 into main Jul 28, 2026
7 checks passed
@TheCraftyMaker
TheCraftyMaker deleted the docs/post-remediation-sweep branch July 28, 2026 09:42
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.

1 participant