canopycms 0.0.67-int.90 → 0.0.67

package/dist/cli/init.js

@@ -334,18 +334,18 @@ var init_config = __esm({
       onAccountClick: z5.function().returns(z5.void()).optional(),
       onLogoutClick: z5.function().returns(z5.void()).optional(),
       // Optional: custom account component (e.g., Clerk's UserButton)
-      AccountComponent: z5.custom().optional()
+      AccountComponent: z5.custom().optional(),
+      // Optional: provider sign-in UI for signed-out users (see EditorSignInProps)
+      SignInComponent: z5.custom().optional()
     });
     CanopyConfigSchema = z5.object({
       media: mediaSchema.optional(),
-      // No outer .optional() here: defaultBranchAccessSchema/defaultPathAccessSchema already
-      // have .default('deny'), so the field is optional on input but always resolves to
-      // 'allow'/'deny' (never undefined) on output. An outer .optional() would short-circuit
-      // before the inner default runs, defeating the fail-closed default (SCH-M1).
-      // defaultPathAccessSchema's union keeps the same rule: the .default('deny') sits on the
-      // OUTER union, not inside defaultPathAccessLevelsSchema, so an omitted top-level field
-      // still resolves to 'deny' and an omitted level inside the object form stays undefined
-      // (resolved to 'deny' at read time by resolveDefaultPathAccess).
+      // No outer .optional(): both schemas already .default('deny'), so the field is optional on
+      // input but always resolves to 'allow'/'deny' (never undefined) on output — an outer
+      // .optional() would short-circuit before the inner default runs, defeating the fail-closed
+      // default (SCH-M1). defaultPathAccessSchema's .default('deny') sits on the OUTER union, not
+      // inside defaultPathAccessLevelsSchema, so an omitted level in the object form stays
+      // undefined (resolved to 'deny' at read time by resolveDefaultPathAccess).
       defaultBranchAccess: defaultBranchAccessSchema,
       defaultPathAccess: defaultPathAccessSchema,
       // .optional() deliberately defeats defaultBaseBranchSchema's .default('main'):
@@ -369,16 +369,11 @@ var init_config = __esm({
       allowNetworkRemoteInProd: z5.boolean().optional(),
       settingsBranch: z5.string().optional(),
       autoCreateSettingsPR: z5.boolean().optional(),
-      // Deliberately `deploymentNameSchema.optional()`, NOT `deploymentNameSchema` alone.
-      // deploymentNameSchema.default('prod') would make `parse(undefined)` resolve to
-      // the literal 'prod' instead of staying `undefined` — collapsing the
-      // env > config > modeDefault precedence chain that resolveDeploymentName
-      // (operating-mode/deployment-name.ts) implements: config would then always
-      // "win" over modeDefault (masking dev's real default of 'local'), and the env
-      // var would just be racing config's baked-in 'prod' instead of a true absence.
-      // `.optional()` here is what keeps an omitted deploymentName reaching
-      // resolveDeploymentName as `undefined`, so it can fall through to modeDefault.
-      // Do not "fix" this by removing `.optional()`.
+      // `.optional()`, NOT bare `deploymentNameSchema`: its own `.default('prod')` would make
+      // `parse(undefined)` resolve to 'prod' instead of staying `undefined`, collapsing the
+      // env > config > modeDefault precedence chain `resolveDeploymentName`
+      // (operating-mode/deployment-name.ts) implements — config would always "win" over
+      // modeDefault, masking dev's real default of 'local'. Do not remove `.optional()`.
       deploymentName: deploymentNameSchema.optional(),
       contentRoot: contentRootSchema.default("content"),
       sourceRoot: sourceRootSchema.optional(),
@@ -522,7 +517,6 @@ var init_fs = __esm({
 // dist/cli/templates.js
 var templates_exports = {};
 __export(templates_exports, {
-  SCAFFOLD_STACK_NAME: () => SCAFFOLD_STACK_NAME,
   aiConfig: () => aiConfig,
   aiRoute: () => aiRoute,
   apiRoute: () => apiRoute,
@@ -588,9 +582,8 @@ async function aiRoute(options) {
   const template = await readTemplate("ai-route.ts.template");
   return template.replace("{{CONFIG_IMPORT}}", options.configImport);
 }
-async function middleware(options) {
-  const templateName = options.authProvider === "clerk" ? "middleware-clerk.ts.template" : "middleware.ts.template";
-  return readTemplate(templateName);
+async function middleware() {
+  return readTemplate("middleware.ts.template");
 }
 async function nextConfig(options) {
   const templateName = options.staticBuild ? "next.config-static.ts.template" : "next.config.ts.template";
@@ -638,8 +631,7 @@ __export(project_detect_exports, {
   detectDefaultBranch: () => detectDefaultBranch,
   detectGitHubRepo: () => detectGitHubRepo,
   detectPackageManager: () => detectPackageManager,
-  missingCdkDependencies: () => missingCdkDependencies,
-  readPackageJson: () => readPackageJson
+  missingCdkDependencies: () => missingCdkDependencies
 });
 import fs3 from "node:fs/promises";
 import path3 from "node:path";
@@ -768,14 +760,13 @@ var init_project_detect = __esm({
       pnpm: {
         lockfile: "pnpm-lock.yaml",
         ciInstall: "corepack enable && pnpm install --frozen-lockfile",
-        // pnpm-workspace.yaml holds settings the install obeys even in a single-package app: pnpm
-        // 11's `allowBuilds` decisions, `overrides`, `patchedDependencies`. pnpm 11 fails the
-        // install on any dependency build script without a decision, and an app with the editor has
-        // several (es5-ext through the editor, sharp through Next). The `[l]` glob keeps the file
-        // optional: COPY rejects a missing literal source, but accepts a pattern that matches
-        // nothing when another source matches. Measured 2026-09-13 on Docker Engine 29.6.2 (BuildKit
-        // v0.31.2): `COPY package.json pnpm-workspace.yam[l] ./` builds with no pnpm-workspace.yaml
-        // in the context, and the same line with the literal name fails with "not found".
+        // pnpm-workspace.yaml holds settings the install obeys even in a single-package app
+        // (pnpm 11's `allowBuilds` decisions, `overrides`, `patchedDependencies`); pnpm 11 fails
+        // the install on any dependency build script without a decision, and an app with the
+        // editor has several (es5-ext, sharp). The `[l]` glob keeps the file optional: on Docker
+        // Engine 29.6.2 (BuildKit v0.31.2), `COPY package.json pnpm-workspace.yam[l] ./` builds
+        // with no pnpm-workspace.yaml in the context, while the same line with the literal name
+        // fails with "not found".
         dockerCopy: "COPY package.json pnpm-lock.yaml pnpm-workspace.yam[l] ./",
         dockerInstall: "RUN corepack enable && pnpm install --frozen-lockfile",
         build: "pnpm run build",
@@ -810,7 +801,7 @@ var init_project_detect = __esm({
   }
 });
 
-// dist/worker/task-queue-config.js
+// dist/task-queue/task-queue-config.js
 var task_queue_config_exports = {};
 __export(task_queue_config_exports, {
   getTaskQueueDir: () => getTaskQueueDir
@@ -828,7 +819,7 @@ function getTaskQueueDir(config) {
   }
 }
 var init_task_queue_config = __esm({
-  "dist/worker/task-queue-config.js"() {
+  "dist/task-queue/task-queue-config.js"() {
     "use strict";
     init_config2();
   }
@@ -861,15 +852,11 @@ var init_debug = __esm({
         return LOG_LEVELS[level] >= LOG_LEVELS[minLevel];
       }
       /**
-       * The ISO-8601 timestamp leads the line BARE - not wrapped in brackets as it
-       * once was. `CANOPYCMS_DEBUG=true` can be set on the EC2 worker, whose stdout
-       * appends to /var/log/canopy-worker/worker.log; the CloudWatch agent's
-       * `multi_line_start_pattern` matches the timestamp at the START of a line
-       * (see worker/log.ts's INVARIANT and cms-service.ts's agent config), so a
-       * leading `[` meant every debug line was silently folded into the previous
-       * event instead of starting its own. The bracketed `[prefix:category]` and
-       * `[level]` fields still follow, so the human-readable shape is unchanged
-       * apart from those two characters.
+       * The ISO-8601 timestamp leads the line BARE, never bracketed. `CANOPYCMS_DEBUG=true` can
+       * be set on the EC2 worker, whose stdout appends to /var/log/canopy-worker/worker.log, and
+       * the CloudWatch agent's `multi_line_start_pattern` matches a timestamp at the START of a
+       * line (see worker/log.ts's INVARIANT and cms-service.ts's agent config): any leading
+       * character folds the line into the previous event instead of starting its own.
        */
       formatMessage(level, category, message) {
         const timestamp = (/* @__PURE__ */ new Date()).toISOString();
@@ -902,15 +889,9 @@ var init_debug = __esm({
           throw new Error(errorMsg);
         }
       }
-      /**
-       * Start timing an operation
-       */
       time(label) {
         this.timers.set(label, Date.now());
       }
-      /**
-       * End timing an operation and log the duration
-       */
       timeEnd(category, label) {
         const start = this.timers.get(label);
         if (start === void 0) {
@@ -922,9 +903,6 @@ var init_debug = __esm({
         this.debug(category, `${label} completed`, { durationMs: duration });
         return duration;
       }
-      /**
-       * Wrap an async function with automatic timing
-       */
       async timed(category, label, fn) {
         this.time(label);
         try {
@@ -1375,17 +1353,9 @@ var init_task_queue = __esm({
   }
 });
 
-// dist/task-queue/index.js
-var init_task_queue2 = __esm({
-  "dist/task-queue/index.js"() {
-    "use strict";
-    init_task_queue();
-  }
-});
-
-// dist/worker/task-queue.js
-var task_queue_exports = {};
-__export(task_queue_exports, {
+// dist/task-queue/cms-task-queue.js
+var cms_task_queue_exports = {};
+__export(cms_task_queue_exports, {
   cleanupOldTasks: () => cleanupOldTasks,
   cmsTaskQueueLogger: () => cmsTaskQueueLogger,
   completeTask: () => completeTask,
@@ -1394,7 +1364,6 @@ __export(task_queue_exports, {
   failTask: () => failTask,
   getQueueStats: () => getQueueStats,
   getTask: () => getTask,
-  getTaskResult: () => getTask,
   listCorruptTaskFiles: () => listCorruptTaskFiles,
   listTasks: () => listTasks,
   recoverOrphanedTasks: () => recoverOrphanedTasks,
@@ -1402,11 +1371,11 @@ __export(task_queue_exports, {
   retryTask: () => retryTask
 });
 var debugLogger, cmsTaskQueueLogger;
-var init_task_queue3 = __esm({
-  "dist/worker/task-queue.js"() {
+var init_cms_task_queue = __esm({
+  "dist/task-queue/cms-task-queue.js"() {
     "use strict";
     init_debug();
-    init_task_queue2();
+    init_task_queue();
     debugLogger = createDebugLogger({ prefix: "TaskQueue" });
     cmsTaskQueueLogger = {
       debug(message, data) {
@@ -1427,7 +1396,6 @@ var ProdClientSafeStrategy = class {
   constructor() {
     this.mode = "prod";
   }
-  // UI Feature Flags
   supportsBranching() {
     return true;
   }
@@ -1440,7 +1408,6 @@ var ProdClientSafeStrategy = class {
   supportsPullRequests() {
     return true;
   }
-  // Simple Data
   getPermissionsFileName() {
     return "permissions.json";
   }
@@ -1458,7 +1425,6 @@ var DevClientSafeStrategy = class {
   constructor() {
     this.mode = "dev";
   }
-  // UI Feature Flags
   supportsBranching() {
     return true;
   }
@@ -1471,7 +1437,6 @@ var DevClientSafeStrategy = class {
   supportsPullRequests() {
     return false;
   }
-  // Simple Data
   getPermissionsFileName() {
     return "permissions.json";
   }
@@ -1512,11 +1477,6 @@ function resolveDeploymentName(config, modeDefault) {
 // dist/operating-mode/client-unsafe-strategy.js
 init_config2();
 var ProdStrategy = class extends ProdClientSafeStrategy {
-  // All client-safe methods inherited automatically from ProdClientSafeStrategy:
-  // - mode, supportsBranching(), supportsStatusBadge(), supportsComments()
-  // - supportsPullRequests(), getPermissionsFileName(), getGroupsFileName()
-  // - shouldCommit(), shouldPush()
-  // Add client-unsafe methods (use Node.js APIs)
   getWorkspaceRoot(_sourceRoot) {
     return path.resolve(process.env.CANOPYCMS_WORKSPACE_ROOT ?? DEFAULT_PROD_WORKSPACE);
   }
@@ -1570,7 +1530,6 @@ var ProdStrategy = class extends ProdClientSafeStrategy {
   }
 };
 var DevStrategy = class extends DevClientSafeStrategy {
-  // Inherits client-safe methods from DevClientSafeStrategy
   getWorkspaceRoot(sourceRoot) {
     return path.resolve(sourceRoot ?? process.cwd(), ".canopy-dev");
   }
@@ -1760,7 +1719,7 @@ async function init(options) {
   } else {
     await writeFile(path7.join(projectDir, "next.config.ts"), await nextConfig2({ staticBuild }), writeOpts);
   }
-  await writeFile(path7.join(projectDir, path7.dirname(appDir), "middleware.ts"), await middleware2({ authProvider }), writeOpts);
+  await writeFile(path7.join(projectDir, path7.dirname(appDir), "middleware.ts"), await middleware2(), writeOpts);
   const gitignorePath = path7.join(projectDir, ".gitignore");
   const CANOPY_GITIGNORE_BLOCK = "# CanopyCMS\n.canopy-dev/\n";
   if (await filePathExists(gitignorePath)) {
@@ -1971,7 +1930,7 @@ CanopyCMS worker run-once (mode: ${mode}, auth: ${authMode})
       process.exitCode = 1;
     }
   }
-  const { dequeueTask: dequeueTask2, completeTask: completeTask2, listTasks: listTasks2 } = await Promise.resolve().then(() => (init_task_queue3(), task_queue_exports));
+  const { dequeueTask: dequeueTask2, completeTask: completeTask2, listTasks: listTasks2 } = await Promise.resolve().then(() => (init_cms_task_queue(), cms_task_queue_exports));
   if (mode === "prod") {
     const pending = await listTasks2(taskDir, "pending");
     if (pending.length > 0) {

package/dist/cli/migrate.d.ts

@@ -12,7 +12,7 @@
  * so re-running is a no-op. Source-specific ordering conventions (e.g.
  * Nextra _meta.json) are out of scope — order defaults to alphabetical.
  */
-export declare const MIGRATE_FORMATS: readonly ["md", "mdx", "json", "yaml"];
+declare const MIGRATE_FORMATS: readonly ["md", "mdx", "json", "yaml"];
 export type MigrateFormat = (typeof MIGRATE_FORMATS)[number];
 export interface MigrateOptions {
     projectDir: string;
@@ -20,7 +20,6 @@ export interface MigrateOptions {
     contentRoot?: string;
     /** Entry type name written into .collection.json and file names (e.g. 'doc') */
     entryType?: string;
-    /** File format to migrate */
     format?: MigrateFormat;
     /** Entry schema registry key written into .collection.json (e.g. 'docSchema') */
     schema?: string;
@@ -29,21 +28,25 @@ export interface MigrateOptions {
     /** Skip the confirmation prompt */
     force?: boolean;
 }
-/** Migration precondition failure — thrown so the CLI exits non-zero. */
+/**
+ * Migration precondition failure — thrown so the CLI exits non-zero.
+ * @internal Exported for tests.
+ */
 export declare class MigrateError extends Error {
     constructor(message: string);
 }
 /**
- * Normalize a file/directory base name into a slug the whole CMS accepts.
- * Must satisfy parseSlug (/^[a-z0-9][a-z0-9-]*$/) — underscores are NOT allowed:
- * the public read path (readByUrlPath/read) rejects them, so a migrated page
- * carrying one is unreachable and now fails the production build outright
- * (static/index.ts's assertRoutableSlugs). Migration writes files directly
- * rather than through the write API, so its [SLUG] create guard does not cover
- * this — normalizing here is what keeps the migrated tree buildable.
+ * Normalizes a file/directory base name into a slug parseSlug accepts
+ * (/^[a-z0-9][a-z0-9-]*$/) — underscores are NOT allowed: the public read path
+ * rejects them, so a migrated page carrying one is unreachable and fails the
+ * production build (static/index.ts's assertRoutableSlugs). Migration writes
+ * files directly, bypassing the write API's [SLUG] create guard, so this
+ * normalization is the only thing that keeps the migrated tree buildable.
+ * @internal Exported for tests.
  */
 export declare function slugifyName(name: string): string;
 /** Run the migrate command. Returns the number of operations applied. */
 export declare function migrate(options: MigrateOptions): Promise<{
     opCount: number;
 }>;
+export {};

package/dist/cli/migrate.js

@@ -25,8 +25,11 @@ import { withLock } from '../utils/async-mutex.js';
 import { withOccFileLock, OccWriteConflictError } from '../utils/occ-json-write.js';
 import { BranchMetadataFileManager } from '../branch-metadata.js';
 import { invalidateBranchContentCaches } from '../content-index-generation.js';
-export const MIGRATE_FORMATS = ['md', 'mdx', 'json', 'yaml'];
-/** Migration precondition failure — thrown so the CLI exits non-zero. */
+const MIGRATE_FORMATS = ['md', 'mdx', 'json', 'yaml'];
+/**
+ * Migration precondition failure — thrown so the CLI exits non-zero.
+ * @internal Exported for tests.
+ */
 export class MigrateError extends Error {
     constructor(message) {
         super(message);
@@ -34,13 +37,13 @@ export class MigrateError extends Error {
     }
 }
 /**
- * Normalize a file/directory base name into a slug the whole CMS accepts.
- * Must satisfy parseSlug (/^[a-z0-9][a-z0-9-]*$/) — underscores are NOT allowed:
- * the public read path (readByUrlPath/read) rejects them, so a migrated page
- * carrying one is unreachable and now fails the production build outright
- * (static/index.ts's assertRoutableSlugs). Migration writes files directly
- * rather than through the write API, so its [SLUG] create guard does not cover
- * this — normalizing here is what keeps the migrated tree buildable.
+ * Normalizes a file/directory base name into a slug parseSlug accepts
+ * (/^[a-z0-9][a-z0-9-]*$/) — underscores are NOT allowed: the public read path
+ * rejects them, so a migrated page carrying one is unreachable and fails the
+ * production build (static/index.ts's assertRoutableSlugs). Migration writes
+ * files directly, bypassing the write API's [SLUG] create guard, so this
+ * normalization is the only thing that keeps the migrated tree buildable.
+ * @internal Exported for tests.
  */
 export function slugifyName(name) {
     const slug = name
@@ -145,7 +148,6 @@ export async function migrate(options) {
     if (!(await filePathExists(contentDir))) {
         throw new MigrateError(`Content directory not found: ${contentRoot}/ (expected at ${contentDir})`);
     }
-    // Resolve entry type / format / schema from flags, prompting for what's missing
     let entryType = options.entryType;
     if (!entryType) {
         const result = await p.text({
@@ -218,27 +220,18 @@ export async function migrate(options) {
             return { opCount: 0 };
         }
     }
-    // migrate's target (`projectDir`, resolved by walking up from cwd to the
-    // nearest canopycms.config.ts — see cli/project-root.ts) is USUALLY the
-    // developer's live source repo, not a branch clone: migrate is meant to run
-    // once, before any branch workspace has ever been created, converting a
-    // plain content tree into CanopyCMS conventions. In that (common) case
-    // there is no cached schema/content-index to invalidate, and bumping the
-    // markers there would be a no-op nobody reads — no consumer treats the
-    // live project root as a cached branchRoot outside build/static mode, which
-    // skips the disk cache entirely — and would risk violating the
-    // never-write-.canopy-meta-at-the-project-root invariant documented on
+    // `projectDir` (resolved by cli/project-root.ts) is usually the live source repo,
+    // not a branch clone — migrate typically runs before any branch workspace exists.
+    // The live root has no cached schema/content-index to invalidate, and touching one
+    // would risk the never-write-.canopy-meta-at-the-project-root invariant owned by
     // BranchSchemaCache.
     //
-    // But projectDir CAN resolve to an actual branch clone workspace if the CLI
-    // happens to be invoked with cwd inside one: branch clones are full git
-    // clones (see GitManager.cloneRepo), so they carry their own
-    // canopycms.config.ts and satisfy findProjectRoot just as well as the true
-    // project root. Guard on that directly — a branch clone always has
-    // .canopy-meta/branch.json (BranchMetadataFileManager), the live project
-    // root never does — rather than assuming based on how migrate is "usually"
-    // invoked. Computed BEFORE applying ops so the same check gates both the
-    // surrogate schema lock below and the post-migration cache invalidation.
+    // But `projectDir` CAN be an actual branch clone if cwd is inside one (clones are
+    // full git checkouts, see GitManager.cloneRepo, with their own canopycms.config.ts).
+    // Guard on that directly: a branch clone always has .canopy-meta/branch.json, the
+    // live project root never does. Computed before applying ops so this one check
+    // gates both the surrogate schema lock below and the post-migration cache
+    // invalidation.
     const isBranchClone = Boolean(await BranchMetadataFileManager.loadOnly(projectDir));
     const applyOps = async () => {
         for (const op of ops) {
@@ -276,7 +269,6 @@ export async function migrate(options) {
     if (isBranchClone) {
         await invalidateBranchContentCaches(projectDir);
     }
-    // Sanity-check the result: all .collection.json files must parse
     try {
         const result = await loadCollectionMetaFiles(contentDir);
         p.log.success(`Validated: ${result.collections.length} collection(s)${result.root ? ' + root' : ''} loaded cleanly.`);

package/dist/cli/project-detect.d.ts

@@ -4,19 +4,15 @@
  *
  * Everything here is best-effort by design: `init-deploy aws` must never fail
  * because a project has no git remote, no lockfile, or no git binary at all.
- * Each detector falls back to the value the templates used before detection
- * existed, so an npm project in a `main`-default repo gets byte-identical
- * output to what shipped previously.
+ * Each detector falls back to a fixed default (e.g. 'npm', 'main') it cannot
+ * verify, keeping the output deterministic instead of failing the command.
  */
 export type PackageManager = 'npm' | 'pnpm' | 'yarn' | 'yarn-berry';
 /**
- * The package-manager-specific command and file strings the deployment
- * templates need.
- *
- * These reach two very different places -- a GitHub Actions step and a
- * Dockerfile layer -- so they are kept together: a `Dockerfile.cms` that
- * installs with npm while the workflow installs with pnpm is exactly the
- * half-fix that moves a failure rather than removing it.
+ * Package-manager-specific command and file strings the deployment templates
+ * need, kept together because they reach two different places (a GitHub
+ * Actions step and a Dockerfile layer): a `Dockerfile.cms` using npm while
+ * the workflow uses pnpm would just move the failure, not remove it.
  */
 export interface PackageManagerCommands {
     /** Lockfile that identifies this manager, for the workflow's `paths:` filter. */
@@ -34,27 +30,21 @@ export interface PackageManagerCommands {
 }
 export declare function commandsFor(manager: PackageManager): PackageManagerCommands;
 /**
- * Identify the adopter's package manager.
- *
- * `packageManager` (the corepack field) wins when present -- it is the
- * declared intent. Otherwise the lockfile decides. With neither, we return
- * 'npm', which is what every template hardcoded before this existed.
+ * Identifies the adopter's package manager. `packageManager` (the corepack
+ * field) wins when present — it's the declared intent; otherwise the lockfile
+ * decides; with neither, this returns 'npm'.
  *
- * Yarn is split into classic vs Berry because the two need different install
- * flags and a different Docker build context, and `yarn.lock`'s *name* cannot
- * tell them apart -- only its first lines can.
+ * Yarn splits into classic vs Berry because the two need different install
+ * flags and Docker build contexts, and `yarn.lock`'s name alone can't tell
+ * them apart — only its first lines can.
  */
 export declare function detectPackageManager(projectDir: string): Promise<PackageManager>;
 /**
- * The branch the deploy workflow should trigger on.
- *
- * Only `origin/HEAD` counts. The obvious-looking fallback -- "use the branch
- * that's checked out" -- would be worse than the hardcoded `main` it replaces:
- * an adopter scaffolding from a setup branch would get
- * `branches: [add-cms]` baked into the workflow, so the deploy would go quiet
- * the moment that branch merged. That silent-trigger failure is the exact LOW
- * this detection exists to fix, so we do not reintroduce it in a
- * harder-to-predict form.
+ * The branch the deploy workflow should trigger on. Only `origin/HEAD` counts —
+ * "use the currently checked-out branch" looks like a better fallback than the
+ * hardcoded `main` it replaces, but scaffolding from a setup branch would bake
+ * `branches: [add-cms]` into the workflow, so the deploy would silently go
+ * quiet the moment that branch merges.
  */
 export declare function detectDefaultBranch(projectDir: string): Promise<string>;
 export interface GitHubRepo {
@@ -67,9 +57,6 @@ export interface GitHubRepo {
  * (`https://github.com/owner/repo`) forms.
  */
 export declare function detectGitHubRepo(projectDir: string): Promise<GitHubRepo | null>;
-type PackageJson = Record<string, unknown>;
-/** Read the adopter's package.json, or null when absent/unparseable. */
-export declare function readPackageJson(projectDir: string): Promise<PackageJson | null>;
 /**
  * Dependencies the generated CDK app needs at deploy time.
  *
@@ -89,4 +76,3 @@ export declare const CDK_DEPENDENCIES: readonly ["canopycms", "canopycms-cdk", "
  * manifest certainly has none of them installed.
  */
 export declare function missingCdkDependencies(projectDir: string): Promise<string[]>;
-export {};

package/dist/cli/project-detect.js

@@ -4,9 +4,8 @@
  *
  * Everything here is best-effort by design: `init-deploy aws` must never fail
  * because a project has no git remote, no lockfile, or no git binary at all.
- * Each detector falls back to the value the templates used before detection
- * existed, so an npm project in a `main`-default repo gets byte-identical
- * output to what shipped previously.
+ * Each detector falls back to a fixed default (e.g. 'npm', 'main') it cannot
+ * verify, keeping the output deterministic instead of failing the command.
  */
 import fs from 'node:fs/promises';
 import path from 'node:path';
@@ -24,14 +23,13 @@ const COMMANDS = {
     pnpm: {
         lockfile: 'pnpm-lock.yaml',
         ciInstall: 'corepack enable && pnpm install --frozen-lockfile',
-        // pnpm-workspace.yaml holds settings the install obeys even in a single-package app: pnpm
-        // 11's `allowBuilds` decisions, `overrides`, `patchedDependencies`. pnpm 11 fails the
-        // install on any dependency build script without a decision, and an app with the editor has
-        // several (es5-ext through the editor, sharp through Next). The `[l]` glob keeps the file
-        // optional: COPY rejects a missing literal source, but accepts a pattern that matches
-        // nothing when another source matches. Measured 2026-09-13 on Docker Engine 29.6.2 (BuildKit
-        // v0.31.2): `COPY package.json pnpm-workspace.yam[l] ./` builds with no pnpm-workspace.yaml
-        // in the context, and the same line with the literal name fails with "not found".
+        // pnpm-workspace.yaml holds settings the install obeys even in a single-package app
+        // (pnpm 11's `allowBuilds` decisions, `overrides`, `patchedDependencies`); pnpm 11 fails
+        // the install on any dependency build script without a decision, and an app with the
+        // editor has several (es5-ext, sharp). The `[l]` glob keeps the file optional: on Docker
+        // Engine 29.6.2 (BuildKit v0.31.2), `COPY package.json pnpm-workspace.yam[l] ./` builds
+        // with no pnpm-workspace.yaml in the context, while the same line with the literal name
+        // fails with "not found".
         dockerCopy: 'COPY package.json pnpm-lock.yaml pnpm-workspace.yam[l] ./',
         dockerInstall: 'RUN corepack enable && pnpm install --frozen-lockfile',
         build: 'pnpm run build',
@@ -58,15 +56,13 @@ export function commandsFor(manager) {
     return COMMANDS[manager];
 }
 /**
- * Identify the adopter's package manager.
+ * Identifies the adopter's package manager. `packageManager` (the corepack
+ * field) wins when present — it's the declared intent; otherwise the lockfile
+ * decides; with neither, this returns 'npm'.
  *
- * `packageManager` (the corepack field) wins when present -- it is the
- * declared intent. Otherwise the lockfile decides. With neither, we return
- * 'npm', which is what every template hardcoded before this existed.
- *
- * Yarn is split into classic vs Berry because the two need different install
- * flags and a different Docker build context, and `yarn.lock`'s *name* cannot
- * tell them apart -- only its first lines can.
+ * Yarn splits into classic vs Berry because the two need different install
+ * flags and Docker build contexts, and `yarn.lock`'s name alone can't tell
+ * them apart — only its first lines can.
  */
 export async function detectPackageManager(projectDir) {
     for (const dir of await workspaceSearchPath(projectDir)) {
@@ -86,20 +82,17 @@ const MAX_WORKSPACE_DEPTH = 8;
 /**
  * Directories to consult for package-manager evidence, nearest first.
  *
- * Normally just `projectDir`. The exception is a monorepo: in a pnpm/npm/yarn
- * workspace the lockfile and `packageManager` field live at the repo root,
- * while the Next.js app -- the directory an adopter naturally runs
- * `init-deploy aws` in, because that is where `canopycms init` told them to
- * run -- is `apps/site` and has neither. Looking only at `projectDir` there
- * returns 'npm' for a pnpm repo and writes `npm ci` into both the workflow and
- * Dockerfile.cms: silently wrong, and the exact failure this detection exists
- * to prevent.
+ * Normally just `projectDir`. In a pnpm/npm/yarn monorepo the lockfile and
+ * `packageManager` field live at the repo root, while the Next.js app —
+ * where `canopycms init` told the adopter to run `init-deploy aws` — is a
+ * subdirectory (e.g. `apps/site`) with neither. Looking only at `projectDir`
+ * there would return 'npm' for a pnpm repo and silently write `npm ci` into
+ * both the workflow and Dockerfile.cms.
  *
- * The walk starts only when `projectDir` has a package.json but no evidence of
- * its own -- the signal of a workspace member -- and stops at the directory
- * holding `.git`. Both bounds matter: without them a project with no lockfile
- * anywhere would keep climbing into unrelated directories and adopt a
- * stranger's package manager.
+ * The walk starts only when `projectDir` has a package.json but no evidence
+ * of its own (the signal of a workspace member), and stops at the directory
+ * holding `.git` — otherwise a project with no lockfile anywhere would climb
+ * into unrelated directories and adopt a stranger's package manager.
  */
 async function workspaceSearchPath(projectDir) {
     const start = path.resolve(projectDir);
@@ -152,15 +145,11 @@ async function isYarnBerryLockfile(projectDir) {
     }
 }
 /**
- * The branch the deploy workflow should trigger on.
- *
- * Only `origin/HEAD` counts. The obvious-looking fallback -- "use the branch
- * that's checked out" -- would be worse than the hardcoded `main` it replaces:
- * an adopter scaffolding from a setup branch would get
- * `branches: [add-cms]` baked into the workflow, so the deploy would go quiet
- * the moment that branch merged. That silent-trigger failure is the exact LOW
- * this detection exists to fix, so we do not reintroduce it in a
- * harder-to-predict form.
+ * The branch the deploy workflow should trigger on. Only `origin/HEAD` counts —
+ * "use the currently checked-out branch" looks like a better fallback than the
+ * hardcoded `main` it replaces, but scaffolding from a setup branch would bake
+ * `branches: [add-cms]` into the workflow, so the deploy would silently go
+ * quiet the moment that branch merges.
  */
 export async function detectDefaultBranch(projectDir) {
     const head = await gitRaw(projectDir, ['symbolic-ref', '--short', 'refs/remotes/origin/HEAD']);
@@ -203,7 +192,7 @@ async function gitRaw(projectDir, args) {
     }
 }
 /** Read the adopter's package.json, or null when absent/unparseable. */
-export async function readPackageJson(projectDir) {
+async function readPackageJson(projectDir) {
     try {
         const raw = await fs.readFile(path.join(projectDir, 'package.json'), 'utf-8');
         const parsed = JSON.parse(raw);