§6 External review periods

This implements VERSIONING.md §3.4 condition 5. No review period has been opened for VER 1.1 as of this document. standards/ver/1.1-draft/RELEASE.md row 17 records the review period half as not started and BLOCKING (its current wording: "Half done — still BLOCKING"), and it stays blocking until someone actually opens one under the mechanics below. Publishing this document is not that act.

Announcing one. A maintainer opens a review period with a pull request that (1) adds a dated entry to the draft release's RELEASE.md, against the row that names the review period (row 17, for 1.1) — open date, minimum close date, where comments are collected — and (2) opens a GitHub issue labeled review-period, linking to that entry, that stays open for the duration and collects discussion not already homed somewhere more specific (a PR against the draft text, for instance). The close date is computed from the open date stated in that entry, never asserted independently of it.

Minimum duration: 30 days from the announcement above.

Where comments go: the review-period issue, or a more specific PR/issue it links to; a comment that rises to a formal objection follows §5 instead (and is still logged in the closing report below).

Closing artifact. A review period closes by publishing docs/standards/VER-<release>-review-report.md (for 1.1: docs/standards/VER-1.1-review-report.md), listing every comment received and its disposition, using the same accepted / accepted-with-changes / rejected-with-reasons vocabulary as §5. This report must be published before ratification — before the publication checklist in VERSIONING.md §3.3 is run for that release, and before the corresponding RELEASE.md row is marked resolved. A review period that ran its 30 days but produced no report has not closed.