Format entire codebase with Prettier (mechanical, no behavior change)

.claude/skills/doc-update/SKILL.md

@@ -18,7 +18,7 @@ Documentation serves two purposes — know **where to look** and know **what to
 are valuable, but at different levels of detail:
 
 - **Navigation map** (good): "Preview flow: `LivePreview.tsx` → `prepareSpecForRender()` (core) → `vega-embed`" — lists the files and their roles so you don't read a dozen files to find the right four.
-- **Decision rule** (good): "The fit-mode/reference-resolution transform runs on a *copy* of the spec — never mutate the stored spec" — captures a non-obvious convention.
+- **Decision rule** (good): "The fit-mode/reference-resolution transform runs on a _copy_ of the spec — never mutate the stored spec" — captures a non-obvious convention.
 - **Code walkthrough** (bad): "SnippetStore.updateDraft sets draftSpec, which a startup subscriber watches, debounces, then calls snippetStore.put… " — restates the code, goes stale on any rename.
 
 **Navigation maps** use file/module names (stable) to show flow direction. **Decision
@@ -30,13 +30,13 @@ For documentation organization, see **[CLAUDE.md](../../../CLAUDE.md)** and the
 
 ## The three documentation layers (know which one a gap belongs to)
 
-- **`docs/spec/`** — the *what*: behavioral contract (what the app does, acceptance points).
+- **`docs/spec/`** — the _what_: behavioral contract (what the app does, acceptance points).
   This is a **contract**. Only change it when product behavior genuinely changes, and do so
   deliberately — never as a casual "fill a doc gap" edit. A how-detail does NOT belong here.
-- **`docs/architecture/`** — the *how*: the patterns behind each layer (state, persistence,
+- **`docs/architecture/`** — the _how_: the patterns behind each layer (state, persistence,
   modals, routing, rendering, inference, relationships). Most navigation maps and decision
   rules land here.
-- **`docs/IMPLEMENTATION-PLAN.md`** — the *when*: milestone sequence and scope.
+- **`docs/IMPLEMENTATION-PLAN.md`** — the _when_: milestone sequence and scope.
 
 ## Process
 
@@ -59,19 +59,19 @@ not do Y"). If you can't state it concisely, it may be too implementation-specif
 
 Map each gap to the right document:
 
-| Gap type | Target document |
-| --- | --- |
+| Gap type                                          | Target document                                                               |
+| ------------------------------------------------- | ----------------------------------------------------------------------------- |
 | Product behavior, capabilities, acceptance points | `docs/spec/` (the relevant 00–10 section) — **contract; change deliberately** |
-| State / Zustand stores | `docs/architecture/01-state-and-stores.md` |
-| Persistence, IndexedDB, localStorage, migrations | `docs/architecture/02-persistence.md` |
-| Modals, dialog lifecycle | `docs/architecture/03-modal-system.md` |
-| URL routing, keyboard/events | `docs/architecture/04-routing-and-events.md` |
-| Rendering, theming, vega-embed, preview | `docs/architecture/05-rendering-theming-preview.md` |
-| Type inference, dataset profiling | `docs/architecture/06-type-inference.md` |
-| Names, snippet↔dataset links, rename propagation | `docs/architecture/07-naming-and-relationships.md` |
-| Milestone scope, build order | `docs/IMPLEMENTATION-PLAN.md` |
-| Project philosophy / identity | `SOUL.md` |
-| Onboarding, conventions, stack | `AGENTS.md` / `CLAUDE.md` |
+| State / Zustand stores                            | `docs/architecture/01-state-and-stores.md`                                    |
+| Persistence, IndexedDB, localStorage, migrations  | `docs/architecture/02-persistence.md`                                         |
+| Modals, dialog lifecycle                          | `docs/architecture/03-modal-system.md`                                        |
+| URL routing, keyboard/events                      | `docs/architecture/04-routing-and-events.md`                                  |
+| Rendering, theming, vega-embed, preview           | `docs/architecture/05-rendering-theming-preview.md`                           |
+| Type inference, dataset profiling                 | `docs/architecture/06-type-inference.md`                                      |
+| Names, snippet↔dataset links, rename propagation  | `docs/architecture/07-naming-and-relationships.md`                            |
+| Milestone scope, build order                      | `docs/IMPLEMENTATION-PLAN.md`                                                 |
+| Project philosophy / identity                     | `SOUL.md`                                                                     |
+| Onboarding, conventions, stack                    | `AGENTS.md` / `CLAUDE.md`                                                     |
 
 If a gap fits no existing document, consider a new section in the closest one; prefer
 extending over creating. A brand-new architecture topic can become `docs/architecture/08-*.md`