dotmd-cli 0.48.0 → 0.48.1

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "dotmd-cli",
-  "version": "0.48.0",
+  "version": "0.48.1",
   "description": "CLI for managing markdown documents with YAML frontmatter — index, query, validate, graph, export, Notion sync, AI summaries.",
   "type": "module",
   "license": "MIT",

package/src/config.mjs

@@ -66,6 +66,11 @@ const DEFAULTS = {
 
   taxonomy: {
     surfaces: null,
+    // modules: when null (default), the project doesn't enumerate product
+    // modules — the modules-required validator silently skips. When set to
+    // an array, modules are taxonomy-enforced AND moduleRequiredFor activates.
+    // Mirrors the long-standing semantics of `taxonomy.surfaces`.
+    modules: null,
     moduleRequiredFor: ['partial', 'paused', 'awaiting', 'queued-after'],
   },
 
@@ -444,6 +449,9 @@ export async function resolveConfig(cwd, explicitConfigPath) {
   const validSurfaces = config.taxonomy.surfaces
     ? new Set(config.taxonomy.surfaces)
     : null;
+  const validModules = config.taxonomy.modules
+    ? new Set(config.taxonomy.modules)
+    : null;
   const moduleRequiredStatuses = new Set(config.taxonomy.moduleRequiredFor);
 
   const indexPath = config.index?.path
@@ -497,6 +505,7 @@ export async function resolveConfig(cwd, explicitConfigPath) {
     lifecycle: { archiveStatuses, skipStaleFor, skipWarningsFor, terminalStatuses, filedStatuses },
 
     validSurfaces,
+    validModules,
     moduleRequiredStatuses,
 
     indexPath,

package/src/validate.mjs

@@ -117,8 +117,13 @@ export function validateDoc(doc, frontmatter, headingTitle, config) {
     doc.errors.push({ path: doc.path, level: 'error', message: '`modules` must be a YAML list when present.' });
   }
 
-  if (config.moduleRequiredStatuses.has(doc.status) && !doc.modules?.length) {
-    doc.errors.push({ path: doc.path, level: 'error', message: '`modules` is required for active/ready/planned/blocked docs; use a real module, `platform`, or `none`.' });
+  // modules-required gate: only fires when the project has actively declared
+  // a module taxonomy (`taxonomy.modules` is an array). Repos with no product
+  // modules (CLIs, dev tooling, single-domain apps) shouldn't be forced to
+  // sprinkle `modules: [none]` on every plan as a sentinel. Mirrors the
+  // long-standing `taxonomy.surfaces` opt-in semantics.
+  if (config.validModules && config.moduleRequiredStatuses.has(doc.status) && !doc.modules?.length) {
+    doc.errors.push({ path: doc.path, level: 'error', message: '`modules` is required for this status; declare a real module from `taxonomy.modules`, or `none` as the explicit no-module sentinel.' });
   }
 
   if (config.validSurfaces && !config.lifecycle.skipWarningsFor.has(doc.status)) {