feat(mcp): enter_project becomes a small primer: goal, recent work, open work, vocabulary (#4045)

The handshake carried the whole project record, every milestone's plan, full
rule text, the notes most recently edited and ~9k of design guidance. For
project 2 that was ~222k characters, past what an MCP client accepts as a tool
result. Each category was walked through with the operator and sized to what a
session needs on arrival; each names the call that has the rest.

- project: id, title, status and the full goal (session start's "full goal"
  pointer still lands here). get_project keeps the whole record.
- milestone_summary: the 5 most recently touched milestones, any status, most
  recent first, without plans. Summaries gain last_touched_at: the later of
  the milestone's own edit and its newest step update, from the query that
  already counts steps. milestone_summary_omitted counts the rest and points
  to list_milestones. get_project and list_milestones list every milestone,
  also without plans.
- open_tasks: the 10 most recently touched open tasks, with or without a
  milestone, each naming its milestone. list_notes gains sort="touched"
  (the later of updated_at and the newest work-log), because a log doesn't
  bump updated_at.
- recent_notes: dropped. Retrieval surfaces notes by relevance, and
  get_recent covers recency.
- systems: id and name.
- design_system: summary plus guidance_call. get_design_system gains
  resolved_guidance, the chain-merged prose; its own guidance field is only
  the departures, so session start's old pointer to it led to a fragment.
  The session start pointer and using-scribe's "Building UI" section now
  name resolved_guidance.
- rules: rules_payload(brief=True) gives project_rules as id and title plus
  subscribed_rulebooks, and records only what it shows. Retrieval delivers
  rules in full and ignores subscriptions (#4052). Other callers unchanged.
- pattern_coverage, inception and systems_bootstrap: unchanged.

Clients: the plugin's using-scribe skill, the compaction notice and session
start are updated here; the REST project summary only gains last_touched_at.
Plugin version minted.

Tests: a size ceiling on the handshake for a large project; milestone and
task selection and naming; brief rules; resolved_guidance; the session
start pointer; and a real-Postgres test that a work-log touches its task and
a step update touches its milestone.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01821k5B3Ysecp9fNYs92Kuy

src/scribe/mcp/tools/design_systems.py

@@ -108,14 +108,22 @@ async def get_design_system(design_system_id: int) -> dict:
     For what it actually resolves to once inheritance is applied, use
     `resolve_design_system`. The two answer different questions and a system
     that overrides nothing has an empty token list but a full resolved set.
+
+    `resolved_guidance` is the prose to build UI from: the guidance of every
+    system in the inheritance chain, outermost ancestor first, so the house
+    style comes before this system's departures from it. `design_system`'s
+    own `guidance` field is only the departures. Read `resolved_guidance`
+    before writing UI; enter_project carries just the summary (#4045).
     """
     uid = current_user_id()
     system = await ds_svc.get_design_system(uid, design_system_id)
     if system is None:
         raise ValueError(f"design system {design_system_id} not found")
     tokens = await ds_svc.list_tokens(uid, design_system_id)
+    context = await ds_svc.design_context(uid, design_system_id)
     return {
         "design_system": system.to_dict(),
+        "resolved_guidance": context["guidance"] if context else [],
         "tokens": [t.to_dict() for t in tokens],
     }