v0.2.0
Adds dataset table extraction and timestamp sorting, and brings exit codes and check severity in line with the tools agents
already know (ls, grep, linters).
Added
wiki table <file>— extract a dataset's markdown table as text, csv, tsv, or json, so it pipes straight into jq, duckdb,
or an LLM. One clean table per file needs no flag; for a file with several,--n N(1-based) picks one, and the command lists
them rather than guessing.wiki list --sort=path|timestamp(with--reverse) — order entries by their curated frontmatter timestamp, falling back to
file mtime when it is absent. Newest-first by default; --reverse gives oldest-first, handy for a grooming pass.
Changed
- Exit codes now follow ls/grep/lint conventions. The enumeration and diagnostic commands (
list, tasks, tags, properties, property, links, backlinks, orphans, unresolved) exit0when they find nothing, the way ls of an empty directory succeeds
(previously they returned 1). Exit1now means a genuine "no match": search with no hits, table with no such table, and
check with conformance errors. Exit2remains a real error (no bundle, bad arguments, unreadable file).- Scripts heads-up: if you branched on exit 1 to detect "no results" from a query command, test the output instead (e.g.
[ -n "$(wiki unresolved)" ]). search keeps its grep-like 1 on no match.
- Scripts heads-up: if you branched on exit 1 to detect "no results" from a query command, test the output instead (e.g.
wiki check: a broken link is now a warning, not an error. A bundle that links to not-yet-written entries now passes check
(exit 0), matching the OKF view that an unresolved link is future knowledge, not malformed. Only a missing or invalid type
is still an error (exit 1). wiki unresolved remains the dedicated list of broken links.- CI heads-up: if you relied on check failing for broken links, it no longer does; gate on wiki unresolved being non-empty
instead.
- CI heads-up: if you relied on check failing for broken links, it no longer does; gate on wiki unresolved being non-empty