fix(docs): rewrite SCR-006 so the prose gate accepts it

[cursor]

What & why

The post-merge canary failed prose on main at 207fda240 and filed #6548. SCR-006 is a new file, so it has no prose allowance. Two constructions failed the banned-phrase check: the filler adverb deliberate, and issue numbers in the origin line and the rationale. The canary prints phrase failures and returns, so it did not also print the reading grade. A new file is held to 6.00, and the merged text scores above that. This rewrite keeps the directive and states it in short sentences.

python3 scripts/check-prose.py passes on this branch, judged against 207fda240, which is the tip of main. python3 scripts/check-prose.py --absolute passes too, which is the mode scripts/main-canary.sh runs.

The same commit also failed docs-guards, because docs/manifest.json had no SCR-006 entry. The second commit on this branch adds that entry. #6550 carries the same five lines on its own branch. Whichever of the two lands second will fail empty-diff on the manifest and should close. The frontmatter title is unchanged, so the entry matches either way.

Closes #6548

The witness

• No witness needed (docs / CI). scripts/check-prose.py is the gate. It fails on 207fda240 and passes on this commit, including --absolute. docs-guards is the gate for the manifest entry, and it passes on this commit.
• This PR includes a witness test. Not applicable; the checks above are the witness.

The gate

Docs-only. No Rust sources changed, so the compile tiers are CI's.

• cargo fmt --check: no Rust change
• cargo clippy --workspace --all-targets -- -D warnings: no Rust change
• cargo test --workspace: no Rust change
• Docs updated where behavior/flags changed: the record is the change
• CLA signed (the bot prompts on your first PR, nothing to do per commit)
• Closes #6548 appears above and as a commit trailer

Fix over file

• Extra fixes in this PR: the docs/manifest.json entry for SCR-006, which repairs the docs-guards failure on the same broken commit
• Filed, with the reason a fix could not ride this PR: Stella still carries docs/scr/, which oxagen's ADR-137 retired (residue #6552) #6555 removes stella's docs/scr/ corpus. See the residue section below.

P2 residue

Oxagen's ADR-137, accepted on 2026-09-22, moves the standing decisions into .oxagen/rules/*.toml in oxagen and removes docs/scr/ from all five repositories. Oxagen's scr-corpus-check now fails while any repository still holds a file under docs/scr/. The five-repository sync this section used to describe is retired, so no copy of SCR-006 should be synced anywhere.

#6555 carries stella's side of ADR-137. It deletes docs/scr/, removes the seven scr/* entries from docs/manifest.json, and points the AGENTS.md standing-decision bullets at oxagen's TOML records. That removal does not ride this PR, because this PR repairs a red main and a corpus removal deserves its own review. #6555 also supersedes the definition of done in #6554. Pillar: maintainability.

Until #6555 lands, this PR keeps the file readable and the manifest consistent, so main goes green.

Ground-rule check

No engine, dependency, or network change.

Anything reviewers should know?

Sourcery's title thread on #6547 is already resolved. The suggestion that landed is the compiled bullet above. It does not equal the record title, and the check that Sourcery cited compares short titles across repositories, not a short title to the frontmatter title.

The main is not known-broken check reads the unblocks-main label, which this PR carries because it is the repair for #6548.

  

Summary by Sourcery

Rewrite SCR-006 for prose-gate compliance and register it in the documentation manifest.

Bug Fixes:

• Rewrite SCR-006 to satisfy the prose gate and restore successful canary checks.

Enhancements:

• Clarify the schema-change directive, rationale, compliance guidance, and exceptions with shorter, plainer prose while preserving the policy.

Documentation:

• Register SCR-006 in the documentation manifest so documentation guards recognize the record.

---

Note

Low Risk
Documentation and manifest metadata only; no runtime, CI workflow, or schema-migration behavior changes in this repo.

Overview
Repairs SCR-006 after the main canary failed prose and docs-guards on the newly merged record (#6548).

The SCR text is rewritten, not re-scoped: same directive (migration-required, no deploy until production migration, no auto-apply in pipelines), but shorter sentences and plainer wording so scripts/check-prose.py passes (banned filler like “deliberate”, issue numbers in origin, and reading-grade limits on new files). The rationale now links the four oxagen incidents as URLs instead of #1275-style references. Agent compliance and exceptions are the same policy, broken into bullet-sized steps.

docs/manifest.json gains the missing scr/006-schema-changes-are-labelled entry so docs guard validation sees the file.

^{Reviewed by Cursor Bugbot for commit fbed89d. Configure here.}

[sourcery-ai]

Reviewer's Guide

This docs-only change rewrites SCR-006’s origin, enforcement, directive, rationale, compliance guidance, and exceptions into prose-gate-compliant short sentences, without changing the record’s frontmatter title or policy intent.

File-Level Changes

Change	Details	Files
Rewrote the SCR-006 record to satisfy the repository’s prose gate while preserving its schema-migration directive.	Replaced banned phrasing and issue-number references with neutral, short-sentence prose. Reformatted the directive, rationale, compliance steps, and exceptions into shorter paragraphs and sentences. Preserved the frontmatter title and the substantive policy about labeling schema changes and running migrations before or with deployment.	docs/scr/SCR-006-schema-changes-are-labelled.md

Assessment against linked issues

Issue	Objective	Addressed	Explanation
#6548	Remove the prose violations in SCR-006, including the filler adverb and issue-number references, without adding a prose baseline entry.	✅
#6548	Ensure the prose check passes for the repaired document, including the absolute mode used by the main-canary.	✅
#6548	Land the prose repair as a focused documentation change from the affected main tree rather than folding it into an unrelated fix.	✅

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[github-actions]

SCR-003 DoD check passed — every linked issue's definition of done is fully checked.

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, add credits to your account and enable them for code reviews in your settings.

[sourcery-ai]

Sorry @macanderson, you've used your own review budget of 250,000 diff characters for the last 7 days.

You can request another review in 4 days and 23 hours by commenting @sourcery-ai review. Upgrade to get a review now.

[cursor]

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: serverGenReqId_8da1c6b5-e5b2-4c1a-9cf5-05e5dc7030e6)

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
🔒 Security Review	✅ Completed 2026-09-22T23:48:16.661550Z	b003e4d	Draft marked ready

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[sourcery-ai]

Sourcery assessment

Approved.

[macanderson]

Heads-up from #6550: both pull requests add the same five docs/manifest.json lines for SCR-006. scripts/check-empty-diff.sh tests the merge tree, so whichever of the two lands second fails PR carries a diff until it drops the shared hunk. #6550 is the five-line manifest repair and is meant to land first. Once it merges, rebase this branch onto main and the manifest hunk disappears on its own. If this one lands first, #6550 gets closed as superseded.

[macanderson]

Adversarial review round 1: the prose repair passes its gate (grade 11.02 to 4.75, verified); the PR body plans residue against a corpus that ADR-137 retired, and one rewritten line contradicts the compiled bullet.

[cursor]

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: serverGenReqId_26577bb4-99bf-4dee-ae52-94498a5117fe)

[macanderson]

Adversarial review round 2: all four round 1 findings are fixed on fbed89d0, and check-prose.py passes in both modes. Two new findings are about the PR body: one wrong landing instruction (P2) and one duplicate residue issue (P3). The dispatch named b003e4df; this review is against the live head fbed89d0. CI on that head: 27 checks pass or skip, and Analyze (rust) is still pending.

[cursor]

CI on fbed89d0 is green. Docs guards, the prose-only path, empty-diff, and dod passed. There is no CI failure to repair. Neither review round found a P0 or a P1, so there is no per-P1 ticket after the second pass.

Round 1 is fixed on this head. The label step says the author adds migration-required by hand where no bot does. The four oxagen incidents are backticked URLs under the rationale. The compliance fragments are folded into the steps they belong to. The residue section follows ADR-137 and names a filed issue.

Round 2 is still open, and this run could not apply it. The GitHub integration returns 403 on updatePullRequest, on in-thread replies, and on issue comments, and the thread resolver rejects threads opened by macanderson. The two edits are:

1. In the body, replace "Whichever of the two lands second will fail empty-diff on the manifest and should close." with: "If #6550 lands first, this PR still carries the SCR-006 rewrite and must land; drop the manifest hunk or let the identical hunk merge clean. If this PR lands first, #6550 fails empty-diff and should close as superseded."
2. Point the residue section at #6554. Close #6555 as a duplicate of #6554, and add #6555's two extra definition-of-done lines to #6554: rg -n 'docs/scr' --hidden returns only historical records, and oxagen's scr-corpus-check reports no file under docs/scr/ in stella.

#6554 is already the one residue ticket for the corpus removal. No second ticket was opened.

  

_{Sent by Cursor Automation: Fix Review Comments & CI Failures}

[cursor]

No P0 or P1 on this pull request. CI on fbed89d0 is green, including Analyze (rust).

Round 1's four findings are fixed on this head. Round 2's two findings are the pull request body and the tracker. This run can resolve review threads. It cannot edit the pull request body, edit an issue, or close an issue: pull_requests=read, issues=read, and AddPullRequestReviewComment is forbidden for cursor[bot]. The notes on docs/manifest.json lines 762 and 763 are the edits those writes would have made.

No new residue issue. #6554 is the open issue for the docs/scr/ deletion, and #6555 duplicates it. No P1 remained after two review rounds.

  

_{Sent by Cursor Automation: Fix Review Comments & CI Failures}