feat(shapes): the practice is written where it is read, and the coverage line measures the slip (milestone 439 step 6)

- reusing-code: "Before the turn ends — say what you built" — the four
  verdicts, the one classify_shapes(repo=…) call, and the component file as a
  shape. Description names the end-of-turn moment.
- shape-accounting: the writer judges; audits are the check that it held.
  The write path SUGGESTS (no more hook instances); component file rows and
  whole-file canon described; scoped covers Svelte too.
- _INSTRUCTIONS reuse line: "before the turn ends, say what you built
  (create_snippet the reusable, classify_shapes the rest)" — 1570/1600.
- Coverage line: "written-shape check (7d): N turns checked, M asked, K left
  unjudged", from the Stop hook's recorded outcomes; silent until the
  question has been put.
- test_guidance_ownership pins the new topic on reusing-code.
- prior-art hook header no longer says it stamps instance rows.

Plugin version minted.

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

plugin/skills/shape-accounting/SKILL.md

@@ -18,8 +18,8 @@ row carries a status:
 - `exempt` — judged genuinely one-off. **Reason required.** A recorded
   judgment, not silence — it stops the next pass re-litigating it.
 - `scoped` — one-off **by construction**, stamped by the coverage sync
-  (a Vue component's scoped `<style>` rules and its `<script setup>`
-  functions — unreachable from any other file). Accounted for without a
+  (a Vue or Svelte component's own styles and instance-script functions —
+  unreachable from any other file). Accounted for without a
   judgment; still proposed against, grouped and flagged; any judgment you
   make overrides it. Not the todo.
 - `unclassified` — nobody has judged it yet. **This is the todo list.**
@@ -39,22 +39,32 @@ row carries a status:
    nothing. Rows, never prose — a consumer list in a note or verification
    detail cannot be sorted, queried, or diffed.
 
-## Rows that arrive on their own
+## The writer judges; audits check that it happened
 
-Two feeds keep the ledger current between your batches, so most shapes never
-need a hand judgment:
+The ledger is filled from your answers, given while you still know them. When
+a turn wrote definitions nobody has judged, the plugin's Stop hook lists them
+once — with whatever the machinery holds as evidence — and you classify them
+in one `classify_shapes(project_id, repo=…, …)` call (the `reusing-code` skill
+says what each verdict means). `repo` lets a verdict land on a shape the sync
+has not read yet. So a project worked this way stays accounted as it grows,
+and an audit pass is a CHECK that the reflex held — the coverage line names
+what slipped — not the way rows get classified.
+
+What still arrives without you:
 
 - **The sync** stamps a snippet's own reference location `canonical`
-  (`classified_by: mechanical`).
-- **The write path** stamps instances as you work: when you `get_snippet` a
-  canon and then write code that references or resembles it, the
-  definitions being written land as `instance` rows (`classified_by: hook`,
-  the evidence in `reason`), and the prior-art hint tells you what landed
-  ("Shape accounting: recorded at … → instance of #N"). Offered-but-unopened
-  snippets stamp nothing — so *pull the canon you are instantiating*; that
-  pull is what turns your reuse into accounting. A `hook` row is evidence, not
-  judgment: it never overrides a classification you made, and a
-  `classify_shapes` call overrides it.
+  (`classified_by: mechanical`) — including a component FILE row when the
+  snippet's location names the file and no symbol.
+- **The write path suggests**: when you `get_snippet` a canon and then write
+  code that references or resembles it, the shapes being written carry it as
+  a proposal, and the prior-art hint says "→ looks like #N". It is evidence
+  for your verdict, never a verdict — so *pull the canon you are
+  instantiating*; that pull is what puts it in front of you at the end of the
+  turn. Rows the hook stamped `instance` before it stopped doing so are listed
+  by `stamps_to_review` for judgment.
+- **A component is a row of its own** (`kind: "file"`, named by its stem): a
+  file that renders and defines nothing named after itself. It is judged like
+  any other shape.
 
 ## The machine proposes, judgment classifies