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

docs/spec/05-datasets.md

@@ -7,13 +7,13 @@ The **Dataset Manager** is a modal for creating and managing named, reusable dat
 Datasets are named blobs of data stored in the user's local library, independent of any single snippet. A snippet references a dataset by name rather than embedding the data inline, so the same data can power many snippets and be edited in one place.
 
 - Datasets persist locally across sessions in a high-capacity local store, far larger than the budget available to snippets — large datasets belong here, not inline in specs.
-- A snippet references a dataset using a Vega-Lite named-data reference, e.g. `{ "data": { "name": "MyDataset" } }`. When the *Live Preview* renders a spec, it resolves any such named reference against the dataset library (see *Live Preview*).
-- See *Data Model* for the stored shape of a dataset.
+- A snippet references a dataset using a Vega-Lite named-data reference, e.g. `{ "data": { "name": "MyDataset" } }`. When the _Live Preview_ renders a spec, it resolves any such named reference against the dataset library (see _Live Preview_).
+- See _Data Model_ for the stored shape of a dataset.
 
 ## Opening & Navigation
 
 - Opened from a header control or via the keyboard shortcut Cmd/Ctrl+K.
-- The current view and the selected dataset are reflected in the URL, so a selected dataset produces a shareable/back-navigable location (see *Application Shell & Navigation*).
+- The current view and the selected dataset are reflected in the URL, so a selected dataset produces a shareable/back-navigable location (see _Application Shell & Navigation_).
 - Closing the modal clears the current selection and any open create form.
 
 ## Layout
@@ -38,7 +38,7 @@ Clicking an item selects it and shows its detail. Per-item actions (delete, plus
 A dataset has one of two source types, chosen when creating it:
 
 - **Inline** — the data itself is pasted in and stored directly in the library.
-- **URL** — the dataset stores a remote URL (http/https). The data is not copied locally; it is fetched on demand when a referencing spec is rendered (see *Live Preview*).
+- **URL** — the dataset stores a remote URL (http/https). The data is not copied locally; it is fetched on demand when a referencing spec is rendered (see _Live Preview_).
 
 For inline datasets the library holds the full data and can profile it. For URL datasets the library holds only the link, so row/column/size figures are typically not computed up front and show as "N/A".
 
@@ -80,7 +80,7 @@ The detail pane for a selected dataset shows:
 - **Comment** (optional free-text notes), when present.
 - **Overview**: statistics (rows, columns, size), the **column list** with each column's name and inferred type shown with a simple type indicator, and created/modified timestamps.
 - **Preview**: a truncated rendering of the data (raw text for CSV/TSV/URL, pretty-printed for JSON/TopoJSON).
-- **Linked Snippets**: the list of snippets that reference this dataset by name. This is the dataset side of bidirectional dataset↔snippet linking (see *Snippet Library*).
+- **Linked Snippets**: the list of snippets that reference this dataset by name. This is the dataset side of bidirectional dataset↔snippet linking (see _Snippet Library_).
 
 ## Actions
 
@@ -94,14 +94,14 @@ Each action raises a confirming toast (or an error toast on failure).
 
 ## Build Chart From Dataset
 
-From a selected dataset the user can launch the visual *Chart Builder* (see *Chart Builder*) pre-targeted at that dataset, producing a new snippet whose spec references the dataset by name.
+From a selected dataset the user can launch the visual _Chart Builder_ (see _Chart Builder_) pre-targeted at that dataset, producing a new snippet whose spec references the dataset by name.
 
 ## Extract Inline Data → Dataset
 
-The reverse flow starts in the editor: a user can extract inline `data.values` out of a spec into a new named dataset (see *Spec Editor & Draft/Published Workflow*). The result appears here as a new dataset, and the originating snippet's spec is rewritten to reference it by name.
+The reverse flow starts in the editor: a user can extract inline `data.values` out of a spec into a new named dataset (see _Spec Editor & Draft/Published Workflow_). The result appears here as a new dataset, and the originating snippet's spec is rewritten to reference it by name.
 
 ## Naming & Uniqueness
 
 - Dataset names must be **unique**. Attempting to create a dataset with a name already in use is rejected with an error toast.
-- During bulk operations such as import, conflicting names are automatically suffixed to remain unique rather than overwriting existing datasets (see *Import & Export*).
+- During bulk operations such as import, conflicting names are automatically suffixed to remain unique rather than overwriting existing datasets (see _Import & Export_).
 - Renaming a dataset that is referenced by snippets keeps references consistent by updating the matching named-data references in affected specs.