@noy-db/hub 0.2.0-pre.30 → 0.2.0-pre.31

package/dist/util/index.d.cts

@@ -1,79 +0,0 @@
-export { i as isDiscriminant } from '../discriminant-BN9REW3o.cjs';
-
-/**
- * Target-profile aware filename sanitizer.
- *
- * Pure string in / string out. No filesystem access, no I/O. Use this
- * at the boundary where a user-supplied filename meets a storage
- * destination — local FS, ZIP archive, S3 key, URL path, SMB share —
- * to defuse the canonical 14-class footgun before it reaches that
- * destination.
- *
- * ## Threat model
- *
- *   1. Path injection — `..`, NUL bytes, `\` on POSIX, absolute paths.
- *   2. Windows reserved names — `CON`, `PRN`, `AUX`, `NUL`,
- *      `COM1-9`, `LPT1-9`, with or without an extension.
- *   3. Windows reserved chars — `< > : " / \ | ? *` plus ASCII 0-31.
- *   4. Trailing `.` and ` ` on Windows / SMB.
- *   5. Unicode normalization drift — same display, different bytes →
- *      "two files with the same name" sync ghosts.
- *   6. Bidi override spoofing — U+202E reversing `harmless.exe.txt`
- *      into `harmless.txt.exe`.
- *   7. URL `+` ambiguity in S3 presigned URLs.
- *   8. ZIP general-purpose-flag bit 11 (UTF-8 filename) optional in
- *      pre-2006 readers.
- *   9-14. Length caps, leading/trailing whitespace + controls,
- *      `.DS_Store`-style hidden noise, etc.
- *
- * ## Always-on transforms (every profile)
- *
- *   - NFC normalize (`String.prototype.normalize('NFC')`).
- *   - Reject NUL — hard fail, not strip. Silent strip enables a
- *     classic truncation bypass (`safe.txt\0.exe` → `safe.txt`).
- *   - Strip bidi overrides (`U+202A..U+202E`, `U+2066..U+2069`).
- *   - Trim leading/trailing whitespace and ASCII control chars.
- *
- * ## Non-goals (i18n boundary policy, )
- *
- *   - No transliteration.
- *   - No locale-aware slugging.
- *   - No script-specific segmentation.
- *
- * @module
- */
-/**
- * One of seven storage destinations the sanitizer knows how to defang
- * for. Pick the most restrictive that covers your write site:
- * `'macos-smb'` is the safe default for "I don't know where these
- * files end up but they're going to a real filesystem somewhere."
- */
-type FilenameProfile = 'posix' | 'windows' | 'macos-smb' | 'zip' | 'url-path' | 's3-key' | 'opaque';
-interface SanitizeFilenameOptions {
-    /** Target-destination profile. */
-    readonly profile: FilenameProfile;
-    /**
-     * Override the per-profile length cap. Useful when leaving headroom
-     * for a collision suffix — e.g. `maxBytes: 240` on a `posix` write
-     * site that wants 15 bytes of slack for `-1`, `-2`, …
-     */
-    readonly maxBytes?: number;
-    /**
-     * Required when `profile === 'opaque'`. The opaque profile replaces
-     * the entire input with `${opaqueId}.${ext}` (extension preserved
-     * from the input when present).
-     */
-    readonly opaqueId?: string;
-}
-/**
- * Sanitize a filename for a target-destination profile. Pure: same
- * input + options always returns the same output, no I/O.
- *
- * Returns the sanitized name. Throws {@link FilenameSanitizationError}
- * when the input cannot be made safe at all (NUL byte, empty after
- * normalization, missing `opaqueId` for the opaque profile,
- * `..` segment that would fall out of any reasonable target).
- */
-declare function sanitizeFilename(name: string, opts: SanitizeFilenameOptions): string;
-
-export { type FilenameProfile, type SanitizeFilenameOptions, sanitizeFilename };

package/dist/with-materialized-view-DfgPcvi9.d.cts

@@ -1,27 +0,0 @@
-import { aK as MaterializedViewStrategy, aL as MaterializedViewStrategyHandle } from './types-CdVfiQgt.cjs';
-
-/**
- * Register a materialized view: a declared query whose result is
- * persisted as a queryable collection and kept fresh as sources
- * change. Writes go through the standard `Collection.put` pipeline;
- * refresh-driven deletes route through `Collection._internalDelete` so
- * user `onDelete` guards on the output collection aren't tripped by
- * housekeeping.
- *
- * Two registration modes:
- *   - **single-source** — declare `query: (db) => Query<TRow>`; the
- *     dependency analyzer derives source collections from the plan.
- *   - **UNION** — declare `unionSources: [{ collection, map }, ...]`
- *     plus optional `groupBy` + `aggregate`; the executor reads each
- *     arm, maps to the unified row shape, concatenates, then groups
- *     and aggregates.
- *
- * The two modes are mutually exclusive — exactly one of `query` /
- * `unionSources` must be set at registration time.
- *
- * See docs/superpowers/specs/2026-05-20-dim14-mv-v2-design.md (single-source v2)
- * and docs/superpowers/specs/2026-05-21-dim14-mv-multikey-and-union.md (UNION).
- */
-declare function withMaterializedView<TRow extends Record<string, unknown>>(spec: MaterializedViewStrategy<TRow>): MaterializedViewStrategyHandle;
-
-export { withMaterializedView as w };

package/dist/with-overlayed-view-Cvfkx1lg.d.cts

@@ -1,13 +0,0 @@
-import { aM as OverlayedViewStrategy, aR as OverlayedViewStrategyHandle } from './types-CdVfiQgt.cjs';
-
-/**
- * Register a read-shadow overlay: bind an MV-owned base collection to
- * a user-writable overlay so consumers can express operator-editable
- * lifecycles as one declarative block (MV v2 spec § Composition
- * with operator-editable lifecycle).
- *
- * See docs/superpowers/specs/2026-05-20-dim14-mv-v2-design.md.
- */
-declare function withOverlayedView(spec: OverlayedViewStrategy): OverlayedViewStrategyHandle;
-
-export { withOverlayedView as w };

package/dist/with-rollup-nIxo7h9z.d.cts

@@ -1,47 +0,0 @@
-import { aC as DerivationStrategy, aG as DerivationStrategyHandle } from './types-CdVfiQgt.cjs';
-
-/**
- * Register a deterministic derivation: one source collection → one or
- * more typed outputs, computed by the user's `derive` function on
- * plaintext after DEK unwrap. Outputs are encrypted with the same DEK
- * as the source and written via the standard `Collection.put` path.
- *
- * See docs/superpowers/specs/2026-05-01-dim14-derivation-v1-design.md.
- */
-declare function withDerivation<TSource extends Record<string, unknown>, TOutputs extends Record<string, Record<string, unknown>>>(spec: DerivationStrategy<TSource, TOutputs>): DerivationStrategyHandle;
-
-/**
- * `withRollup` — aggregate many child records onto a single field of their
- * parent (#376 slice 2). The reverse of a join: instead of reading children
- * on demand, the parent carries a maintained summary.
- *
- * ```ts
- * withRollup<Sale, Buyer>({
- *   from: 'sales',          // child collection (the trigger)
- *   key: 'buyerId',         // FK on the child → parent id
- *   into: 'buyers',         // parent collection
- *   field: 'revenueByYear', // field on the parent to maintain
- *   compute: (sales) => groupSumByYear(sales, 'total'),
- * })
- * ```
- *
- * On every write OR delete of a `from` record, the parent at id `child[key]`
- * is recomputed: `compute(allChildren where child[key] === parentId)` is
- * patched onto `parent[field]`. A parent write also recomputes its own
- * aggregate (so a parent created after its children still fills in). Only the
- * `field` is touched — the rest of the parent record is never clobbered — and
- * a value-equality guard suppresses no-op writes. The aggregate is gap-free
- * with respect to child inserts, updates, and deletes.
- *
- * Desugars to a `withDerivation` strategy carrying a `rollup` marker; dispatch
- * handles it without invoking the executor. Eager-only in this slice.
- */
-declare function withRollup<TChild extends Record<string, unknown> = Record<string, unknown>, TParent extends Record<string, unknown> = Record<string, unknown>>(config: {
-    from: string;
-    key: keyof TChild & string;
-    into: string;
-    field: keyof TParent & string;
-    compute: (children: TChild[]) => unknown;
-}): DerivationStrategyHandle;
-
-export { withRollup as a, withDerivation as w };