feat(family): an idea links to the rule topic holding its norms - set_family_topic, the readouts name the rules, the idea row shows the link (milestone 463 step 1 gap, found in step 7, #4993)

Step 1 added family_ideas.topic_id but nothing could set it, so the note<->topic
link the milestone promised existed only as a column. set_family_topic links or
unlinks (0) a topic in a rulebook the caller owns, one idea per topic; the
version does not move. get_family_idea and get_family_adoption list the topic's
rules; list_family_ideas and the Family page name the topic. The model
docstrings no longer claim the topic's rules are platform-scoped in retrieval.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

plugin/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "scribe",
   "description": "Scribe for Claude Code: connects the scribe MCP server, adds the hooks that deliver live project state and relevant records at the right moment, ships the shared client-neutral Scribe skills (using-scribe, writing-plans, reporting-back, systematic-debugging, verification, brainstorming, reusing-code, shape-accounting, family-canon), and syncs your saved Scribe Processes as skills (/scribe:sync).",
-  "version": "2026.10.06.1726",
+  "version": "2026.10.06.1827",
   "author": {
     "name": "Bryan Van Deusen"
   },

plugin/skills/family-canon/SKILL.md

@@ -33,6 +33,9 @@ wrote what you wrote:
    needs support you can name; **one criterion with no support vetoes it**.
 3. Promote it, or leave it a candidate with the reason. A held candidate is
    precedent too, so the reason is the record — never skip writing it.
+4. If rules already bind the idea — a rule topic written for it — link that
+   topic with `set_family_topic`. The note teaches; the topic's rules bind,
+   and every assessment then reads them beside the idea.
 
 A milestone closing on a platform project hints without recording anything:
 ask whether what it built is something every project on the platform will