@north-light/crouter 0.3.198 → 0.3.199

package/dist/pages/types.js

@@ -1,23 +0,0 @@
-/**
- * The response contract the page bundle produces, as plain browser-safe types.
- *
- * These mirror `src/core/human/page-schema.ts` field-for-field — `commentSchema`,
- * `commentAnchorSchema`, and the four `*ResponseSchema`s — and are deliberately a
- * separate declaration rather than an import: nothing under `src/pages/` may reach
- * a runtime package (zod) or a module outside this directory, because the bundle is
- * a browser IIFE. The schemas remain the source of truth; a change there is a change
- * that must land here in the same commit.
- *
- * Two rules the shapes are built around:
- *
- *  1. **One comment shape everywhere.** Every response-bearing element carries
- *     comments, and every comment is `{ id, anchor, text }`. A comment on an option,
- *     a table row, a card, or a range of prose differs only in its `anchor`.
- *  2. **Selection is ids, never indexes or values.** The agent authored the ids it is
- *     asking about, so the response keys straight off them.
- *
- * Config types are NOT here: a config is one element's private input, mirrored in that
- * element's own module. A response is what crosses `window.crtr.respond`, so it is
- * shared.
- */
-export {};