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

docs/architecture/07-naming-and-relationships.md

@@ -10,7 +10,7 @@ Two concerns live here, and they reinforce each other:
    key users see and the key snippets reference, so duplicates would be
    ambiguous. We reject duplicate names on create/rename, and auto-suffix
    collisions during bulk import.
-2. **Relationship tracking** — a snippet references datasets *by name* through
+2. **Relationship tracking** — a snippet references datasets _by name_ through
    its `datasetRefs: string[]` field. This is a bidirectional, name-based link:
    from a snippet you read its refs; from a dataset you scan snippets to find
    who uses it. Renaming a dataset must propagate to every snippet that points
@@ -25,7 +25,7 @@ read and mutate stores live in `src/app/services/`.
 
 Datasets carry a numeric `id`, but snippets reference them **by name** because
 that is what Vega-Lite uses: a spec resolves data through a named-data
-reference, `{ "data": { "name": "MyDataset" } }`. The name *is* the contract
+reference, `{ "data": { "name": "MyDataset" } }`. The name _is_ the contract
 between a spec and the dataset library. Storing a numeric id in the spec would
 mean the spec is no longer a standalone, paste-anywhere Vega-Lite document.
 
@@ -122,7 +122,7 @@ export function makeUniqueName(desired: string, existingNames: Iterable<string>)
 
 - **Forward** (snippet → datasets): read `snippet.datasetRefs`. Cheap, stored.
 - **Reverse** (dataset → snippets): there is no stored back-pointer. We compute
-  it by scanning snippets. Keeping it *derived* means it can never disagree with
+  it by scanning snippets. Keeping it _derived_ means it can never disagree with
   the forward links — there is one source of truth.
 
 `datasetRefs` is **derived from the spec**, not hand-maintained. It is
@@ -216,9 +216,9 @@ import type { Snippet } from '../../core/types';
 /** Snippets whose datasetRefs include `name` (case-insensitive). */
 export function findSnippetsReferencingDataset(name: string): Snippet[] {
   const lower = name.toLowerCase();
-  return useSnippetStore.getState().snippets.filter((s) =>
-    s.datasetRefs.some((ref) => ref.toLowerCase() === lower),
-  );
+  return useSnippetStore
+    .getState()
+    .snippets.filter((s) => s.datasetRefs.some((ref) => ref.toLowerCase() === lower));
 }
 
 /** Count for the usage badge. */
@@ -240,7 +240,7 @@ they update the moment any snippet is published with changed refs.
 **Don't**
 
 - Don't add a `referencedBy` array to datasets. A stored reverse pointer is a
-  second source of truth that *will* fall out of sync with `datasetRefs`.
+  second source of truth that _will_ fall out of sync with `datasetRefs`.
 
 ---
 
@@ -249,7 +249,7 @@ they update the moment any snippet is published with changed refs.
 On import we never overwrite an existing dataset. A dataset whose name collides
 is renamed to a unique name via `makeUniqueName`, and **every rename is
 collected and reported to the user** (toast / summary) so the change is never
-silent. Crucially, names are reserved *as we go* — within a single import, two
+silent. Crucially, names are reserved _as we go_ — within a single import, two
 incoming `Sales` datasets become `Sales 2` and `Sales 3`, not two `Sales 2`.
 
 ```ts
@@ -292,7 +292,7 @@ export function dedupeIncomingDatasetNames(
 
 **Do**
 
-- Reserve each chosen name immediately so collisions *within* one import are
+- Reserve each chosen name immediately so collisions _within_ one import are
   also resolved.
 - Return the rename list and show it; a silent rename looks like data loss.
 
@@ -331,7 +331,8 @@ export function renameDatasetInSpec(spec: Json, oldName: string, newName: string
       for (const [k, v] of Object.entries(node as Record<string, Json>)) {
         if (
           k === 'data' &&
-          v && typeof v === 'object' &&
+          v &&
+          typeof v === 'object' &&
           (v as Record<string, Json>).name === oldName
         ) {
           out[k] = { ...(v as object), name: newName };
@@ -416,17 +417,17 @@ export function renameDatasetEverywhere(oldName: string, newName: string): { upd
 
 ## 7. Where things live
 
-| Concern | Location | Pure? | Tested |
-|---|---|---|---|
-| `makeUniqueName`, `isNameTaken` | `src/core/naming.ts` | yes | unit |
-| `extractDatasetRefs`, `recomputeDatasetRefs` | `src/core/spec-refs.ts` | yes | unit |
-| `renameDatasetInSpec` | `src/core/spec-refs.ts` | yes | unit |
-| `findSnippetsReferencingDataset`, usage count | `src/app/services/RelationshipService.ts` | no (reads store) | integration |
-| `renameDatasetEverywhere` | `src/app/services/RelationshipService.ts` | no (mutates stores) | integration |
-| `dedupeIncomingDatasetNames` | `src/app/services/ImportService.ts` | nearly (uses `makeUniqueName`) | unit/integration |
+| Concern                                       | Location                                  | Pure?                          | Tested           |
+| --------------------------------------------- | ----------------------------------------- | ------------------------------ | ---------------- |
+| `makeUniqueName`, `isNameTaken`               | `src/core/naming.ts`                      | yes                            | unit             |
+| `extractDatasetRefs`, `recomputeDatasetRefs`  | `src/core/spec-refs.ts`                   | yes                            | unit             |
+| `renameDatasetInSpec`                         | `src/core/spec-refs.ts`                   | yes                            | unit             |
+| `findSnippetsReferencingDataset`, usage count | `src/app/services/RelationshipService.ts` | no (reads store)               | integration      |
+| `renameDatasetEverywhere`                     | `src/app/services/RelationshipService.ts` | no (mutates stores)            | integration      |
+| `dedupeIncomingDatasetNames`                  | `src/app/services/ImportService.ts`       | nearly (uses `makeUniqueName`) | unit/integration |
 
 The dividing line: anything that takes plain data and returns plain data is
 **core** and unit-tested in isolation; anything that reaches into a Zustand store
-is an **app service**. The rename rule of thumb — *the spec is the source of
-truth, `datasetRefs` mirrors it, the reverse lookup is derived* — is what keeps
+is an **app service**. The rename rule of thumb — _the spec is the source of
+truth, `datasetRefs` mirrors it, the reverse lookup is derived_ — is what keeps
 the bidirectional link from ever needing manual repair.