Kapi 1.2.0

What's new in 1.2.0

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. …

Full release notes »