kblisted

# Knowledge Base Management The user wants to view or manage the Orchestray knowledge base. ## Protocol 1. **Parse arguments**: `$ARGUMENTS` - If empty or `list`: List all KB entries. - If starts with `view`: View full content of a specific KB entry by ID. - If starts with `add`: Create a new KB entry with the given category and topic. - If `clean`: Remove all stale entries past their TTL. - If `stats`: Show KB statistics. - If `reconcile`: Scan KB directories and rebuild index from existing files. 2. **Read index**: Read `.orchestray/kb/index.json`. If the file or directory does not exist, report: "No knowledge base found. The KB is populated automatically during orchestrations when agents write findings." and stop. ### List Operation Parse the `entries` array from `.orchestray/kb/index.json`. For each entry, determine staleness: an entry is stale if today's date exceeds `created_at` + `ttl_days`. Display as a table: ``` ## Knowledge Base | ID | Category | Topic | Source Agent | Created | Stale? | |----|----------|-------|-------------|---------|--------| | {id} | {category} | {topic} | {source_agent} | {created_at} | {Yes/No} | ... ``` Below the table: "{N} entries total, {S} stale." Show usage hints: - `view {id}` -- Show full entry content - `add {category} {topic}` -- Add a new entry - `clean` -- Remove stale entries - `stats` -- Show KB statistics If the `entries` array is empty: "Knowledge base is empty. Entries are created automatically d