Skip to content

TODO.md

Latest commit

 

History

History
executable file
·
99 lines (83 loc) · 13.5 KB

TODO.md

File metadata and controls

executable file
·
99 lines (83 loc) · 13.5 KB
Raw

Claude Code Rules - TODO

Last Updated: 2026-08-11 Current Release: v10.68 published, fresh-public verified, installed, and immutable Active Wave: none selected; P151 complete History: 2026-08-10 movement; 2026-08-09 movement; 2026-08-09 pre-rollover snapshot; earlier history Done Detail: rules release closeouts; todo/done/

Active / In Progress

No active RULES release wave is selected.

Recently Completed

  • P151 / v10.68 Active Project Root source authority was committed and fast-forwarded from the Active Project Root, annotated-tagged, released, fresh-public verified, and installed.

    • Delivered authority-and-scope.md 2.8 and document-integrity.md 1.14 with Case 19/M41-M45 while preserving the exact ordered 19-Rule runtime inventory.
    • Verified the exact 22-path release scope, two advanced and 17 byte/mode-protected Runtime Rules, four identical installer arrays, 366 local links, Bash/PowerShell fixtures, Patch tests 32/32, 179/0 Patch inventory, two-pass disposable install, and independent review corrections.
    • Preserved all 1,188 pre-existing plugin/** baseline entries with zero drift: 63 modified tracked, 1,125 untracked, 1,187 regular files, and one symlink.
    • Published release commit 04c1c91faa6cff50cdb61b3d31c82cbb3c23819f at immutable annotated tag object 2a68d0e09511f879327831b5f21170399cf7be2a; Release: https://github.com/DarKWinGTM/claude-code-rules/releases/tag/v10.68
    • Fresh-public full-history tag fixtures passed. Captured owner-only rollback snapshot /home/node/.claude/rules-rollback/v10.68-04c1c91faa6cff50cdb61b3d31c82cbb3c23819f-preinstall, then installed the exact released payload twice with 19/19 byte-mode parity, identical second pass, and unrelated-file preservation.

  • P150 / v10.67 architecture conformance and no-fork gates was fast-forwarded to public master, annotated-tagged, released, fresh-public verified, and installed.

    • Published release commit bd3aa36ff0d7c7712270750249031f362968854c at immutable annotated tag object 24c3b8982c9e8ad01456bb6139a9e6cee9246fa7; Release: https://github.com/DarKWinGTM/claude-code-rules/releases/tag/v10.67
    • Verified exact 25-path scope, three changed and 16 byte/mode-protected Runtime Rules, exact ordered 19-file arrays, Case 18/M35-M40, links/modes, Bash/PowerShell fixtures, Patch tests 32/32, Patch inventory 173/0, and fresh-public master/tag reproduction.
    • Captured the approved rollback snapshot at /home/node/.claude/rules-rollback/v10.67-bd3aa36ff0d7c7712270750249031f362968854c-preinstall, then installed the exact public-tag payload twice with 19/19 byte-and-mode parity, identical second pass, ownership-manifest convergence, unrelated-file preservation, and no unexpected quarantine.
    • The runtime inventory remains exactly 19. The dirty backup checkout and unrelated repository/runtime state remained excluded.

  • P149-01 / v10.66 playground flow-diagram format correction was fast-forwarded to public master, annotated-tagged, released, and fresh-public master/tag verified.

    • Published release commit d8bffccaa304b949a713b40cd7dd2e7da4f6486e at immutable annotated tag object f785e254d844b895340328c3c689a728ae449384; Release: https://github.com/DarKWinGTM/claude-code-rules/releases/tag/v10.66
    • Verified exact 9/12/1 commit scopes and 13-path cumulative scope, zero U+2500–U+257F characters in the corrected scenarios and added Markdown lines, semantic preservation, protected bytes, links/modes, independent reviews, Bash/PowerShell fixtures, and two-pass disposable 19/19 installations locally and from fresh public master/tag clones.
    • All 19 Runtime Rules and installers remained unchanged, so no real runtime reinstall was required. Patch posture remained none.

  • P149 / v10.65 proof reachability and authenticated evidence was installed, pushed to public master, annotated-tagged, released, and fresh-public technically verified.

    • Published release commit 2e751bbb620eb68527e5a67eb6348196a67727e7 at immutable annotated tag object cc7d322d3b1e4e7785373370d2d3c9eb8a8a395e; Release: https://github.com/DarKWinGTM/claude-code-rules/releases/tag/v10.65
    • A delayed audit found prohibited Unicode Box Drawing characters introduced in Case 04 and Case 12. The historical v10.65 diagram-format gate remains failed; P149-01/v10.66 owns the prospective correction without changing v10.65.

  • P148 / v10.64 Patch timeline governance and RULES Tool was synchronized to canonical, installed into the root profile, pushed to public master, annotated-tagged, released, and fresh-public master/tag verified.

    • Added verified original-creation UTC Patch identity, matching Created At/Creation Evidence, exact-reference migration integrity, and the reusable dependency-free script/patch-timeline.mjs Tool without Patch IDs or an index.
    • Verified 32 focused Tool tests, independent Tool/governance reviews, the NodeClaw 576-selected/199-preserved zero-mutation audit, Bash/PowerShell fixtures, exact 27-path canonical parity, two-pass root and fresh-public 19/19 installation parity/idempotence, Tool exclusion, and no quarantine.
    • Published release commit fe44a0af3885b2cf64d3556b6b3e620b9078e5c5 at immutable annotated tag object aba1ab0775188aa9ae65165a19c30e9138210014; actual NodeClaw Patch migration remains unselected.
    • Release: https://github.com/DarKWinGTM/claude-code-rules/releases/tag/v10.64

  • memory-context-intelligence v0.1.79 / package 0.9.31 corrective public-skill alignment was pushed on the dedicated corrective branch, annotated-tagged, released, and fresh-tag verified.

    • Corrected the immutable v0.9.30 metadata defect by aligning the manifest, analysis skill, and init skill at 0.9.31; also corrected user-scope config wording, evidence/release descriptions, and the native-agent design shard metadata.
    • Verified exact 17-path plugin scope with zero deletions, focused 21 passed, source/clean-candidate/fresh-tag full suites 132 passed, plugin validation PASS, remote branch/tag parity at 5e58f018a2b057ffdd009aeca3d88146e0cfab20, and non-draft/non-prerelease GitHub Release identity.
    • Confirmed the earlier v0.9.30 branch and annotated tag still resolve to 02b15e29fe5eaf7c05e0a81d0b92ef4773cfd677; no tag or release was moved or replaced.
    • Release: https://github.com/DarKWinGTM/claude-code-rules/releases/tag/memory-context-intelligence--v0.9.31

  • memory-context-intelligence v0.1.78 / package 0.9.30 deterministic standalone additional-stage emission was pushed on the dedicated plugin branch, annotated-tagged, released, and fresh-tag verified.

    • Delivered read-only initial analysis, explicit later trial selection, one rich standalone artifact per Topic, normalized evidence, full-set collision refusal, no overwrite path, and additional-root containment while keeping Main RULES promotion separate.
    • Verified exact 37-path plugin scope with zero unexpected paths/deletions, clean-clone 113 passed focused and 132 passed full suites, remote branch/tag parity at 02b15e29fe5eaf7c05e0a81d0b92ef4773cfd677, non-draft GitHub Release identity, and fresh-tag manifest 0.9.30 with 132 passed plus plugin validation PASS.
    • Main RULES, other plugins, and the fifteen existing additional-stage artifacts remained outside the release scope.
    • Release: https://github.com/DarKWinGTM/claude-code-rules/releases/tag/memory-context-intelligence--v0.9.30

  • P073-15 / v10.63 Case 17 bounded-goal route-scope correction was pushed to public master, tagged, released, and fresh-public-tag verified.

    • Corrected the final Case 17 contradiction by keeping queue/worker-lease work as the only selected plan/proof slice and retaining retry/backoff plus status visibility solely as deferred sibling notes outside execution and proof.
    • Verified exact nine-path release scope/modes/links, section-bounded assertions, independent whole-file doctrine review, protected 19-Rule bytes, Bash/PowerShell fixtures, disposable installation, canonical convergence, two-pass root installation, annotated tag and GitHub Release identity, and fresh-public master/tag reproduction.
    • Runtime Rules and installer sources remained unchanged; root installation was an operator-requested idempotent 19/19 parity witness.
    • Release: https://github.com/DarKWinGTM/claude-code-rules/releases/tag/v10.63

  • P073-13 / v10.61 Case 17 semantic-owner consistency correction was pushed to public master, tagged, released, and fresh-public-tag verified.

    • Corrected candidate/advisory posture separation, goal-authoring route ownership, phase/TODO evidence/linkage boundaries, and the narrow queue/worker-lease goal; P073-14 owns the later visible-order/branch residuals and P073-15 owns the final retry/status route-scope contradiction.
    • Verified the exact tagged v10.61 scope, protected-byte identity, Bash/PowerShell fixtures, disposable install, candidate/canonical/public/tag parity, annotated tag, GitHub Release identity, and v10.60 immutability.
    • Runtime Rules and root installation remained unchanged at 19/19 parity.
    • Release: https://github.com/DarKWinGTM/claude-code-rules/releases/tag/v10.61

  • P073-12 / v10.60 runtime owner-boundary repair and bounded compression was installed, pushed to public master, tagged, released, and fresh-public-tag verified.

    • Delivered the Runtime Rule decision → construction → rendering contract, conditional diagram startup/synchronization, Agent Team safety-to-worker lifecycle separation, and all-19 bounded Runtime Rule compaction.
    • Verified the exact 77-path scope, 19 aligned/body-sufficient triads, protected registries/force words, zero newly introduced broken links, Bash/PowerShell fixture matrices, disposable install, candidate/canonical/root/public-tag parity, unrelated-file preservation, annotated tag, and GitHub Release identity. A later integrated review found stale owner wording isolated to Case 17; P073-13 owns that corrective release.
    • Runtime reduction: 7,214 bytes, 141 lines, and 1,286 words; active inventory remains exactly 19.
    • Release: https://github.com/DarKWinGTM/claude-code-rules/releases/tag/v10.60

  • P147 / v10.59 evidence-first counter-analysis and owner-integrity corrections was installed, pushed to public master, tagged, released, and fresh-public-tag verified.

    • Delivered premise-before-expansion, completed-baseline protection, proactive counter-analysis, evidence-shaped agreement and explicit retraction, corrected changelog owner vocabulary, and bounded-helper authority clarification while keeping the 19-Rule runtime boundary unchanged.
    • Verified the exact 35-path allowlist, four advanced triads, 15 byte-identical Runtime Rules, scenario/matrix anchors, Bash and PowerShell fixture matrices, disposable install, 35/35 candidate/canonical parity, 19/19 canonical/root/tag parity and body sufficiency, unrelated-file preservation, annotated tag, and GitHub Release identity.
    • Release: https://github.com/DarKWinGTM/claude-code-rules/releases/tag/v10.59

  • P146 / v10.58 strategic design completeness and authority convergence was installed, pushed to master, tagged, released, and fresh-public-clone verified.

  • P073-11 / v10.57 runtime owner semantic conflict resolution and compression was installed, pushed, tagged, released, and verified.

  • Earlier completed release detail remains reachable through the 2026-08-09 pre-rollover snapshot, rules release closeouts, and dedicated completed phase/patch/changelog files.

Deferred / Not Selected

  • memory-context-intelligence phase 030 shared-marketplace bridge/reproof remains planned and approval-sensitive.
    • Gate: recheck current runtime state and obtain explicit action-and-scope approval before marketplace/install/enable/registry/cache mutation.
  • memory-context-intelligence phases 017-018 main RULES promotion/merge remain deferred; trial and historical evidence do not authorize promotion.
  • README and master changelog density repair remains deferred to a dedicated post-P150 document-integrity / document-governance phase; P150 uses exact anchored edits only, and the repair must open before the next broad absorption into either parent. Master-design pressure remains part of the same owner review.
  • Automated documentation-compliance validation and broad integration testing remain deferred by user direction.

History and Preservation