Summary
base-demo's Quick Start shows basectl history --project base-demo --limit 5 but not basectl history --report, a v1.7.0 feature for generating local Markdown/JSON activity summaries.
Details
- base v1.7.0 added
basectl history --report to generate local Markdown or JSON activity summaries from recent command history and log metadata without dumping raw logs or uploading telemetry (base's CHANGELOG.md [1.7.0] section).
- README.md's Quick Start shows plain
basectl history --project base-demo --limit 5 only.
Impact
--report is a distinct, higher-value view of the same history data already being demonstrated (raw list vs. a summarized report), and its "no telemetry upload" framing is directly relevant to the trust-building goal of this repository.
Suggested fix
Add a basectl history --report example after the existing basectl history line in the README Quick Start (and/or an observability_step addition in demo/demo.sh).
Summary
base-demo's Quick Start shows
basectl history --project base-demo --limit 5but notbasectl history --report, a v1.7.0 feature for generating local Markdown/JSON activity summaries.Details
basectl history --reportto generate local Markdown or JSON activity summaries from recent command history and log metadata without dumping raw logs or uploading telemetry (base'sCHANGELOG.md[1.7.0]section).basectl history --project base-demo --limit 5only.Impact
--reportis a distinct, higher-value view of the same history data already being demonstrated (raw list vs. a summarized report), and its "no telemetry upload" framing is directly relevant to the trust-building goal of this repository.Suggested fix
Add a
basectl history --reportexample after the existingbasectl historyline in the README Quick Start (and/or anobservability_stepaddition indemo/demo.sh).