Promote develop to main: the standup branch bootstrap and the partial-coverage remedy

[ptr727]

Promotes develop to main, carrying five merged pull requests.

What is being promoted

• #6178515666, the branch rename written -M rather than --move --force, which git gained later, checked against git's own option tables at v1.5.4 and v2.0.0.
• #61608cf819, the partial-coverage status line counting the unread files rather than asserting there is one.
• #614f39e0c0, the branch bootstrap step in STANDUP.md. Section 0B states the sequence that keeps the exploratory standup off main and develop, carries the procedure's only git init alongside both of section 0's identity checks, and records why the post-hoc cleanup is unavailable. It also carries one Disproved Claims entry and the removal of the shipped backlog cluster.
• #613676a2bd, the partial-coverage remedy in scripts/pr_review.py and its two documentation mirrors, corrected to what the record supports after measuring 4 pull requests and 7 rounds with 0 recoveries.
• #6121892d6f, a Dependabot group bump of four actions.

#616 and #617 both answer findings raised by the review on this promotion. A promotion's head is develop, so neither could be fixed here, and each took its own pull request into develop and its own review rounds before merging.

Review state

Each of the five was reviewed and merged on its own pull request, so this promotion carries no unreviewed change. #614 ran 13 rounds, 12 findings accepted and 1 declined and recorded under Disproved Claims. #616 ran 3 rounds and #617 ran 2, all findings accepted.

Merge shape

This is a promotion, so it merges as a merge commit rather than a squash, per GOVERNANCE.md "Branching Model". Its head is develop itself, so it must not be merged with --delete-branch.

[Copilot]

Pull request overview

Promotes the current develop state to main, incorporating already-merged updates to the standup bootstrap procedure, Copilot review partial-coverage guidance, and pinned GitHub Actions versions.

Changes:

• Add a new STANDUP.md section describing how to create main/develop early and run the standup on a feature branch.
• Update the review-reader guidance (scripts/pr_review.py, scripts/README.md, .github/copilot-instructions.md, TODO.md) to reflect measured behavior for partial-coverage rounds.
• Bump pinned workflow action SHAs in validation and release workflows.

Reviewed changes

Copilot reviewed 7 out of 7 changed files in this pull request and generated 1 comment.

Show a summary per file

File	Description
TODO.md	Removes the shipped standup-bootstrap backlog item and adds a new research item for identifying the skipped file in partial-coverage rounds.
STANDUP.md	Introduces section 0B with an explicit branch-bootstrap sequence to keep exploratory standup history off main/develop.
scripts/README.md	Documents the measured behavior that partial coverage does not recover via re-request, and clarifies the intended operator response.
scripts/pr_review.py	Updates exit-code 42 guidance and digest output text to stop recommending re-request as a remedy for partial coverage.
.github/workflows/validate-task.yml	Updates pinned SHAs for checkout and markdownlint action wrappers.
.github/workflows/publish-release.yml	Updates pinned SHAs for setup-dotnet, checkout, and release actions.
.github/copilot-instructions.md	Updates the runbook guidance for partial coverage and adds a Disproved Claims entry related to STANDUP.md grammar.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[Copilot]

Pull request overview

Copilot reviewed 8 out of 8 changed files in this pull request and generated no new comments.

Suppressed comments (1)

STANDUP.md:67

• The branch rename uses long options (--move --force), but the paragraph below explicitly says the block "needs no minimum version". Using the long options may impose a newer Git requirement than the short form, so this can undermine the compatibility claim. Prefer the traditional -M form here to keep the bootstrap as version-agnostic as possible.

git branch --move --force main # Renames whichever branch git init produced, in a repo holding only it.

[Copilot]

Pull request overview

Copilot reviewed 8 out of 8 changed files in this pull request and generated no new comments.

[ptr727]

Answering the suppressed finding raised on 08cf819 here, since a suppressed comment has no thread to resolve. Accepted, and fixed in 8515666 through #617 rather than on this pull request.

The branch rename uses long options (--move --force), but the paragraph below explicitly says the block "needs no minimum version". Using the long options may impose a newer Git requirement than the short form, so this can undermine the compatibility claim. Prefer the traditional -M form here to keep the bootstrap as version-agnostic as possible.

Checked against git's own option tables rather than taken on faith, since the finding is a claim about when a spelling became available:

Tag	git branch option table
v1.5.4	OPT_BIT('m', NULL, ...), OPT_BIT('M', NULL, ...), OPT_BOOLEAN('f', NULL, ...)
v2.0.0	OPT_BIT('m', "move", ...), OPT_BIT('M', NULL, ...), OPT__FORCE(...)

Neither long option exists in 1.5.4 and both do by 2.0.0, and -M has no long equivalent in either, so the direction of the finding is right. It also bounds it: the long forms are far older than git switch at 2.23 and git init --initial-branch at 2.28, which the paragraph named, so nothing here would have failed on a plausible host. The claim was no floor at all rather than a floor earlier than those two.

The line is git branch -M main now. #617 also narrowed the paragraph, after a second finding there that the replacement claim covered the whole block while only the rename had been checked, so it explains the rename alone.

The fix took its own pull request because this one is a promotion, whose head is develop. Both findings this promotion's review has raised were closed that way, and this pull request carries the results as two of the five commits it promotes.