Revalidate stale DOC findings before using the Planfile backlog for prioritization

[tom-sapletta-com]

Confirmed during MONAG report audit, 2026-09-19. Scope: backlog intake and GitHub Issue publication only; implementation must join the existing governed workstream.

Evidence:
The 2026-09-19 MONAG report lists 191 remaining records from root planfile.yaml. DOC-109, DOC-116, DOC-119 and DOC-120 are critical broken-link findings against an older docs/README.md (some cite lines 256-303). At HEAD 91b30fe that document has 12 lines and none of the cited ./LICENSE, ./CONTRIBUTING.md, ./docs/api.md or ./examples link targets; it now uses ../README.md and ../examples/README.md. DOC-002/003 also cite old CHANGELOG line locations. This proves stale evidence for the four critical records, not that all 191 tasks can be closed. Related broader documentation work: #10.

Owning repository HEAD at intake: 91b30fe

Acceptance criteria:

• Re-run the relevant docval checks against a recorded current SHA and reconcile each existing DOC record with fresh evidence.
• Close/supersede only findings proven resolved; preserve distinct occurrences even when titles match.
• Separate severity from urgency and bind refreshed findings to source revision and stable location.
• Ensure remaining real issues have verified project-local Planfile to GitHub mappings; avoid creating 191 duplicate issues.

---

Strategy Metadata:

• repository: semcod/costs
• planfile_id: semcod/costs:652308e41fcb1f03:PLF-010

Implementation: #15 at 091948e. Full suite 56 passed; required GitHub checks passed. 152 obsolete DOC records superseded with hashes (including DOC-001 already done in primary); 31 candidates preserved for Issue #10. Pushed, awaiting protected Validator merge.