docs: require direct-main authorization evidence

[flyingrobots]

Summary

• requires direct-main exception records to cite explicit authorizer identity and authorization evidence
• updates the changelog entry for the existing direct-main exception procedure

Validation

• git diff --check
• pnpm exec markdownlint-cli2 CHANGELOG.md docs/procedures/DIRECT-MAIN-EXCEPTION-LOG.md
• cargo xtask lint-dead-refs --file CHANGELOG.md --file docs/procedures/DIRECT-MAIN-EXCEPTION-LOG.md

Summary by CodeRabbit

• Documentation
  • Updated direct-main exception procedures to require recording explicit authorizer identity and authorization evidence when documenting future exceptions.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: 1f4a027a-337e-47b6-970a-f05170020165

📥 Commits

Reviewing files that changed from the base of the PR and between 6c94fea and 68e1835.

📒 Files selected for processing (2)

• CHANGELOG.md
• docs/procedures/DIRECT-MAIN-EXCEPTION-LOG.md

---

📝 Walkthrough

Walkthrough

CHANGELOG.md and the direct-main exception procedure guide are updated to require recording explicit authorizer identity and supporting authorization evidence (issue link, PR comment, thread, or chat log reference) before approving docs-only direct pushes to main.

Changes

Authorization evidence documentation requirement

Layer / File(s)	Summary
Authorization evidence documentation requirement CHANGELOG.md, docs/procedures/DIRECT-MAIN-EXCEPTION-LOG.md	Procedure and changelog updated to mandate recording the named authorizer and specific authorization evidence (issue link, PR comment, thread, or chat log reference) for direct main exceptions.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

• flyingrobots/echo#340: Concurrent update to the same direct-main exception procedure documentation with matching authorizer and evidence requirements.

Poem

🔐 When pushing docs straight to main's holy gate,
Record who blessed it—don't leave it to fate.
Name the authorizer, link the decree,
Proof of approval, for all eyes to see. ✨

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'docs: require direct-main authorization evidence' directly summarizes the main change: adding a requirement for authorization evidence in direct-main exception records.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch stack/direct-main-authorization-evidence

---

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.}