@elytracms/cli 0.0.87 → 0.0.88

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@elytracms/cli",
   "author": "finaldream <hi@finaldream.de>",
-  "version": "0.0.87",
+  "version": "0.0.88",
   "description": "The Elytra CLI — run a consuming repo's studio, frontend, and Convex backend under one command.",
   "license": "MIT",
   "type": "module",
@@ -17,7 +17,7 @@
     "node": ">=22.18.0"
   },
   "dependencies": {
-    "@elytracms/core": "^0.0.87"
+    "@elytracms/core": "^0.0.88"
   },
   "devDependencies": {
     "vitest": "^4.1.10"

package/src/cli.js

@@ -117,7 +117,9 @@ and are checked in the studio), and reports the generated-previews artifacts
 (manifest/files present; hash staleness lives in \`elytra previews --check\`).
 With studio/ deps installed, config validity is checked for real: doctor
 executes elytra.config.ts through your studio's own Vite (takes a few
-seconds); without deps it stays an honest "unknown" with the reason.
+seconds); without deps it stays an honest "unknown" with the reason. With
+the config resolved, it also reads the public delivery snapshot and warns
+about published documents whose collection the config does not declare.
 Exit non-zero if any check fails. Read-only.
 
 Options:

package/src/doctor.js

@@ -1,6 +1,7 @@
 import { readFileSync } from 'node:fs'
 import { createRequire } from 'node:module'
 import { dirname, join } from 'node:path'
+import { orphanedCollections } from '@elytracms/core/cms-core'
 import {
   REVALIDATE_ENV_ENDPOINT,
   REVALIDATE_ENV_SECRET,
@@ -8,6 +9,7 @@ import {
   checkDeploymentReady,
   expectedDeploymentEnv,
   probeAuthSigningKeys,
+  probeDeliverySnapshot,
   probeDeployedFunctionsVersion,
   probeRevalidateEndpoint,
 } from '@elytracms/core/export-sync/deployment-ready'
@@ -201,7 +203,7 @@ export function configFactsFromOutcome(outcome) {
     issueCount: issues.length,
     ...(firstIssue ? { firstIssue: formatConfigIssue(firstIssue) } : {}),
   }
-  const project = valid ? result.projects?.[0] : undefined
+  const project = resolvedProjectOf(outcome)
   const collections = project?.collections
   // EC-524: the `componentIds` fact was gathered here for EC-508's presentation
   // check, which resolved a collection's declared `presentation.wrapper` against
@@ -216,6 +218,60 @@ export function configFactsFromOutcome(outcome) {
   }
 }
 
+/**
+ * The project a resolved config outcome describes — the first one, the same choice
+ * {@link configFactsFromOutcome} makes for `collections` — or `undefined` when the
+ * config did not resolve validly (or was never evaluated). Pure.
+ */
+export function resolvedProjectOf(outcome) {
+  if (!outcome || outcome.kind !== 'resolved' || outcome.result?.ok !== true) return undefined
+  return outcome.result.projects?.[0]
+}
+
+// --- Published orphans (EC-606) -----------------------------------------------------
+//
+// A published document whose collection the config does not declare is still on the
+// public delivery snapshot, but no route or query addresses it and the studio hides it.
+// The doctor reads the snapshot (public, published-only — what every visitor receives)
+// and runs core's ONE counter (`orphanedCollections`, the same one the studio's session
+// hydration runs) against the resolved config's collection ids.
+
+/**
+ * Gather the `publishedOrphans` fact for a convex target, or `undefined` for any other
+ * target (no deployment, no snapshot). Without a declared set — the config did not
+ * resolve here — the fact is an honest `unknown` carrying why, and no request is made.
+ * `project` is {@link resolvedProjectOf}'s answer; `configFacts` is what
+ * {@link configFactsFromOutcome} returned (for the reason text).
+ */
+export async function gatherPublishedOrphans({
+  target,
+  project,
+  configFacts = {},
+  fetchImpl = fetch,
+  probe = probeDeliverySnapshot,
+} = {}) {
+  if (target?.kind !== 'convex') return undefined
+  if (!project || !Array.isArray(project.collections)) {
+    const reason =
+      configFacts.config !== undefined && !configFacts.config.valid
+        ? 'fix the workspace config issues first (see config-valid).'
+        : (configFacts.configUnavailableDetail ?? 'elytra.config.ts was not evaluated here.')
+    return {
+      status: 'unknown',
+      detail: `Published documents were not checked against the declared collections — ${reason}`,
+    }
+  }
+  const snapshot = await probe(target.url, project.slug, fetchImpl)
+  if (snapshot.status !== 'answered') return { status: 'unknown', detail: snapshot.detail }
+  return {
+    status: 'counted',
+    orphans: orphanedCollections(
+      snapshot.collections.map((collection) => ({ collection, published: true })),
+      project.collections.map((collection) => collection.id),
+    ),
+  }
+}
+
 // --- Deployment env-var presence (EC-399) --------------------------------------
 //
 // The Convex deployment's own env (`npx convex env set …`) lives in NO file a
@@ -441,6 +497,11 @@ export function formatReport(report) {
  * version and the `functions-version` check gets a real answer; otherwise the fact is
  * omitted → an honest `unknown`. Resolution stays at the entry point so this function
  * remains pure/injected like every other gatherer here.
+ *
+ * EC-606: against a convex target the `app` bucket also reports PUBLISHED ORPHANS —
+ * published documents whose collection the resolved config does not declare — read
+ * from the public delivery snapshot ({@link gatherPublishedOrphans}). A `warn` at most,
+ * so the exit code never changes; without a resolved config it is an honest `unknown`.
  */
 export async function runDoctor({
   env = {},
@@ -491,12 +552,23 @@ export async function runDoctor({
   // (announced by the harness itself — the boot costs seconds). Merged BEFORE the
   // contract composes the report so `config-valid`/`asset-collection` are real checks.
   let configFacts = {}
+  let outcome
   if (configOutcome !== undefined || root !== undefined) {
-    const outcome = configOutcome ?? (await executeWorkspaceConfig({ root, studioDir, log }))
+    outcome = configOutcome ?? (await executeWorkspaceConfig({ root, studioDir, log }))
     configFacts = configFactsFromOutcome(outcome)
     Object.assign(facts, configFacts)
   }
 
+  // EC-606: published documents of undeclared collections — one more request on the
+  // same public query API, made only when the config resolved (it needs the declared set).
+  const publishedOrphans = await gatherPublishedOrphans({
+    target,
+    project: resolvedProjectOf(outcome),
+    configFacts,
+    fetchImpl,
+  })
+  if (publishedOrphans) facts.publishedOrphans = publishedOrphans
+
   const report = checkDeploymentReady(facts)
 
   // EC-440: the previews bucket (repo artifacts, backend-independent). Appended to