The STATUS banner correctly notes that basectl history is implemented. However, the detailed description of basectl history — output format, filter options (--project, --command, --status, --limit, --format json), and relationship to basectl logs — lives under a section literally called "Future Commands." Any reader consulting this doc to understand the shipped basectl history command is sent the wrong signal: the content is accurate but the section label says the feature is future work.
Fix: Rename "Future Commands" to "Shipped Commands" (covering basectl history), and move the still-unimplemented items (basectl explain last-error, basectl report) to a separate "Planned Commands" or "Future Work" subsection below it.
File: docs/observability.md
The STATUS banner correctly notes that
basectl historyis implemented. However, the detailed description ofbasectl history— output format, filter options (--project,--command,--status,--limit,--format json), and relationship tobasectl logs— lives under a section literally called "Future Commands." Any reader consulting this doc to understand the shippedbasectl historycommand is sent the wrong signal: the content is accurate but the section label says the feature is future work.Fix: Rename "Future Commands" to "Shipped Commands" (covering
basectl history), and move the still-unimplemented items (basectl explain last-error,basectl report) to a separate "Planned Commands" or "Future Work" subsection below it.File:
docs/observability.md