Repository navigation
Conversation
From kapi 1.3 a project's terms, voice profiles, content memory and recorded decisions live in kapi's workspace outside git, and a runner starts with an empty one. Both workflows take a context-sync input and pass it to kapi-action@v1, which runs kapi context pull before the command and, with true, kapi context push after it. The default, false, keeps the current behaviour. The gate workflow's comment says an established threshold needs the pull, in place of the retired reviewed threshold and kapi commit. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01PWc9qYQJ93y88XrN6TkMvT
The README describes kapi as a content engine rather than a continuous-localization path. The run description names the content memory, terms and voice, settles the source first, and says a unit with a failing finding stays translated and holds its language out of shipping. Approvals are recorded in the project's context and shared through its context backend or the connected server, in place of kapi commit and .kapi/state/, and raise established coverage. The gate text names the voice, terms and QA gates, says each finding fails or reports, and covers a check that did not run. Both input lists gain context-sync. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01PWc9qYQJ93y88XrN6TkMvT
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The README described the workflows as the continuous-localization path and pointed at a committed
.kapi-state.json, which kapi 1.3 does not have. It now describes them in content-engine terms with the 1.3 status ladder (draft, translated, established) and gates (voice, terms, QA; findings fail or report). The gate workflow's comments drop the retiredreviewedthreshold andkapi commit.Both workflows gain a
context-syncinput (defaultfalse) passed through to kapi-action, which already has it in v1.6.0, so a project that shares its context through a backend can bring its approvals onto the runner.No input or output names change, so v1 consumers are unaffected. Release as v1.3.0.
🤖 Generated with Claude Code