Filed by the domain:devx execution seat (session session_01WLJQhde67SeTccsmnBVarV) at #14043's landing window, per the obligation recorded on that card's claim. ⛔ Unassigned — pm:* grading is triage's.
The gap, one sentence
content/docs/protocol/backward-compatibility.mdx:207 (position dated to origin/main b360cc7d — re-derive) reads: "the condition that closes the window is tracked separately and is deliberately not stated here." That deferral was correct when written (PR #14211, whose dispatch fence forbade inventing the end condition). The end condition is now WRITTEN and maintainer-ruled: PR #14227 recorded it in scripts/check-changeset-no-major.mjs's header — at GA (the fixed group's first general-availability major), the group returns to strict semver.
What to do
Replace the "deliberately not stated here" deferral with the ruled one-liner (window closes at GA; strict semver resumes), consistent with the gate-header text — ⛔ no dates, no version numbers, nothing the ruling does not contain. The customer reading this page is exactly the audience triage identified when it linked this half to #14043: they judge "when can I go back to reading MAJOR as the risk signal" from this sentence.
Read-only measurements already taken by #14043's dev (2026-09-01): the page's two other references to the gate (:115, :195) are accurate and need no change.
Scope notes for triage
Dedup
#13893 (closed — rewrote both pages but deliberately deferred this sentence) · #14043 (closed — the internal half) · #14210 (open — phantom labels + 2-MINOR dwell on the same page, different defect). No open card covers this sentence.
Filed by the
domain:devxexecution seat (sessionsession_01WLJQhde67SeTccsmnBVarV) at #14043's landing window, per the obligation recorded on that card's claim. ⛔ Unassigned —pm:*grading is triage's.The gap, one sentence
content/docs/protocol/backward-compatibility.mdx:207(position dated toorigin/main b360cc7d— re-derive) reads: "the condition that closes the window is tracked separately and is deliberately not stated here." That deferral was correct when written (PR #14211, whose dispatch fence forbade inventing the end condition). The end condition is now WRITTEN and maintainer-ruled: PR #14227 recorded it inscripts/check-changeset-no-major.mjs's header — at GA (the fixed group's first general-availability major), the group returns to strict semver.What to do
Replace the "deliberately not stated here" deferral with the ruled one-liner (window closes at GA; strict semver resumes), consistent with the gate-header text — ⛔ no dates, no version numbers, nothing the ruling does not contain. The customer reading this page is exactly the audience triage identified when it linked this half to #14043: they judge "when can I go back to reading MAJOR as the risk signal" from this sentence.
Read-only measurements already taken by #14043's dev (2026-09-01): the page's two other references to the gate (
:115,:195) are accurate and need no change.Scope notes for triage
content/docs/protocol/**(NOTreleases/**, so no docs-only-PR fence applies).Dedup
#13893 (closed — rewrote both pages but deliberately deferred this sentence) · #14043 (closed — the internal half) · #14210 (open — phantom labels + 2-MINOR dwell on the same page, different defect). No open card covers this sentence.