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

.claude/skills/alignment/SKILL.md

@@ -46,7 +46,7 @@ Review all changes in scope. If changes span multiple patterns below, apply all
    fix whitespace/formatting (trailing newlines etc.) — Prettier owns that.
 
 6. **Code Comments**: Comments should not duplicate what the code already says. Remove
-   parroting comments. Ensure comments capture non-obvious *why* — design decisions,
+   parroting comments. Ensure comments capture non-obvious _why_ — design decisions,
    constraints, gotchas. Flag missing comments where a reader would reasonably ask "why is this
    done this way?"
 
@@ -58,7 +58,7 @@ Review all changes in scope. If changes span multiple patterns below, apply all
 8. **Pre-existing & out-of-scope issues — leave a breadcrumb.** For anything you notice but
    don't fix (pre-existing patterns the new code follows; observations the change exposes but
    that are out of scope), mark it with a `// TODO:` at the relevant code site explaining
-   *what* could be improved and *why* (1–3 lines). **If an observation is important enough to
+   _what_ could be improved and _why_ (1–3 lines). **If an observation is important enough to
    mention in the summary, it is important enough to deserve a `// TODO:` at the code location**
    — otherwise the next reader has no way to recover the context.
 
@@ -104,25 +104,31 @@ Review all changes in scope. If changes span multiple patterns below, apply all
 ## Pattern A: New Functionality
 
 ### Testing
+
 - Unit tests for new `src/core/` logic (test the core hardest).
 - Lighter component/interaction tests for new UI.
 - Tests pass before proceeding.
 
 ### Documentation
+
 Update relevant docs if the feature is significant:
+
 - **`docs/spec/`** — if product behavior changed (this is a contract; change deliberately).
 - **`docs/architecture/`** — if a new pattern, navigation map, or decision rule emerged.
 - **`docs/IMPLEMENTATION-PLAN.md`** — mark milestone progress.
-Use the `/doc-update` skill for session-discovered gaps. The list is not exclusive.
+  Use the `/doc-update` skill for session-discovered gaps. The list is not exclusive.
 
 ### Dependencies
+
 If `package.json` changed:
+
 - Flag each new dependency; explain what it does and why it's needed.
 - Could a small custom implementation avoid it? Note the trade-off.
 - Prefer dependencies that solve genuinely hard problems (parsing, rendering) over those that
   save boilerplate.
 
 ### Alignment Check
+
 - **SOUL.md** — philosophy (must not violate without good reason).
 - **`docs/spec/`** — behavioral contract.
 - **`docs/architecture/`** — the relevant pattern doc.
@@ -132,14 +138,17 @@ If `package.json` changed:
 ## Pattern B: Bug Fixes
 
 ### Testing
+
 - Add a regression test that reproduces the bug and verifies the fix.
 - Interaction test if the bug affected UI behavior.
 
 ### Documentation
+
 Usually not required unless the bug revealed incorrect docs, or the fix changes documented
 (spec) behavior.
 
 ### Alignment Check
+
 - **SOUL.md** philosophy; **`docs/spec/`** behavioral contract; **`docs/architecture/`** patterns.
 
 ---
@@ -147,24 +156,29 @@ Usually not required unless the bug revealed incorrect docs, or the fix changes
 ## Pattern C: Refactoring
 
 ### Impact Analysis
+
 1. **Search for usages** of modified functions/types across the codebase (Grep).
 2. **Identify call sites** (components, stores, services, infrastructure, tests).
 3. **Check exports** used by other modules.
 4. **Review dependencies** — what the code depends on and what depends on it.
 
 ### Testing
+
 - Update existing tests to the new structure; verify all call sites.
 - Run `npm test` and `npm run typecheck`.
 
 ### Documentation
+
 Update `docs/architecture/` if a pattern, module responsibility, or navigation map changed.
 Update JSDoc/inline comments if signatures or behavior changed.
 
 ### Alignment Check
+
 - **SOUL.md** (simplicity, no parallel systems); **`docs/architecture/`** (consistent with the
   documented patterns); **`docs/spec/`** (behavior unchanged unless intended).
 
 ### Common Refactoring Checks
+
 - Function signatures → all call sites updated.
 - Type definitions → search type usages.
 - Imports → correct after file moves.
@@ -176,10 +190,10 @@ Update JSDoc/inline comments if signatures or behavior changed.
 
 ## Reference Documents
 
-| Document | Purpose |
-| --- | --- |
-| [SOUL.md](../../../SOUL.md) | Project philosophy and core values |
-| [AGENTS.md](../../../AGENTS.md) | AI onboarding and project context |
-| [docs/spec/](../../../docs/spec/) | Behavioral contract — *what* the app does |
-| [docs/architecture/](../../../docs/architecture/00-overview.md) | Architecture playbook — *how* it's built |
-| [docs/IMPLEMENTATION-PLAN.md](../../../docs/IMPLEMENTATION-PLAN.md) | Milestone sequence and scope |
+| Document                                                            | Purpose                                   |
+| ------------------------------------------------------------------- | ----------------------------------------- |
+| [SOUL.md](../../../SOUL.md)                                         | Project philosophy and core values        |
+| [AGENTS.md](../../../AGENTS.md)                                     | AI onboarding and project context         |
+| [docs/spec/](../../../docs/spec/)                                   | Behavioral contract — _what_ the app does |
+| [docs/architecture/](../../../docs/architecture/00-overview.md)     | Architecture playbook — _how_ it's built  |
+| [docs/IMPLEMENTATION-PLAN.md](../../../docs/IMPLEMENTATION-PLAN.md) | Milestone sequence and scope              |