dotmd-cli 0.15.1 → 0.16.1

package/README.md

@@ -117,12 +117,12 @@ The default plan vocabulary is shaped around the **unstuck-action test**: every
 | `planned` | Wait for trigger | Queued; not yet ready to execute. |
 | `blocked` | **Monitor** | External arrival on its own schedule (hardware, vendor, third-party rollout). You can't speed it up. |
 | `partial` | **Spawn successors** | Shipped most of the plan; tail deferred. Body should reference successor plans tracking the tail. Visible but quiet (no nagging). |
-| `paused` | **Re-evaluate** | Intentionally set aside, no external dependency. Resume by deciding the work is still worth doing. Quiet. |
+| `paused` | **Re-evaluate** | Started but stopped mid-work; needs near-term review. NOT quiet — short (3-day) stale threshold so resume-decisions don't decay. |
 | `awaiting` | **Ask** | Needs a human decision or input. NOT quiet — pings get forgotten, so this status generates stale pressure to chase the answer. |
 | `queued-after` | **Check predecessor** | Sequenced behind another plan; can start once that one ships. Quiet. |
 | `archived` | — | No longer relevant; auto-moved to the archive directory on transition. |
 
-Each *quiet* status (`partial`, `paused`, `queued-after`, `archived`) is exempt from stale-warning pressure but still appears in active scope and metrics — quietness is a presentation flag, not a closure flag. `awaiting` deliberately stays loud so unanswered questions don't decay into invisible backlog.
+Each *quiet* status (`partial`, `queued-after`, `archived`) is exempt from stale-warning pressure but still appears in active scope and metrics — quietness is a presentation flag, not a closure flag. `awaiting` and `paused` deliberately stay loud so unanswered questions and stalled mid-flight work don't decay into invisible backlog.
 
 > **Heads-up:** versions before 0.15 included a `done` plan status in the defaults. It saw effectively zero real-world use (plans went `in-session`/`active` → `archived` directly), so it was dropped from the built-in vocabulary. To finish a plan, run `dotmd archive <plan-file>` — or, if you preferred the previous behavior, add `done` back via the `types.plan.statuses` key in your config.
 
@@ -423,6 +423,34 @@ dotmd lint                   # report issues
 dotmd lint --fix             # fix all issues
 ```
 
+### Manage Statuses
+
+```bash
+dotmd statuses                                              # table view, all types
+dotmd statuses --type plan                                  # one type
+dotmd statuses --json                                       # machine-readable
+
+dotmd statuses add paused --type plan --like blocked --quiet  # clone blocked, then quiet
+dotmd statuses set archived --type plan --no-quiet            # tweak a flag
+dotmd statuses remove obsolete --type plan                    # refuses if any docs use it
+
+dotmd statuses migrate plan                                 # array-form → rich-form
+```
+
+`--like <existing>` is the affordance for "kinda like X but…" — clones every
+flag from another status, then user flags override. Write commands print a flag
+diff and prompt for confirmation; pass `--yes` to skip the prompt or
+`--dry-run` to preview without writing. Edits are atomic: the rewrite lands in
+a sibling temp file, is validated by re-importing it and running
+`resolveConfig`, then renamed into place — a syntax error or new warning
+leaves the original untouched.
+
+**Lifecycle-override gotcha.** If your config has both rich-form `types` and an
+explicit `export const lifecycle = {...}`, the explicit lifecycle silently
+overrides per-status flags at runtime. `dotmd statuses` write commands refuse
+to write into that state and recommend deleting the explicit `lifecycle` block;
+pass `--ignore-lifecycle-override` to write anyway.
+
 ### Rename
 
 ```bash

package/bin/dotmd.mjs

@@ -59,6 +59,7 @@ Create & Export:
 
 Setup:
   init                              Create starter config + docs directory
+  statuses [list|add|set|remove|migrate]  Manage per-project status taxonomy
   watch [command]                   Re-run a command on file changes
   completions <shell>               Shell completion script (bash, zsh)
 
@@ -449,6 +450,53 @@ Options:
   --list                 List all glossary terms
   --json                 Output as JSON`,
 
+  statuses: `dotmd statuses — manage per-project status taxonomy
+
+Subcommands:
+  list [--type <t>] [--json]            Default. Table view of every status × type with all flags.
+                                        --type accepts comma-separated types.
+  add <name> --type <t> [--like <e>] [flags...]
+                                        Add a new status. --like <existing> clones every flag from
+                                        another status; user flags override. Inserts before the
+                                        first terminal/archive status. Refuses if name already
+                                        exists or is invalid.
+  set <name> --type <t> <flags...>      Edit flags on an existing status. Refuses if status doesn't
+                                        exist. Flags overwrite individually.
+  remove <name> --type <t>              Delete a status entry. Refuses if any docs use the status
+                                        (lists offenders, suggests \`dotmd migrate\`). Warns if an
+                                        explicit lifecycle export references the name.
+  migrate <type>                        One-shot conversion of array-form types.<t>.statuses to
+                                        rich form, pulling in peer staleDays/context and per-status
+                                        requiresModule from taxonomy.moduleRequiredFor.
+
+Flags accepted by add/set:
+  --context <expanded|listed|counted>   Briefing layout bucket
+  --staleDays <n|null>                  Stale threshold; null = never stale
+  --requiresModule / --no-requiresModule
+  --terminal / --no-terminal            Closure state — excluded from active-work scope
+  --archive / --no-archive              Auto-move to archive dir on transition
+  --skipStale / --no-skipStale
+  --skipWarnings / --no-skipWarnings
+  --quiet / --no-quiet                  Sugar for skipStale + skipWarnings (explicit overrides win)
+
+Workflow flags:
+  --yes                                 Skip the confirmation prompt
+  --dry-run, -n                         Show the diff without writing
+  --ignore-lifecycle-override           Write even when an explicit \`lifecycle\` export
+                                        would silently mask the per-status flags
+
+Examples:
+  dotmd statuses                                                  # list everything
+  dotmd statuses add paused --type plan --like blocked --quiet
+  dotmd statuses set archived --type plan --no-quiet
+  dotmd statuses remove obsolete --type plan
+  dotmd statuses migrate plan                                     # array → rich
+
+Lifecycle-override gotcha: if your config has both rich-form types and an explicit
+\`export const lifecycle\`, the runtime ignores per-status flags. The CLI refuses
+to write in that case unless you pass --ignore-lifecycle-override; the recommended
+fix is to delete the explicit \`lifecycle\` block so flags take effect.`,
+
   bulk: `dotmd bulk archive <f1> <f2> ... — archive multiple files at once
 
 Archives each file: sets status to archived, moves to archive
@@ -569,6 +617,7 @@ async function main() {
   if (command === 'migrate') { const { runMigrate } = await import('../src/migrate.mjs'); runMigrate(restArgs, config, { dryRun }); return; }
   if (command === 'fix-refs') { const { runFixRefs } = await import('../src/fix-refs.mjs'); runFixRefs(restArgs, config, { dryRun }); return; }
   if (command === 'doctor') { const { runDoctor } = await import('../src/doctor.mjs'); runDoctor(restArgs, config, { dryRun }); return; }
+  if (command === 'statuses') { const { runStatuses } = await import('../src/statuses.mjs'); await runStatuses(restArgs, config, { dryRun, type: typeArg }); return; }
 
   // All remaining commands need the index + render modules
   const { buildIndex } = await import('../src/index.mjs');
@@ -819,7 +868,7 @@ async function main() {
     'focus', 'query', 'plans', 'stale', 'actionable', 'index', 'pickup', 'finish', 'status', 'archive', 'bulk', 'touch', 'doctor',
     'unblocks', 'health', 'glossary',
     'fix-refs', 'lint', 'rename', 'migrate', 'notion', 'export', 'summary',
-    'watch', 'diff', 'new', 'init', 'completions',
+    'watch', 'diff', 'new', 'init', 'completions', 'statuses',
   ];
   const matches = allCommands
     .map(c => ({ cmd: c, dist: levenshtein(command, c) }))

package/dotmd.config.example.mjs

@@ -50,7 +50,7 @@ export const excludeDirs = ['evidence'];
 //       'planned':      { context: 'listed', staleDays: 30, requiresModule: true },
 //       'blocked':      { context: 'listed', staleDays: 30, requiresModule: true },
 //       'partial':      { context: 'expanded', requiresModule: true, quiet: true },     // shipped + deferred tail; visible, no nagging
-//       'paused':       { context: 'listed', requiresModule: true, quiet: true },       // intentionally set aside, no external dep
+//       'paused':       { context: 'listed', staleDays: 3, requiresModule: true },      // stopped mid-work, near-term review — loud (short stale threshold)
 //       'awaiting':     { context: 'listed', staleDays: 14, requiresModule: true },     // human input/decision wait — NOT quiet (pings get forgotten)
 //       'queued-after': { context: 'counted', requiresModule: true, quiet: true },      // sequenced behind another plan
 //       'archived':     { context: 'counted', archive: true, terminal: true, quiet: true },
@@ -103,13 +103,20 @@ export const statuses = {
 };
 
 // Lifecycle behavior — which statuses trigger special handling.
-// When using rich status definitions, these are derived from per-status flags.
-export const lifecycle = {
-  archiveStatuses: ['archived'],      // auto-move to archiveDir on transition
-  skipStaleFor: ['archived'],         // skip staleness checks
-  skipWarningsFor: ['archived'],      // skip validation warnings (summary, etc.)
-  terminalStatuses: ['archived', 'deprecated', 'reference', 'done'],  // skip current_state/next_step warnings, exclude from stats scope
-};
+//
+// IMPORTANT: only enable this block if you're using ARRAY-form types (above) or
+// no `types` definition. With rich-form types, the runtime derives these from
+// per-status `terminal` / `archive` / `skipStale` / `skipWarnings` / `quiet`
+// flags. An explicit `lifecycle` export sitting alongside rich-form types will
+// SILENTLY OVERRIDE the per-status flags — `dotmd statuses` will warn you
+// before writing into a config in that state.
+//
+// export const lifecycle = {
+//   archiveStatuses: ['archived'],      // auto-move to archiveDir on transition
+//   skipStaleFor: ['archived'],         // skip staleness checks
+//   skipWarningsFor: ['archived'],      // skip validation warnings (summary, etc.)
+//   terminalStatuses: ['archived', 'deprecated', 'reference'],  // skip current_state/next_step warnings, exclude from stats scope
+// };
 
 // Taxonomy validation — set fields to null to skip validation.
 // moduleRequiredFor is derived from requiresModule when using rich status definitions.

package/package.json

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