Maestro Knowledge

• background: false is the default. Use foreground dispatch whenever the result determines the current answer or next action.
• Use background: true only for independent work. If this turn must consume a background result, call observe exactly once with action: "wait" and a bounded timeout before continuing; never continue independently while the result is pending.
• Otherwise end the turn and wait for the automatic teammate-complete notification. Do not rely on SendMessage, team_msg, or hook callbacks as completion signals.
• Never silently ignore an unfinished dispatch.

1. Explicit keyword present → use its execution document or direct CLI lifecycle command (deterministic shortcut).
2. Otherwise infer from the intent (see the table above), e.g. "审计/清理知识库" → audit, "从工件/session 提取" → harvest, "知识图谱/wiki 健康" → wiki, "注册术语 X" → domain.
3. review / stage / promote map directly to the corresponding maestro knowledge CLI. review --refresh includes reconciliation; review --resolve includes disposition resolution; stage --signal --signal-ids includes signal recording. Preserve stable knowledge IDs, graph aliases, Run ID, Session ID, signal, candidate ID, disposition, target, and reason exactly; do not translate these operations into direct spec/knowhow writes.
4. For wiki, classify the sub-action: connect/连接 → ~/.maestro/workflows/wiki-connect.md; digest/摘要 → ~/.maestro/workflows/wiki-digest.md; health/search/cleanup/stats/健康/检查/(none) → ~/.maestro/workflows/wiki-manage.md.
5. Ambiguous → display the operation table and ask the user to pick.

Routing rules

• Remaining tokens after classification become the chosen step's own arguments.
• During an active Run, reusable knowhow is staged here with maestro knowledge stage knowhow ...; project knowhow is written only by explicit promotion. Outside a Run, direct /maestro-knowhow capture remains available.
• Outside any Run entirely (no Run to bind), maestro knowhow add --type <type> --title "<title>" --body-file <path> is the fast path — it writes .workflow/knowhow/ directly with no Session, no --evidence, and no review/promote cycle. Use it for standalone insights (tips, recipes, decisions) that do not belong to any Run's outcome; reserve stage → review → promote for candidates needing adjudication against the corpus.
• Stage candidate content from a temp file or stdin, never inline: write the content to a file and pass maestro knowledge stage <target> "<title>" --content-file <path|->. Inline positional content containing spaces, quotes, unicode (e.g. …), newlines, or leading dashes is misparsed and shifts later arguments.
• --signal-ids takes comma-separated IDs (--signal-ids spec:project:a,knowhow:b); space-separated values leak into positional arguments and corrupt the stage call.
• Use maestro knowledge review <session-id> as the human review surface. It shows fresh/missing/stale receipts, diversified evidence-backed matches, and copyable promote commands. --refresh reconciles all candidate source Runs. --resolve <candidate-id> --as <choice> --reason "..." resolves a candidate inline before displaying the refreshed view.
• Reconciliation is mandatory before completion but is not a popularity vote: exact identity, diversified semantic matches, and recorded/KG associations are evaluated separately. Unresolved semantic duplicate/conflict/supersession candidates may be sealed, but promotion must fail closed until resolved via review --resolve.
• promote --all promotes all eligible pending candidates (observed-only emits a warning); --include-observed has been removed.
• audit --prune --apply may only perform backed-up soft lifecycle transitions. Never physically delete knowledge or prune solely because it has low usage.