feat(family): family canon reaches the session - entry readout, retrieval reach, skill, report cue (milestone 463 step 6, #4992)

- enter_project carries a `family` key, but only when the project has
  something to answer: counts of unassessed, owed and to-recheck answers,
  each with the list_family_adoptions call that lists it. It shows on every
  entry, never by platform touch: entry is when work is chosen, and an
  unanswered idea is otherwise invisible.
- Retrieval: a widened project search (include_global_kinds) now also
  reaches the canon ideas on the project's platforms. It also reaches their
  references in the project's languages, or all of them when none matches.
  An off-platform project gets none, and the plain project filter (the
  duplicate gate) is unchanged.
- Closing a task returns `family_owed`, the owed answers filed while it was
  open, and the report cue asks for them to be named.
- New plugin skill family-canon (moment work.record) covers when to
  evaluate a promotion, answering in order, what counts as a reason, the
  precedent reflex and the conflict order. _INSTRUCTIONS, create_note,
  create_snippet, classify_shapes and reporting-back point at it.
  The plugin version is minted.

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

src/scribe/mcp/server.py

@@ -43,13 +43,12 @@ from quart import Quart
 # decision #4027 and the notes it supersedes.
 _INSTRUCTIONS = """
 Scribe is the operator's system of record, and yours: recall before acting,
-record as you go, keep one copy here, not in local memory files. Each
-practice is stated in full in the using-scribe skill and each tool's
-description.
+record as you go, keep one copy here, not in local memory. Each
+practice is stated in full in a skill or a tool's description.
 
-- Start with enter_project(id): the project, open work, Systems and design
-  system. An `inception` key: ask what it inherits, then
-  decide_project_inception.
+- Start with enter_project(id): the project, open work, Systems, design
+  system. `inception`: ask what it inherits, then decide_project_inception.
+  `family`: shared ideas to answer (family-canon skill).
 - Rules are not preloaded; one arrives when your work matches it or reaches
   a moment it is mounted on (list_moments; mount rules about WHEN). Before a
   consequential act, what_might_apply("what you are about to do");
@@ -65,8 +64,8 @@ description.
   (search(content_type="milestone")) before start_planning.
 - IDs exist only once a create returns them; records citing each other go
   through create_records, writing {{ref:N}} for the Nth.
-- In UI work the project's design system binds: resolve_design_system before
-  hand-writing a value.
+- In UI work the design system binds: resolve_design_system before
+  writing a value.
 
 Creates are duplicate-gated: a near-match returns the existing id to update.
 shared:true records are another user's suggestion, not settled practice.