⛔ Ungraded and unrouted — domain:*, priority and type are triage's. Filed unassigned by the domain:devx execution seat (session_016vtdMao3dQS9EfQfpyWixd) as the measured residual of #15869, which was closed as completed at 2026-09-05T14:36Z.
What #15869 fixed, and what it did not
PR #15896 (merged 2026-09-05T14:27:59Z) holds the census page's row N references to the table by seam, and refuses when the numbering moves under them. That mechanism is real and enforced — verified on origin/main.
But 2 of the 21 references are declared unheld, and an unheld entry is LOCATED without having its number compared. Measured on origin/main:
scripts/check-system-context-census.mjs:2386 'and the real run really resolved them
(10 page references + 9 `why:` mentions, 2 declared unheld)'
scripts/check-system-context-census.mjs:479 'unheld entries are still LOCATED, so one cannot decay into "not there".'
scripts/check-system-context-census.mjs:583 / :639 the two unheld entries
The two, quoted from content/docs/permissions/system-context.mdx on origin/main:
| line |
the sentence |
why no key is derivable |
:90 |
Lose: all of rows 2–6 at once — this is the single largest behaviour on the page |
a RANGE whose endpoints the sentence never names; nothing in it picks a first or last row, and the two are not a section extent |
:423 |
- [Sharing Rules](/docs/permissions/sharing-rules) — what row 30 is skipping |
the bullet's only subject is the linked doc title, and several rows are about sharing rules, so no key in the sentence picks one |
⇒ The defect #15869 named survives in exactly these two places. An insertion above row 30 still moves what :423 points at, and nothing reds — which is the card's own failure mode («a falsified reference is worse than a dangling one, because it resolves»). It is now declared rather than silent, which is a genuine improvement, but it is not closed.
Why this is its own card
The remedy is not more gate code — it is rewording the two sentences so each names the seam it is about, after which the existing PAGE_ROW_REFERENCES mechanism holds them with no new machinery. The --fix leg that renumbers prose needs the same write.
⛔ Blocked today, and by what
Both need content/docs/permissions/system-context.mdx written, and that page is merge=os-regen routed and currently held by eight open PRs — #15889, #15888, #15879, #15878, #15863, #15838, #15673, #15235 (enumerated 2026-09-05, by changed-file page per PR). Suggested hold condition for triage, machine-readable:
Restart-when: no open PR touches content/docs/permissions/system-context.mdx
Restart-touch: content/docs/permissions/system-context.mdx
Landing note measured on the PR: none of those eight inserts or removes a numbered row — each is a pure anchor rewrite — so the new [row-ref-…] refusals will not fire spuriously as they land.
⛔ What is deliberately NOT claimed
Re-check
git show origin/main:scripts/check-system-context-census.mjs | grep -n 'declared unheld'
git show origin/main:content/docs/permissions/system-context.mdx | sed -n '90p;423p'
# the blocker, re-derived rather than trusted:
# list open PRs, then GET /pulls/N/files for each, and grep for the page path
Dedup: searched open and closed issues for the census page / unheld / seam-key wording before filing — 3 results, none is this residual (#15869 itself, #12360, #8895).
Related: #15869 (the mechanism, closed) · PR #15896 · #15687 (the insertion that falsified three references) · #15395 (the removal that made them true again by coincidence).
⛔ Ungraded and unrouted —
domain:*, priority and type are triage's. Filed unassigned by thedomain:devxexecution seat (session_016vtdMao3dQS9EfQfpyWixd) as the measured residual of #15869, which was closed as completed at 2026-09-05T14:36Z.What #15869 fixed, and what it did not
PR #15896 (merged
2026-09-05T14:27:59Z) holds the census page'srow Nreferences to the table by seam, and refuses when the numbering moves under them. That mechanism is real and enforced — verified onorigin/main.But 2 of the 21 references are declared
unheld, and anunheldentry is LOCATED without having its number compared. Measured onorigin/main:The two, quoted from
content/docs/permissions/system-context.mdxonorigin/main::90Lose: all of rows 2–6 at once — this is the single largest behaviour on the page:423- [Sharing Rules](/docs/permissions/sharing-rules) — what row 30 is skipping⇒ The defect #15869 named survives in exactly these two places. An insertion above row 30 still moves what
:423points at, and nothing reds — which is the card's own failure mode («a falsified reference is worse than a dangling one, because it resolves»). It is now declared rather than silent, which is a genuine improvement, but it is not closed.Why this is its own card
The remedy is not more gate code — it is rewording the two sentences so each names the seam it is about, after which the existing
PAGE_ROW_REFERENCESmechanism holds them with no new machinery. The--fixleg that renumbers prose needs the same write.⛔ Blocked today, and by what
Both need
content/docs/permissions/system-context.mdxwritten, and that page ismerge=os-regenrouted and currently held by eight open PRs — #15889, #15888, #15879, #15878, #15863, #15838, #15673, #15235 (enumerated 2026-09-05, by changed-file page per PR). Suggested hold condition for triage, machine-readable:Landing note measured on the PR: none of those eight inserts or removes a numbered row — each is a pure anchor rewrite — so the new
[row-ref-…]refusals will not fire spuriously as they land.⛔ What is deliberately NOT claimed
why:strings, under a greencheck:system-context-census#15869 should have stayed open. Its filer (thedomain:engineseat,5552521314) closed it on a measured landing of the mechanism, and that measurement is sound — this seat re-ran the relevant greps againstorigin/mainrather than reading the docblock, and agrees.Re-check
Dedup: searched open and closed issues for the census page /
unheld/ seam-key wording before filing — 3 results, none is this residual (#15869 itself, #12360, #8895).Related: #15869 (the mechanism, closed) · PR #15896 · #15687 (the insertion that falsified three references) · #15395 (the removal that made them true again by coincidence).