@tapestry-mud/cli 0.9.0 → 0.12.0

package/CLAUDE.md

@@ -0,0 +1,42 @@
+# CLAUDE.md
+
+This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
+
+## What this is
+
+`@tapestry-mud/cli` is a Node.js CLI that manages Tapestry MUD game projects: scaffolding, pack management, registry operations, and engine lifecycle. Entry point: `bin/tapestry.js`. Commands are wired via `commander`.
+
+## Commands
+
+```sh
+npm ci          # install deps
+npm test        # run all tests (jest)
+npx jest test/path/to/file.test.js   # run a single test file
+npx jest --testNamePattern "name"    # run tests matching a name
+```
+
+No build step. No lint config in this repo.
+
+## Running the CLI locally
+
+```sh
+node bin/tapestry.js <command>
+```
+
+## Layout
+
+```
+bin/            entry point (tapestry.js)
+src/
+  commands/     one file per CLI command (~30 commands)
+  lib/          shared logic (auth, registry client, pack ops, etc.)
+  schema/       zod schemas
+  scaffold/     template files for `tapestry init`
+  util/         small helpers
+specs/          capability specs -- source of truth for system behavior
+test/           jest tests, mirrors src/ structure
+```
+
+## System behavior
+
+All behavior is documented in `specs/`. Read the relevant spec before changing any command logic. `specs/README.md` lists the index and explains the format contract (anchored claims, change records, lint rules).

package/bin/tapestry.js

@@ -33,6 +33,7 @@ const { trustAdd, trustList, trustRm } = require('../src/commands/trust');
 const { syncArea } = require('../src/commands/sync-area');
 const { harvest } = require('../src/commands/harvest');
 const { status } = require('../src/commands/status');
+const { types } = require('../src/commands/types');
 
 const program = new Command();
 
@@ -62,7 +63,7 @@ program.configureHelp({
       },
       {
         title: 'Pack Authoring',
-        commands: ['create', 'validate', 'pack', 'publish', 'unpublish', 'harvest', 'status'],
+        commands: ['create', 'validate', 'pack', 'publish', 'unpublish', 'harvest', 'status', 'types'],
       },
       {
         title: 'Trusted Publishing',
@@ -376,6 +377,18 @@ program
     }
   });
 
+program
+  .command('types')
+  .description('Write the @tapestry/engine type declarations into types/ for ESM pack authoring')
+  .action(() => {
+    try {
+      types({});
+    } catch (e) {
+      console.error(`error: ${e.message}`);
+      process.exit(1);
+    }
+  });
+
 async function runHarvest(areaRef, opts) {
   try {
     await harvest(areaRef, {
@@ -398,15 +411,15 @@ async function runHarvest(areaRef, opts) {
 program
   .command('harvest <areaRef>')
   .description('Harvest an authored area into a portable pack (areaRef = namespace:area-id)')
-  .option('--sink <sink>', 'Output sink: file | git (auto-detected by default)')
+  .option('--sink <sink>', 'Output sink: file | git | registry (auto-detected by default)')
   .option('--out <path>', '(file sink) where the .tgz lands')
-  .option('--name <name>', '(file sink) override the synthesized pack name (@scope/pack)')
+  .option('--name <name>', '(file/registry sink) override the synthesized pack name (@scope/pack)')
   .option('--pack <dir>', 'Target pack directory (auto-detected from linked packs by default)')
   .option('--game-root <path>', 'Game root containing data/ (default: current dir)')
   .option('--keep-sidecars', 'Copy instead of move (leave the game-root side-cars in place)')
   .option('--force', 'Overwrite pack files that diverge from the side-car')
-  .option('--minor', 'Bump the pack minor version (git sink only; default: patch)')
-  .option('--major', 'Bump the pack major version (git sink only; default: patch)')
+  .option('--minor', 'Bump the pack minor version (git/registry sink, owned pack only; default: patch)')
+  .option('--major', 'Bump the pack major version (git/registry sink, owned pack only; default: patch)')
   .action(runHarvest);
 
 // Deprecated: sync-area is now harvest --sink git.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@tapestry-mud/cli",
-  "version": "0.9.0",
+  "version": "0.12.0",
   "description": "CLI for the Tapestry MUD engine",
   "repository": {
     "type": "git",
@@ -10,22 +10,25 @@
     "tapestry": "./bin/tapestry.js"
   },
   "scripts": {
-    "test": "jest"
+    "test": "jest",
+    "spec-lint": "spec-lint specs/"
   },
   "publishConfig": {
     "access": "public"
   },
   "dependencies": {
     "commander": "11.1.0",
-    "form-data": "4.0.5",
+    "form-data": "4.0.6",
     "inquirer": "8.2.7",
     "js-yaml": "4.1.1",
     "node-fetch": "2.7.0",
     "semver": "7.6.2",
     "tar": "7.5.15",
+    "typescript": "5.7.3",
     "zod": "3.22.4"
   },
   "devDependencies": {
+    "@tapestry-mud/spec-lint": "0.2.1",
     "jest": "29.7.0"
   }
 }

package/specs/README.md

@@ -0,0 +1,59 @@
+# Tapestry CLI -- specs
+
+Capability specs for the Tapestry CLI. Each file describes one system's current behavior,
+known constraints, and change history. This directory is the canonical, public source of
+truth for how each system behaves now -- a fresh agent or contributor answers "how does X
+behave?" from the relevant file alone.
+
+## Index
+
+| Capability | File | Last Updated |
+|------------|------|--------------|
+| pack-lifecycle | [pack-lifecycle.md](pack-lifecycle.md) | 2026-06-20 |
+| validate | [validate.md](validate.md) | 2026-06-13 |
+| harvest | [harvest.md](harvest.md) | 2026-06-13 |
+| registry-auth | [registry-auth.md](registry-auth.md) | 2026-06-13 |
+| engine-management | [engine-management.md](engine-management.md) | 2026-06-13 |
+
+## Contract summary
+
+Each capability spec has four required sections: Overview, Behavior, Rejected and Reverted,
+Change Log. Change records live in `specs/changes/` and use the frontmatter fields `release:`
+(the version that shipped it) and `specs:` (capability files touched).
+
+Hotfixes, regressions, and dependency bumps owe no change record. Tombstones on any reversal
+of shipped behavior are mandatory.
+
+A capability spec is current if its Change Log references the latest shipped change record
+that names it in `specs:`.
+
+## Format rules (mechanically linted)
+
+- Behavior claims carry inline anchors in exactly one form: `(repo-relative/path/File.ext:123)`,
+  where the line part may be a single line `:123` or a range `:123-145`, and may be omitted only
+  for whole-file claims. Several anchors may share one set of parentheses, joined by `; `. A test
+  name in the same parentheses also counts. Lint pattern (the gate IS this regex, keep them in
+  sync): `\([@\w./\\-]+\.(js|mjs|cjs)(:\d+(-\d+)?)?[^)]*\)`. A file with no matches in its Behavior
+  section fails validation outright.
+- An empty Rejected and Reverted section contains the single line `- None on record.` under the
+  heading (the heading itself is always present).
+- Change Log is a one-line-per-record list, newest first: `- YYYY-MM-DD [slug](changes/...)`.
+  Not a table.
+
+<!-- spec-lint:start -->
+Mode: strict
+
+Required sections: Overview, Behavior, Rejected and Reverted, Change Log
+
+Anchor regex (Behavior): \([@\w./\\-]+\.(cs|js|ts|json|ya?ml|md)(:\d+(-\d+)?)?[^)]*\)
+
+Empty-reversal sentinel: - None on record.
+
+Change Log: list, newest-first by date, not a table. Empty is valid for unmodified capabilities.
+
+Index sync: every capability .md on disk appears in README index; every indexed file exists on disk; index date matches file last-updated.
+
+Currency: for each change record naming a capability, the top Change Log entry references that record and last-updated >= record date. A capability named by zero records may have an empty Change Log.
+
+Tombstone: a change record with status:reverted requires a tombstone entry in the capability Rejected and Reverted (not the empty sentinel).
+<!-- spec-lint:end -->

package/specs/changes/2026-06-20-pack-esm-build.md

@@ -0,0 +1,28 @@
+---
+release: 0.10.0
+specs: [pack-lifecycle.md]
+---
+
+# Pack ESM Build
+
+## Why
+
+Packs are authored in TypeScript and ship native ES modules, but the CLI had no
+build step: `pack` and `publish` archived whatever was on disk. An ESM pack
+declares `content.scripts_format: esm` and points `content.scripts` at compiled
+output under `dist/scripts/`, which is gitignored - so without a compile the
+tarball shipped no runnable scripts. Pack authors also had no typed surface for
+the engine API they call, so editors could not check `tapestry.*` usage.
+
+## What
+
+- `pack` and `publish` compile an ESM pack's `scripts/**/*.ts` to
+  `dist/scripts/**/*.js` with the bundled `tsc` and the pack's `tsconfig.json`
+  before building the tarball. The compile runs before any network or auth work
+  in `publish`. Legacy packs (no `scripts_format: esm`) are a no-op, so the step
+  is backward compatible.
+- New `tapestry types` command vendors the `@tapestry/engine` type definitions
+  into a project's `types/` so `tsc` and editors can type-check pack scripts
+  against the engine API surface the pack calls.
+- `typescript` is pinned exactly as a CLI dependency (no caret) so the compile is
+  reproducible.

package/specs/engine-management.md

@@ -0,0 +1,140 @@
+---
+capability: engine-management
+last-updated: 2026-06-13
+---
+
+# engine-management
+
+Capability spec for acquiring, configuring, running, and stopping the Tapestry engine.
+
+## Overview
+
+engine-management covers the lifecycle of the Tapestry engine process from the CLI's
+perspective: reading the engine configuration from `tapestry.yaml`, fetching or building the
+engine artifact, starting it, and stopping it. Three launch modes are supported: `docker`
+(recommended; pulls and runs a container image), `binary` (downloads a pre-built platform
+binary from GitHub Releases), and `source` (git-clones the engine and runs it via
+`dotnet run`). Named channels (`stable`, `nightly`) resolve to concrete versions via the
+registry for the docker mode.
+
+Commands: `engine install`, `engine update`, `engine info`, `engine versions`, `start`, `stop`.
+
+## Behavior
+
+### Configuration
+
+Engine configuration is read from the `engine` key in `tapestry.yaml`. The key must be an
+object (not a plain string, which is the pack manifest format). Required fields are
+`engine.version` and `engine.mode`; `mode` must be one of `docker`, `binary`, or `source`.
+(src/lib/engine-manager.js:249-278)
+
+Derived values from `readEngineConfig`: (src/lib/engine-manager.js:248-278)
+
+- `image` defaults to `ghcr.io/tapestry-mud/tapestry` if not specified.
+- `network` is null if not specified.
+- `envFile` is null if not specified (`engine.env_file`).
+- `installDir` is always `<cwd>/.tapestry-engine`.
+- `projectName` is the manifest `name` lowercased and with non-alphanumeric/hyphen characters
+  replaced by `-`.
+
+### Channel resolution (docker mode only)
+
+Channel names `stable` and `nightly` are the two recognized named channels.
+(src/lib/engine-manager.js:6)
+
+When the configured version is a named channel, `resolveDockerTag` fetches
+`<registry>/v1/engine-channels/<channel>` and returns the `docker_tag` field.
+(src/lib/engine-manager.js:14-35)
+
+- If the registry is unreachable, the channel name is used as the tag directly with a warning.
+  (src/lib/engine-manager.js:19-22)
+- If the registry returns 404, throws with a hint to run `engine versions`.
+  (src/lib/engine-manager.js:23-27)
+- If the version string is not a named channel, it is used as the Docker tag directly.
+  (src/lib/engine-manager.js:13-14)
+
+### engine install
+
+- **docker mode**: Calls `docker pull <image>:<version>`. If the tagged pull fails, falls back
+  to `docker pull <image>:latest` and re-tags to the requested version.
+  (src/lib/engine-manager.js:44-59)
+- **binary mode**: Determines the platform (`linux`, `osx`, or `windows`), downloads the
+  engine tarball from
+  `https://github.com/tapestry-mud/tapestry/releases/download/v<version>/tapestry-<platform>.tar.gz`
+  using `curl`, extracts it to `.tapestry-engine/binary/<version>/`, then deletes the
+  downloaded tarball. (src/lib/engine-manager.js:124-151)
+- **source mode**: `git clone`s `https://github.com/tapestry-mud/tapestry.git` into
+  `.tapestry-engine/source/`. Throws if the source directory already exists (use
+  `engine update` instead). (src/lib/engine-manager.js:180-194)
+
+### engine update
+
+- **docker mode**: Same pull logic as install (re-pulls the tag).
+  (src/lib/engine-manager.js:294-298)
+- **binary mode**: Re-runs `binaryInstall` for the configured version.
+  (src/lib/engine-manager.js:299-300)
+- **source mode**: Runs `git pull` inside `.tapestry-engine/source/`; throws if the source
+  directory is absent. (src/lib/engine-manager.js:195-207)
+
+### engine info
+
+Prints `Mode`, `Version`, and either `Image` (docker) or `Path` and `Status` (binary/source).
+(src/commands/engine.js:13-23)
+
+For binary and source modes, `installed` is true if the expected directory exists on disk.
+(src/lib/engine-manager.js:174) (src/lib/engine-manager.js:226)
+
+### engine versions
+
+Fetches `/v1/engine-channels` from the registry and prints a table of Channel, Version, and
+Updated columns. Prints "No engine channels registered." if the list is empty.
+(src/commands/engine-versions.js:7-31)
+
+### start
+
+- Requires `packs/` directory and `server.yaml` in the project root; throws otherwise.
+  (src/lib/engine-manager.js:321-327)
+- Creates `data/` directory if absent. (src/lib/engine-manager.js:328)
+- **docker mode**: Calls `docker rm -f <containerName>` to clear any stale container, then
+  `docker run --detach` with port mappings `-p 4000:4000 -p 4001:4001`, volume mounts for
+  `packs/`, `server.yaml`, and `data/`, optional `--network` and `--env-file`, and any link
+  mounts from `dockerLinkMounts`. (src/lib/engine-manager.js:69-99)
+- **binary mode**: Materializes links into `packs/`, spawns the engine binary detached, and
+  writes the PID to `.tapestry.pid`. (src/lib/engine-manager.js:154-171)
+  (src/lib/process-tracker.js:8-10)
+- **source mode**: Materializes links, runs `dotnet run` in `.tapestry-engine/source/` with
+  `--packs` and `--config` arguments, detached, and writes the PID to `.tapestry.pid`.
+  (src/lib/engine-manager.js:208-222) (src/lib/process-tracker.js:8-10)
+- **docker mode with `engine.env_file`**: Resolves the path relative to the project root and
+  throws if the file does not exist before starting. (src/lib/engine-manager.js:330-338)
+- Container name for docker mode is `tapestry-<projectName>`. (src/lib/engine-manager.js:70)
+- Prints "Engine started. Container: <name>" (docker) or "Engine started (PID <pid>)"
+  (binary/source) and the telnet/websocket addresses. (src/lib/engine-manager.js:96-99)
+  (src/lib/engine-manager.js:168-171)
+
+### stop
+
+- **docker mode**: Runs `docker stop <containerName>` then `docker rm <containerName>`.
+  Throws if either command fails. (src/lib/engine-manager.js:101-112)
+- **binary/source mode**: Reads the PID from `.tapestry.pid`, sends `SIGTERM`, and clears the
+  file. If the process is already gone when `SIGTERM` is sent, the error is swallowed and the
+  PID file is still cleared. Throws if no PID file is found.
+  (src/lib/engine-manager.js:232-243) (src/lib/process-tracker.js:14-20)
+  (src/lib/process-tracker.js:22-27)
+
+### Process tracker
+
+- `writePid` writes the PID as a string to `<cwd>/.tapestry.pid`.
+  (src/lib/process-tracker.js:8-10)
+- `readPid` reads and parses the PID; returns null if the file is absent or the value is not a
+  positive integer. (src/lib/process-tracker.js:13-20)
+- `clearPid` deletes the file if present; no-op otherwise.
+  (src/lib/process-tracker.js:22-27)
+
+## Rejected and Reverted
+
+- None on record.
+
+## Change Log
+
+- None on record.

package/specs/harvest.md

@@ -0,0 +1,169 @@
+---
+capability: harvest
+last-updated: 2026-06-13
+---
+
+# harvest
+
+Capability spec for world-state classification and the authoring-to-pack pipeline.
+
+## Overview
+
+This capability covers two closely related concerns:
+
+1. **World-state** -- classifying each authored area in the game root's `data/areas/` tree
+   as Clean, Edited, Fork, or WIP by reading only on-disk side-car facts. The `tapestry status`
+   command is the user-facing view of this classification.
+
+2. **Harvest** -- promoting authored area content from the game-root side-car tree into a
+   pack. Two sinks exist: the `git` sink renders the content into a linked pack repository,
+   bumps the pack version, and commits; the `file` sink renders into a temp build directory
+   and produces a portable `.tgz` at the current version without bumping.
+
+The `sync-area` command is a deprecated alias for `harvest --sink git`. The `export-area`
+command is a hidden deprecated alias for the same.
+
+The area reference format is `namespace:area-id` (e.g. `example-pack:village-green`).
+(src/lib/pack-resolve.js:8-13)
+
+## Behavior
+
+### World-state classification
+
+The state vocabulary is defined in `src/lib/world-state.js` and maps to four values:
+(src/lib/world-state.js:11)
+
+- **WIP** -- `area.yaml` exists and its `area.flags` array contains the string `wip`.
+  Checked before all other states; a WIP area is not visible to players.
+  (src/lib/world-state.js:14-22) (src/lib/world-state.js:51)
+- **Clean** -- no room files exist under `data/areas/<area>/rooms/*.yaml`, OR all existing
+  room files are byte-for-byte equal (via JSON round-trip of YAML) to their counterparts in
+  the linked pack directory. (src/lib/world-state.js:57-59) (src/lib/world-state.js:64-70)
+- **Edited** -- at least one room file under the side-car tree either has no counterpart in
+  the pack or differs from it. The pack must be owned (namespace resolves to a linked pack).
+  (src/lib/world-state.js:62-70)
+- **Fork** -- the area's namespace does not resolve to any linked pack the user owns (the
+  area belongs to an official or foreign pack). (src/lib/world-state.js:63-65)
+
+Namespace is inferred from the `id` field of the first room file (`ns:key` format).
+(src/lib/world-state.js:44-49)
+
+`computeAreaStates` iterates `data/areas/` directories alphabetically. It never queries the
+registry and never reads the engine's runtime state. (src/lib/world-state.js:26-77)
+
+#### status command
+
+Prints one line per area: `<State padded to 7> <area-dir> (<namespace>) rooms:<count> [WIP]`.
+(src/commands/status.js:13-15)
+
+Prints a legend line: "Clean = shipped; Edited = ready to harvest; Fork = owned by another
+pack; WIP = hidden from players." (src/commands/status.js:18)
+
+Prints "Strict boot remains the authority; this is a lighter on-host view."
+(src/commands/status.js:19)
+
+With `--game-root <path>`, reads `data/areas/` from that path instead of the current
+directory. (src/commands/status.js:5)
+
+### Harvest -- sink selection
+
+`harvest` auto-detects the sink when `--sink` is not given: it calls `resolvePackDirOrNull`
+for the area's namespace; if exactly one linked pack matches AND that directory is a git repo,
+the git sink is used; otherwise the file sink is used.
+(src/commands/harvest.js:15-19)
+
+With `--sink git` or `--sink file`, the choice is explicit; any other value throws.
+(src/commands/harvest.js:20-33)
+
+### Harvest -- git sink (`sync-area`)
+
+The git sink delegates entirely to `syncArea`.
+(src/commands/harvest.js:21-23)
+
+- Requires a linked pack for the namespace; throws if none or multiple match.
+  (src/lib/pack-resolve.js:44-55)
+- Requires `pack.yaml` in the target pack directory. (src/commands/sync-area.js:22-25)
+- Asserts that the pack's namespace (derived from `manifest.name` by replacing `@scope/`
+  separator with `-`) matches the area namespace. Throws on mismatch.
+  (src/lib/render-core.js:91-101) (src/lib/pack-resolve.js:17-20)
+- Calls `renderArea` to fold the side-car rooms into the pack (see below).
+  (src/commands/sync-area.js:29)
+- Bumps `pack.yaml` version using `semver.inc` at the requested level (default: patch).
+  (src/lib/pack-manifest.js:71-85) (src/commands/sync-area.js:31)
+- If the pack directory is a git repo, commits all changes with the message
+  `content(<area>): sync authored edits, bump <old> -> <new>`.
+  (src/commands/sync-area.js:33-38)
+- If the pack directory is not a git repo, bumps but does not commit; warns.
+  (src/commands/sync-area.js:39-41)
+- `--minor` and `--major` flags set the bump level; default is patch.
+  (bin/tapestry.js:406-408)
+- Prints "To publish + deploy, push the pack repo" with the pack directory path.
+  (src/commands/sync-area.js:46-48)
+
+### Harvest -- file sink
+
+The file sink never bumps the version; it captures an exact snapshot at the manifest's
+current version. (src/lib/file-sink.js:19-21)
+
+- If a linked pack exists for the namespace, copies the entire pack directory (excluding
+  `.git`, `node_modules`, `.DS_Store`, and `.tgz` files) into a temp build directory.
+  The rendered area content is then folded into that copy.
+  (src/lib/file-sink.js:30-39) (src/lib/tarball-builder.js:7)
+- If no linked pack exists (hobbyist / no owned repo), synthesizes a minimal `pack.yaml`
+  using the namespace to derive `@scope/name`. (src/lib/file-sink.js:36-38)
+  (src/lib/pack-manifest.js:53-68)
+- Calls `renderArea` to fold the side-car rooms into the temp build directory.
+  (src/lib/file-sink.js:39)
+- Builds a `.tgz` from the temp dir. Output path defaults to `<shortName>-<version>.tgz`
+  in the current directory; overridden with `--out <path>`. (src/lib/file-sink.js:43-49)
+- Cleans up the temp directory in a `finally` block. (src/lib/file-sink.js:56-58)
+- Prints "This .tgz is a portable, installable pack" after completion.
+  (src/lib/file-sink.js:55-56)
+- `--name <@scope/pack>` overrides the synthesized pack name (file sink only; only
+  meaningful when no linked pack is found). (src/lib/file-sink.js:36)
+
+### renderArea (shared by both sinks)
+
+- Reads room YAML files from `<gameRoot>/data/areas/<area>/rooms/*.yaml`.
+  Throws if the directory is absent or empty. (src/lib/render-core.js:13-20)
+- Copies `area.yaml` from the game-root side-car if present; creates a minimal one if absent
+  and the target does not already have one. (src/lib/render-core.js:26-35)
+- Writes each room file to `<targetDir>/areas/<area>/rooms/<file>`, creating directories as
+  needed. (src/lib/render-core.js:37-50)
+- Without `--force`: throws if a room file in the target differs from the incoming side-car.
+  (src/lib/render-core.js:41-45)
+- With `--force`: overwrites divergent room files silently. (src/lib/render-core.js:40-49)
+- After writing rooms, copies oracle side-car files: `places-oracle.yaml` at the area root and
+  any `*-oracle-table.yaml` files anywhere under the area tree (including inside `mobs/` and
+  `items/` subdirectories). The same divergence guard (throw without `--force`, overwrite with
+  `--force`) applies. (src/lib/render-core.js) (src/lib/pack-manifest.js)
+- After copying oracle side-cars, copies all `*.yaml` files from `mobs/` and `items/` under the
+  area side-car tree into the corresponding `areas/<area>/mobs/` and `areas/<area>/items/`
+  directories in the target pack, including any `*-oracle-table.yaml` files in those directories.
+  The same divergence guard applies. (src/lib/render-core.js)
+- After writing, calls `ensureContentGlobs` to additively add `area_definitions`, `rooms`,
+  `oracle_tables`, `places_oracle`, `mobs`, and `items` glob entries to `pack.yaml` if not
+  already present. (src/lib/render-core.js) (src/lib/pack-manifest.js)
+- `reconcileDependencies` is a deliberate no-op: rooms are self-contained; the seam is wired
+  for a future slice that will scan for cross-pack references in mobs/items/quests.
+  (src/lib/render-core.js)
+
+### Side-car removal (default behavior)
+
+After rendering, unless `--keep-sidecars` is given, `removeSideCars` deletes the room files
+from the game-root side-car tree and prunes the `rooms/` and area directories if they become
+empty. `area.yaml` in the game root is also deleted. (src/lib/render-core.js:69-88)
+
+## Rejected and Reverted
+
+- `sync-area` was the original name for `harvest --sink git`. It prints a deprecation warning
+  and delegates to `harvest` with `sink: 'git'` forced.
+  (bin/tapestry.js:412-425)
+- `export-area` is a hidden alias with the same deprecation path.
+  (bin/tapestry.js:428-439)
+
+## Change Log
+
+- 2026-06-23 (0.11.0): renderArea carries oracle table side-cars (places-oracle.yaml, *-oracle-table.yaml)
+  and mints mob/item instance files (mobs/*.yaml, items/*.yaml) into the target pack alongside
+  area.yaml and rooms/. CONTENT_GLOBS gains oracle_tables, places_oracle, mobs, items.

package/specs/lint.config.json

@@ -0,0 +1 @@
+{}