canopycms 0.0.67-int.90 → 0.0.67

package/dist/schema/types.d.ts

@@ -13,14 +13,10 @@ export type EntrySchemaRegistry = Record<string, EntrySchema>;
 export interface SchemaSourceInfo {
     /** File path relative to content root */
     path: string;
-    /** Type of schema source */
     type: 'root' | 'collection';
     /** Collection names defined in this source */
     collections: string[];
 }
-/**
- * Result of schema resolution.
- */
 export interface SchemaResolutionResult {
     /** Resolved schema ready for use */
     schema: RootCollectionConfig;

package/dist/server.d.ts

@@ -5,22 +5,17 @@ export * from './context.js';
 export { operatingStrategy } from './operating-mode/index.js';
 export * from './authorization/groups/index.js';
 /**
- * One-call factory for a **build/admin** Canopy context — for standalone
- * scripts that run entirely outside a Next.js request or build phase (index
- * builders, content audits, codegen, ad hoc reports). Reads the filesystem
- * directly as a synthetic admin user and bypasses ALL branch/path ACLs —
- * never use it in request-handling code. See the source JSDoc for the full
- * security note and the `createNextCanopyContext().getCanopyForBuild()`
- * comparison this mirrors.
+ * One-call factory for a **build/admin** Canopy context, for standalone scripts outside a
+ * Next.js request or build phase. Reads the filesystem as a synthetic admin user and bypasses
+ * ALL branch/path ACLs — never use it in request-handling code. Full security note in the
+ * source JSDoc.
  */
 export { createBuildCanopy, type CreateBuildCanopyOptions } from './build-canopy.js';
 /**
- * Resolve a CanopyUser for a request: loads internal groups from the
- * settings workspace (the single source of truth — never a content branch
- * clone) and merges them into an auth-plugin result via
- * `authResultToCanopyUser`. Shared by the core HTTP handler and the Next.js
- * SSR wrapper so the "authenticate -> load groups -> merge" pipeline can't
- * drift between the two again.
+ * Resolve a CanopyUser for a request: loads internal groups from the settings workspace (the
+ * single source of truth — never a content branch clone) and merges them into an auth-plugin
+ * result via `authResultToCanopyUser`. Shared by the core HTTP handler and the Next.js SSR
+ * wrapper so the "authenticate -> load groups -> merge" pipeline cannot drift between them.
  */
 export { resolveCanopyUser, type ResolveCanopyUserDeps } from './resolve-canopy-user.js';
 export * from './branch-workspace.js';
@@ -28,44 +23,31 @@ export * from './content-store.js';
 export { loadCollectionMetaFiles, resolveCollectionReferences, watchCollectionMetaFiles, resolveSchema, } from './schema/index.js';
 export type { CollectionMeta, RootCollectionMeta } from './schema/index.js';
 /**
- * Create a type-safe entry schema registry with runtime validation.
- *
- * Maps each entry-type's name to its `EntrySchema`. Keys are referenced by
- * `.collection.json` files via the `entry.schema` property. Recommended
- * convention is to key by entry-type name (filename token, also the value of
- * `meta.entryType` in tree-builder callbacks) — that way
- * `EntryTypesFromRegistry<typeof yourRegistry>` derives the
- * discriminated-union map for `buildContentTree`'s `TEntryTypes` parameter
- * automatically. See `createEntrySchemaRegistry`'s source-file JSDoc for the
- * full example.
+ * Create a type-safe entry schema registry with runtime validation. Keys are the strings
+ * `.collection.json` files reference via `entry.schema`; key them by entry-type name so
+ * `EntryTypesFromRegistry<typeof yourRegistry>` derives `buildContentTree`'s `TEntryTypes` map.
+ * Source JSDoc has the example and the full validation list.
  */
 export { createEntrySchemaRegistry } from './entry-schema-registry.js';
 /**
- * Validate that entry-schema references in `.collection.json` files exist in
- * the registry. Useful at build time to fail fast on stale references rather
- * than at request time.
+ * Validate that entry-schema references in `.collection.json` files exist in the registry —
+ * at build time, so a stale reference fails there rather than at request time.
  */
 export { validateEntrySchemaRegistry } from './entry-schema-registry.js';
 /**
- * Derive a discriminated-union entry-type map from a registry value. Pass
- * `typeof entrySchemaRegistry` as the type argument. The registry must be
- * keyed by entry-type name for the result to plug straight into
- * `buildContentTree`'s `TEntryTypes` generic.
+ * Derive a discriminated-union entry-type map from a registry value: pass
+ * `typeof entrySchemaRegistry`. The registry must be keyed by entry-type name for the result
+ * to plug straight into `buildContentTree`'s `TEntryTypes` generic.
  */
 export type { EntryTypesFromRegistry } from './entry-schema.js';
 /**
- * Resolve a display title for an entry using the full fallback chain: a
- * schema-marked `isTitle` field, then `data.title`/`data.name`, then an
- * entry-type label, then a humanized slug, then `"Untitled"`. Useful
- * anywhere an entry needs a display title without re-deriving this chain —
- * search-document/index builders in particular, since a search UI needs a
- * title for every result regardless of which field the schema uses.
+ * Resolve an entry's display title through the full fallback chain: a schema-marked `isTitle`
+ * field, then `data.title`/`data.name`, then an entry-type label, then a humanized slug, then
+ * `"Untitled"`. Search-document and index builders in particular need a title for every result
+ * regardless of which field the schema uses.
  *
- * Client-safe (no dependencies beyond `FieldConfig`/`InlineGroupFieldConfig`
- * type imports, which are erased at compile time) — also re-exported from
- * the root `canopycms` entry for that reason. Exported here too because
- * build/admin scripts (the primary reason this was unreachable before) are
- * more likely to `import` from `canopycms/server` than the root entry.
+ * Client-safe (its only imports are types, erased at compile time), so it is exported from the
+ * root `canopycms` entry as well as here, where build/admin scripts look for it.
  */
 export { resolveEntryTitle } from './utils/title-field.js';
 /** Generate a Canopy-format 12-character Base58 content ID. */
@@ -73,47 +55,41 @@ export { generateId } from './id.js';
 /** Returns true if a string is a valid 12-character Base58 Canopy ID. */
 export { isValidId } from './id.js';
 /**
- * Build a hierarchical tree of content nodes from the schema and filesystem.
- *
- * Pass `TEntryTypes` (typically `EntryTypesFromRegistry<typeof entrySchemaRegistry>`)
- * to get narrowed access to `meta.indexEntry.data` after switching on
- * `meta.entryType` in your `extract` callback.
- *
- * Adopters using `canopycms-next` typically call `canopy.buildContentTree(...)`
- * via `getCanopyForBuild()` rather than the bare function.
+ * Build a hierarchical tree of content nodes from the schema and filesystem. Pass `TEntryTypes`
+ * (typically `EntryTypesFromRegistry<typeof entrySchemaRegistry>`) for narrowed access to
+ * `meta.indexEntry.data` after switching on `meta.entryType` in an `extract` callback.
+ * `canopycms-next` adopters usually call `canopy.buildContentTree(...)` via
+ * `getCanopyForBuild()` instead of the bare function.
  */
 export { buildContentTree } from './content-tree.js';
 export type { ContentTreeNode, BuildContentTreeOptions, ContentTreeExtractMeta, EntryTypeMap, DefaultEntryTypes, } from './content-tree.js';
 /**
- * `buildContentTree`'s default URL path builder: strips the `{contentRootName}/`
- * prefix, collapses an entry's `index` slug to its parent collection's path, and
- * lowercases the result. Call it from inside a custom `buildPath` to extend the
- * default rather than reimplement it — `buildContentTree`'s `buildPath` option
- * replaces the default outright, it does not compose with it.
+ * `buildContentTree`'s default URL path builder: strips the `{contentRootName}/` prefix,
+ * collapses an entry's `index` slug to its parent collection's path, and lowercases the result.
+ * Call it from inside a custom `buildPath` rather than reimplementing it — the `buildPath`
+ * option REPLACES the default outright, it does not compose with it.
  */
 export { defaultBuildPath } from './content-tree.js';
 /** List all content entries as a flat array. */
 export { listEntries } from './content-listing.js';
 export type { ListEntriesItem, ListEntriesOptions } from './content-listing.js';
 /**
- * Parse a content filename of the form `{type}.{slug}.{id}.{ext}` into its
- * `{ type, slug, id }` parts. `id` must be a valid 12-character Base58 content ID
- * (excludes the ambiguous characters `0`, `O`, `I`, `l`) or the parse fails.
- * Pass `entryTypes` to also require `type` to match a known entry-type name;
- * omit it to parse the filename shape without that check. See the source JSDoc
- * for the full filename grammar.
+ * Parse a content filename `{type}.{slug}.{id}.{ext}` into `{ type, slug, id }`. `id` must be a
+ * valid 12-character Base58 content ID (no ambiguous `0`, `O`, `I`, `l`) or the parse fails.
+ * Pass `entryTypes` to also require `type` to match a known entry-type name. Full grammar in
+ * the source JSDoc.
  */
 export { parseTypedFilename } from './content-listing.js';
 /**
  * Resolve a canopy entry-link to its URL. Pair with the field-walker variants
- * (`resolveEntryLinksInText`, `resolveEntryLinksInData`) when rendering MDX
- * bodies or arbitrary frontmatter that may contain link tokens.
+ * (`resolveEntryLinksInText`, `resolveEntryLinksInData`) when rendering MDX bodies or
+ * frontmatter that may contain link tokens.
  */
 export { resolveEntryUrl, resolveEntryLinksInText, resolveEntryLinksInData, extractEntryLinkIds, } from './entry-link-resolver.js';
 export type { EntryLinkUrlResolver } from './entry-link-resolver.js';
 /**
- * Compute the canonical URL for an entry given its logical path + slug, and the shared
- * "is this the collection-index slug?" predicate that decides whether it collapses.
+ * The canonical URL for an entry from its logical path + slug, plus the shared "is this the
+ * collection-index slug?" predicate that decides whether it collapses.
  */
 export { computeEntryUrl, isIndexSlug } from './utils/entry-url.js';
 /** Collect static paths for `generateStaticParams` / sitemap emission. */
@@ -124,65 +100,58 @@ export { collectRoutableEntries } from './static/index.js';
 export type { RoutableEntry, CollectRoutableEntriesOptions } from './static/index.js';
 /**
  * Find every URL claimed by more than one entry — the check a production build already runs
- * (and fails on). Exported so a content-integrity test can assert it directly rather than
+ * and fails on. Exported so a content-integrity test can assert it directly instead of
  * hand-rolling the same scan over `listEntries`.
  */
 export { findDuplicateUrlPaths } from './static/index.js';
 export type { DuplicateUrlPath } from './static/index.js';
 /**
- * SEO field extraction and URL shaping (framework-agnostic). `isNoindexEntry` is the single
+ * SEO field extraction and URL shaping, framework-agnostic. `isNoindexEntry` is the single
  * predicate behind both `robots: noindex` and sitemap exclusion.
  */
 export { DEFAULT_SEO_FIELD_NAMES, extractSeoFields, isNoindexEntry, isAbsoluteUrl, withTrailingSlash, resolveSeoUrl, stripTrailingSlashes, } from './static/index.js';
 export type { SeoFields, SeoFieldNames, SeoFieldLocation, SeoOgType, SeoTwitterCard, ExtractSeoFieldsOptions, ResolveSeoUrlOptions, } from './static/index.js';
 /**
- * Start a chokidar-backed watcher that detects divergence between the dev
- * working tree and the resolved branch clone. Dev mode only.
+ * Start a chokidar-backed watcher for divergence between the dev working tree and the resolved
+ * branch clone. Dev mode only.
  */
 export { startDevContentWatcher } from './dev-content-watcher.js';
 export type { StartDevContentWatcherOptions } from './dev-content-watcher.js';
 /**
- * Instantiate the AssetStore configured by a site's `media` config
- * (`config.media`). Returns undefined when no store applies: `media` is
- * unset and no `devAssetsDir` fallback was given, `adapter: 'local'` omits
- * `directory` with no fallback, or `adapter: 'lfs'` (config literal kept,
- * not yet implemented).
+ * Instantiate the AssetStore configured by a site's `config.media`. Returns undefined when no
+ * store applies: `media` unset with no `devAssetsDir` fallback, `adapter: 'local'` without
+ * `directory` and no fallback, or `adapter: 'lfs'` (config literal kept, not yet implemented).
  */
 export { createAssetStore } from './assets/factory.js';
 /**
- * The five S3/local bucket-prefix strings (`asset-originals/`, `asset-staging/`,
- * `asset-meta/`, `assets/`, `assets/t/`). Re-exported so server-only consumers
- * outside this package - notably the prod transform Lambda
- * (`packages/canopycms-cdk/lambda/asset-transform`) - can build/parse asset
- * keys through the same constants `S3AssetStore` uses, rather than
- * duplicating the literal prefix strings.
+ * The five S3/local bucket-prefix strings (`asset-originals/`, `asset-staging/`, `asset-meta/`,
+ * `assets/`, `assets/t/`). Exported so server-only consumers outside this package — notably the
+ * prod transform Lambda (`packages/canopycms-cdk/lambda/asset-transform`) — build and parse
+ * asset keys through the same constants `S3AssetStore` uses rather than duplicating the strings.
  */
 export { ASSET_PREFIXES, type AssetPrefixes } from './assets/keys.js';
 /** Asset metadata sidecar shape (`asset-meta/{hash32}.json`), written by the finalize pipeline and read by the transform layer (dev-mode emulation and the prod transform Lambda). */
 export type { AssetMeta } from './assets/types.js';
 /**
- * Parse the three path segments after `assets/t/` (`{directives}/{hash32}/{slug}.{ext}`)
- * into a validated `TransformDirectives` set, or a structured parse error.
- * Reused unchanged by the dev-mode lazy `/assets/t/*` emulation (`api/assets.ts`)
- * and the prod transform Lambda (`packages/canopycms-cdk/lambda/asset-transform`)
- * so the URL grammar is defined in exactly one place.
+ * Parse the three path segments after `assets/t/` (`{directives}/{hash32}/{slug}.{ext}`) into a
+ * validated `TransformDirectives` set, or a structured parse error. Reused unchanged by the
+ * dev-mode lazy `/assets/t/*` emulation (`api/assets.ts`) and the prod transform Lambda, so the
+ * URL grammar is defined in exactly one place.
  */
 export { parseTransformPath } from './assets/transform-directives.js';
 export type { ParsedTransformPath, ParseTransformPathResult } from './assets/transform-directives.js';
 /**
- * Canonical string form of a `TransformDirectives` set - the cache key every
- * transform output is stored under (`assets/t/{formatDirectives(...)}/{hash32}/{slug}.{ext}`).
- * Equivalent directive sets (different key order/float formatting) always
- * format to the same string. Reused by the prod transform Lambda so its
- * canonical writes agree with the dev-mode emulation and `assetUrl()`.
+ * Canonical string form of a `TransformDirectives` set — the cache key every transform output is
+ * stored under (`assets/t/{formatDirectives(...)}/{hash32}/{slug}.{ext}`). Equivalent directive
+ * sets (different key order or float formatting) always format to the same string. Reused by the
+ * prod transform Lambda so its writes agree with the dev-mode emulation and `assetUrl()`.
  */
 export { formatDirectives } from './assets/transform-directives.js';
 /**
  * Apply a parsed `TransformDirectives` set to source image bytes with sharp:
- * resize/format/quality/crop, with EXIF stripped on every re-encode (even
- * identity). Server-only (sharp) - reused unchanged by the dev-mode lazy
- * `/assets/t/*` emulation and the prod transform Lambda
- * (`packages/canopycms-cdk/lambda/asset-transform`).
+ * resize/format/quality/crop, EXIF stripped on every re-encode, identity included. Server-only
+ * (sharp); reused unchanged by the dev-mode lazy `/assets/t/*` emulation and the prod transform
+ * Lambda.
  */
 export { applyTransform } from './assets/transform.js';
 export type { ApplyTransformInput, TransformResult } from './assets/transform.js';

package/dist/server.js

@@ -1,8 +1,7 @@
-// Public server-side API for adopters. JSDoc is duplicated at each named
-// re-export so it shows on hover in adopter editors — TypeScript propagation
-// through `export { X } from './module.js'` is inconsistent across LSP versions
-// and module-resolution modes. New top-level public re-exports should follow
-// the same pattern (see DEVELOPING.md).
+// Public server-side API for adopters. Every named re-export carries its own JSDoc, because
+// TypeScript's propagation through `export { X } from './module.js'` is inconsistent across LSP
+// versions and module-resolution modes and adopters would otherwise get no hover text. Follow the
+// pattern for new top-level public re-exports (see DEVELOPING.md).
 export * from './content-reader.js';
 export * from './services.js';
 export * from './build-mode.js';
@@ -10,59 +9,42 @@ export * from './context.js';
 export { operatingStrategy } from './operating-mode/index.js';
 export * from './authorization/groups/index.js';
 /**
- * One-call factory for a **build/admin** Canopy context — for standalone
- * scripts that run entirely outside a Next.js request or build phase (index
- * builders, content audits, codegen, ad hoc reports). Reads the filesystem
- * directly as a synthetic admin user and bypasses ALL branch/path ACLs —
- * never use it in request-handling code. See the source JSDoc for the full
- * security note and the `createNextCanopyContext().getCanopyForBuild()`
- * comparison this mirrors.
+ * One-call factory for a **build/admin** Canopy context, for standalone scripts outside a
+ * Next.js request or build phase. Reads the filesystem as a synthetic admin user and bypasses
+ * ALL branch/path ACLs — never use it in request-handling code. Full security note in the
+ * source JSDoc.
  */
 export { createBuildCanopy } from './build-canopy.js';
 /**
- * Resolve a CanopyUser for a request: loads internal groups from the
- * settings workspace (the single source of truth — never a content branch
- * clone) and merges them into an auth-plugin result via
- * `authResultToCanopyUser`. Shared by the core HTTP handler and the Next.js
- * SSR wrapper so the "authenticate -> load groups -> merge" pipeline can't
- * drift between the two again.
+ * Resolve a CanopyUser for a request: loads internal groups from the settings workspace (the
+ * single source of truth — never a content branch clone) and merges them into an auth-plugin
+ * result via `authResultToCanopyUser`. Shared by the core HTTP handler and the Next.js SSR
+ * wrapper so the "authenticate -> load groups -> merge" pipeline cannot drift between them.
  */
 export { resolveCanopyUser } from './resolve-canopy-user.js';
 export * from './branch-workspace.js';
 export * from './content-store.js';
 export { loadCollectionMetaFiles, resolveCollectionReferences, watchCollectionMetaFiles, resolveSchema, } from './schema/index.js';
 /**
- * Create a type-safe entry schema registry with runtime validation.
- *
- * Maps each entry-type's name to its `EntrySchema`. Keys are referenced by
- * `.collection.json` files via the `entry.schema` property. Recommended
- * convention is to key by entry-type name (filename token, also the value of
- * `meta.entryType` in tree-builder callbacks) — that way
- * `EntryTypesFromRegistry<typeof yourRegistry>` derives the
- * discriminated-union map for `buildContentTree`'s `TEntryTypes` parameter
- * automatically. See `createEntrySchemaRegistry`'s source-file JSDoc for the
- * full example.
+ * Create a type-safe entry schema registry with runtime validation. Keys are the strings
+ * `.collection.json` files reference via `entry.schema`; key them by entry-type name so
+ * `EntryTypesFromRegistry<typeof yourRegistry>` derives `buildContentTree`'s `TEntryTypes` map.
+ * Source JSDoc has the example and the full validation list.
  */
 export { createEntrySchemaRegistry } from './entry-schema-registry.js';
 /**
- * Validate that entry-schema references in `.collection.json` files exist in
- * the registry. Useful at build time to fail fast on stale references rather
- * than at request time.
+ * Validate that entry-schema references in `.collection.json` files exist in the registry —
+ * at build time, so a stale reference fails there rather than at request time.
  */
 export { validateEntrySchemaRegistry } from './entry-schema-registry.js';
 /**
- * Resolve a display title for an entry using the full fallback chain: a
- * schema-marked `isTitle` field, then `data.title`/`data.name`, then an
- * entry-type label, then a humanized slug, then `"Untitled"`. Useful
- * anywhere an entry needs a display title without re-deriving this chain —
- * search-document/index builders in particular, since a search UI needs a
- * title for every result regardless of which field the schema uses.
+ * Resolve an entry's display title through the full fallback chain: a schema-marked `isTitle`
+ * field, then `data.title`/`data.name`, then an entry-type label, then a humanized slug, then
+ * `"Untitled"`. Search-document and index builders in particular need a title for every result
+ * regardless of which field the schema uses.
  *
- * Client-safe (no dependencies beyond `FieldConfig`/`InlineGroupFieldConfig`
- * type imports, which are erased at compile time) — also re-exported from
- * the root `canopycms` entry for that reason. Exported here too because
- * build/admin scripts (the primary reason this was unreachable before) are
- * more likely to `import` from `canopycms/server` than the root entry.
+ * Client-safe (its only imports are types, erased at compile time), so it is exported from the
+ * root `canopycms` entry as well as here, where build/admin scripts look for it.
  */
 export { resolveEntryTitle } from './utils/title-field.js';
 /** Generate a Canopy-format 12-character Base58 content ID. */
@@ -70,44 +52,38 @@ export { generateId } from './id.js';
 /** Returns true if a string is a valid 12-character Base58 Canopy ID. */
 export { isValidId } from './id.js';
 /**
- * Build a hierarchical tree of content nodes from the schema and filesystem.
- *
- * Pass `TEntryTypes` (typically `EntryTypesFromRegistry<typeof entrySchemaRegistry>`)
- * to get narrowed access to `meta.indexEntry.data` after switching on
- * `meta.entryType` in your `extract` callback.
- *
- * Adopters using `canopycms-next` typically call `canopy.buildContentTree(...)`
- * via `getCanopyForBuild()` rather than the bare function.
+ * Build a hierarchical tree of content nodes from the schema and filesystem. Pass `TEntryTypes`
+ * (typically `EntryTypesFromRegistry<typeof entrySchemaRegistry>`) for narrowed access to
+ * `meta.indexEntry.data` after switching on `meta.entryType` in an `extract` callback.
+ * `canopycms-next` adopters usually call `canopy.buildContentTree(...)` via
+ * `getCanopyForBuild()` instead of the bare function.
  */
 export { buildContentTree } from './content-tree.js';
 /**
- * `buildContentTree`'s default URL path builder: strips the `{contentRootName}/`
- * prefix, collapses an entry's `index` slug to its parent collection's path, and
- * lowercases the result. Call it from inside a custom `buildPath` to extend the
- * default rather than reimplement it — `buildContentTree`'s `buildPath` option
- * replaces the default outright, it does not compose with it.
+ * `buildContentTree`'s default URL path builder: strips the `{contentRootName}/` prefix,
+ * collapses an entry's `index` slug to its parent collection's path, and lowercases the result.
+ * Call it from inside a custom `buildPath` rather than reimplementing it — the `buildPath`
+ * option REPLACES the default outright, it does not compose with it.
  */
 export { defaultBuildPath } from './content-tree.js';
 /** List all content entries as a flat array. */
 export { listEntries } from './content-listing.js';
 /**
- * Parse a content filename of the form `{type}.{slug}.{id}.{ext}` into its
- * `{ type, slug, id }` parts. `id` must be a valid 12-character Base58 content ID
- * (excludes the ambiguous characters `0`, `O`, `I`, `l`) or the parse fails.
- * Pass `entryTypes` to also require `type` to match a known entry-type name;
- * omit it to parse the filename shape without that check. See the source JSDoc
- * for the full filename grammar.
+ * Parse a content filename `{type}.{slug}.{id}.{ext}` into `{ type, slug, id }`. `id` must be a
+ * valid 12-character Base58 content ID (no ambiguous `0`, `O`, `I`, `l`) or the parse fails.
+ * Pass `entryTypes` to also require `type` to match a known entry-type name. Full grammar in
+ * the source JSDoc.
  */
 export { parseTypedFilename } from './content-listing.js';
 /**
  * Resolve a canopy entry-link to its URL. Pair with the field-walker variants
- * (`resolveEntryLinksInText`, `resolveEntryLinksInData`) when rendering MDX
- * bodies or arbitrary frontmatter that may contain link tokens.
+ * (`resolveEntryLinksInText`, `resolveEntryLinksInData`) when rendering MDX bodies or
+ * frontmatter that may contain link tokens.
  */
 export { resolveEntryUrl, resolveEntryLinksInText, resolveEntryLinksInData, extractEntryLinkIds, } from './entry-link-resolver.js';
 /**
- * Compute the canonical URL for an entry given its logical path + slug, and the shared
- * "is this the collection-index slug?" predicate that decides whether it collapses.
+ * The canonical URL for an entry from its logical path + slug, plus the shared "is this the
+ * collection-index slug?" predicate that decides whether it collapses.
  */
 export { computeEntryUrl, isIndexSlug } from './utils/entry-url.js';
 /** Collect static paths for `generateStaticParams` / sitemap emission. */
@@ -116,58 +92,51 @@ export { collectStaticPaths } from './static/index.js';
 export { collectRoutableEntries } from './static/index.js';
 /**
  * Find every URL claimed by more than one entry — the check a production build already runs
- * (and fails on). Exported so a content-integrity test can assert it directly rather than
+ * and fails on. Exported so a content-integrity test can assert it directly instead of
  * hand-rolling the same scan over `listEntries`.
  */
 export { findDuplicateUrlPaths } from './static/index.js';
 /**
- * SEO field extraction and URL shaping (framework-agnostic). `isNoindexEntry` is the single
+ * SEO field extraction and URL shaping, framework-agnostic. `isNoindexEntry` is the single
  * predicate behind both `robots: noindex` and sitemap exclusion.
  */
 export { DEFAULT_SEO_FIELD_NAMES, extractSeoFields, isNoindexEntry, isAbsoluteUrl, withTrailingSlash, resolveSeoUrl, stripTrailingSlashes, } from './static/index.js';
 /**
- * Start a chokidar-backed watcher that detects divergence between the dev
- * working tree and the resolved branch clone. Dev mode only.
+ * Start a chokidar-backed watcher for divergence between the dev working tree and the resolved
+ * branch clone. Dev mode only.
  */
 export { startDevContentWatcher } from './dev-content-watcher.js';
 /**
- * Instantiate the AssetStore configured by a site's `media` config
- * (`config.media`). Returns undefined when no store applies: `media` is
- * unset and no `devAssetsDir` fallback was given, `adapter: 'local'` omits
- * `directory` with no fallback, or `adapter: 'lfs'` (config literal kept,
- * not yet implemented).
+ * Instantiate the AssetStore configured by a site's `config.media`. Returns undefined when no
+ * store applies: `media` unset with no `devAssetsDir` fallback, `adapter: 'local'` without
+ * `directory` and no fallback, or `adapter: 'lfs'` (config literal kept, not yet implemented).
  */
 export { createAssetStore } from './assets/factory.js';
 /**
- * The five S3/local bucket-prefix strings (`asset-originals/`, `asset-staging/`,
- * `asset-meta/`, `assets/`, `assets/t/`). Re-exported so server-only consumers
- * outside this package - notably the prod transform Lambda
- * (`packages/canopycms-cdk/lambda/asset-transform`) - can build/parse asset
- * keys through the same constants `S3AssetStore` uses, rather than
- * duplicating the literal prefix strings.
+ * The five S3/local bucket-prefix strings (`asset-originals/`, `asset-staging/`, `asset-meta/`,
+ * `assets/`, `assets/t/`). Exported so server-only consumers outside this package — notably the
+ * prod transform Lambda (`packages/canopycms-cdk/lambda/asset-transform`) — build and parse
+ * asset keys through the same constants `S3AssetStore` uses rather than duplicating the strings.
  */
 export { ASSET_PREFIXES } from './assets/keys.js';
 /**
- * Parse the three path segments after `assets/t/` (`{directives}/{hash32}/{slug}.{ext}`)
- * into a validated `TransformDirectives` set, or a structured parse error.
- * Reused unchanged by the dev-mode lazy `/assets/t/*` emulation (`api/assets.ts`)
- * and the prod transform Lambda (`packages/canopycms-cdk/lambda/asset-transform`)
- * so the URL grammar is defined in exactly one place.
+ * Parse the three path segments after `assets/t/` (`{directives}/{hash32}/{slug}.{ext}`) into a
+ * validated `TransformDirectives` set, or a structured parse error. Reused unchanged by the
+ * dev-mode lazy `/assets/t/*` emulation (`api/assets.ts`) and the prod transform Lambda, so the
+ * URL grammar is defined in exactly one place.
  */
 export { parseTransformPath } from './assets/transform-directives.js';
 /**
- * Canonical string form of a `TransformDirectives` set - the cache key every
- * transform output is stored under (`assets/t/{formatDirectives(...)}/{hash32}/{slug}.{ext}`).
- * Equivalent directive sets (different key order/float formatting) always
- * format to the same string. Reused by the prod transform Lambda so its
- * canonical writes agree with the dev-mode emulation and `assetUrl()`.
+ * Canonical string form of a `TransformDirectives` set — the cache key every transform output is
+ * stored under (`assets/t/{formatDirectives(...)}/{hash32}/{slug}.{ext}`). Equivalent directive
+ * sets (different key order or float formatting) always format to the same string. Reused by the
+ * prod transform Lambda so its writes agree with the dev-mode emulation and `assetUrl()`.
  */
 export { formatDirectives } from './assets/transform-directives.js';
 /**
  * Apply a parsed `TransformDirectives` set to source image bytes with sharp:
- * resize/format/quality/crop, with EXIF stripped on every re-encode (even
- * identity). Server-only (sharp) - reused unchanged by the dev-mode lazy
- * `/assets/t/*` emulation and the prod transform Lambda
- * (`packages/canopycms-cdk/lambda/asset-transform`).
+ * resize/format/quality/crop, EXIF stripped on every re-encode, identity included. Server-only
+ * (sharp); reused unchanged by the dev-mode lazy `/assets/t/*` emulation and the prod transform
+ * Lambda.
  */
 export { applyTransform } from './assets/transform.js';

package/dist/services.d.ts

@@ -1,22 +1,17 @@
 /**
- * `CanopyServices` — the long-lived, per-deployment service container.
+ * `CanopyServices` — the long-lived, per-deployment service container, built
+ * once by `createCanopyServices` and threaded through `ApiContext.services` to
+ * every API handler. Holds config, the schema registry and cache, the ACL
+ * checkers, the git-manager factory, the branch registry, the GitHub service,
+ * and four branch-workflow operations. Not `context.ts`, which is the
+ * per-REQUEST facade built on top of this.
  *
- * Built once by `createCanopyServices` and threaded through `ApiContext.services`
- * to every API handler. Holds config, the schema registry and cache, the ACL
- * checkers, the git-manager factory, the branch registry, the GitHub service, and
- * four branch-workflow operations (`commitFiles`, `submitBranch`,
- * `commitToSettingsBranch`, `getSettingsBranchRoot`).
+ * SCOPE WARNING: a service locator every api module reaches, so adding a field
+ * is free and therefore constant, and no handler's signature reveals what it
+ * touches. Give a new capability its own narrow interface instead.
  *
- * SCOPE WARNING: this is a service locator with 15 members, reached by every one of
- * the 26 api modules, so adding a field is free and therefore constant — and no handler's
- * signature reveals what it actually touches. Prefer giving a new capability its
- * own narrow interface over a 23rd field here.
- *
- * Not to be confused with `context.ts`, which is the per-REQUEST facade built on
- * top of this.
- *
- * `createTestCanopyServices` is test-only despite living in a production module;
- * it reaches the published surface through a wildcard re-export.
+ * `createTestCanopyServices` is test-only despite living in a production
+ * module; it reaches the published surface through a wildcard re-export.
  *
  * Module map: ./AGENTS.md.
  */
@@ -30,8 +25,8 @@ import { BranchRegistry } from './branch-registry.js';
 import { type GitHubService } from './github-service.js';
 import { BranchSchemaCache } from './branch-schema-cache.js';
 /**
- * Parse bootstrap admin IDs from environment variable.
- * These users are always treated as Admins regardless of group membership.
+ * Bootstrap admin IDs from the environment. These users are treated as Admins
+ * whatever their group membership.
  */
 export declare const getBootstrapAdminIds: () => Set<string>;
 export interface CanopyServices {
@@ -49,9 +44,9 @@ export interface CanopyServices {
     checkBranchAccess: (context: BranchContext, user: CanopyUser) => ReturnType<ReturnType<typeof createCheckBranchAccess>>;
     checkContentAccess: ReturnType<typeof createCheckContentAccess>;
     /**
-     * Build a batch content-access checker that loads permissions once and returns
-     * a synchronous per-path checker. Use this when checking many paths in a single
-     * request (e.g. listing entries) to avoid re-loading permissions per path.
+     * A batch content-access checker: loads permissions once, returns a
+     * synchronous per-path check. Use it whenever one request checks many paths,
+     * so permissions are not re-loaded per path.
      */
     createContentAccessChecker: (context: BranchContext, branchRoot: string, user: CanopyUser) => Promise<ContentAccessChecker>;
     createGitManagerFor: (repoPath: string, opts?: {
@@ -90,44 +85,25 @@ export interface CanopyServices {
     /** Get the root path for settings storage (ensures workspace exists) */
     getSettingsBranchRoot: () => Promise<string>;
 }
-/**
- * Options for createCanopyServices and createTestCanopyServices.
- */
 export interface CreateCanopyServicesOptions {
-    /**
-     * Entry schema registry for resolving .collection.json references.
-     * Maps entry schema names to field definitions.
-     */
+    /** Entry schema names → field definitions, for resolving .collection.json references. */
     entrySchemaRegistry?: EntrySchemaRegistry;
     /**
-     * Test-only: Custom branch schema cache.
-     * When provided, bypasses the default BranchSchemaCache creation.
+     * Test-only: bypasses the default BranchSchemaCache creation.
      * @internal
      */
     branchSchemaCache?: BranchSchemaCache;
     /**
-     * Test-only: Override for getSettingsBranchRoot.
-     * When provided, bypasses the real git workspace setup for settings.
+     * Test-only: bypasses the real git workspace setup for settings.
      * @internal
      */
     getSettingsBranchRoot?: () => Promise<string>;
 }
 /**
- * Create reusable helpers from a validated CanopyConfig.
- * Intended to be called once at startup and injected where needed
- * (e.g., request handlers, loaders).
- *
- * Schema is now loaded per-branch via BranchSchemaCache, not at startup.
- *
- * @param config - Validated Canopy configuration
- * @param options - Optional settings including entry schema registry
+ * Build the reusable helpers from a validated CanopyConfig — once at startup,
+ * then injected into request handlers and loaders. Schema is not loaded here;
+ * BranchSchemaCache loads it per branch.
  */
 export declare const createCanopyServices: (config: CanopyConfig, options?: CreateCanopyServicesOptions) => Promise<CanopyServices>;
-/**
- * Create services for testing.
- * Schema is loaded per-branch via BranchSchemaCache.
- *
- * @param config - Validated Canopy configuration
- * @param options - Optional settings including entry schema registry
- */
+/** {@link createCanopyServices} for tests, with branch identity pinned. */
 export declare const createTestCanopyServices: (config: CanopyConfig, options?: CreateCanopyServicesOptions) => Promise<CanopyServices>;