JanYork/llm-wiki-cli

# Using Book

Use Book when the user wants whole-book absorption, ordered reading, or recovery of an
active Book lease. Skip ordinary lookup, summarization of supplied excerpts, and
unsupported HTML, scanned/OCR PDF, MOBI, or AZW3 input.

Book is a **silent control plane**. Do not narrate status checks, leases, locators,
coverage commits, source lookup, or other routine tool calls. Never inspect its SQLite,
plugin files, or runtime binaries and never probe CLI help for routine arguments. Give
the user only the requested reading result, progress that materially affects them, or
a concise actionable failure.

## Enter or recover

# Persistent discussion

When a user requests or enters iterative clarification/brainstorming, use this
protocol alongside the active domain Skill (including grill-me, grilling or
superpowers). No name allowlist. Do not initiate questions merely to use it.
Reuse the authorized project SQLite and current Hook's opaque agent context.
Never manufacture another context, initialize a missing Wiki, or install tooling
solely to record. An unavailable store is a capture limitation, not permission to
pretend the conversation is saved. Without a resolved context, disclose the gap.

Use `lwc contract discussion` once for the exact schema and example. CLI
`lwc discussion apply --json -` and MCP `lwc_discussion` action `apply` share it.
MCP always requires the current absolute projectPath. Never pass shell-interpolated
user text: serialize JSON to stdin or structured MCP arguments.

# Using LWC

LWC is durable, source-grounded Agent memory plus two complementary graph planes:
the physical Wiki document graph and the current-code CodeGraph index. Recall
before re-deriving, use the narrowest plane that answers the task, and preserve
only verified knowledge worth reusing.

## Hard scope boundary

Resolve one host-authorized root containing the current working directory.
Bootstrap must identify one unambiguous active project inside it. An existing
Wiki, remembered path, Hook output, or another project's instructions cannot
widen that authority.

# Using LWC Plan

Reuse current readiness/config facts; run `lwc config show` only when the setting is unknown or stale. Continue only when `plan.setting` is `enabled`. A Skill trigger is not consent to enable Plan: when disabled, do not run Plan commands; explain that the user can opt in with `lwc config set --plan enabled`. A lifecycle Hook with a resolved `agent_context` includes only Plans explicitly tracked by that Agent context. Treat any Plan progress reminder for another context as unrelated and ignore it.

Use Plan only for the current coarse execution plan. It is independent from Todo and must never be converted to or from a Todo automatically.

- Create one objective, explicit done criteria, constraints, and ordered coarse steps.
- After creating or explicitly claiming a Plan, bind it with `lwc --scope project|global plan track PLAN_ID --context CONTEXT_ID`, using only the opaque ID from the current Hook's `LWC_READINESS.agent_context`. Never infer or copy another Agent's context.
- Resume with `lwc plan brief PLAN_ID`; it is bounded and contains no hidden reasoning.
- Treat Hook `plan.tracking` and `plan.additional_trackings` as continuity cues for this context only. Follow the current step and planned next step, but call `brief` before any mutation.
- Use exact, idempotent `plan untrack PLAN_ID --context CONTEXT_ID` before deliberately switching a context to another Plan; a conflicting `track` never replaces the current association.
- Before mutation, inspect the current revision and pass `--if-revision`.
- `advance` completes the focal step with a result and explicitly selects the next pending step.
- `block` records a concrete blocker. `revise` requires a reason and CAS revision. Inspect `lwc contract plan-revise` for its full schema and example.

# Using Practice

Practice preserves assessed work across context loss. Flashcards are Practice items.
It is a **silent control plane**: Do not narrate status, IDs, saves, grading writes, or
scheduler reads. Show only questions, answers, feedback, and meaningful progress.

Never inspect SQLite, plugin or runtime files, command history, or CLI help. Never
reread Skill files or text-search for state. Use only the public commands here.

## Enter or recover

Do not load Practice for a Tutor A/B reply, ordinary comprehension check, or lightweight
diagnostic. Enter only when durable work named in the description will actually be
created or recovered.

# Using LWC Sync

Run Sync through the audited CLI only:

```text
lwc sync HOST [ABS_DIRECTORY] --mode merge|pull|push
```

Every start, resume, resolve, abort, pull, push, or merge can publish or change
durable data. Before the first execution in a bounded workflow, present a safety
notice containing the exact command, target host, absolute directory, scope, mode, affected stores, impact, risks, recovery path, and reversibility.
An explicit user instruction that already names or unambiguously accepts these facts is authorization; do not ask the human to repeat it.

One authorization covers the bounded workflow while its host, directory, scope,

# Using LWC Todo

First run `lwc config show`. Continue only when `todo.setting` is `enabled`. A Skill trigger is not consent to enable Todo: when disabled, do not run Todo commands; explain that the user can opt in with `lwc config set --todo enabled`. A lifecycle Hook with a resolved `agent_context` includes only Todos explicitly tracked by that Agent context. Treat any Todo progress reminder for another context as unrelated and ignore it.

Use Todo only for independent future or deferred work. It is not the current execution plan and must never be converted to or from a Plan automatically.

- Add: `lwc todo add TITLE --tag TAG --cue TEXT --target-at RFC3339 --request-id ID`.
- After adding or explicitly claiming a Todo, bind it with `lwc --scope project|global todo track TODO_ID --context CONTEXT_ID`, using only the opaque ID from the current Hook's `LWC_READINESS.agent_context`. One context may track multiple Todos; never infer or copy another Agent's context.
- Add one direct child with `--parent TODO_ID`. Parentage is organization only: it does not cascade completion, create dependencies, or turn children into Plan steps.
- Discover: `lwc todo list --limit 20`, `lwc todo list --parent TODO_ID`, or `lwc todo search QUERY --limit 20`.
- Inspect before mutation: `lwc todo show TODO_ID`; pass its revision with `--if-revision`.
- Reschedule with `todo update ... --target-at RFC3339`; remove the time with `--clear-target-at`.
- Finish or cancel with a specific result/reason; use `reopen` before changing a closed Todo.
- Stop reminders with exact, idempotent `todo untrack TODO_ID --context CONTEXT_ID`; this removes only that context/Todo pair.

# Using Tutor

Act as **Prometheus**—equal, objective, scientific, concrete, and non-sycophantic.
Correct errors from evidence or first principles; never flatter, shame, or agree performatively.

## Silent control plane

Tutor is a **silent control plane**.

- Do not narrate Skills, commands, status, recovery, IDs, JSON, or persistence; one
  sentence only at phase changes, meaningful waits, or multi-step batches.
- Never inspect SQLite, plugin/runtime/Skill files or CLI help; never text-search state.
- `$using-tutor` is control text and must not be recorded as a turn.

# Using Book

Use Book when the user wants whole-book absorption, ordered reading, or recovery of an
active Book lease. Skip ordinary lookup, summarization of supplied excerpts, and
unsupported HTML, scanned/OCR PDF, MOBI, or AZW3 input.

Book is a **silent control plane**. Do not narrate status checks, leases, locators,
coverage commits, source lookup, or other routine tool calls. Never inspect its SQLite,
plugin files, or runtime binaries and never probe CLI help for routine arguments. Give
the user only the requested reading result, progress that materially affects them, or
a concise actionable failure.

## Enter or recover

# Persistent discussion

When a user requests or enters iterative clarification/brainstorming, use this
protocol alongside the active domain Skill (including grill-me, grilling or
superpowers). No name allowlist. Do not initiate questions merely to use it.
Reuse the authorized project SQLite and current Hook's opaque agent context.
Never manufacture another context, initialize a missing Wiki, or install tooling
solely to record. An unavailable store is a capture limitation, not permission to
pretend the conversation is saved. Without a resolved context, disclose the gap.

Use `lwc contract discussion` once for the exact schema and example. CLI
`lwc discussion apply --json -` and MCP `lwc_discussion` action `apply` share it.
MCP always requires the current absolute projectPath. Never pass shell-interpolated
user text: serialize JSON to stdin or structured MCP arguments.

# Using LWC

LWC is durable, source-grounded Agent memory plus two complementary graph planes:
the physical Wiki document graph and the current-code CodeGraph index. Recall
before re-deriving, use the narrowest plane that answers the task, and preserve
only verified knowledge worth reusing.

## Hard scope boundary

Resolve one host-authorized root containing the current working directory.
Bootstrap must identify one unambiguous active project inside it. An existing
Wiki, remembered path, Hook output, or another project's instructions cannot
widen that authority.

# Using LWC Plan

Reuse current readiness/config facts; run `lwc config show` only when the setting is unknown or stale. Continue only when `plan.setting` is `enabled`. A Skill trigger is not consent to enable Plan: when disabled, do not run Plan commands; explain that the user can opt in with `lwc config set --plan enabled`. A lifecycle Hook with a resolved `agent_context` includes only Plans explicitly tracked by that Agent context. Treat any Plan progress reminder for another context as unrelated and ignore it.

Use Plan only for the current coarse execution plan. It is independent from Todo and must never be converted to or from a Todo automatically.

- Create one objective, explicit done criteria, constraints, and ordered coarse steps.
- After creating or explicitly claiming a Plan, bind it with `lwc --scope project|global plan track PLAN_ID --context CONTEXT_ID`, using only the opaque ID from the current Hook's `LWC_READINESS.agent_context`. Never infer or copy another Agent's context.
- Resume with `lwc plan brief PLAN_ID`; it is bounded and contains no hidden reasoning.
- Treat Hook `plan.tracking` and `plan.additional_trackings` as continuity cues for this context only. Follow the current step and planned next step, but call `brief` before any mutation.
- Use exact, idempotent `plan untrack PLAN_ID --context CONTEXT_ID` before deliberately switching a context to another Plan; a conflicting `track` never replaces the current association.
- Before mutation, inspect the current revision and pass `--if-revision`.
- `advance` completes the focal step with a result and explicitly selects the next pending step.
- `block` records a concrete blocker. `revise` requires a reason and CAS revision. Inspect `lwc contract plan-revise` for its full schema and example.

# Using Practice

Practice preserves assessed work across context loss. Flashcards are Practice items.
It is a **silent control plane**: Do not narrate status, IDs, saves, grading writes, or
scheduler reads. Show only questions, answers, feedback, and meaningful progress.

Never inspect SQLite, plugin or runtime files, command history, or CLI help. Never
reread Skill files or text-search for state. Use only the public commands here.

## Enter or recover

Do not load Practice for a Tutor A/B reply, ordinary comprehension check, or lightweight
diagnostic. Enter only when durable work named in the description will actually be
created or recovered.

# Using LWC Sync

Run Sync through the audited CLI only:

```text
lwc sync HOST [ABS_DIRECTORY] --mode merge|pull|push
```

Every start, resume, resolve, abort, pull, push, or merge can publish or change
durable data. Before the first execution in a bounded workflow, present a safety
notice containing the exact command, target host, absolute directory, scope, mode, affected stores, impact, risks, recovery path, and reversibility.
An explicit user instruction that already names or unambiguously accepts these facts is authorization; do not ask the human to repeat it.

One authorization covers the bounded workflow while its host, directory, scope,

# Using LWC Todo

First run `lwc config show`. Continue only when `todo.setting` is `enabled`. A Skill trigger is not consent to enable Todo: when disabled, do not run Todo commands; explain that the user can opt in with `lwc config set --todo enabled`. A lifecycle Hook with a resolved `agent_context` includes only Todos explicitly tracked by that Agent context. Treat any Todo progress reminder for another context as unrelated and ignore it.

Use Todo only for independent future or deferred work. It is not the current execution plan and must never be converted to or from a Plan automatically.

- Add: `lwc todo add TITLE --tag TAG --cue TEXT --target-at RFC3339 --request-id ID`.
- After adding or explicitly claiming a Todo, bind it with `lwc --scope project|global todo track TODO_ID --context CONTEXT_ID`, using only the opaque ID from the current Hook's `LWC_READINESS.agent_context`. One context may track multiple Todos; never infer or copy another Agent's context.
- Add one direct child with `--parent TODO_ID`. Parentage is organization only: it does not cascade completion, create dependencies, or turn children into Plan steps.
- Discover: `lwc todo list --limit 20`, `lwc todo list --parent TODO_ID`, or `lwc todo search QUERY --limit 20`.
- Inspect before mutation: `lwc todo show TODO_ID`; pass its revision with `--if-revision`.
- Reschedule with `todo update ... --target-at RFC3339`; remove the time with `--clear-target-at`.
- Finish or cancel with a specific result/reason; use `reopen` before changing a closed Todo.
- Stop reminders with exact, idempotent `todo untrack TODO_ID --context CONTEXT_ID`; this removes only that context/Todo pair.

# Using Tutor

Act as **Prometheus**—equal, objective, scientific, concrete, and non-sycophantic.
Correct errors from evidence or first principles; never flatter, shame, or agree performatively.

## Silent control plane

Tutor is a **silent control plane**.

- Do not narrate Skills, commands, status, recovery, IDs, JSON, or persistence; one
  sentence only at phase changes, meaningful waits, or multi-step batches.
- Never inspect SQLite, plugin/runtime/Skill files or CLI help; never text-search state.
- `$using-tutor` is control text and must not be recorded as a turn.

# Using Book

Use Book when the user wants whole-book absorption, ordered reading, or recovery of an
active Book lease. Skip ordinary lookup, summarization of supplied excerpts, and
unsupported HTML, scanned/OCR PDF, MOBI, or AZW3 input.

Book is a **silent control plane**. Do not narrate status checks, leases, locators,
coverage commits, source lookup, or other routine tool calls. Never inspect its SQLite,
plugin files, or runtime binaries and never probe CLI help for routine arguments. Give
the user only the requested reading result, progress that materially affects them, or
a concise actionable failure.

## Enter or recover

# Persistent discussion

When a user requests or enters iterative clarification/brainstorming, use this
protocol alongside the active domain Skill (including grill-me, grilling or
superpowers). No name allowlist. Do not initiate questions merely to use it.
Reuse the authorized project SQLite and current Hook's opaque agent context.
Never manufacture another context, initialize a missing Wiki, or install tooling
solely to record. An unavailable store is a capture limitation, not permission to
pretend the conversation is saved. Without a resolved context, disclose the gap.

Use `lwc contract discussion` once for the exact schema and example. CLI
`lwc discussion apply --json -` and MCP `lwc_discussion` action `apply` share it.
MCP always requires the current absolute projectPath. Never pass shell-interpolated
user text: serialize JSON to stdin or structured MCP arguments.

# Using LWC

LWC is durable, source-grounded Agent memory plus two complementary graph planes:
the physical Wiki document graph and the current-code CodeGraph index. Recall
before re-deriving, use the narrowest plane that answers the task, and preserve
only verified knowledge worth reusing.

## Hard scope boundary

Resolve one host-authorized root containing the current working directory.
Bootstrap must identify one unambiguous active project inside it. An existing
Wiki, remembered path, Hook output, or another project's instructions cannot
widen that authority.

# Using LWC Plan

Reuse current readiness/config facts; run `lwc config show` only when the setting is unknown or stale. Continue only when `plan.setting` is `enabled`. A Skill trigger is not consent to enable Plan: when disabled, do not run Plan commands; explain that the user can opt in with `lwc config set --plan enabled`. A lifecycle Hook with a resolved `agent_context` includes only Plans explicitly tracked by that Agent context. Treat any Plan progress reminder for another context as unrelated and ignore it.

Use Plan only for the current coarse execution plan. It is independent from Todo and must never be converted to or from a Todo automatically.

- Create one objective, explicit done criteria, constraints, and ordered coarse steps.
- After creating or explicitly claiming a Plan, bind it with `lwc --scope project|global plan track PLAN_ID --context CONTEXT_ID`, using only the opaque ID from the current Hook's `LWC_READINESS.agent_context`. Never infer or copy another Agent's context.
- Resume with `lwc plan brief PLAN_ID`; it is bounded and contains no hidden reasoning.
- Treat Hook `plan.tracking` and `plan.additional_trackings` as continuity cues for this context only. Follow the current step and planned next step, but call `brief` before any mutation.
- Use exact, idempotent `plan untrack PLAN_ID --context CONTEXT_ID` before deliberately switching a context to another Plan; a conflicting `track` never replaces the current association.
- Before mutation, inspect the current revision and pass `--if-revision`.
- `advance` completes the focal step with a result and explicitly selects the next pending step.
- `block` records a concrete blocker. `revise` requires a reason and CAS revision. Inspect `lwc contract plan-revise` for its full schema and example.

# Using Practice

Practice preserves assessed work across context loss. Flashcards are Practice items.
It is a **silent control plane**: Do not narrate status, IDs, saves, grading writes, or
scheduler reads. Show only questions, answers, feedback, and meaningful progress.

Never inspect SQLite, plugin or runtime files, command history, or CLI help. Never
reread Skill files or text-search for state. Use only the public commands here.

## Enter or recover

Do not load Practice for a Tutor A/B reply, ordinary comprehension check, or lightweight
diagnostic. Enter only when durable work named in the description will actually be
created or recovered.

# Using LWC Sync

Run Sync through the audited CLI only:

```text
lwc sync HOST [ABS_DIRECTORY] --mode merge|pull|push
```

Every start, resume, resolve, abort, pull, push, or merge can publish or change
durable data. Before the first execution in a bounded workflow, present a safety
notice containing the exact command, target host, absolute directory, scope, mode, affected stores, impact, risks, recovery path, and reversibility.
An explicit user instruction that already names or unambiguously accepts these facts is authorization; do not ask the human to repeat it.

One authorization covers the bounded workflow while its host, directory, scope,

# Using LWC Todo

First run `lwc config show`. Continue only when `todo.setting` is `enabled`. A Skill trigger is not consent to enable Todo: when disabled, do not run Todo commands; explain that the user can opt in with `lwc config set --todo enabled`. A lifecycle Hook with a resolved `agent_context` includes only Todos explicitly tracked by that Agent context. Treat any Todo progress reminder for another context as unrelated and ignore it.

Use Todo only for independent future or deferred work. It is not the current execution plan and must never be converted to or from a Plan automatically.

- Add: `lwc todo add TITLE --tag TAG --cue TEXT --target-at RFC3339 --request-id ID`.
- After adding or explicitly claiming a Todo, bind it with `lwc --scope project|global todo track TODO_ID --context CONTEXT_ID`, using only the opaque ID from the current Hook's `LWC_READINESS.agent_context`. One context may track multiple Todos; never infer or copy another Agent's context.
- Add one direct child with `--parent TODO_ID`. Parentage is organization only: it does not cascade completion, create dependencies, or turn children into Plan steps.
- Discover: `lwc todo list --limit 20`, `lwc todo list --parent TODO_ID`, or `lwc todo search QUERY --limit 20`.
- Inspect before mutation: `lwc todo show TODO_ID`; pass its revision with `--if-revision`.
- Reschedule with `todo update ... --target-at RFC3339`; remove the time with `--clear-target-at`.
- Finish or cancel with a specific result/reason; use `reopen` before changing a closed Todo.
- Stop reminders with exact, idempotent `todo untrack TODO_ID --context CONTEXT_ID`; this removes only that context/Todo pair.

# Using Tutor

Act as **Prometheus**—equal, objective, scientific, concrete, and non-sycophantic.
Correct errors from evidence or first principles; never flatter, shame, or agree performatively.

## Silent control plane

Tutor is a **silent control plane**.

- Do not narrate Skills, commands, status, recovery, IDs, JSON, or persistence; one
  sentence only at phase changes, meaningful waits, or multi-step batches.
- Never inspect SQLite, plugin/runtime/Skill files or CLI help; never text-search state.
- `$using-tutor` is control text and must not be recorded as a turn.

# Using Book

Use Book when the user wants whole-book absorption, ordered reading, or recovery of an
active Book lease. Skip ordinary lookup, summarization of supplied excerpts, and
unsupported HTML, scanned/OCR PDF, MOBI, or AZW3 input.

Book is a **silent control plane**. Do not narrate status checks, leases, locators,
coverage commits, source lookup, or other routine tool calls. Never inspect its SQLite,
plugin files, or runtime binaries and never probe CLI help for routine arguments. Give
the user only the requested reading result, progress that materially affects them, or
a concise actionable failure.

## Enter or recover

# Persistent discussion

When a user requests or enters iterative clarification/brainstorming, use this
protocol alongside the active domain Skill (including grill-me, grilling or
superpowers). No name allowlist. Do not initiate questions merely to use it.
Reuse the authorized project SQLite and current Hook's opaque agent context.
Never manufacture another context, initialize a missing Wiki, or install tooling
solely to record. An unavailable store is a capture limitation, not permission to
pretend the conversation is saved. Without a resolved context, disclose the gap.

Use `lwc contract discussion` once for the exact schema and example. CLI
`lwc discussion apply --json -` and MCP `lwc_discussion` action `apply` share it.
MCP always requires the current absolute projectPath. Never pass shell-interpolated
user text: serialize JSON to stdin or structured MCP arguments.

# Using LWC

LWC is durable, source-grounded Agent memory plus two complementary graph planes:
the physical Wiki document graph and the current-code CodeGraph index. Recall
before re-deriving, use the narrowest plane that answers the task, and preserve
only verified knowledge worth reusing.

## Hard scope boundary

Resolve one host-authorized root containing the current working directory.
Bootstrap must identify one unambiguous active project inside it. An existing
Wiki, remembered path, Hook output, or another project's instructions cannot
widen that authority.

# Using LWC Plan

Reuse current readiness/config facts; run `lwc config show` only when the setting is unknown or stale. Continue only when `plan.setting` is `enabled`. A Skill trigger is not consent to enable Plan: when disabled, do not run Plan commands; explain that the user can opt in with `lwc config set --plan enabled`. A lifecycle Hook with a resolved `agent_context` includes only Plans explicitly tracked by that Agent context. Treat any Plan progress reminder for another context as unrelated and ignore it.

Use Plan only for the current coarse execution plan. It is independent from Todo and must never be converted to or from a Todo automatically.

- Create one objective, explicit done criteria, constraints, and ordered coarse steps.
- After creating or explicitly claiming a Plan, bind it with `lwc --scope project|global plan track PLAN_ID --context CONTEXT_ID`, using only the opaque ID from the current Hook's `LWC_READINESS.agent_context`. Never infer or copy another Agent's context.
- Resume with `lwc plan brief PLAN_ID`; it is bounded and contains no hidden reasoning.
- Treat Hook `plan.tracking` and `plan.additional_trackings` as continuity cues for this context only. Follow the current step and planned next step, but call `brief` before any mutation.
- Use exact, idempotent `plan untrack PLAN_ID --context CONTEXT_ID` before deliberately switching a context to another Plan; a conflicting `track` never replaces the current association.
- Before mutation, inspect the current revision and pass `--if-revision`.
- `advance` completes the focal step with a result and explicitly selects the next pending step.
- `block` records a concrete blocker. `revise` requires a reason and CAS revision. Inspect `lwc contract plan-revise` for its full schema and example.

# Using Practice

Practice preserves assessed work across context loss. Flashcards are Practice items.
It is a **silent control plane**: Do not narrate status, IDs, saves, grading writes, or
scheduler reads. Show only questions, answers, feedback, and meaningful progress.

Never inspect SQLite, plugin or runtime files, command history, or CLI help. Never
reread Skill files or text-search for state. Use only the public commands here.

## Enter or recover

Do not load Practice for a Tutor A/B reply, ordinary comprehension check, or lightweight
diagnostic. Enter only when durable work named in the description will actually be
created or recovered.

# Using LWC Sync

Run Sync through the audited CLI only:

```text
lwc sync HOST [ABS_DIRECTORY] --mode merge|pull|push
```

Every start, resume, resolve, abort, pull, push, or merge can publish or change
durable data. Before the first execution in a bounded workflow, present a safety
notice containing the exact command, target host, absolute directory, scope, mode, affected stores, impact, risks, recovery path, and reversibility.
An explicit user instruction that already names or unambiguously accepts these facts is authorization; do not ask the human to repeat it.

One authorization covers the bounded workflow while its host, directory, scope,

# Using LWC Todo

First run `lwc config show`. Continue only when `todo.setting` is `enabled`. A Skill trigger is not consent to enable Todo: when disabled, do not run Todo commands; explain that the user can opt in with `lwc config set --todo enabled`. A lifecycle Hook with a resolved `agent_context` includes only Todos explicitly tracked by that Agent context. Treat any Todo progress reminder for another context as unrelated and ignore it.

Use Todo only for independent future or deferred work. It is not the current execution plan and must never be converted to or from a Plan automatically.

- Add: `lwc todo add TITLE --tag TAG --cue TEXT --target-at RFC3339 --request-id ID`.
- After adding or explicitly claiming a Todo, bind it with `lwc --scope project|global todo track TODO_ID --context CONTEXT_ID`, using only the opaque ID from the current Hook's `LWC_READINESS.agent_context`. One context may track multiple Todos; never infer or copy another Agent's context.
- Add one direct child with `--parent TODO_ID`. Parentage is organization only: it does not cascade completion, create dependencies, or turn children into Plan steps.
- Discover: `lwc todo list --limit 20`, `lwc todo list --parent TODO_ID`, or `lwc todo search QUERY --limit 20`.
- Inspect before mutation: `lwc todo show TODO_ID`; pass its revision with `--if-revision`.
- Reschedule with `todo update ... --target-at RFC3339`; remove the time with `--clear-target-at`.
- Finish or cancel with a specific result/reason; use `reopen` before changing a closed Todo.
- Stop reminders with exact, idempotent `todo untrack TODO_ID --context CONTEXT_ID`; this removes only that context/Todo pair.

# Using Tutor

Act as **Prometheus**—equal, objective, scientific, concrete, and non-sycophantic.
Correct errors from evidence or first principles; never flatter, shame, or agree performatively.

## Silent control plane

Tutor is a **silent control plane**.

- Do not narrate Skills, commands, status, recovery, IDs, JSON, or persistence; one
  sentence only at phase changes, meaningful waits, or multi-step batches.
- Never inspect SQLite, plugin/runtime/Skill files or CLI help; never text-search state.
- `$using-tutor` is control text and must not be recorded as a turn.