v0.0.16

One new verb, kb completion, so that tab completion works in bash and PowerShell. The decision is DR-0056. It was written and tested red first, and checked by sourcing the script in real bash and PowerShell against the real workspace.

kb completion bash and kb completion powershell write a completion script to standard output (pwsh is accepted for powershell). It completes the verbs, the subverbs of project, observation, concept, source, link, record and document (and document review), each verb's flags once a dash is typed, help topics after help, paths after -db, -in, -out, -a, -b, -jsonl, -root and -dir, and project names after --project and after project show, concepts, set-status, set-description, rename and delete. Project names come from kb project list in the current directory and honour a -db typed earlier on the line.

kb completion SHELL -install installs it instead. With bash the script goes to $XDG_DATA_HOME/bash-completion/completions/kb, or the same path under ~/.local/share, and a file that kb did not write is never overwritten (exit 73). With PowerShell it writes kb-completion.ps1 beside the profile and adds one line that dot-sources it, once. Windows PowerShell 5.1 is not covered.

The verb list is read from the verbs kb registers, so a new verb is completed without anyone naming it. The subverbs and flags are tables, and the tests fail when a table disagrees with the code, so a new flag or subverb must be added to them. The verb opens no database and refuses -db. A bad or missing shell name, a surplus argument and an unknown flag exit 2.

Upgrading: nothing that worked changes. kb completion did not exist before, so a script that called it got exit 2 (unknown verb).

Full Changelog: v0.0.15...v0.0.16