docs(agent): record deferred-scope closure discipline

[Sinity]

Summary

Records the close-time convention for deferred Bead scope and links the three historical deferred-scope successors to their closed source Beads.

Problem

Three closed campaign records deferred repair or verification scope without a structured successor edge. The successor work existed after later archaeology, but the relationship was not queryable from the original records.

Solution

Adds the convention to .agent/CONVENTIONS.md: create and link the successor before closing a Bead that defers acceptance, root-cause, or repair scope, then name it in the close reason. Adds related links for gysk3 to slshy, 8b10 to m73wk, and mvq8 to s8s54 in the authoritative Beads workspace. The rule remains a close-time judgment; it deliberately adds no prose-pattern lint.

Verification

• bd dep list polylogue-gysk3 --json, bd dep list polylogue-8b10 --json, and bd dep list polylogue-mvq8 --json each report the intended relates-to successor.
• devtools verify --quick completed successfully in 87.0s.
• Pre-push devtools verify --quick completed successfully in 40.3s.

Bead disposition

Bead	Status
polylogue-aagkt	Satisfied by the documented convention and three structured historical successor links.

Ref polylogue-aagkt.

[coderabbitai]

Important

• 🔍 Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 525d9221-a78c-4324-83c1-5f66072ed5f3

---

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