Skip to content

Releases: DarKWinGTM/claude-code-rules

v10.40 - Released companion plugin README guidance

Choose a tag to compare

@DarKWinGTM DarKWinGTM released this 02 Jun 13:33

Summary

  • add plugin-local image assets for governed-docs and memory-context-intelligence
  • expand both plugin READMEs with stronger orientation and usage guidance
  • add a concise companion-plugin section to the root README

Verification

  • plugin image paths were copied into their plugin-local img directories
  • selected README surfaces were updated and reviewed
  • git diff --check passed for the selected scope
  • push and tag publication succeeded

v10.39 - Released RULES diagram infrastructure doctrine

Choose a tag to compare

@DarKWinGTM DarKWinGTM released this 02 Jun 11:48

Summary

  • make diagram/ required governed-docs infrastructure for RULES
  • require diagram/STRUCTURE.md as the compact active whole-project diagram-side entrypoint
  • preserve design/** as semantic authority and future diagram/history/ / diagram/done/ as preservation infrastructure

Verification

  • runtime install/update verification passed for the touched active runtime owners
  • source/runtime parity and body-sufficiency checks passed in checked scope
  • git diff --check passed
  • source docs/design/changelog/TODO/phase/patch surfaces were synced for the release

memory-context-intelligence v0.9.29

Choose a tag to compare

Summary

  • add public /memory-context-intelligence:init setup surface
  • move default config target to ~/.claude/memory-context-intelligence.config.json
  • add shared analysis.scope_policy consumption while preserving explicit runtime narrowing precedence

Verification

  • focused init-wave tests passed
  • full python3 -m unittest discover -s tests -v passed
  • checked local /memory-context-intelligence:init proof completed
  • checked local /memory-context-intelligence:analysis proof confirmed config consumption

🤖 Generated with Claude Code

v10.38

Choose a tag to compare

@DarKWinGTM DarKWinGTM released this 01 Jun 23:17

Summary

  • Require plan-first authoring for actual governed /goal creation
  • Keep emitted /goal compact while referencing a full detailed plan file as route-only support
  • Keep /plan as explicit standalone planning, later route revision, or overflow only

Verification

  • Re-ran RULES install/update verification with 18 active runtime rules plus manifest
  • Re-checked targeted source/runtime parity for execution-and-goal-frame.md, phase-todo-artifact.md, and explanation-and-presentation.md
  • Re-ran git diff --check on the released source state

v10.37

Choose a tag to compare

@DarKWinGTM DarKWinGTM released this 01 Jun 17:18

Released mandatory Kroki-compatible governed diagram doctrine.

  • makes governed diagram source mandatory Kroki-compatible
  • defines allowed breadth as Kroki-compatible + governance-suitable
  • upgrades diagram/STRUCTURE.md into a bodyful whole-project detailed visual structure authority
  • keeps subject diagrams as zoom-in / decomposition views of the global structure
  • keeps inline answer/phase-local text diagrams outside governed source truth unless explicitly promoted

v10.36

Choose a tag to compare

@DarKWinGTM DarKWinGTM released this 01 Jun 12:20

Released unified diagram doctrine correction.

  • adds a dedicated governed diagram/ visual lane
  • opens diagram/STRUCTURE.md as the whole-repo visual anchor
  • keeps design/ as semantic authority when text and diagram differ
  • rejects automatic diagram splitting from design-shard symmetry
  • keeps inline answer/phase-local text-diagram formatting separate from repository diagram-source doctrine
  • preserves governed-docs/plugin behavior as downstream support rather than doctrine ownership

memory-context-intelligence v0.9.28

Choose a tag to compare

Summary

  • harden packet/additional emission so one selected topic always maps to one artifact
  • forbid combined multi-topic additional output and keep adaptive multi-topic deepening advisory-only before selection
  • sync plugin docs/tests/version surfaces for the split-contract release closeout

Verification

  • python3 -m unittest discover -s tests -v
  • claude plugin validate plugin/memory-context-intelligence
  • packet-path dry-run proof: single-topic preview contains topic-scope section and multi-topic packet build is rejected

🤖 Generated with Claude Code

memory-context-intelligence v0.9.27

Choose a tag to compare

Summary

  • re-cut the plugin-only release from an isolated clean checkout so the branch-first merge, push, tag, and GitHub release path are proven without unrelated working-tree drift in the release workspace
  • keep the README plugin-specific with the Claude Code installation tutorial still removed
  • preserve the checked adaptive deep-analysis runtime contract while bumping the package to 0.9.27 and the governed chain to 0.1.75

Included in this release

  • corrective clean plugin-only release recut records (phase/changelog/patch)
  • package/governed version sync for the clean recut
  • clone-path test portability fix so the full suite can pass in an isolated clean checkout

Boundaries

  • /memory-context-intelligence:analysis remains the only proved public surface
  • review and packet remain deferred
  • trace_evidence remains the live promotion anchor
  • this release still does not claim broad production readiness beyond checked plugin-scoped proof

v10.35 - README Core Capabilities list and doctrine framing

Choose a tag to compare

@DarKWinGTM DarKWinGTM released this 31 May 18:55
  • Replaces the README Core Capabilities grid with a readable doctrine-grounded list.
  • Rewrites capability wording to explain active doctrine and current-state behavior directly rather than phase or release chronology.
  • Keeps Runtime Context Discipline front-page scoped instead of turning the README into a phase summary.
  • Promotes document-governance v1.10 to make README capability/current-state presentation explicitly front-page scoped and doctrine-grounded.
  • Preserves the 18-rule runtime install boundary and the non-runtime playground/ payload boundary.

v10.34 - explicit phase grammar forms and legacy-only alphanumeric handling

Choose a tag to compare

@DarKWinGTM DarKWinGTM released this 31 May 11:08
  • Makes phase-NNN, phase-NNN-NN, and phase-NNN-NN-NN explicit forward-valid numeric phase forms.
  • Keeps observed alphanumeric phase forms such as phase-NNN-NNa as legacy-only unless a later doctrine explicitly normalizes them.
  • Rejects deeper hybrid forms such as phase-NNN-NN-NNb as forward-valid grammar by default.
  • Syncs touched runtime/design/changelog/TODO/phase/patch/README surfaces for the P126 release wave.
  • Preserves the no-rename posture for checked NodeClaw phase files in this wave.