@elytracms/studio 0.0.91 → 0.0.93

package/dist/components/cms/use-save-mode.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"use-save-mode.js","sourceRoot":"","sources":["../../../src/components/cms/use-save-mode.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,SAAS,EAAE,MAAM,EAAE,MAAM,OAAO,CAAA;AAIzC;;;;;;;;;;;GAWG;AACH,MAAM,UAAU,kBAAkB,CAAC,KAAgD;IACjF,OAAO,CAAC,KAAK,CAAC,YAAY,IAAI,KAAK,CAAC,KAAK,CAAA;AAC3C,CAAC;AAED;;;;;;;;GAQG;AACH,MAAM,UAAU,WAAW,CAAC,KAK3B;IACC,MAAM,EAAE,UAAU,EAAE,KAAK,EAAE,KAAK,EAAE,MAAM,EAAE,GAAG,KAAK,CAAA;IAClD,MAAM,YAAY,GAAG,CAAC,UAAU,CAAA;IAChC,MAAM,QAAQ,GAAG,MAAM,CAAC,KAAK,CAAC,CAAA;IAC9B,QAAQ,CAAC,OAAO,GAAG,KAAK,CAAA;IACxB,MAAM,QAAQ,GAAG,MAAM,CAAC,KAAK,CAAC,CAAA;IAC9B,QAAQ,CAAC,OAAO,GAAG,KAAK,CAAA;IACxB,MAAM,SAAS,GAAG,MAAM,CAAC,MAAM,CAAC,CAAA;IAChC,SAAS,CAAC,OAAO,GAAG,MAAM,CAAA;IAC1B,MAAM,eAAe,GAAG,MAAM,CAAC,YAAY,CAAC,CAAA;IAC5C,eAAe,CAAC,OAAO,GAAG,YAAY,CAAA;IAEtC,SAAS,CAAC,GAAG,EAAE;QACb,IAAI,YAAY;YAAE,OAAM,CAAC,kDAAkD;QAC3E,IAAI,CAAC,KAAK;YAAE,OAAM;QAClB,MAAM,KAAK,GAAG,MAAM,CAAC,UAAU,CAAC,GAAG,EAAE,CAAC,SAAS,CAAC,OAAO,CAAC,IAAI,CAAC,QAAQ,CAAC,OAAO,CAAC,EAAE,IAAI,CAAC,CAAA;QACrF,OAAO,GAAG,EAAE,CAAC,MAAM,CAAC,YAAY,CAAC,KAAK,CAAC,CAAA;IACzC,CAAC,EAAE,CAAC,KAAK,EAAE,KAAK,EAAE,YAAY,CAAC,CAAC,CAAA;IAEhC,6EAA6E;IAC7E,6EAA6E;IAC7E,4EAA4E;IAC5E,SAAS,CACP,GAAG,EAAE,CAAC,GAAG,EAAE;QACT,IAAI,kBAAkB,CAAC,EAAE,YAAY,EAAE,eAAe,CAAC,OAAO,EAAE,KAAK,EAAE,QAAQ,CAAC,OAAO,EAAE,CAAC;YACxF,SAAS,CAAC,OAAO,CAAC,IAAI,CAAC,QAAQ,CAAC,OAAO,CAAC,CAAA;IAC5C,CAAC,EACD,EAAE,CACH,CAAA;IAED,OAAO,EAAE,YAAY,EAAE,CAAA;AACzB,CAAC","sourcesContent":["import { useEffect, useRef } from 'react'\nimport type { CmsDocument } from '@elytracms/core/cms-core'\nimport type { CollectionViewSource } from '@elytracms/studio/lib/collection-view/collection-view-source'\n\n/**\n * EC-225 / EC-240 — the two persistence disciplines the detail editor supports,\n * as one pure decision so the autosave scheduler and the unmount flush can never\n * diverge on WHEN a dirty draft is persisted silently:\n *\n * - A **publishing** rail AUTOSAVES: the draft persists 1s after the last edit and\n *   publish is the deliberate commit — so a dirty draft is flushed both on the\n *   debounce timer and on unmount (navigating away inside the debounce window).\n * - A **non-publishing** rail (users, EC-240) SAVES EXPLICITLY: edits stay in the\n *   draft until the Save button, and an `UnsavedChangesGuard` protects navigation —\n *   so it NEVER persists silently (returns false here).\n */\nexport function shouldPersistDraft(input: { explicitSave: boolean; dirty: boolean }): boolean {\n  return !input.explicitSave && input.dirty\n}\n\n/**\n * EC-225 autosave · EC-240 explicit save. Owns the debounced autosave timer and\n * the unmount flush for a publishing rail; a non-publishing rail persists only via\n * its Save button (the caller's `UnsavedChangesGuard` covers navigation). Refs let\n * the unmount flush read the latest values without re-subscribing.\n *\n * Returns `explicitSave` — the caller renders the Save button + guard (explicit)\n * or the autosave status text (autosave) from it.\n */\nexport function useSaveMode(input: {\n  canPublish: boolean\n  dirty: boolean\n  draft: CmsDocument\n  source: CollectionViewSource\n}): { explicitSave: boolean } {\n  const { canPublish, dirty, draft, source } = input\n  const explicitSave = !canPublish\n  const draftRef = useRef(draft)\n  draftRef.current = draft\n  const dirtyRef = useRef(dirty)\n  dirtyRef.current = dirty\n  const sourceRef = useRef(source)\n  sourceRef.current = source\n  const explicitSaveRef = useRef(explicitSave)\n  explicitSaveRef.current = explicitSave\n\n  useEffect(() => {\n    if (explicitSave) return // explicit rails persist only via the Save button\n    if (!dirty) return\n    const timer = window.setTimeout(() => sourceRef.current.save(draftRef.current), 1000)\n    return () => window.clearTimeout(timer)\n  }, [dirty, draft, explicitSave])\n\n  // Flush a still-pending AUTOSAVE edit on unmount (navigating away inside the\n  // debounce window) so nothing is lost. Explicit rails never flush silently —\n  // their `UnsavedChangesGuard` catches the navigation instead. Unmount-only.\n  useEffect(\n    () => () => {\n      if (shouldPersistDraft({ explicitSave: explicitSaveRef.current, dirty: dirtyRef.current }))\n        sourceRef.current.save(draftRef.current)\n    },\n    [],\n  )\n\n  return { explicitSave }\n}\n"]}

package/dist/lib/assets/asset-placements.d.ts

@@ -1,28 +0,0 @@
-/** The ids the field should hold next. The shape follows the field's cardinality. */
-export type AssetPlacementTarget = {
-    multiple: false;
-    id: string | null;
-} | {
-    multiple: true;
-    ids: readonly string[];
-};
-/**
- * Return the field's next value with every placement's per-use sub-fields kept.
- *
- * - **Single field.** The placement's sub-fields carry over to whatever id now fills
- *   it, so swapping the image keeps the caption. Re-picking the same id is a no-op,
- *   and `null` clears the field (`undefined`).
- * - **Multiple field.** An id the value already held keeps its entry verbatim, with
- *   its sub-fields and its form (a bare id stays bare). Entries are matched in order,
- *   so an image placed twice keeps both placements. An id the value did not hold
- *   becomes a new envelope. A held entry whose id is not in `ids` is removed, and an
- *   emptied list is ABSENT (`undefined`, EC-586), never `[]`.
- *
- * The rule carries every key except `type`/`id`, the same set that `assetSubfieldsOf`
- * reads. That includes keys the config no longer declares (AD-14: the schema is a
- * lens, so a writer never deletes what the lens does not show).
- *
- * When nothing changes it returns `current` itself (the same reference), so a caller
- * can skip the write.
- */
-export declare function carryAssetPlacements(current: unknown, next: AssetPlacementTarget): unknown;

package/dist/lib/assets/asset-placements.js

@@ -1,83 +0,0 @@
-/**
- * The per-use sub-field carry rule for an asset field's value (EC-558).
- *
- * An asset field that declares per-use sub-fields (EC-301) stores envelopes such as
- * `{ type: 'asset', id, caption }`. Those sub-fields are PLACEMENT data: they
- * describe this use of the image, not the image itself (owner ruling 2026-09-26;
- * data that describes the image belongs on the asset record's `meta`). A writer
- * that changes which image a placement shows must therefore keep the placement's
- * sub-fields. Before EC-558 only the detail editor did that. The table cell and AI
- * `updateFields` rebuilt the value from bare ids and lost them.
- *
- * {@link carryAssetPlacements} is the one declaration of that rule. Two operations
- * go through it:
- *  - **append / pick**: the table cell and the detail editor
- *    (`applyAssetSelection` / `appendAssetSelections` in
- *    `components/assets/asset-selection.ts`). The next list is the held list plus
- *    the picked ids, and a single field swaps its one placement's image.
- *  - **replace-with-list**: AI `updateFields` (`lib/ai/update-fields.ts`). The next
- *    list is the list the model sent.
- *
- * It lives in `lib/` because `lib/ai` may not import from `components/`, and both
- * sides need it. Its only dependency is `@elytracms/core/cms-core`, so the AI host
- * route pulls in nothing from the browser. Its natural home is next to `assetNode`
- * in `core/cms-core/envelopes.ts`. Move it there if a writer outside the studio
- * (import, CLI, MCP) appears.
- */
-import { assetNode, assetSubfieldsOf, readAssetId } from '@elytracms/core/cms-core';
-/**
- * A BRAND-NEW placement, which has no sub-fields yet: always the canonical envelope
- * (EC-586, ratified 2c — an asset value is `{ type: 'asset', id, … }`). There used to be
- * a second, bare spelling (`'bare'`, a plain id string) for fields without sub-fields;
- * the write lens wrapped it on save, so the in-session draft held a shape the stored one
- * did not, and a def-less "has unpublished changes" verdict read the two as different.
- */
-function newPlacement(id) {
-    return assetNode(id);
-}
-/**
- * Return the field's next value with every placement's per-use sub-fields kept.
- *
- * - **Single field.** The placement's sub-fields carry over to whatever id now fills
- *   it, so swapping the image keeps the caption. Re-picking the same id is a no-op,
- *   and `null` clears the field (`undefined`).
- * - **Multiple field.** An id the value already held keeps its entry verbatim, with
- *   its sub-fields and its form (a bare id stays bare). Entries are matched in order,
- *   so an image placed twice keeps both placements. An id the value did not hold
- *   becomes a new envelope. A held entry whose id is not in `ids` is removed, and an
- *   emptied list is ABSENT (`undefined`, EC-586), never `[]`.
- *
- * The rule carries every key except `type`/`id`, the same set that `assetSubfieldsOf`
- * reads. That includes keys the config no longer declares (AD-14: the schema is a
- * lens, so a writer never deletes what the lens does not show).
- *
- * When nothing changes it returns `current` itself (the same reference), so a caller
- * can skip the write.
- */
-export function carryAssetPlacements(current, next) {
-    if (!next.multiple) {
-        if (next.id === null)
-            return undefined;
-        // `singleAssetIdOf` tolerates a legacy one-item array on a single field, so read
-        // its placement the same way.
-        const held = Array.isArray(current) ? current[0] : current;
-        if (readAssetId(held) === next.id)
-            return current;
-        const subfields = assetSubfieldsOf(held);
-        return Object.keys(subfields).length > 0 ? assetNode(next.id, subfields) : newPlacement(next.id);
-    }
-    const held = Array.isArray(current) ? current : [];
-    const used = new Set();
-    const out = next.ids.map((id) => {
-        const index = held.findIndex((entry, i) => !used.has(i) && readAssetId(entry) === id);
-        if (index < 0)
-            return newPlacement(id);
-        used.add(index);
-        return held[index];
-    });
-    const unchanged = out.length === held.length && out.every((entry, i) => entry === held[i]);
-    if (unchanged && Array.isArray(current))
-        return current;
-    return out.length === 0 ? undefined : out;
-}
-//# sourceMappingURL=asset-placements.js.map

package/dist/lib/assets/asset-placements.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"asset-placements.js","sourceRoot":"","sources":["../../../src/lib/assets/asset-placements.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;;;;GAyBG;AACH,OAAO,EAAE,SAAS,EAAE,gBAAgB,EAAE,WAAW,EAAE,MAAM,0BAA0B,CAAA;AAOnF;;;;;;GAMG;AACH,SAAS,YAAY,CAAC,EAAU;IAC9B,OAAO,SAAS,CAAC,EAAE,CAAC,CAAA;AACtB,CAAC;AAED;;;;;;;;;;;;;;;;;;GAkBG;AACH,MAAM,UAAU,oBAAoB,CAAC,OAAgB,EAAE,IAA0B;IAC/E,IAAI,CAAC,IAAI,CAAC,QAAQ,EAAE,CAAC;QACnB,IAAI,IAAI,CAAC,EAAE,KAAK,IAAI;YAAE,OAAO,SAAS,CAAA;QACtC,iFAAiF;QACjF,8BAA8B;QAC9B,MAAM,IAAI,GAAG,KAAK,CAAC,OAAO,CAAC,OAAO,CAAC,CAAC,CAAC,CAAC,OAAO,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,OAAO,CAAA;QAC1D,IAAI,WAAW,CAAC,IAAI,CAAC,KAAK,IAAI,CAAC,EAAE;YAAE,OAAO,OAAO,CAAA;QACjD,MAAM,SAAS,GAAG,gBAAgB,CAAC,IAAI,CAAC,CAAA;QACxC,OAAO,MAAM,CAAC,IAAI,CAAC,SAAS,CAAC,CAAC,MAAM,GAAG,CAAC,CAAC,CAAC,CAAC,SAAS,CAAC,IAAI,CAAC,EAAE,EAAE,SAAS,CAAC,CAAC,CAAC,CAAC,YAAY,CAAC,IAAI,CAAC,EAAE,CAAC,CAAA;IAClG,CAAC;IAED,MAAM,IAAI,GAAG,KAAK,CAAC,OAAO,CAAC,OAAO,CAAC,CAAC,CAAC,CAAE,OAAqB,CAAC,CAAC,CAAC,EAAE,CAAA;IACjE,MAAM,IAAI,GAAG,IAAI,GAAG,EAAU,CAAA;IAC9B,MAAM,GAAG,GAAG,IAAI,CAAC,GAAG,CAAC,GAAG,CAAC,CAAC,EAAE,EAAE,EAAE;QAC9B,MAAM,KAAK,GAAG,IAAI,CAAC,SAAS,CAAC,CAAC,KAAK,EAAE,CAAC,EAAE,EAAE,CAAC,CAAC,IAAI,CAAC,GAAG,CAAC,CAAC,CAAC,IAAI,WAAW,CAAC,KAAK,CAAC,KAAK,EAAE,CAAC,CAAA;QACrF,IAAI,KAAK,GAAG,CAAC;YAAE,OAAO,YAAY,CAAC,EAAE,CAAC,CAAA;QACtC,IAAI,CAAC,GAAG,CAAC,KAAK,CAAC,CAAA;QACf,OAAO,IAAI,CAAC,KAAK,CAAC,CAAA;IACpB,CAAC,CAAC,CAAA;IACF,MAAM,SAAS,GAAG,GAAG,CAAC,MAAM,KAAK,IAAI,CAAC,MAAM,IAAI,GAAG,CAAC,KAAK,CAAC,CAAC,KAAK,EAAE,CAAC,EAAE,EAAE,CAAC,KAAK,KAAK,IAAI,CAAC,CAAC,CAAC,CAAC,CAAA;IAC1F,IAAI,SAAS,IAAI,KAAK,CAAC,OAAO,CAAC,OAAO,CAAC;QAAE,OAAO,OAAO,CAAA;IACvD,OAAO,GAAG,CAAC,MAAM,KAAK,CAAC,CAAC,CAAC,CAAC,SAAS,CAAC,CAAC,CAAC,GAAG,CAAA;AAC3C,CAAC","sourcesContent":["/**\n * The per-use sub-field carry rule for an asset field's value (EC-558).\n *\n * An asset field that declares per-use sub-fields (EC-301) stores envelopes such as\n * `{ type: 'asset', id, caption }`. Those sub-fields are PLACEMENT data: they\n * describe this use of the image, not the image itself (owner ruling 2026-09-26;\n * data that describes the image belongs on the asset record's `meta`). A writer\n * that changes which image a placement shows must therefore keep the placement's\n * sub-fields. Before EC-558 only the detail editor did that. The table cell and AI\n * `updateFields` rebuilt the value from bare ids and lost them.\n *\n * {@link carryAssetPlacements} is the one declaration of that rule. Two operations\n * go through it:\n *  - **append / pick**: the table cell and the detail editor\n *    (`applyAssetSelection` / `appendAssetSelections` in\n *    `components/assets/asset-selection.ts`). The next list is the held list plus\n *    the picked ids, and a single field swaps its one placement's image.\n *  - **replace-with-list**: AI `updateFields` (`lib/ai/update-fields.ts`). The next\n *    list is the list the model sent.\n *\n * It lives in `lib/` because `lib/ai` may not import from `components/`, and both\n * sides need it. Its only dependency is `@elytracms/core/cms-core`, so the AI host\n * route pulls in nothing from the browser. Its natural home is next to `assetNode`\n * in `core/cms-core/envelopes.ts`. Move it there if a writer outside the studio\n * (import, CLI, MCP) appears.\n */\nimport { assetNode, assetSubfieldsOf, readAssetId } from '@elytracms/core/cms-core'\n\n/** The ids the field should hold next. The shape follows the field's cardinality. */\nexport type AssetPlacementTarget =\n  | { multiple: false; id: string | null }\n  | { multiple: true; ids: readonly string[] }\n\n/**\n * A BRAND-NEW placement, which has no sub-fields yet: always the canonical envelope\n * (EC-586, ratified 2c — an asset value is `{ type: 'asset', id, … }`). There used to be\n * a second, bare spelling (`'bare'`, a plain id string) for fields without sub-fields;\n * the write lens wrapped it on save, so the in-session draft held a shape the stored one\n * did not, and a def-less \"has unpublished changes\" verdict read the two as different.\n */\nfunction newPlacement(id: string): unknown {\n  return assetNode(id)\n}\n\n/**\n * Return the field's next value with every placement's per-use sub-fields kept.\n *\n * - **Single field.** The placement's sub-fields carry over to whatever id now fills\n *   it, so swapping the image keeps the caption. Re-picking the same id is a no-op,\n *   and `null` clears the field (`undefined`).\n * - **Multiple field.** An id the value already held keeps its entry verbatim, with\n *   its sub-fields and its form (a bare id stays bare). Entries are matched in order,\n *   so an image placed twice keeps both placements. An id the value did not hold\n *   becomes a new envelope. A held entry whose id is not in `ids` is removed, and an\n *   emptied list is ABSENT (`undefined`, EC-586), never `[]`.\n *\n * The rule carries every key except `type`/`id`, the same set that `assetSubfieldsOf`\n * reads. That includes keys the config no longer declares (AD-14: the schema is a\n * lens, so a writer never deletes what the lens does not show).\n *\n * When nothing changes it returns `current` itself (the same reference), so a caller\n * can skip the write.\n */\nexport function carryAssetPlacements(current: unknown, next: AssetPlacementTarget): unknown {\n  if (!next.multiple) {\n    if (next.id === null) return undefined\n    // `singleAssetIdOf` tolerates a legacy one-item array on a single field, so read\n    // its placement the same way.\n    const held = Array.isArray(current) ? current[0] : current\n    if (readAssetId(held) === next.id) return current\n    const subfields = assetSubfieldsOf(held)\n    return Object.keys(subfields).length > 0 ? assetNode(next.id, subfields) : newPlacement(next.id)\n  }\n\n  const held = Array.isArray(current) ? (current as unknown[]) : []\n  const used = new Set<number>()\n  const out = next.ids.map((id) => {\n    const index = held.findIndex((entry, i) => !used.has(i) && readAssetId(entry) === id)\n    if (index < 0) return newPlacement(id)\n    used.add(index)\n    return held[index]\n  })\n  const unchanged = out.length === held.length && out.every((entry, i) => entry === held[i])\n  if (unchanged && Array.isArray(current)) return current\n  return out.length === 0 ? undefined : out\n}\n"]}

package/dist/lib/cms/document-gate.d.ts

@@ -1,47 +0,0 @@
-import type { CmsDocument, CmsValidationIssue } from '@elytracms/core/cms-core';
-/**
- * The publish-gate seam (EC-497) — a framework-free module store, the same shape
- * as the current-document seam (`lib/ai-current-document`).
- *
- * `createOperations` is a module singleton built long before (and independently
- * of) any React tree, while gate-strength validation needs the live CMS session:
- * its document store, its asset oracle, its published-ness pointer. So the CMS
- * session PUBLISHES a validator here while mounted, and
- * `createStudioOperations` hands this module's reader to the operations layer
- * once, at bootstrap.
- *
- * **EC-546 — a gate that cannot see says so.** The first cut had the reader return
- * `undefined` with nothing registered, meaning "no session context here", and
- * the operations gate answered that by falling back to an optionless
- * `validateDocument` over the adapter's schema record: scalar rules only, no
- * store, no locale config, no composition or embed leash. Measured: a document
- * carrying a component outside its slot's `allow` published through
- * `createStudioOperations` whenever the stack was empty. That is the exact
- * weaker, mode-dependent gate EC-497 removed, kept alive by a mount-state side
- * channel. So the reader now answers with issues ONLY: with nothing registered it
- * returns one blocking `error` issue — the publish is refused and the refusal is
- * visible — and the operations layer no longer has a fallback to take (its
- * `DocumentValidator` cannot return `undefined`).
- *
- * This module imports nothing but types, so hanging the seam off it never drags
- * the CMS session (or the component registry behind the composition validators)
- * into the operations bootstrap's module graph.
- */
-export type SessionDocumentValidator = (document: CmsDocument) => readonly CmsValidationIssue[];
-/** The catalog key of the refusal the reader emits with no session mounted (EC-546). */
-export declare const NO_VALIDATION_SESSION_MESSAGE_KEY = "cms.issueMessage.noValidationSession";
-/** Publish the session's canonical document validator (`null` clears the stack). */
-export declare function setSessionDocumentValidator(next: SessionDocumentValidator | null): void;
-/**
- * Remove this validator — the unmount race guard. Removing an INNER session
- * leaves the outer one in place; removing one that already left is a no-op (a
- * remount registers the new validator before the old effect's cleanup runs).
- */
-export declare function clearSessionDocumentValidator(owned: SessionDocumentValidator): void;
-/**
- * The reader handed to `createOperations`. The innermost session's verdict, or —
- * with no session mounted — the blocking refusal described on
- * {@link SessionDocumentValidator}. Never `undefined`: the operations layer's
- * `DocumentValidator` has no fallback to offer and no longer accepts one (EC-546).
- */
-export declare function sessionValidateDocument(document: CmsDocument): readonly CmsValidationIssue[];

package/dist/lib/cms/document-gate.js

@@ -1,61 +0,0 @@
-/**
- * Registered sessions, innermost LAST — a stack, not a single slot, because more
- * than one `CmsProvider` can be mounted at a time: the "Use in document…"
- * transfer dialog mounts its own over the app's
- * (`components/transfer-dialog.tsx:92`). With a single slot, closing that dialog
- * would clear the seam and silently drop the publish gate back to its fallback
- * for the rest of the app's life — a regression invisible until something
- * published. Popping restores the outer session instead.
- */
-const registered = [];
-/** The catalog key of the refusal the reader emits with no session mounted (EC-546). */
-export const NO_VALIDATION_SESSION_MESSAGE_KEY = 'cms.issueMessage.noValidationSession';
-/**
- * The verdict with no session mounted: one blocking issue, never a pass and never
- * `undefined`. `custom-validation` is the code for a rule the engine's field
- * vocabulary does not name — this is a host rule ("publish only through a mounted
- * session"), not a finding about the document — and the message carries the
- * meaning. Published via the same `messageRef` the engine's issues use, so the
- * studio's operation-error banner renders it in the active locale (EC-494).
- */
-const NO_SESSION_REFUSAL = [
-    {
-        code: 'custom-validation',
-        severity: 'error',
-        message: 'No validation session is mounted — refusing to publish unvalidated.',
-        messageRef: { key: NO_VALIDATION_SESSION_MESSAGE_KEY },
-        path: [],
-    },
-];
-/** Publish the session's canonical document validator (`null` clears the stack). */
-export function setSessionDocumentValidator(next) {
-    if (next === null) {
-        registered.length = 0;
-        return;
-    }
-    const at = registered.indexOf(next);
-    if (at >= 0)
-        registered.splice(at, 1);
-    registered.push(next);
-}
-/**
- * Remove this validator — the unmount race guard. Removing an INNER session
- * leaves the outer one in place; removing one that already left is a no-op (a
- * remount registers the new validator before the old effect's cleanup runs).
- */
-export function clearSessionDocumentValidator(owned) {
-    const at = registered.indexOf(owned);
-    if (at >= 0)
-        registered.splice(at, 1);
-}
-/**
- * The reader handed to `createOperations`. The innermost session's verdict, or —
- * with no session mounted — the blocking refusal described on
- * {@link SessionDocumentValidator}. Never `undefined`: the operations layer's
- * `DocumentValidator` has no fallback to offer and no longer accepts one (EC-546).
- */
-export function sessionValidateDocument(document) {
-    const session = registered.at(-1);
-    return session ? session(document) : NO_SESSION_REFUSAL;
-}
-//# sourceMappingURL=document-gate.js.map

package/dist/lib/cms/document-gate.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"document-gate.js","sourceRoot":"","sources":["../../../src/lib/cms/document-gate.ts"],"names":[],"mappings":"AAgCA;;;;;;;;GAQG;AACH,MAAM,UAAU,GAA+B,EAAE,CAAA;AAEjD,wFAAwF;AACxF,MAAM,CAAC,MAAM,iCAAiC,GAAG,sCAAsC,CAAA;AAEvF;;;;;;;GAOG;AACH,MAAM,kBAAkB,GAAkC;IACxD;QACE,IAAI,EAAE,mBAAmB;QACzB,QAAQ,EAAE,OAAO;QACjB,OAAO,EAAE,qEAAqE;QAC9E,UAAU,EAAE,EAAE,GAAG,EAAE,iCAAiC,EAAE;QACtD,IAAI,EAAE,EAAE;KACT;CACF,CAAA;AAED,oFAAoF;AACpF,MAAM,UAAU,2BAA2B,CAAC,IAAqC;IAC/E,IAAI,IAAI,KAAK,IAAI,EAAE,CAAC;QAClB,UAAU,CAAC,MAAM,GAAG,CAAC,CAAA;QACrB,OAAM;IACR,CAAC;IACD,MAAM,EAAE,GAAG,UAAU,CAAC,OAAO,CAAC,IAAI,CAAC,CAAA;IACnC,IAAI,EAAE,IAAI,CAAC;QAAE,UAAU,CAAC,MAAM,CAAC,EAAE,EAAE,CAAC,CAAC,CAAA;IACrC,UAAU,CAAC,IAAI,CAAC,IAAI,CAAC,CAAA;AACvB,CAAC;AAED;;;;GAIG;AACH,MAAM,UAAU,6BAA6B,CAAC,KAA+B;IAC3E,MAAM,EAAE,GAAG,UAAU,CAAC,OAAO,CAAC,KAAK,CAAC,CAAA;IACpC,IAAI,EAAE,IAAI,CAAC;QAAE,UAAU,CAAC,MAAM,CAAC,EAAE,EAAE,CAAC,CAAC,CAAA;AACvC,CAAC;AAED;;;;;GAKG;AACH,MAAM,UAAU,uBAAuB,CAAC,QAAqB;IAC3D,MAAM,OAAO,GAAG,UAAU,CAAC,EAAE,CAAC,CAAC,CAAC,CAAC,CAAA;IACjC,OAAO,OAAO,CAAC,CAAC,CAAC,OAAO,CAAC,QAAQ,CAAC,CAAC,CAAC,CAAC,kBAAkB,CAAA;AACzD,CAAC","sourcesContent":["import type { CmsDocument, CmsValidationIssue } from '@elytracms/core/cms-core'\n\n/**\n * The publish-gate seam (EC-497) — a framework-free module store, the same shape\n * as the current-document seam (`lib/ai-current-document`).\n *\n * `createOperations` is a module singleton built long before (and independently\n * of) any React tree, while gate-strength validation needs the live CMS session:\n * its document store, its asset oracle, its published-ness pointer. So the CMS\n * session PUBLISHES a validator here while mounted, and\n * `createStudioOperations` hands this module's reader to the operations layer\n * once, at bootstrap.\n *\n * **EC-546 — a gate that cannot see says so.** The first cut had the reader return\n * `undefined` with nothing registered, meaning \"no session context here\", and\n * the operations gate answered that by falling back to an optionless\n * `validateDocument` over the adapter's schema record: scalar rules only, no\n * store, no locale config, no composition or embed leash. Measured: a document\n * carrying a component outside its slot's `allow` published through\n * `createStudioOperations` whenever the stack was empty. That is the exact\n * weaker, mode-dependent gate EC-497 removed, kept alive by a mount-state side\n * channel. So the reader now answers with issues ONLY: with nothing registered it\n * returns one blocking `error` issue — the publish is refused and the refusal is\n * visible — and the operations layer no longer has a fallback to take (its\n * `DocumentValidator` cannot return `undefined`).\n *\n * This module imports nothing but types, so hanging the seam off it never drags\n * the CMS session (or the component registry behind the composition validators)\n * into the operations bootstrap's module graph.\n */\nexport type SessionDocumentValidator = (document: CmsDocument) => readonly CmsValidationIssue[]\n\n/**\n * Registered sessions, innermost LAST — a stack, not a single slot, because more\n * than one `CmsProvider` can be mounted at a time: the \"Use in document…\"\n * transfer dialog mounts its own over the app's\n * (`components/transfer-dialog.tsx:92`). With a single slot, closing that dialog\n * would clear the seam and silently drop the publish gate back to its fallback\n * for the rest of the app's life — a regression invisible until something\n * published. Popping restores the outer session instead.\n */\nconst registered: SessionDocumentValidator[] = []\n\n/** The catalog key of the refusal the reader emits with no session mounted (EC-546). */\nexport const NO_VALIDATION_SESSION_MESSAGE_KEY = 'cms.issueMessage.noValidationSession'\n\n/**\n * The verdict with no session mounted: one blocking issue, never a pass and never\n * `undefined`. `custom-validation` is the code for a rule the engine's field\n * vocabulary does not name — this is a host rule (\"publish only through a mounted\n * session\"), not a finding about the document — and the message carries the\n * meaning. Published via the same `messageRef` the engine's issues use, so the\n * studio's operation-error banner renders it in the active locale (EC-494).\n */\nconst NO_SESSION_REFUSAL: readonly CmsValidationIssue[] = [\n  {\n    code: 'custom-validation',\n    severity: 'error',\n    message: 'No validation session is mounted — refusing to publish unvalidated.',\n    messageRef: { key: NO_VALIDATION_SESSION_MESSAGE_KEY },\n    path: [],\n  },\n]\n\n/** Publish the session's canonical document validator (`null` clears the stack). */\nexport function setSessionDocumentValidator(next: SessionDocumentValidator | null): void {\n  if (next === null) {\n    registered.length = 0\n    return\n  }\n  const at = registered.indexOf(next)\n  if (at >= 0) registered.splice(at, 1)\n  registered.push(next)\n}\n\n/**\n * Remove this validator — the unmount race guard. Removing an INNER session\n * leaves the outer one in place; removing one that already left is a no-op (a\n * remount registers the new validator before the old effect's cleanup runs).\n */\nexport function clearSessionDocumentValidator(owned: SessionDocumentValidator): void {\n  const at = registered.indexOf(owned)\n  if (at >= 0) registered.splice(at, 1)\n}\n\n/**\n * The reader handed to `createOperations`. The innermost session's verdict, or —\n * with no session mounted — the blocking refusal described on\n * {@link SessionDocumentValidator}. Never `undefined`: the operations layer's\n * `DocumentValidator` has no fallback to offer and no longer accepts one (EC-546).\n */\nexport function sessionValidateDocument(document: CmsDocument): readonly CmsValidationIssue[] {\n  const session = registered.at(-1)\n  return session ? session(document) : NO_SESSION_REFUSAL\n}\n"]}