Repository navigation
docs(kaizen): diagrams and counts match the code again, held by a contract test (4.1.3) - #42
Merged
Merged
Conversation
…tract test (4.1.3) hooks.svg drew six hook registrations for nine, review-pipeline.svg ten reviewers for eleven, and six diagrams still drew deploy, monitor and postmortem as core skills after the move to kaizen-ops. Diagrams fixed in their generator (new `ops` style), stale counts and ops attributions fixed in the docs and READMEs. tests/diagrams.test.mjs now holds the SVGs to the generator, hooks.json, agents/ and the kaizen-ops split, and every counted claim to the code; run against 4.1.2 it fails on each drift. Co-Authored-By: Claude Opus 5.5 <[email protected]> Claude-Session: https://claude.ai/code/session_012iZk6aQ3fhJy4jrZhfWtaf
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
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.
Summary
The READMEs were held by contract tests; the 14 SVGs and the counted claims in the docs were not, and they had drifted.
Diagrams (fixed in
docs/media/source/diagrams.mjs, then regenerated):hooks.svg: six registrations drawn for nine — adds theSessionStartheartbeat, the PreToolUse reviewer launch log and the Stop token ledger.review-pipeline.svg: eleven reviewers (renderingwas missing) and the cost estimate before launch.push-gate.svg: launch log andreview record --run.opsstyle (dashed teal) + legend:deploy,monitor,postmortemare no longer drawn as core skills inkaizen-loop,artifacts-map,deploy-flow,incident-lifecycle,learnings-loop,help-routing. The loop shows the four-command start.Docs: "Five hook registrations" (the-loop) → nine, "ten code reviewers" (review) → eleven; README, positioning, help guide, metrics skill attribute deploy/monitor/postmortem to kaizen-ops; root README row no longer lists postmortems among what core reads back by itself, mentions the four-command start and the cost per feature.
Contract test
plugins/kaizen/tests/diagrams.test.mjs:KAIZEN_DIAGRAMS_OUT; CRLF-normalized for Windows checkouts);hooks.svgdraws everyhooks.jsonregistration and announces their count;review-pipeline.svgdraws exactly the code reviewers ofagents/;/kaizen:deploy|monitor|postmortem;Kaizen 4.1.3.
Test plan
node --test plugins/kaizen/tests/*.test.mjs plugins/kaizen-ops/tests/*.test.mjs→ 212 pass, 0 failmain(4.1.2): fails on the hooks, reviewers, kaizen-ops-as-core and counts driftshelp-routing.svgdrew the/kaizen-ops:commands as core skillsGenerated by Claude Code