docs(dev-cycle): require linked bicameral decision on org-member PRs

[jinhongkuan]

Summary

• Adds a ## Linked decisions section to the §4.3 PR body template, parallel to ## Linked issues.
• Codifies the rule: every PR authored by a BicameralAI org member references at least one decision:<surrealdb-id>.
• External contributors are exempt — the shepherding maintainer ingests the decision on their behalf at merge time.

Why

The PR body already tells reviewers what changed and which issue it closes; the bicameral ledger tells us which decision it satisfies. Today the link between the two is implicit (a reviewer either knows the decision exists or they don't). Making it explicit:

• Forces the author to verify the change actually traces to an ingested decision before opening the PR (catches "drift via PR" — code that lands ahead of the decision-of-record).
• Gives reviewers a concrete artifact to verify against, alongside the linked issue.
• Closes the loop with bicameral.preflight — preflight surfaces the decision; the PR cites it; the post-commit sync resolves compliance against it.

External contributors are exempt because bicameral access is org-internal. Gating community PRs on internal tooling is the wrong tradeoff; a maintainer ingesting on their behalf at merge time keeps the audit trail intact without exporting our internal substrate.

Linked issues

(none — this is a process change that doesn't close a specific issue)

Linked decisions

(meta: this PR's own linked-decision section is empty by intent — the decision codified here was made in conversation today and ingestion is blocked by an unrelated MCP-server outage on the dev box. Will ingest + back-link in a follow-up comment once the MCP server is restored.)

Plan / Audit / Seal

• Plan: trivial; risk:L1 (doc-only rule addition, no CI enforcement yet)

Test plan

• Visual review of docs/DEV_CYCLE.md §4.3 diff — template renders correctly in GitHub markdown.
• No code paths touched; existing CI suites are sufficient.

Out of scope

• CI lint that enforces a decision:<id> token in org-member PR bodies. Worth doing if compliance slips, but the doctrine update lands first so reviewers can hold the line manually.
• Updating the GitHub PR template (.github/pull_request_template.md) — that file doesn't exist yet; if/when it's added, mirror the §4.3 template.

🤖 Generated with Claude Code

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: befa8013-f6a4-42b2-8fa7-04ca32ff3457

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch docs/dev-cycle-require-linked-decision

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}