@objectstack/metadata-fs 17.0.0-rc.0 → 17.0.0-rc.1

package/CHANGELOG.md

@@ -0,0 +1,708 @@
+# @objectstack/metadata-fs
+
+## 17.0.0-rc.1
+
+### Patch Changes
+
+- 2e836de: chore(packaging): CHANGELOG.md ships in every npm tarball (#4261)
+
+  The AGENTS.md post-task checklist requires breaking changesets to carry their
+  FROM → TO migration because "this text ships to consumers as `CHANGELOG.md`
+  inside the npm package and is what an upgrading agent greps after the tombstone
+  error." That delivery path was severed for 68 of the 69 publishable packages:
+  npm packs `package.json` / `README*` / `LICENSE*` unconditionally but — unlike
+  older npm versions — not `CHANGELOG.md`, and the canonical
+  `"files": ["dist", "README.md"]` whitelist never named it. Measured on npm
+  10.9.7: `npm pack --dry-run` on `@objectstack/types` shipped 3 files while its
+  70KB `CHANGELOG.md` stayed behind. Only `@objectstack/spec` listed it
+  explicitly.
+
+  The tombstone-error scenario is precisely the one where the repo is out of
+  reach — the upgrading agent has `node_modules` and nothing else — so the
+  migration text has to ride in the tarball. Every publishable package now
+  declares `CHANGELOG.md` in `files`, and the canonical whitelist is
+  `["dist", "README.md", "CHANGELOG.md"]`.
+
+  The other half is the gate: `check:published-files` gains a fifth invariant,
+  COMPLETE — a whitelist that fails to cover `CHANGELOG.md` fails the
+  always-required lint job, so the next package cannot silently sever the path
+  again. `@objectstack/spec`'s per-package EXTRA_ENTRIES exemption dissolves
+  into the canonical set.
+
+  Consumer-visible change: one more file per install (the package's changelog,
+  e.g. 70.8KB for `@objectstack/types`), and `grep -r "removed key"
+node_modules/@objectstack/*/CHANGELOG.md` now finds the migration it was
+  promised.
+
+- Updated dependencies [f5a4ef0]
+- Updated dependencies [2e836de]
+  - @objectstack/metadata-core@17.0.0-rc.1
+
+## 17.0.0-rc.0
+
+### Patch Changes
+
+- Updated dependencies [db48ad5]
+- Updated dependencies [c073b8c]
+  - @objectstack/metadata-core@17.0.0-rc.0
+
+## 16.1.0
+
+### Patch Changes
+
+- @objectstack/metadata-core@16.1.0
+
+## 16.0.0
+
+### Patch Changes
+
+- Updated dependencies [62a2117]
+- Updated dependencies [06cb319]
+  - @objectstack/metadata-core@16.0.0
+
+## 16.0.0-rc.1
+
+### Patch Changes
+
+- Updated dependencies [62a2117]
+  - @objectstack/metadata-core@16.0.0-rc.1
+
+## 16.0.0-rc.0
+
+### Patch Changes
+
+- Updated dependencies [06cb319]
+  - @objectstack/metadata-core@16.0.0-rc.0
+
+## 15.1.1
+
+### Patch Changes
+
+- @objectstack/metadata-core@15.1.1
+
+## 15.1.0
+
+### Patch Changes
+
+- @objectstack/metadata-core@15.1.0
+
+## 15.0.0
+
+### Patch Changes
+
+- @objectstack/metadata-core@15.0.0
+
+## 14.8.0
+
+### Patch Changes
+
+- @objectstack/metadata-core@14.8.0
+
+## 14.7.0
+
+### Patch Changes
+
+- @objectstack/metadata-core@14.7.0
+
+## 14.6.0
+
+### Patch Changes
+
+- @objectstack/metadata-core@14.6.0
+
+## 14.5.0
+
+### Patch Changes
+
+- @objectstack/metadata-core@14.5.0
+
+## 14.4.0
+
+### Patch Changes
+
+- Updated dependencies [7953832]
+  - @objectstack/metadata-core@14.4.0
+
+## 14.3.0
+
+### Patch Changes
+
+- @objectstack/metadata-core@14.3.0
+
+## 14.2.0
+
+### Patch Changes
+
+- @objectstack/metadata-core@14.2.0
+
+## 14.1.0
+
+### Patch Changes
+
+- @objectstack/metadata-core@14.1.0
+
+## 14.0.0
+
+### Patch Changes
+
+- @objectstack/metadata-core@14.0.0
+
+## 13.0.0
+
+### Patch Changes
+
+- @objectstack/metadata-core@13.0.0
+
+## 12.6.0
+
+### Patch Changes
+
+- @objectstack/metadata-core@12.6.0
+
+## 12.5.0
+
+### Patch Changes
+
+- @objectstack/metadata-core@12.5.0
+
+## 12.4.0
+
+### Patch Changes
+
+- Updated dependencies [60dc3ba]
+  - @objectstack/metadata-core@12.4.0
+
+## 12.3.0
+
+### Patch Changes
+
+- @objectstack/metadata-core@12.3.0
+
+## 12.2.0
+
+### Patch Changes
+
+- Updated dependencies [da807f7]
+  - @objectstack/metadata-core@12.2.0
+
+## 12.1.0
+
+### Patch Changes
+
+- @objectstack/metadata-core@12.1.0
+
+## 12.0.0
+
+### Patch Changes
+
+- @objectstack/metadata-core@12.0.0
+
+## 11.10.0
+
+### Patch Changes
+
+- @objectstack/metadata-core@11.10.0
+
+## 11.9.0
+
+### Patch Changes
+
+- @objectstack/metadata-core@11.9.0
+
+## 11.8.0
+
+### Patch Changes
+
+- @objectstack/metadata-core@11.8.0
+
+## 11.7.0
+
+### Patch Changes
+
+- @objectstack/metadata-core@11.7.0
+
+## 11.6.0
+
+### Patch Changes
+
+- @objectstack/metadata-core@11.6.0
+
+## 11.5.0
+
+### Patch Changes
+
+- @objectstack/metadata-core@11.5.0
+
+## 11.4.0
+
+### Patch Changes
+
+- @objectstack/metadata-core@11.4.0
+
+## 11.3.0
+
+### Patch Changes
+
+- @objectstack/metadata-core@11.3.0
+
+## 11.2.0
+
+### Patch Changes
+
+- @objectstack/metadata-core@11.2.0
+
+## 11.1.0
+
+### Patch Changes
+
+- @objectstack/metadata-core@11.1.0
+
+## 11.0.0
+
+### Patch Changes
+
+- Updated dependencies [4d99a5c]
+  - @objectstack/metadata-core@11.0.0
+
+## 10.3.0
+
+### Patch Changes
+
+- @objectstack/metadata-core@10.3.0
+
+## 10.2.0
+
+### Patch Changes
+
+- @objectstack/metadata-core@10.2.0
+
+## 10.1.0
+
+### Patch Changes
+
+- @objectstack/metadata-core@10.1.0
+
+## 10.0.0
+
+### Patch Changes
+
+- @objectstack/metadata-core@10.0.0
+
+## 9.11.0
+
+### Patch Changes
+
+- @objectstack/metadata-core@9.11.0
+
+## 9.10.0
+
+### Patch Changes
+
+- @objectstack/metadata-core@9.10.0
+
+## 9.9.1
+
+### Patch Changes
+
+- @objectstack/metadata-core@9.9.1
+
+## 9.9.0
+
+### Patch Changes
+
+- @objectstack/metadata-core@9.9.0
+
+## 9.8.0
+
+### Patch Changes
+
+- @objectstack/metadata-core@9.8.0
+
+## 9.7.0
+
+### Patch Changes
+
+- @objectstack/metadata-core@9.7.0
+
+## 9.6.0
+
+### Patch Changes
+
+- @objectstack/metadata-core@9.6.0
+
+## 9.5.1
+
+### Patch Changes
+
+- @objectstack/metadata-core@9.5.1
+
+## 9.5.0
+
+### Patch Changes
+
+- @objectstack/metadata-core@9.5.0
+
+## 9.4.0
+
+### Patch Changes
+
+- Updated dependencies [fef38ec]
+  - @objectstack/metadata-core@9.4.0
+
+## 9.3.0
+
+### Patch Changes
+
+- @objectstack/metadata-core@9.3.0
+
+## 9.2.0
+
+### Patch Changes
+
+- @objectstack/metadata-core@9.2.0
+
+## 9.1.0
+
+### Patch Changes
+
+- @objectstack/metadata-core@9.1.0
+
+## 9.0.1
+
+### Patch Changes
+
+- @objectstack/metadata-core@9.0.1
+
+## 9.0.0
+
+### Patch Changes
+
+- @objectstack/metadata-core@9.0.0
+
+## 8.0.1
+
+### Patch Changes
+
+- @objectstack/metadata-core@8.0.1
+
+## 8.0.0
+
+### Patch Changes
+
+- @objectstack/metadata-core@8.0.0
+
+## 7.9.0
+
+### Patch Changes
+
+- @objectstack/metadata-core@7.9.0
+
+## 7.8.0
+
+### Patch Changes
+
+- @objectstack/metadata-core@7.8.0
+
+## 7.7.0
+
+### Patch Changes
+
+- Updated dependencies [764c747]
+  - @objectstack/metadata-core@7.7.0
+
+## 7.6.0
+
+### Patch Changes
+
+- @objectstack/metadata-core@7.6.0
+
+## 7.5.0
+
+### Patch Changes
+
+- @objectstack/metadata-core@7.5.0
+
+## 7.4.1
+
+### Patch Changes
+
+- @objectstack/metadata-core@7.4.1
+
+## 7.4.0
+
+### Patch Changes
+
+- @objectstack/metadata-core@7.4.0
+
+## 7.3.0
+
+### Patch Changes
+
+- @objectstack/metadata-core@7.3.0
+
+## 7.2.1
+
+### Patch Changes
+
+- @objectstack/metadata-core@7.2.1
+
+## 7.2.0
+
+### Patch Changes
+
+- @objectstack/metadata-core@7.2.0
+
+## 7.1.0
+
+### Patch Changes
+
+- @objectstack/metadata-core@7.1.0
+
+## 7.0.0
+
+### Patch Changes
+
+- @objectstack/metadata-core@7.0.0
+
+## 6.9.0
+
+### Patch Changes
+
+- @objectstack/metadata-core@6.9.0
+
+## 6.8.1
+
+### Patch Changes
+
+- @objectstack/metadata-core@6.8.1
+
+## 6.8.0
+
+### Patch Changes
+
+- @objectstack/metadata-core@6.8.0
+
+## 6.7.1
+
+### Patch Changes
+
+- @objectstack/metadata-core@6.7.1
+
+## 6.7.0
+
+### Patch Changes
+
+- @objectstack/metadata-core@6.7.0
+
+## 6.6.0
+
+### Patch Changes
+
+- @objectstack/metadata-core@6.6.0
+
+## 6.5.1
+
+### Patch Changes
+
+- @objectstack/metadata-core@6.5.1
+
+## 6.5.0
+
+### Patch Changes
+
+- @objectstack/metadata-core@6.5.0
+
+## 6.4.0
+
+### Patch Changes
+
+- @objectstack/metadata-core@6.4.0
+
+## 6.3.0
+
+### Patch Changes
+
+- @objectstack/metadata-core@6.3.0
+
+## 6.2.0
+
+### Patch Changes
+
+- @objectstack/metadata-core@6.2.0
+
+## 6.1.1
+
+### Patch Changes
+
+- @objectstack/metadata-core@6.1.1
+
+## 6.1.0
+
+### Patch Changes
+
+- @objectstack/metadata-core@6.1.0
+
+## 6.0.0
+
+### Patch Changes
+
+- @objectstack/metadata-core@6.0.0
+
+## 5.2.0
+
+### Patch Changes
+
+- Updated dependencies [bab2b20]
+  - @objectstack/metadata-core@5.2.0
+
+## 5.1.0
+
+### Patch Changes
+
+- 75f4ee6: feat(metadata): introduce `executionPinned` capability for runtime version pinning (ADR-0009)
+
+  Adds a new capability flag on the metadata type registry so that types whose runtime
+  transaction rows reference a specific historical version (flow, workflow, approval)
+  get unified pinning behavior — instead of every business table re-implementing its
+  own snapshot column.
+
+  - `MetadataTypeRegistryEntrySchema` gains `executionPinned: boolean`, enforced
+    invariant `executionPinned ⇒ supportsVersioning`.
+  - `flow`, `workflow`, `approval` flipped to `executionPinned: true`. `approval`
+    also corrected to `supportsVersioning: true` (it was wrongly `false`).
+  - `MetadataRepository.getByHash(ref, hash)` added to the interface. Production
+    implementation in `SysMetadataRepository` resolves historical bodies through
+    `sys_metadata_history` keyed by `(organization_id, type, name, checksum)`.
+    In-memory and FS repositories serve HEAD-only matches.
+  - `sys_metadata_history` gains an index on `(organization_id, type, name, checksum)`
+    to keep hash lookups O(log n).
+  - `HistoryCleanupManager` skips pinned types entirely (both age-based and
+    count-based retention) — pinned-type history must never be GC'd.
+
+  See `docs/adr/0009-execution-pinned-metadata.md` for full rationale and the
+  list of rejected alternatives (no shared snapshot table, no inlined snapshot column).
+
+- Updated dependencies [75f4ee6]
+  - @objectstack/metadata-core@5.1.0
+
+## 5.0.0
+
+### Minor Changes
+
+- 5e9dcb4: **BREAKING — metadata: remove `project` and `branch` from `MetaRef`**
+
+  The metadata layer no longer models project or branch. Customisation is now
+  scoped purely to **organisation**. Project remains exclusively as an artifact
+  packaging concept (the `objectstack.json` bundle envelope); branching is left
+  to Git.
+
+  What changed:
+
+  - `MetaRef` is now `{ org, type, name, version? }` (was
+    `{ org, project, branch, type, name, version? }`). `refKey()` is the two
+    segment string `${org}/${type}/${name}` (was five segments).
+  - `MetadataItem.seq` is monotonic **per org** (was per branch).
+  - `BranchRef`, `MergeStrategy`, `MergeResult` types and the optional
+    `fork`/`merge` methods on `MetadataRepository` are removed.
+  - `ListFilter` / `WatchFilter` / `HistoryOptions` no longer accept `project`
+    or `branch`.
+  - `FileSystemRepository` disk layout simplified to
+    `<root>/<type>/<name>.json` (was `<root>/<project>/<branch>/<type>/<name>.json`);
+    change-log path is now `.objectstack/.log/main.jsonl` regardless of any
+    branch concept. Constructor no longer accepts `project` / `branch`.
+  - `SysMetadataRepository`: removed `projectLabel` / `branchLabel` options;
+    the `sys_metadata` schema's `project_id` / `branch` columns (if present)
+    are ignored. A future major release will `DROP` them.
+  - `MetadataManager.setRepository(repo, opts)` no longer takes an opts object
+    with `branch`.
+
+  Migration:
+
+  ```diff
+  -const ref = { org: 'acme', project: 'crm', branch: 'main', type: 'view', name: 'home' };
+  +const ref = { org: 'acme', type: 'view', name: 'home' };
+
+  -new FileSystemRepository({ root, org: 'acme', project: 'crm', branch: 'main' });
+  +new FileSystemRepository({ root, org: 'acme' });
+  ```
+
+  Existing `sys_metadata` rows continue to load; the deprecated columns are
+  ignored at read time.
+
+- 32ce912: Add `@objectstack/metadata-fs` — Node-only `FileSystemRepository`
+  implementation of the M0 Repository contract.
+
+  Layout:
+
+  ```
+  <root>/
+    <type>/<name>.json          # canonical body (atomic rename writes)
+    .objectstack/.log/<branch>.jsonl   # append-only change log
+  ```
+
+  Features:
+
+  - All 17 contract tests pass (`singleBranch: true`).
+  - Per-key serialization via `KeyedMutex`.
+  - Atomic writes via tmpfile + rename.
+  - Heads and `seq` recovered from the JSONL log on `start()` — survives
+    process restart.
+  - chokidar watcher translates external edits (e.g. VSCode saves) into
+    `MetadataEvent`s with `source: 'fs'`.
+  - Self-write suppression: 200ms window prevents the watcher from
+    re-emitting events for files we wrote ourselves.
+  - Manual `AsyncIterator` for `watch()` to mirror the in-memory pattern.
+
+  Also (`metadata-core`):
+
+  - Add `singleBranch` option to `runRepositoryContractTests` so
+    single-branch backends (like the FS one) skip the cross-branch test.
+  - Switch tsup `splitting: true` so `index.js` and `testing.js` share a
+    single `ConflictError` class identity (was double-bundled before).
+
+  See ADR-0008 §10 PR-4.
+
+### Patch Changes
+
+- 96ad4df: Fix dev-mode HMR data-reload for `*.view.ts` / `*.flow.ts` source-file edits.
+
+  Three coordinated fixes close the long-standing gap where editing a
+  declarative-metadata source file in dev (e.g. `case.view.ts`) would
+  recompile `dist/objectstack.json` but the running server kept serving
+  the stale boot-time value:
+
+  1. **`@objectstack/objectql`** — `ObjectStackProtocolImplementation.getMetaItem`
+     now consults `MetadataService` (HMR-aware) **before** the in-memory
+     `SchemaRegistry` (boot-time cache). Previously the registry shadowed
+     freshly-registered values: `manager.register('view','case',newDef)`
+     updated MetadataManager but `getMetaItem` returned the stale registry
+     copy because step 2 (registry) ran before step 3 (service). Reordered
+     to "1. sys_metadata overlay → 2. MetadataService → 3. SchemaRegistry".
+
+  2. **`@objectstack/runtime`** — `createStandaloneStack` now enables the
+     `MetadataPlugin` artifact-file watcher in non-production environments
+     (`NODE_ENV !== 'production'`). Previously hard-coded to `watch: false`,
+     leaving nothing watching `dist/objectstack.json` when the CLI dev mode
+     recompiled it.
+
+  3. **`@objectstack/metadata`** & **`@objectstack/metadata-fs`** — Both
+     chokidar watchers now use `usePolling: true` to avoid `fs.watch`
+     EMFILE on macOS / busy dev hosts where the native file-descriptor
+     pool can be exhausted by other long-running node processes.
+
+  With these three changes:
+
+  - CLI edits source → recompile artifact (~400ms)
+  - Server's polling chokidar detects artifact change → `_loadFromLocalFile`
+  - `_loadFromLocalFile` calls `manager.register(type, name, item)`
+  - MetadataService now has the fresh value
+  - Read path returns the fresh value via the new step-2 lookup
+  - Studio SSE listeners re-render
+
+- Updated dependencies [5e9dcb4]
+- Updated dependencies [4150fe4]
+- Updated dependencies [8337cdb]
+- Updated dependencies [58835a6]
+- Updated dependencies [8cc30b4]
+- Updated dependencies [32ce912]
+  - @objectstack/metadata-core@5.0.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@objectstack/metadata-fs",
-  "version": "17.0.0-rc.0",
+  "version": "17.0.0-rc.1",
   "license": "Apache-2.0",
   "description": "FileSystemRepository: Node-only Repository implementation backed by JSON files and a JSONL change log (ADR-0008).",
   "type": "module",
@@ -15,7 +15,8 @@
   },
   "files": [
     "dist",
-    "README.md"
+    "README.md",
+    "CHANGELOG.md"
   ],
   "keywords": [
     "objectstack",
@@ -25,7 +26,7 @@
   ],
   "dependencies": {
     "chokidar": "^5.0.0",
-    "@objectstack/metadata-core": "17.0.0-rc.0"
+    "@objectstack/metadata-core": "17.0.0-rc.1"
   },
   "devDependencies": {
     "@types/node": "^26.1.1",
@@ -52,6 +53,7 @@
     "dev": "tsc --watch",
     "clean": "rm -rf dist",
     "test": "vitest run",
-    "test:watch": "vitest"
+    "test:watch": "vitest",
+    "typecheck": "tsc --noEmit"
   }
 }