tileflow 0.1.0-alpha.18 → 0.1.0-alpha.19

package/README.md

@@ -59,9 +59,6 @@ for reproducible evidence, and `compare` for saved captures, semantic edits, sty
 baselines. `preview` opens Inspector. These tools work in independent projects with
 custom maps and data; official maps are optional.
 
-See the [map authoring workflow](https://github.com/tileflow/tileflow-sdk/blob/main/packages/cli/docs/map-authoring.md)
-for command examples, bounded JSON queries, compatible aliases and efficient agent workflows.
-
 ## Preview and compare
 
 `preview` binds to `127.0.0.1` by default. `--host` explicitly accepts an IP literal or `localhost`;
@@ -111,9 +108,7 @@ npx tileflow inspect session --url http://127.0.0.1:3333 --json
 ```
 
 Use the origin printed by your running preview. This reads browser observations, including their
-age and stale flag; exact source lines and token ownership are not inferred. See the
-[Inspector workflow](https://github.com/tileflow/tileflow-sdk/blob/main/packages/cli/docs/map-authoring.md#work-with-a-person-and-an-agent)
-for storage and context bounds.
+age and stale flag; exact source lines and token ownership are not inferred.
 
 `--api-base-url` or `TILEFLOW_API_URL` changes the API origin used by the official preview sources.
 It does not change the map's authored data ownership or publish any data.
@@ -122,8 +117,6 @@ It does not change the map's authored data ownership or publish any data.
 
 Captures return reusable IDs. Compare two saved renders with
 `tileflow compare --before <id> --after <id> --json`; no config, browser, or network is needed.
-The [authoring workflow](https://github.com/tileflow/tileflow-sdk/blob/main/packages/cli/docs/map-authoring.md)
-describes storage, integrity checks, mismatch outcomes and watch-session reuse.
 
 Add a concrete-theme scene to `tileflow.config.ts`:
 
@@ -176,7 +169,7 @@ Do not run a separate `tileflow preview` server beside the application.
 
 ## Render a timed shot
 
-Commit a [capture shot](https://github.com/tileflow/tileflow-sdk/blob/main/packages/core/docs/capture-shots.md)
+Commit a capture shot
 under `shots` on the same map: a concrete theme, a viewport, and two or more center-camera
 keyframes, optionally with a theme blend. Then render it:
 
@@ -209,8 +202,7 @@ receipt. Use `visual compare` for an authenticated two-style review with matched
 renderer, and data identity. Neither operation approves a baseline. Capture watch mode emits NDJSON
 generation events rather than a single JSON document.
 
-The [capture contract](https://github.com/tileflow/tileflow-sdk/blob/main/docs/contracts/local-visual-capture.md)
-documents readiness, receipts, comparison limits, and CLI output formats.
+Use `tileflow capture --help` and `tileflow compare --help` for installed command options.
 
 ## Publish data and deploy a map
 
@@ -316,26 +308,10 @@ Missing fonts or sprites require the complete prepared output. Hosted compatibil
 be fixed before authentication or upload, not bypassed with repeated deployment attempts.
 
 See [deployment documentation](https://tileflow.dev/docs/deploy),
-[SDK responsibility boundaries](https://github.com/tileflow/tileflow-sdk/blob/main/docs/contracts/sdk-responsibilities.md),
+[SDK responsibility boundaries](https://github.com/tileflow/tileflow-sdk/blob/main/README.md),
 and [issues](https://github.com/tileflow/tileflow-sdk/issues). Source `main` may be newer than npm;
 use the installed CLI's help and generated contracts for that release.
 
-## Detailed guides
-
-These guides are also included in the installed package under `docs/`. They describe this source
-revision; prefer the installed copy when working with an older release.
-
-- [CLI setup and defaults](https://github.com/tileflow/tileflow-sdk/blob/main/packages/cli/docs/cli-setup-and-defaults.md)
-- [Build artifacts](https://github.com/tileflow/tileflow-sdk/blob/main/packages/cli/docs/build-artifacts.md)
-- [Deterministic agent diagnostics](https://github.com/tileflow/tileflow-sdk/blob/main/packages/cli/docs/deterministic-agent-diagnostics.md)
-- [Coordinates](https://github.com/tileflow/tileflow-sdk/blob/main/packages/cli/docs/coordinates.md)
-- [Command families](https://github.com/tileflow/tileflow-sdk/blob/main/packages/cli/docs/command-families.md)
-- [Local visual feedback](https://github.com/tileflow/tileflow-sdk/blob/main/packages/cli/docs/local-visual-feedback.md)
-- [Inspect vector features](https://github.com/tileflow/tileflow-sdk/blob/main/packages/cli/docs/inspect-vector-features.md)
-- [Hosted authentication and deploy](https://github.com/tileflow/tileflow-sdk/blob/main/packages/cli/docs/hosted-authentication-and-deploy.md)
-- [Agent icon composition](https://github.com/tileflow/tileflow-sdk/blob/main/packages/cli/docs/agent-icon-composition.md)
-- [Read-only icon comparison](https://github.com/tileflow/tileflow-sdk/blob/main/packages/cli/docs/read-only-icon-comparison.md)
-
 ## Validate icon representations
 
 `tileflow validate`, development and build resolve icon capabilities before returning a map.
@@ -348,4 +324,4 @@ reports the invalid generation while retaining its last valid artifact.
 
 Declare defaults in `tileflow.icons.json`; inspect effective appearances and text-fitting layouts with
 `tileflow icons list --json`. Diff reports detect default-only changes and show rendered previews.
-See [Author recolorable and adaptable icons](https://github.com/tileflow/tileflow-sdk/blob/main/packages/dev/docs/native-icons.md) for the source profile and halo bounds.
+See [Author recolorable and adaptable icons](https://github.com/tileflow/tileflow-sdk/blob/main/packages/dev/README.md) for the source profile and halo bounds.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "tileflow",
-  "version": "0.1.0-alpha.18",
+  "version": "0.1.0-alpha.19",
   "license": "Apache-2.0",
   "description": "CLI-only tools for Tileflow config, capture, visual testing, and deploy.",
   "type": "module",
@@ -25,7 +25,6 @@
   },
   "files": [
     "dist",
-    "docs",
     "LICENSE"
   ],
   "bin": {
@@ -36,16 +35,16 @@
   },
   "dependencies": {
     "@hono/node-server": "2.1.3",
-    "@tileflow/capture": ">=0.1.0-alpha.35 <0.1.0-beta.0",
-    "@tileflow/coordinates": ">=0.1.0-alpha.2 <0.1.0-beta.0",
-    "@tileflow/coordinates-runtime": ">=0.1.0-alpha.5 <0.1.0-beta.0",
-    "@tileflow/core": ">=0.1.0-alpha.41 <0.1.0-beta.0",
-    "@tileflow/dev": ">=0.1.0-alpha.38 <0.1.0-beta.0",
-    "@tileflow/maps": ">=0.1.0-alpha.15 <0.1.0-beta.0",
+    "@tileflow/capture": ">=0.1.0-alpha.36 <0.1.0-beta.0",
+    "@tileflow/coordinates": ">=0.1.0-alpha.3 <0.1.0-beta.0",
+    "@tileflow/coordinates-runtime": ">=0.1.0-alpha.6 <0.1.0-beta.0",
+    "@tileflow/core": ">=0.1.0-alpha.43 <0.1.0-beta.0",
+    "@tileflow/dev": ">=0.1.0-alpha.39 <0.1.0-beta.0",
+    "@tileflow/maps": ">=0.1.0-alpha.17 <0.1.0-beta.0",
     "commander": "^15.0.0",
-    "hono": "4.13.13",
+    "hono": "4.13.14",
     "picocolors": "^1.1.1",
-    "zod": "^4.4.3"
+    "zod": "^4.6.7"
   },
   "devDependencies": {
     "@types/pngjs": "6.0.5",

package/docs/agent-icon-composition.md

@@ -1,68 +0,0 @@
-# Agent icon composition
-
-Start with the [tileflow guide](https://github.com/tileflow/tileflow-sdk/blob/main/packages/cli/README.md) for installation and a complete first example.
-
-List the effective local catalog used by the exported map:
-
-```sh
-npx tileflow icons list --json
-```
-
-The successful stdout contract is one deterministic JSON document followed by exactly one newline.
-Its top-level fields, in order, are `schemaVersion: 3`, `pathBase: "cwd"`, and `maps`.
-Schema version 3 is a compatibility boundary: removing or renaming a field or changing an enum's
-meaning requires a new schema version. Additive optional fields require corresponding documentation
-and tests. It replaces version 2's directory-only shape so a locked `iconSet('@team/set')`
-contributor can be represented without inventing a local path.
-
-Each sorted map entry has one `id` and an `icons` value. `icons.kind` is `none` for `icons: []`, or
-`sources` for a prepared ordered composition. A `sources` entry contains:
-
-- `contributors`, in the exact left-to-right authoring order. Each has a `kind` of `local`,
-  `package` or `icon-set`, a `label` (a config-relative path, a safe `npm:<package>/<path>`
-  descriptor, or the canonical `@team/set` reference) and the `iconIds` it declares. Filesystem
-  contributors also report `insideWorkingTree`; shared contributors report their exact locked
-  `reference` and integer `version`.
-- `finalIds`, the sorted canonical lower-kebab IDs in the resulting sprite;
-- `replacements`, naming the replaced and winning contributor export for every later exact-ID
-  replacement, by authored file for filesystem contributors and by `@team/set` for shared ones;
-- `sources`, one entry for each winning ID. A `file` entry carries the cwd-relative `path`, format,
-  byte length and intrinsic dimensions; an `icon-set` entry carries the exact `reference` and
-  `version` and deliberately has no path, because a shared revision publishes verified generated
-  cells rather than original artwork. Both carry the winning `contributor` ordinal.
-- `composition`, the exact ordered receipt when the map declares a shared set, and `null`
-  otherwise. It uses `tileflow-icon-composition-v2` when an effective winner has SDF appearance
-  or stretch/content layout; metadata-free compositions retain v1;
-- optional `appearances` and `layouts`, keyed by effective icon ID; and
-- `insideWorkingTree` and the deterministic generated `packageHash`.
-
-Listing reads the exact `tileflow.icons.lock.json` beside the selected config. It never resolves a
-catalog head, so a newly published revision does not change this output until `tileflow icons
-install`, `update` or `pin` changes the lock. `--cache-dir` selects the verified artifact cache root
-and `--offline` fails a cache miss instead of hydrating it.
-
-There is deliberately no parallel catalog registry, provider kind, semantic mapping, external
-sprite branch, or arbitrary source-to-runtime renaming. `<id>.<ext>` publishes `<id>` and the
-reserved pattern form `<id>.pattern.<ext>` also publishes `<id>`. This lets an
-agent answer “which directory wins this icon?” directly from one map record without reconstructing
-hidden provider state. Use `--map <id>` to select one exact map when internal orchestration supplies
-more than one.
-
-All reported paths are relative to the invocation working directory. A source outside that tree
-uses `../` and `insideWorkingTree: false`; no absolute path is emitted. Listing follows local
-authoring semantics. Run `npx tileflow validate --target hosted` separately before a
-hosted deploy to check containment, portable IDs, SVG safety, and hosted limits.
-
-The Tileflow command performs no authentication or browser/server launch and never writes config,
-repository locks or frontend manifests. A cold cache can download and store the exact public
-sprite artifacts. It performs no network request when every locked artifact is already in the
-verified cache, and `--offline` forbids hydration entirely. `--json` is required; use `--config`
-(or `-c`) to select another config file. It removes an ambient `TILEFLOW_API_KEY` before importing config. As with every config-aware
-command, loading `tileflow.config.ts` executes repository code and is not a sandbox; side effects in
-that code remain the repository's responsibility. Success emits no ANSI or progress prose. Usage,
-config, source, decode, and render failures exit 1, write diagnostics to stderr, and leave stdout
-empty.
-
-The output contains no source contents or source hash, rendered cells, atlas coordinates,
-image/base64 payload, credential, timestamp, random value, or absolute path. Open a reported local
-source path with normal repository tools only when the pixels themselves are needed.

package/docs/build-artifacts.md

@@ -1,40 +0,0 @@
-# Build artifacts
-
-Start with the [tileflow guide](https://github.com/tileflow/tileflow-sdk/blob/main/packages/cli/README.md) for installation and a complete first example.
-
-`tileflow build` resolves the exported map lineage, validates executable config and MapLibre
-semantics, compiles its ordered package/local icon directories and selected text provider, and
-writes `manifest.json`, one `styles/<map>/<theme>.json` per concrete appearance, and every referenced
-sprite/font asset. The manifest records `defaultTheme`, optional `systemThemes`, and the exact theme
-catalog; it never flattens a default into a second style alias. A
-map with text has exactly one provider: local/package `fonts` directories or a `glyphs` descriptor
-whose `fontStacks` are explicit. The default output is `dist/tileflow`; choose another directory
-explicitly with `--out`:
-
-```sh
-npx tileflow build --out public/tileflow
-```
-
-Named hosted sources with `local` archives are for account-free validation, development, preview,
-and capture. `tileflow build` rejects them instead of copying, publishing, or taking ownership of
-user data. For production, either publish managed data explicitly with `tileset publish` or serve
-it from infrastructure owned by the application. A local declaration never selects either path
-implicitly.
-
-Preview, capture, and the React/Vue/Svelte adapters register Tileflow's local PMTiles protocol
-before MapLibre reads the compiled Style. Its URL is stable by logical tileset ID; physical local
-snapshot generations do not change Style identity. Standalone Capture retains one snapshot for the
-render. Application Capture uses the application's server; Tileflow's local handler provides
-immutable, ETag-guarded PMTiles reads, but does not freeze every local dataset for the complete
-screenshot window.
-
-Build is local and credential-free. Hosted compatibility is a separate
-`tileflow validate --target hosted` preflight. Primary map data must remain Tileflow World; named
-Team sources are validated and resolved independently.
-
-## Choose an artifact renderer
-
-`validate` and `build` accept `--renderer web|native`; omission preserves the web pipeline and its
-bytes. Native artifacts use a separate `native/` output directory and do not establish a running
-mobile SDK. See [native artifact validation and output](native-artifacts.md) for the target matrix,
-JSON diagnostics, prepared fonts and explicit limitations.

package/docs/cli-setup-and-defaults.md

@@ -1,56 +0,0 @@
-# CLI setup and defaults
-
-Start with the [tileflow guide](https://github.com/tileflow/tileflow-sdk/blob/main/packages/cli/README.md) for installation and a complete first example.
-
-CLI-only tools for Tileflow config, preview, validation, capture, and hosted deploy. The package
-requires Node.js 22 or newer and intentionally exposes only the `tileflow` binary; importing
-`tileflow` as a JavaScript library is not a supported surface.
-
-Local config, validation, build, preview, and hosted-compatibility checks require
-no Tileflow account or API key:
-
-```sh
-npm install @tileflow/core@alpha @tileflow/maps@alpha
-npm install --save-dev --save-exact tileflow@alpha
-npx tileflow init
-npx tileflow validate
-npx tileflow validate --target hosted
-npx tileflow build
-npx tileflow preview
-```
-
-The generated config imports `streets`, extends it, materializes a custom dark theme from
-`streetsThemes.dark`, and declares the starter's theme family, modules, and view. Streets already
-owns its complete icon and glyph providers, so the leaf does not repeat font stacks or know a
-delivery URL.
-
-Install the exact project dependency first; then `npx tileflow` runs its local executable. Other
-package managers work; use the equivalent command for the lockfile already owned by the project.
-
-`tileflow preview` previews the map exported by `tileflow.config.ts` and uses its configured `view`.
-Select one of that map's committed standalone scenes explicitly:
-
-```sh
-npx tileflow preview --scene madrid-mobile
-```
-
-To work on another map, point `--config` at another singular config. Multi-map catalogs are internal
-orchestration used by this repository's workbench and are not a second public config shape.
-
-The `preview` name distinguishes this SDK preview server from an application's own `npm run dev`
-process.
-
-`--api-base-url` selects the origin used by official World, Bathymetry vector, Bathymetry DEM,
-Nautical, and terrain TileJSON sources in the generated preview style. In particular, a hybrid
-Bathymetry map resolves `/tiles/bathymetry/tiles.json` and `/tiles/bathymetry/dem/tiles.json` from
-that one origin. `TILEFLOW_API_URL` supplies the same value when the flag is omitted, which lets a
-local tiles stack serve all sidecars without changing map authoring.
-
-The preview binds only `127.0.0.1` by default. Network exposure is never implicit. To bind another
-interface, pass one explicit IP literal (or `localhost`) with `--host`, for example
-`tileflow preview --host 192.0.2.10`. URL-, path-, and hostname-shaped values are rejected.
-
-A map preview accepts `--theme <concrete-name>`; omission selects its declared default. A scene
-preview applies its committed concrete theme, camera, and CSS viewport dimensions. Capture remains the
-authority for exact DPR and pixels. Scenes whose target is an application must be viewed through
-that application's normal development server.

package/docs/command-families.md

@@ -1,36 +0,0 @@
-# Command families
-
-Start with the [tileflow guide](https://github.com/tileflow/tileflow-sdk/blob/main/packages/cli/README.md) for installation and a complete first example.
-
-| Family            | Commands                                                                                       |
-| ----------------- | ---------------------------------------------------------------------------------------------- |
-| Semantic language | `language manifest`, `language schema`                                                         |
-| Map authoring     | `init`, `validate`, `inspect`, `explain`, `semantic-diff`, `build`, `preview`                  |
-| Local evidence    | `setup capture`, `capture`, `visual compare`, `visual analyze`, `visual diff`, `visual update` |
-| Data and assets   | `tileset inspect`, `tileset publish/list/status/purge`, `inspect features`, `icons list/diff`  |
-| Team Icon Sets    | `icon-set publish/list/status/versions/uses/archive/unarchive/purge`                           |
-| Team 3D models    | `models publish/list/status/restore/purge`                                                     |
-| Repository locks  | `icons install`, `icons update`, `icons pin`                                                   |
-| Account           | `login`, `logout`, `whoami`                                                                    |
-| Hosted delivery   | `deploy`, `status`                                                                             |
-
-Run `tileflow <command> --help` (or the family help, such as `tileflow icons --help`) for the exact
-arguments and bounded JSON modes. `preview` defaults to the existing web renderer. The explicit
-`preview --renderer native` mode serves watched `native-v1` artifacts only;
-Metro remains the React Native JavaScript development server. See
-[Native artifacts and local preview](./native-artifacts.md) for the endpoint and qualification
-boundary.
-
-`icon-set` and `icons` are deliberately separate. `icon-set` needs Team authority and changes the
-remote catalog. `icons list --json` needs no credential; a cold cache may download exact public
-artifacts. `icons diff` requires a managed `--map-id`, the configured map ID in `--against`, and
-`status:read` authority for its hosted baseline. `icons install|update|pin` use Team `icons:read`
-authority when resolving revisions and are the only commands that select revisions or write
-`tileflow.icons.lock.json`. See the
-[Team Icon Set workflow](https://github.com/tileflow/tileflow-sdk/blob/main/packages/cli/docs/team-icon-sets.md).
-
-`models` publishes and manages the Team 3D models that maps place by name; see
-[Team 3D models](https://github.com/tileflow/tileflow-sdk/blob/main/packages/cli/docs/team-3d-models.md).
-
-The hidden `projects` command family lists and manages the internal application destinations of an
-account for support. It is not part of the ordinary workflow or the product catalog.

package/docs/coordinates.md

@@ -1,68 +0,0 @@
-# Coordinates
-
-Start with the [tileflow guide](https://github.com/tileflow/tileflow-sdk/blob/main/packages/cli/README.md) for installation and a complete first example.
-
-These local commands require an explicitly provided compatible runtime distribution. No public
-native runtime download is currently offered; package installation or the default setup URL does
-not supply one. The verified production profile is Linux x64 on Debian 12, glibc 2.36 and Node 24.
-The examples below use development artifacts and do not establish public platform support.
-
-Coordinates commands use a locally provisioned execution release. They do not use Map
-configuration, account state, or a Hosted fallback. Provision first from a distribution source, then
-run the local commands against the active cache entry or an explicit runtime directory.
-
-```sh
-tileflow setup coordinates --source /path/to/distribution.json --cache-dir /path/to/coordinates-cache --development --json
-tileflow coordinates search --query ETRS89 --runtime-dir /path/to/installed-release --development --json
-tileflow coordinates describe --id EPSG:25830 --runtime-dir /path/to/installed-release --development --json
-tileflow coordinates operations --from EPSG:4258 --to EPSG:25832 --runtime-dir /path/to/installed-release --development --json
-tileflow coordinates transform --from EPSG:4258 --to EPSG:25832 --positions '[[12,55]]' --runtime-dir /path/to/installed-release --development --json
-```
-
-`setup coordinates --source` accepts a distribution URL, a local `distribution.json`, or a directory
-that contains one. `--archive` is a local archive alias and rejects URLs. Setup verifies every asset
-declared by the selected distribution before it records the active release. `--development` is
-required for a development distribution.
-
-Every execution command accepts `--runtime-dir`, `--release`, and `--development`. With no
-`--runtime-dir`, it opens the cache entry selected by setup. `search` accepts `--query`, `describe`
-accepts `--id`, `operations` accepts `--from` and `--to`, and `transform` also accepts JSON
-`--positions`.
-
-For a complete request, use exactly one of `--request '<json>'` or `--input <file|->`. These forms
-cannot be combined with the command's convenience request flags. Input is limited to 32 KiB, must be
-valid UTF-8 JSON, and `-` reads standard input. Success writes one JSON document to stdout. A
-structured failure writes one JSON document to stderr and exits with status 1. Plain `--help` remains
-human-readable; `--help --json` is a structured failure.
-
-`tileflow explain` compiles exactly one map/theme selection through `createStyleResult()` and emits
-its structured `report` and safe compiler `diagnostics`; it deliberately omits the usually large
-MapLibre `style`. In a singular config, `--map` is optional; a multi-map workbench requires it.
-`--theme` defaults to that map's declared default. `--inspection` adds opt-in, read-only
-physical-output provenance to the report. Its physical layer IDs and indexes are diagnostic
-observations only: they are not stable application or authoring targets, and no semantic operation
-accepts them. The JSON document has this stable projection:
-
-```json
-{
-  "schemaVersion": 1,
-  "command": "explain",
-  "ok": true,
-  "selection": {"map": "madrid", "theme": "dark"},
-  "authoringManifestSchemaVersion": 2,
-  "compilation": {"ok": true, "diagnostics": [], "report": {}},
-  "diagnostics": []
-}
-```
-
-`tileflow semantic-diff --from-config <path> --to-config <path>` compares the sole map exported by
-each ordinary config, which is the normal agent workflow for reviewing a change across two files or
-checkouts. If either endpoint is a multi-map `*.workspace.ts`, select that endpoint explicitly with
-`--from-map` or `--to-map`; selectors are rejected for singular configs. The existing
-`--config <workspace> --from <map> --to <map>` form remains as the same-workspace shortcut. Paired
-config options and workspace options cannot be mixed.
-
-The successful document adds `diff`, whose exact core shape is `{schemaVersion, from, to, summary,
-changes}`; each change is `add`, `remove`, or `change` at an RFC 6901 JSON Pointer. Differences are
-informational, so a non-empty diff still exits successfully. Selection, load, validation, asset, or
-compilation failures leave stdout empty and emit one safe structured document on stderr.

package/docs/deterministic-agent-diagnostics.md

@@ -1,47 +0,0 @@
-# Deterministic agent diagnostics
-
-Start with the [tileflow guide](https://github.com/tileflow/tileflow-sdk/blob/main/packages/cli/README.md) for installation and a complete first example.
-
-Use JSON mode when an agent or CI job needs to validate or reason about the resolved config:
-
-```sh
-npx tileflow validate --json
-npx tileflow inspect --json
-npx tileflow inspect --map madrid --json
-npx tileflow language manifest --json
-npx tileflow language schema --json
-npx tileflow explain --map madrid --theme dark --json
-npx tileflow semantic-diff --from-config before/tileflow.config.ts --to-config after/tileflow.config.ts --json
-npx tileflow semantic-diff --config maps.workspace.ts --from before --to after --json
-```
-
-`validate`, `inspect`, `explain`, and `semantic-diff` success writes exactly one
-schema-version-1 command envelope to stdout. The two discovery commands intentionally return their
-contracts raw instead of wrapping them: `language manifest --json` emits authoring-manifest version
-2 and `language schema --json` emits config-reference version 4. Every JSON-mode failure, including
-failure to load either raw discovery contract, leaves stdout empty and writes one schema-version-1
-command failure to stderr. Command summaries and every failure diagnostic contain `phase`, `code`,
-`path`, `severity`, `message`, and a bounded safe `suggestion`; diagnostics are sorted and
-deduplicated deterministically.
-
-Config inspection returns the resolved map, parent-to-leaf lineage, declared paths, leaf-level merge
-provenance, and an explicit `themeContract`: default/system selection, shared token schema,
-concrete values, typography, lighting, differences from the default, and stable audit diagnostics.
-It omits the executable input-file graph and sanitizes credentials, URL queries,
-secret-shaped values, data URLs, and absolute filesystem paths. The generated
-[`modules-api-reference.json`](https://github.com/tileflow/tileflow-sdk/blob/main/docs/modules-api-reference.json) is the machine-readable
-map/module schema; its default `authoring` entrypoint tells an agent how to write the singular
-config with `extends` and `scenes`, while its named `resolved` entrypoint matches inspection and
-compiler input. Both are produced from executable core schemas rather than a handwritten parallel
-API list.
-
-`tileflow language manifest --json` discovers the complete closed semantic language without loading
-a project: compiler identity, domains and their dependencies, public operations, expression-builder
-signatures and limits, render selectors, semantic fields/features, diagnostics, reports, commands,
-and schema references. `tileflow language schema --json` returns the packaged generated JSON Schema
-that those references address. Together they are the canonical bootstrap surface for an authoring
-agent; neither command writes files or accesses the network.
-
-Each manifest command entry declares its `outputKind`, `outputVersion`, and stable
-`outputSchemaRef`. `raw-authoring-manifest` and `raw-config-reference` identify the two bootstrap
-documents above; `command-envelope` identifies the ordinary version-1 CLI contract.