Kapi CLI: vanhemmat versiot ja versiohistoria

kapi 1.2.0
Changes since v1.1.0.
kapi 1.2.0 is the first stable release since 1.1.0. One command, kapi up, brings a project to the state its recipe declares. kapi check holds content to the voice, terms and gates the project binds, and edits are written back into the original formats. Commands, recipe keys and file names changed along the way, so read Upgrading from 1.1.0 before you upgrade an existing project.
Bring a project up to date
- kapi up runs the project's default flow over every collection and target language until each gated scope ships or parks. --plan reports the pending work, content-memory reuse and a token estimate without writing anything. --json prints one event per line, and the record whose type is result carries the outcome.
- In a recipe with a bowrain: block, kapi up runs the loop on the server. --local keeps it on this machine, and --server requires the server.
- The recipe is kapi.yaml. It declares collections:, each with its content, and profiles: that name channels and bind governance. A collection with source_only: true has no target language, and kapi up then works on the source alone.
- kapi status shows each locale's coverage (draft, translated, reviewed, signed off) and whether it clears its ship gate. kapi status --review lists the units awaiting review.
- Decisions are staged in the working store. kapi commit writes them into the committed record under .kapi/state/.
- A source change demotes existing translations instead of deleting them, so reuse and reviewers still see the previous target.
- A recipe step that runs an external command or a script runs only after someone allows it.
- kapi run <name> runs a flow from .kapi/flows/ with the project's bindings.
Check content and gate releases
- kapi check verifies content and prints a versioned report (kapi.check/v1) with stable rule ids, severity and the block location. Inside a project, a bare kapi check checks the project.
- kapi check --ship runs the project's bound gates (voice, terminology, rule-based checks) and its ship gates. --gate selects gates, and --locale scopes the target side to one language.
- --diff-against <rev>, --diff-range A..B, --diff-file <path> and --staged check only the blocks a change touches.
- A check that read no content reports the verdict did_not_run and names the cause, instead of passing. Each analyzer runs a canary first, so a checker that cannot fail is reported.
- Comments in source and markup files are checked at their own point: the one a content entry names with comments: {channel: ...}, else defaults.comments.channel, else the entry's own point. kapi reads Go comments itself, and the sourcecode plugin reads comments in other programming languages.
- A content entry with comments: {only: true} is checked for its comments alone and governs only the comment layer of its files. Their content sits at the next entry that claims the same files, or at the project's default point.
- A voice profile's style.comments sets the limits on sentence and comment length, and on comment density in a check scoped to a diff. A comment line that opens with a directive marker declared under comments: is set aside.
- kapi apply and the MCP tool apply_edits take comment edits for Go and, with the sourcecode plugin 0.3.0, for TypeScript, TSX and JavaScript. An edit in one of those three languages is written only when the project's formatter agrees with it, and that formatter runs code the project controls: kapi apply asks at a terminal or reads KAPI_TRUST_EXEC, while apply_edits never runs one. Such an edit reports that it did not run, writes nothing, and a person applies it with kapi apply.
- term-check, and so kapi check --ship, enforces the do-not-translate terms in the terms store. A ship state is withheld where terminology is bound but was not checked.
- --validate report adds the format readers' structure and encoding findings to the report.
Govern wording with voice profiles, terms and content memory
- kapi voice manages v

Installation
Homebrew (kapi CLI, Apache-2.0, no plugins):
brew install neokapi/tap/kapi-cli
Homebrew (kapi + bowrain plugin):
brew install neokapi/tap/bowrain-cli
Homebrew (Kapi desktop app, macOS):
brew install --cask neokapi/tap/kapi
Homebrew (Bowrain desktop app, macOS):
brew install --cask neokapi/tap/bowrain