docs(lint): backlink R11's doc comment to #8323's measured cross-tenant oracle

[qq9340100]

Fixes #8584

What

One-line backlink added to the doc comment of lintUnscopedDeclaredIndexes (rule unique/unscoped-declared-index, R11, ADR-0120 D5a, packages/lint/src/data-model-rules.ts), pointing at #8323's end-to-end measurement of the cross-tenant 409-vs-201 oracle — the concrete harm this rule's warning exists to prevent.

 * 17.x: warning. Protocol 18 rejects the spelling at validate/publish (#5082).
 * Advisory — never fails a build in 17.x.
 *
 * Concrete harm: #8323 measured the cross-tenant 409-vs-201 oracle end to end.
 *
 * Wiring: own AUTHORING_RULES entry (validate/build), and `lintDataModel`

Why

Follow-through from the #8379 closure (maintainer ruling A, 2026-08-13: closed as already-satisfied). Part 3 of the #8323 ruling was drafted without knowing R11 already delivered its substance, because the connection between the rule and the measured oracle lived nowhere in the tree. This line makes the next sweep/ruling find R11 instead of re-deriving (or re-mandating) it.

Verified against #8323's evidence

Confirmed from #8323's body (not the title) that R11's DECLARED-INDEX bare-unique: true spelling is exactly the shape #8323 measured end-to-end: sys_capability and sys_user_preference (both tenant-scoped, plain unique fields) produced a single global unique index, and the cross-tenant probe showed 409 UNIQUE_VIOLATION on a value invisible to the caller (GET → total 0) — the 409-vs-201 oracle named in the added line. R11's own doc comment already states the mechanism ("materializes over exactly its fields, i.e. installation-wide") and cites the same #4986/#5082 lineage; the added line makes the connection to #8323's measurement explicit rather than leaving it implicit in the mechanism description.

Scope

• Doc comment only — no rule logic, tier, message text, or verdict change.
• Verified: packages/lint/src/data-model-rules.ts had no other in-flight changes at branch time (PR feat(objectql,runtime,lint): tighten views: to the container-only contract; assembled manifests travel non-container view artifacts in viewItems: #8572 touches validate-view-containers.ts/packages/objectql/packages/runtime, not data-model-rules.ts; the objectstack-8543 worktree's diff against origin/main also does not touch this file). Full serial-constraint check result in the dev report comment below.
• skip-changeset — docs-only, not user-visible, releases nothing.
• Draft only; no ready-flip, no auto-merge.

---

Generated by Claude Code

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
objectstack	Ignored		Aug 14, 2026 12:49am

[github-actions]

📓 Docs Drift Check

This PR changes 1 package(s): @objectstack/lint.

3 hand-written doc(s) reference the affected code and may need an implementation-accuracy re-verification:

• content/docs/automation/hook-bodies.mdx (via @objectstack/lint)
• content/docs/deployment/validating-metadata.mdx (via packages/lint)
• content/docs/permissions/authorization.mdx (via @objectstack/lint)

⛔ 1 release-owned page(s) also reference the affected code. These are read-only:

• content/docs/releases/v17.mdx (via @objectstack/lint)

content/docs/releases/ is RELEASE-OWNED (AGENTS.md "Documentation Guardrails"): release
notes are written centrally at release time, and a code PR that edits them is the exact PR
that guardrail exists to stop. They are still audited — read-only. If one of them is actually
wrong, file an issue or open a dedicated docs-only PR; do not edit it here.

Advisory only. To re-verify, run the docs-accuracy-audit workflow scoped to these files:
node scripts/docs-audit/affected-docs.mjs origin/main → pass the list as args.docs.