@taskset/cli 5.1.0 → 6.1.0

package/docs/agent-closeout.md

@@ -0,0 +1,69 @@
+---
+title: Follow the agent closeout contract
+description: Subtasks done, related docs created, taxonomy valid, optional lesson and skill promotion.
+contentType: How-to
+navLabel: Agent Closeout
+---
+
+# Follow the agent closeout contract
+
+Before marking a Taskset task `done`, agents must leave the repository in a state another agent can trust.
+
+## Required
+
+1. Every checklist item for the outcome is checked (`- [x]`), or intentionally removed with rationale.
+2. Every child task is `done` or `canceled` (not left `todo` / `doing` / `blocked`).
+3. Durable outputs exist as documents when the work produced them:
+   - evidence → `research`
+   - lasting choice → `decision` / `adr`
+   - procedure → `runbook`
+   - product context → `story` / `flow`
+   - recurring mistake → `lesson`
+   - residual risk → `concern`
+   - inventory / spot-check → `audit`
+4. Documents and tasks are linked with `--related` (short hex IDs in CLI flags).
+5. Markdown prose that points at those files uses repository-relative filepaths, not bare hex ids.
+6. Labels and projects reuse repository taxonomy; do not invent one-off tags when an allowlist exists.
+7. `taskset doctor --json` reports no errors for the paths you touched.
+
+## Optional config gates
+
+When enabled in `taskset.config.ts`, core blocks `done` transitions that violate:
+
+```typescript
+closeout: {
+  enforceChildCompletion: true,
+  blockDoneWithOpenConcerns: true,
+  requireLessonWhenLabeled: ['requires-lesson'],
+}
+```
+
+Defaults are off so existing repositories keep current behavior.
+
+## Skill promotion bridge
+
+Lessons may declare skill targets:
+
+```bash
+taskset document create lesson \
+  --title "…" \
+  --related-skill .agents/skills/foo/SKILL.md \
+  --related <task-id>
+```
+
+Contract:
+
+- Taskset stores the lesson evidence and correct pattern.
+- The consumer primary skill stores lasting how-to.
+- Agents update the skill in the same change when `--related-skill` is present.
+- Taskset does not auto-edit skills unless a future promote helper is explicitly applied with config opt-in.
+
+## Program closeout
+
+For multi-task programs:
+
+```bash
+taskset task program <parent-id> --json
+```
+
+Treat `closeoutReady: false` as a signal to finish children, accept or archive open concerns, accept research, and complete checklist items before marking the parent done.

package/docs/agents/_meta.ts

@@ -0,0 +1,6 @@
+export default {
+	index: 'For Agents',
+	workflows: 'Agent Workflows',
+	commands: 'Agent Commands',
+	'query-recipes': 'Query Recipes',
+}

package/docs/agents/commands.md

@@ -0,0 +1,94 @@
+---
+title: Use Taskset command contracts
+description: Machine-oriented contracts for discovery, JSON output, clear flags, search, and identifiers.
+contentType: Reference
+navLabel: Agent Commands
+---
+
+# Use Taskset command contracts
+
+This page quotes the contracts agents should rely on. For the full human reference, see [CLI reference](../cli-reference.md).
+
+## Discovery and defaults
+
+| Fact | Contract |
+| --- | --- |
+| Repository marker | Nearest ancestor `.taskset/` directory |
+| Optional config | `taskset.config.ts` beside that root |
+| Missing config | Built-in statuses, priorities, and defaults |
+| `taskset config --json` | Includes `rootDirectory`, `configPath`, `hasConfig`, `dataDirectory`, `config` |
+| `taskset init` | Creates `.taskset/`; `--config` writes optional config |
+
+## Output and exit codes
+
+- Stdout carries requested output
+- Stderr carries diagnostics and generation warnings
+- Exit `0` means success
+- Exit `1` means repository or domain failure
+- Exit `2` means usage or validation failure
+
+## Identifiers and file links
+
+- Entity `id` values are immutable 5–6 character lowercase hex strings
+- Filenames are `{sequence}-{slug}-{id}.md`
+- Commands, frontmatter relationships, and JSON handoffs use the short `id`
+- Filename sequence prefixes are display metadata only—never identity
+- Markdown hyperlinks to docs, skills, or `.taskset/` entities must use the
+  repository-relative filepath (include the `.md` file). Do not use a bare hex
+  id as a link target.
+
+## Array updates and clear flags
+
+Array options replace the whole stored array. Repeat the singular option once per desired value. Clear with the exact plural flag:
+
+- `--clear-dependencies`
+- `--clear-labels`
+- `--clear-assignees`
+- `--clear-reviewers`
+- `--clear-related`
+- `--clear-files`
+- `--clear-directories`
+- `--clear-projects`
+- `--clear-parent`
+- `--clear-owner`
+- `--clear-severity`
+- `--clear-related-skills`
+- `--clear-packs`
+- `--clear-class`
+- `--clear-cadence`
+
+Do not guess a clear flag from the singular setter name.
+
+## Search and impact
+
+- `--search` is token-aware: every normalized term must match title or body
+- Terms may appear in any order
+- `--impact` expands file, directory, or dependency matches to dependent work
+
+## Document kinds
+
+Use only these kinds:
+
+- `story`
+- `flow`
+- `decision` (`adr`, `dr` aliases)
+- `research`
+- `runbook`
+- `lesson` (`antipattern` alias)
+- `concern`
+- `audit`
+
+Document statuses are `draft`, `ready`, `active`, `accepted`, `superseded`, and `archived`.
+
+Lesson options: `--severity`, repeatable `--related-skill`, repeatable `--pack`.
+Concern options: `--class`, `--cadence`. List filters include `--class` and `--severity`.
+
+## Program rollup
+
+```bash
+taskset task program <parent-id> --json
+```
+
+Returns child status counts, blocked deps, related open concerns, research not yet accepted, checklist completion, and `closeoutReady`.
+
+Copy-paste recipes: [Query recipes](query-recipes.md).

package/docs/agents/index.md

@@ -0,0 +1,113 @@
+---
+title: Operate Taskset as an agent
+description: Plan, research, decide, operate, and track repository work with the Taskset CLI, skill, and JSON contracts.
+contentType: How-to
+navLabel: For Agents
+---
+
+# Operate Taskset as an agent
+
+Use this page when you are an agent operating Taskset in a repository. Humans should start with [Getting started](../getting-started.md). Maintainer architecture lives under [Maintainer docs](../maintainers/index.md).
+
+Taskset is not only a task tracker. You use it to capture plans, research, decisions, flows, runbooks, lessons, concerns, audits, and the tasks that execute them in one Git-native graph.
+
+## Load the skill first
+
+Prefer the packaged skill before inventing workflow:
+
+```bash
+npx skills add FalseFoundation/taskset --skill taskset
+```
+
+Project and global skill installs both work. After a project npm install, offline copies also live at `node_modules/@taskset/cli/skills/taskset/SKILL.md`.
+
+## Invoke the CLI
+
+Do not assume `pnpm taskset`. Use whichever runner the environment provides:
+
+```bash
+npx @taskset/cli document list --json
+npx @taskset/cli task list --json
+pnpm dlx @taskset/cli doctor --json
+yarn dlx @taskset/cli document show your_document_id_here --json
+bunx @taskset/cli sync --json
+taskset task list --json
+```
+
+## Discover the repository
+
+1. Walk upward for `.taskset/`
+2. Load optional `taskset.config.ts` at that root when present
+3. Otherwise use built-in defaults
+
+No config file is required. `taskset init` creates `.taskset/` only. Pass `--config` when the repository wants an optional TypeScript overlay.
+
+## Choose the right artifact
+
+| If the work produces… | Create… |
+| --- | --- |
+| A user outcome or acceptance criteria | `story` |
+| A journey with variants and checks | `flow` |
+| Evidence, options, or a recommendation | `research` |
+| A lasting architectural or product choice | `decision` / `adr` |
+| A repeatable recovery or ops procedure | `runbook` |
+| A recurring mistake or correct pattern | `lesson` |
+| An open residual risk | `concern` |
+| A structured inventory or spot-check | `audit` |
+| Scoped execution with status and owners | `task` |
+| Multi-task program health | parent task + `taskset task program` |
+
+Link documents and tasks with `--related`. Keep one-off scratch in the task body. See [Memory model](../memory-model.md) for anti-examples.
+
+## Core operating rules
+
+- Treat `.taskset/tasks/` and kind-specific document directories as the source of truth
+- Mutate through CLI commands when a command exists
+- Use short hex ids such as `a1b2c3` in commands and `--related`. Filename sequence prefixes are display-only.
+- Markdown hyperlinks to files must use repository-relative paths (for example [document types](../document-types.md)), not bare hex ids
+- Prefer `--json` for handoffs
+- Create follow-up tasks or checklist subtasks for newly discovered work
+- Create research, decision, runbook, story, flow, lesson, concern, or audit documents when work produces reusable evidence, lasting choices, recurring patterns, or residual risks
+- Keep statuses current mid-work
+
+## Command map
+
+| Goal | Command |
+| --- | --- |
+| Inspect root and defaults | `taskset config --json` |
+| Validate repository | `taskset doctor --json` |
+| List or search tasks | `taskset task list --search "terms" --json` |
+| List or search documents | `taskset document list research --search "terms" --json` |
+| Open concerns on a path | `taskset document list concern --directory apps/foo --status active --json` |
+| Lessons by search | `taskset document list lesson --search "casl" --json` |
+| Show one entity | `taskset task show your_task_id_here --json` |
+| Create executable work | `taskset task create --title "Describe the work"` |
+| Create durable memory | `taskset document create research --title "Evaluate options" --related your_task_id_here` |
+| Create a lesson | `taskset document create lesson --title "…" --severity high --related your_task_id_here` |
+| Create a concern | `taskset document create concern --title "…" --class authz --related your_task_id_here` |
+| Program health | `taskset task program your_parent_task_id_here --json` |
+| Change status | `taskset task status your_task_id_here doing` |
+| Impact query | `taskset task list --file path/or/dir --impact --json` |
+| Repair and rebuild | `taskset sync --json` |
+
+Full contracts: [CLI reference](../cli-reference.md), [Agent command contracts](commands.md), and [Query recipes](query-recipes.md).
+
+## Workflow checklist
+
+1. Confirm the repository root with `taskset config --json`
+2. Search existing tasks and documents before creating duplicates
+3. Capture durable evidence, decisions, lessons, or concerns as documents mid-work
+4. Create or update tasks for executable delivery
+5. Resolve ownership before mutating assigned work
+6. Keep statuses current, then re-validate with `taskset doctor --json`
+
+## Related pages
+
+- [Agent workflows](workflows.md)
+- [Agent command contracts](commands.md)
+- [Query recipes](query-recipes.md)
+- [Memory model](../memory-model.md)
+- [Agent closeout](../agent-closeout.md)
+- [Security tracking](../security-compliance-tracking.md)
+- [Document types](../document-types.md)
+- [Task files](../task-files.md)

package/docs/agents/llms.txt

@@ -0,0 +1,35 @@
+# Taskset
+
+> Git-native Markdown workspace for planning, research, decisions, operations, residual risk, and delivery.
+
+Taskset stores stories, flows, research, decisions, runbooks, lessons, concerns, audits, and tasks under `.taskset/`. The CLI is published as `@taskset/cli` and runs through package runners or a global install. Config files are optional.
+
+## For agents
+
+- [Operate Taskset as an agent](https://taskset.false.foundation/docs/agents)
+- [Follow agent workflows](https://taskset.false.foundation/docs/agents/workflows)
+- [Use Taskset command contracts](https://taskset.false.foundation/docs/agents/commands)
+- [Query operational memory](https://taskset.false.foundation/docs/agents/query-recipes)
+- [Choose a document type](https://taskset.false.foundation/docs/document-types)
+- [Choose memory layers](https://taskset.false.foundation/docs/memory-model)
+- [Agent closeout contract](https://taskset.false.foundation/docs/agent-closeout)
+- [Security and compliance tracking](https://taskset.false.foundation/docs/security-compliance-tracking)
+- [Understand task files](https://taskset.false.foundation/docs/task-files)
+- [CLI reference](https://taskset.false.foundation/docs/cli-reference)
+
+## For humans
+
+- [Keep the whole delivery story beside the code](https://taskset.false.foundation/docs)
+- [Start a Taskset repository](https://taskset.false.foundation/docs/getting-started)
+- [Configure Taskset defaults](https://taskset.false.foundation/docs/configuration)
+- [Taxonomy cookbook](https://taskset.false.foundation/docs/taxonomy-cookbook)
+
+## Optional offline skill
+
+After install, load `node_modules/@taskset/cli/skills/taskset/SKILL.md`, or install with:
+
+```text
+npx skills add FalseFoundation/taskset --skill taskset
+```
+
+Offline docs also ship at `node_modules/@taskset/cli/docs/`. Prefer repository-relative `.md` filepaths for Markdown hyperlinks; use short hex entity ids only in CLI commands and `--related`.

package/docs/agents/query-recipes.md

@@ -0,0 +1,76 @@
+---
+title: Query operational memory
+description: Copy-paste --json recipes for program blockers and open security concerns.
+contentType: Reference
+navLabel: Query Recipes
+---
+
+# Query operational memory
+
+Prefer `--json` for agent handoffs. Use short hex IDs in commands and
+`--related`. Filename sequence prefixes are display-only. Markdown hyperlinks
+to files must use repository-relative paths (see [commands](commands.md)).
+
+## Open concerns on a path
+
+```bash
+taskset document list concern --directory apps/foo --status active --json
+taskset document list concern --label security --status active --json
+taskset document list concern --class authz --status active --json
+```
+
+## Lessons by search or severity
+
+```bash
+taskset document list lesson --search "casl capability" --json
+taskset document list lesson --severity high --json
+taskset document show <lesson-id> --type lesson --json
+```
+
+## Audits and research
+
+```bash
+taskset document list audit --status ready --json
+taskset document list research --status ready --json
+```
+
+## Program health
+
+```bash
+taskset task program <parent-id> --json
+```
+
+Useful fields:
+
+- `children.byStatus` / `children.openIds`
+- `blockedDependencies`
+- `relatedOpenConcerns`
+- `relatedResearchNotAccepted`
+- `checklist`
+- `closeoutReady`
+
+## Closeout gaps
+
+```bash
+taskset doctor --json
+```
+
+Interpret:
+
+| Code | Meaning |
+| --- | --- |
+| `missing-template-heading` | lesson/concern/audit body missing required `##` section |
+| `missing-reference` | related/dependsOn target ID does not exist |
+| `unknown-taxonomy` | label/project/class outside allowlist |
+| `closeout-gap` | done task labeled for lesson without a related lesson |
+| `missing-owner` | active concern without owner (when configured) |
+| `stale-research` | ready research older than N days without follow-up task |
+
+## Create trail in one change
+
+```bash
+taskset document create concern --title "Telegram capability must not grant CASL" --class authz --related <task-id> --json
+taskset document create lesson --title "Capability flags are enablement only" --severity high --related <concern-or-task-id> --json
+taskset task program <parent-id> --json
+taskset doctor --json
+```

package/docs/agents/workflows.md

@@ -0,0 +1,60 @@
+---
+title: Follow agent workflows in Taskset
+description: Ownership checks, mid-work updates, operational memory, and monorepo habits for agent operators.
+contentType: How-to
+navLabel: Agent Workflows
+---
+
+# Follow agent workflows in Taskset
+
+These workflows assume the CLI is available and `.taskset/` already exists. Initialize with `taskset init` when it does not. Use documents for durable memory and tasks for execution; link them so later agents inherit the full story.
+
+## Before you execute a task
+
+1. Run `taskset task show your_task_id_here --json`
+2. Resolve `git config --get user.name`
+3. Compare owner and assignees with that identity
+4. Pause for confirmation when another person owns or is exclusively assigned the task
+5. Check unresolved dependencies and blockers before status changes
+
+Matching ownership does not override blockers. A generic instruction such as “work on the next task” does not override another person’s assignment.
+
+## While you execute
+
+- Set the active task to `doing` when work starts
+- Create child tasks (`--parent`) or checklist items (`- [ ]`) for newly discovered work
+- Check off finished checklist items as `- [x]`
+- Mark finished child tasks `done`
+- Create research, decision, runbook, story, flow, lesson, concern, or audit documents when evidence, lasting choices, recurring patterns, or residual risks appear
+- Link documents and tasks with `--related` (short hex ids in CLI flags)
+- When linking to those files in Markdown prose, use the repository-relative filepath
+- Update a primary skill when the session designates one and a lasting lesson emerges; if a lesson uses `--related-skill`, update those skill paths in the same change
+- For multi-task programs, inspect health with `taskset task program <parent-id> --json`
+
+Do not leave discovered work only in chat.
+
+## Close-out
+
+1. Confirm acceptance criteria are met
+2. Confirm every tracked subtask is finished or intentionally resolved
+3. Confirm related lessons/concerns/audits exist when the work produced them
+4. Set the parent task to `done` only after children and checklists are complete
+5. Run `taskset doctor --json` when the change touched contracts, taxonomy, or many files
+
+See [Agent closeout](../agent-closeout.md) for the full contract and optional config gates.
+
+## Monorepo habits
+
+- Prefer declared package names and existing Taskset projects over directory-name guesses
+- Record `--depends-on` only for real execution prerequisites
+- Attach the narrowest accurate `--file` or `--directory` scopes
+- Validate the changed package and affected dependents
+- Reuse taxonomy labels and projects; do not invent one-off tags when allowlists exist
+
+## Batch and sync
+
+Use `taskset document batch manifest.json --json` for multi-document jobs. Use `taskset sync --json` after upgrades or when filenames, ids, or generated views need repair.
+
+## Discovery recipes
+
+Copy-paste JSON recipes for open concerns, lessons, and program blockers live in [Query recipes](query-recipes.md).

package/docs/cli-reference.md

@@ -1,16 +1,15 @@
 ---
-title: CLI Reference
+title: Look up Taskset CLI commands
 description: Complete reference for the taskset command-line interface.
+contentType: Reference
+navLabel: CLI Reference
 ---
 
-# CLI Reference
+# Look up Taskset CLI commands
 
-The `taskset` command is a thin adapter over `@taskset/core`. It parses
-arguments, validates command options, calls core operations, and renders human
-or JSON output.
+The `taskset` command is a thin adapter over `@taskset/core` for the full Taskset surface: stories, flows, research, decisions, runbooks, lessons, concerns, audits, and tasks. It parses arguments, validates options, calls core operations, and renders human or JSON output.
 
-Use `pnpm taskset <command>` when Taskset is installed as a project
-dependency. The examples below use `taskset` directly for brevity.
+Invoke it with `npx @taskset/cli`, `pnpm dlx @taskset/cli`, `yarn dlx @taskset/cli`, `bunx @taskset/cli`, a project binary, or a global install. Examples below use `taskset` directly.
 
 ## Common Behavior
 
@@ -46,12 +45,10 @@ Exit codes:
 ### `init`
 
 ```bash
-taskset init [--cwd <path>]
+taskset init [--config] [--cwd <path>]
 ```
 
-Initializes a Taskset repository in the target directory. The command creates
-`taskset.config.ts`, `.taskset/tasks/`, and `.taskset/.gitignore` when they do
-not already exist.
+Initializes a Taskset repository. The command resolves a root from an existing `.taskset/`, Git or workspace markers, or the working directory, then creates `.taskset/` task and document directories plus `.taskset/.gitignore` when they do not already exist. Pass `--config` to also write optional `taskset.config.ts`.
 
 Human output:
 
@@ -65,15 +62,15 @@ Initialized Taskset in <root-directory>
 taskset config [--json] [--cwd <path>]
 ```
 
-Discovers the nearest `taskset.config.ts` by walking upward from the working
-directory.
+Discovers the nearest `.taskset/` directory by walking upward from the working directory. Optional `taskset.config.ts` at that root overlays defaults when present.
 
-Human output is the config file path. JSON output contains:
+Human output is the config file path when a config exists, or `defaults (<root-directory>)` when it does not. JSON output contains:
 
 ```json
 {
   "rootDirectory": "...",
   "configPath": "...",
+  "hasConfig": false,
   "dataDirectory": "...",
   "config": {}
 }
@@ -85,13 +82,14 @@ Human output is the config file path. JSON output contains:
 taskset doctor [--json] [--cwd <path>]
 ```
 
-Validates the repository without modifying files. It scans canonical task
-metadata, paths, and graph relationships.
+Validates the repository without modifying files. It scans canonical task and
+document metadata, paths, graph relationships, required template headings for
+operational kinds, taxonomy allowlists, and optional closeout gaps.
 
 Human success output:
 
 ```text
-Taskset repository is valid (<count> tasks)
+Taskset repository is valid (<count> tasks, <count> documents)
 ```
 
 Human failure output is tab-separated:
@@ -100,8 +98,8 @@ Human failure output is tab-separated:
 <code>	<path-or->	<message>	<remediation>
 ```
 
-JSON output is the full doctor result, including `valid`, `taskCount`, and
-diagnostics.
+JSON output is the full doctor result, including `valid`, `taskCount`,
+`documentCount`, and diagnostics. Warnings do not fail the command; errors do.
 
 ### `generate`
 
@@ -311,7 +309,7 @@ Human output is the serialized task Markdown. JSON output contains:
 
 ```json
 {
-  "relativePath": ".taskset/tasks/0000001-short-title.md",
+  "relativePath": ".taskset/tasks/0000001-short-title-a1b2c3.md",
   "metadata": {},
   "body": "...",
   "derived": {}
@@ -378,17 +376,31 @@ remove those inbound references and delete the target in one mutation.
 Human output is the deleted task ID. JSON output contains `deleted: true`
 alongside the deleted task record.
 
+### `task program`
+
+```bash
+taskset task program <parent-id> [--json] [--cwd <path>]
+```
+
+Summarizes a parent task as a program rollup: child counts by status, open child
+IDs, blocked dependency edges, related open concerns, related research not yet
+accepted, parent checklist completion, and `closeoutReady`.
+
+Human output is one tab-separated summary line. JSON output is the full rollup
+object.
+
 ### `task migrate-ids`
 
 ```bash
 taskset task migrate-ids [--json] [--cwd <path>]
 ```
 
-Atomically converts legacy `TS-` task IDs to seven-digit, title-derived IDs and
-rewrites canonical relationships plus references in repository text files.
-Dependencies, Git internals, build output, caches, generated views, indexes,
-and snapshots are excluded. Human output is a tab-separated
-old-to-new mapping; JSON emits the same mapping as objects.
+Atomically converts legacy `TS-` and sequential task IDs to immutable short hex
+IDs, normalizes filenames to `{sequence}-{slug}-{id}.md`, repairs duplicate
+sequence prefixes by `createdAt`, and rewrites canonical relationships plus
+references in repository text files. Dependencies, Git internals, build output,
+caches, generated views, indexes, and snapshots are excluded. Human output is a
+tab-separated old-to-new mapping; JSON emits the same mapping as objects.
 
 ### `sync`
 
@@ -396,14 +408,17 @@ old-to-new mapping; JSON emits the same mapping as objects.
 taskset sync [--concurrency <count>] [--json] [--cwd <path>]
 ```
 
-Ensures every canonical document directory exists under `.taskset`, applies
-legacy task-ID and repository-reference migrations, and rebuilds generated
-views. Progress counts and percentages are sent to stderr.
+Ensures every canonical document directory exists under `.taskset`, migrates
+legacy task and document IDs to short hex IDs, normalizes filenames, repairs
+duplicate sequence prefixes by `createdAt`, rewrites repository text
+references, and rebuilds generated views. Progress counts and percentages are
+sent to stderr.
 
 ## Document Commands
 
 `document` may be shortened to `doc`. Supported types are `story`, `flow`,
-`decision`, `research`, and `runbook`; `adr` and `dr` alias `decision`.
+`decision`, `research`, `runbook`, `lesson`, `concern`, and `audit`. Aliases:
+`adr` / `dr` → `decision`; `antipattern` → `lesson`.
 
 ```bash
 taskset document create <type> --title <title> [metadata options]
@@ -417,15 +432,19 @@ taskset document delete <document-id> [--type <type>] [--remove-dependencies] [-
 ```
 
 Create uses the type-specific template unless `--body` is supplied and accepts
-the same metadata options as `task create`. Import preserves the Markdown body
-and infers type from a recognized parent directory when possible. It copies by
-default; `--move` deletes the source only after the canonical document is
+the same metadata options as `task create`, plus lesson/concern options:
+`--severity`, repeatable `--related-skill`, repeatable `--pack`, `--class`, and
+`--cadence`. Lesson/concern/audit templates are validated for required headings.
+Import preserves the Markdown body and infers type from a recognized parent
+directory when possible (`lessons/`, `concerns/`, `audits/` included). It copies
+by default; `--move` deletes the source only after the canonical document is
 written successfully.
 
 List, show, update, status, and delete mirror the task commands, including
 search, filters, sort, impact, derived relationships, clear flags, and
-guarded deletion. Document statuses are `draft`, `ready`, `active`, `accepted`,
-`superseded`, and `archived`.
+guarded deletion. Document list also accepts `--class` and `--severity`. Document
+statuses are `draft`, `ready`, `active`, `accepted`, `superseded`, and
+`archived`.
 
 Batch manifests contain an array of `create`, `import`, `update`, and `export`
 operations. Work is paced with bounded concurrency, results preserve manifest