Repository navigation
Conversation
kapi 1.3 reports the plan's exact content-memory count as memoryExact (kapi 1.2 wrote tmExact), so the plan reader read 0 on 1.3. It now reads memoryExact and falls back to tmExact, for the totals and the per-locale table. The output plan-tm-exact becomes plan-memory-exact; plan-tm-exact stays as a deprecated alias with the same value. The step summary, the sticky PR comment and the README say "content memory" in place of "TM", and the README names setup-kapi's parse-cache input. A stub harness checks the plan outputs, summary and comment for both plan shapes. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01PWc9qYQJ93y88XrN6TkMvT
The action description and the README's opening line say the action runs kapi commands that bring a project's content and its translations up to date, gate content quality and plan cost, and report what changed to a delivery step the workflow owns. The README's loop section now matches kapi 1.3: reuse fills from content memory, translation carries the voice context, a unit with a failing finding counts as translated and holds its locale out of shipping, and an approval is recorded in the project's context store and shared with kapi context push. kapi 1.3 has no kapi commit command. The gate summary names a voice gate, and a comment says target-language content. 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.
kapi 1.3 renamed the plan total
tmExacttomemoryExact, so plan mode reported 0 units recoverable from content memory. The plan reader and the per-locale table now readmemoryExact // tmExact // 0, so kapi 1.2 and 1.3 both work, and a stub test (test/plan-outputs.sh) checks both shapes. The outputplan-tm-exactis renamedplan-memory-exact;plan-tm-exactstays as a deprecated alias with the same value.The description, README and summary text use content-engine and content-memory wording, and the cache paragraph names setup-kapi's
parse-cache(withcache-tmfor older setup-kapi).The second commit corrects the README's description of the review loop for 1.3: there is no
kapi commit, decisions are not stored under.kapi/state/, coverage isestablished, and the brand gate is the voice gate. It can be dropped on its own.Release as v1.7.0 after setup-kapi v1.6.0.
🤖 Generated with Claude Code