Correct stale documentation: standard-version reference and the removed daily-repo-status workflow

[Herm71]

Two stale claims, both in ROADMAP §5's own list of things to keep current.

1. .github/copilot-instructions.md still documents standard-version

It was replaced by commit-and-tag-version in a19905c. Three lines:

• 17 — npm install # Install Node dev dependencies (@wordpress/scripts, standard-version)
• 57 — Uses \standard-version` for automated releases:`
• 120 — - **Version bumping**: \wp-plugin-version-updater.js` + `package.json` `standard-version` config`

CLAUDE.md has the correct name, and its "Related" section carries a note about this drift that can come out once the fix lands.

This matters more than a normal typo: the file exists to instruct a coding agent, and an agent acting on it would look for config that isn't there.

2. The daily-repo-status bullet is obsolete

ROADMAP §5 currently reads:

Automated daily-repo-status issues accounted for most of the closed-issue history (#94–#118). If that workflow is still active, consider whether the signal justifies the noise in the issue tracker.

That workflow has been removed. .github/workflows/ now contains only ci.yml and release.yml. The bullet poses a question that is already answered — delete it.

The daily-status and report labels still exist on the repo. Worth deciding whether to remove those too, or keep them so the historical issues stay filterable. Keeping them is reasonable; just worth being deliberate.

Also worth folding in

While editing §5: its Dependabot count says 104 and is now 107 (#137). Either update it or reword so it doesn't carry a number that drifts.

Acceptance criteria

• No reference to standard-version remains in .github/copilot-instructions.md.
• The note about that drift is removed from CLAUDE.md's "Related" section.
• The daily-repo-status bullet is gone from ROADMAP §5.
• A decision on whether the daily-status / report labels stay.

Context

ROADMAP §5, second and third bullets. Related: #137. (#132 has since merged; it corrected a different set of stale claims in these same two files, so there is no longer any sequencing constraint — all four items below were re-verified against main at f477420 and still stand.)