v9.65

Summary

• make implementation-critical truth learned from docs/specs/provider references a governed capture requirement instead of something that can remain only in transient reading memory
• make governed design the primary durable home for extracted implementation-relevant truth, phase reuse that normalized truth during later execution, patch surface the external-requirement basis when review depends on it, and execution continuity stop to capture before later multi-step work outruns that knowledge
• carry doc-derived constraint visibility into the live phase workspace so later phased execution can reuse normalized design truth instead of rediscovering the same external contract details after compact or handoff

Verification

• installed only actual runtime rule files into ~/.claude/rules
• removed repo-only / helper files from runtime install set
• parity-checked installed runtime files against source copies
• synchronized README / design / TODO / phase / changelog / patch surfaces
• committed and pushed the RULES repository updates

🤖 Generated with Claude Code

v9.64

Summary

• make relevant governed /phase context a required task-shaping input when it exists, instead of treating phase context as a soft advisory source that can be ignored
• keep current-phase-first behavior, implied-current-stage alignment, and unopened-future-phase draft boundaries intact while making detached generic task shaping count as drift in the presence of relevant phase context
• strengthen the same doctrine across both todo-standards and phase-implementation so Task List behavior stays visibly phase-first in practice, not only in broad intent

Verification

• installed only actual runtime rule files into ~/.claude/rules
• removed repo-only / helper files from runtime install set
• parity-checked installed runtime files against source copies
• synchronized README / design / TODO / phase / changelog / patch surfaces
• committed and pushed the RULES repository updates

🤖 Generated with Claude Code

v9.63

Summary

• make Task List wording follow the actual active session language pattern more explicitly instead of relying on looser session-alignment wording alone
• keep Thai-led wording as the default when the session is primarily Thai, preserve naturally mixed Thai+English wording when that matches the real session pattern, and keep technical labels in technical form when forced translation would reduce clarity
• extend the same language-pattern rule to phase-linked task wording so phase-driven task creation does not drift back into detached generic phrasing

Verification

• installed only actual runtime rule files into ~/.claude/rules
• removed repo-only / helper files from runtime install set
• parity-checked installed runtime files against source copies
• synchronized README / design / TODO / phase / changelog / patch surfaces
• committed and pushed the RULES repository updates

🤖 Generated with Claude Code

v9.62

Summary

• make light tables more proactively usable in active explanation owners when side-by-side structure materially improves understanding
• broaden answer-presentation beyond comparison-only table use toward analytical clarification, diagnostic fact sets, and multi-field explanation
• broaden explanation-quality so diagnostic and multi-field clarification can use light tables without weakening list-first sequence behavior or prose-first reasoning boundaries

Verification

• installed only actual runtime rule files into ~/.claude/rules
• removed repo-only / helper files from runtime install set
• parity-checked installed runtime files against source copies
• synchronized README / design / TODO / phase / changelog surfaces
• committed and pushed the RULES repository updates

🤖 Generated with Claude Code

v9.61

Summary

• keep Task List behavior current-phase-first while making relevant /phase planning context more actively usable
• allow current phase family, phase ordering/dependencies, and already-authored next planned phases to guide continuity and draft next-work discovery
• preserve the boundary that unopened future phases remain draft/proposal only until explicitly opened or otherwise made active

Verification

• installed root runtime rule files into ~/.claude/rules
• parity-checked installed runtime files against source copies
• synchronized README / design / TODO / phase / changelog surfaces
• committed and pushed the RULES repository updates

🤖 Generated with Claude Code

v9.60

Summary

• keep RULES task creation aligned to active phase or clearly implied staged context, with task wording aligned to the active session language/register
• clarify master/history surfaces so older coordination-flavored rollout records read as historical context only after the ownership split
• add bounded phase-066 / phase-067 and matching patch artifacts for the two documentation-governance waves

Verification

• installed root runtime rule files into ~/.claude/rules
• parity-checked installed runtime files against source copies
• synchronized README / design / TODO / phase / changelog master surfaces
• committed and pushed the RULES repository updates

🤖 Generated with Claude Code

v9.58 - tighten startup governance vs execution continuity

Summary

• make startup artifact governance an explicit precondition before execution continuity takes over
• keep required design/changelog/TODO/phase/patch surfaces visible as governed companions during active execution
• make required TODO sync explicit companion work when
  TODO.md is needed
• make clearly staged/governed work resolve phase posture early instead of drifting into late backfill

Included wave

• phase-065 startup-governance vs execution-continuity tightening

v9.57 - retire memsearch custom-skill doctrine

Summary

• retire discontinued memsearch custom-skill doctrine and the former session-coordination-bridge path from Main RULES active teaching
• replace stale in-repo coordination defers with direct out-of-scope wording across active owners
• reframe retired bridge and memsearch waves as history-only in master/index surfaces
• add bounded phase-064 and retirement patch artifacts

Notes

• active Main RULES now keeps only generic optional external recall wording
• retired plugin/bridge mechanics remain preserved as history rather than current capability

v9.56 - strengthen file-disposal authority and delete guard

Summary

• strengthen file-disposal authority so checked master/governed semantic surfaces outrank git-state cleanup heuristics
• block cleanup/isolation rationale from reading like delete authorization
• sync README and master governance surfaces to the current RULES release state

What changed

File-disposal authority

• updated \
  • 
    authority-and-scope.md
  • project-documentation-standards.md
  • strict-file-hygiene.md
  • artifact-initiation-control.md
• clarified that newly encountered or untracked files must be classified through stronger repo-governed surfaces before they can be treated as junk or disposable

Evidence and delete guard

• materialized functional-intent-verification.md into a real runtime rule body
• updated evidence-grounded-burden-of-proof.md, document-consistency.md, no-variable-guessing.md, and zero-hallucination.md
• kept git-state observations in the weak local-evidence lane instead of semantic-authority truth

Governance artifacts

• added patch/file-disposal-authority-and-delete-guard-refinement.patch.md
• added phase/phase-063-01-refine-file-disposal-authority-and-delete-guard.md
• added phase/phase-063-02-sync-master-surfaces-and-verify-delete-guard.md
• synchronized README.md, TODO.md, phase/SUMMARY.md, design/design.md, and changelog/changelog.md

README cleanup included in this release

• restored README toward the older baseline instead of leaving the earlier over-replacement state
• kept only the necessary active-rule and release-surface updates
• removed stale active coordination/plugin-split doctrine from the current README

Verification

• synchronized touched runtime/design/changelog versions for the wave-063 owner set
• completed the bounded phase-063 master-surface sync and postflight verification
• pushed commit f979b80 to master

v9.51 - keep easy explanations simple through the full answer

Summary

• keep plain-Thai easy explanations simple through the full answer
• stop explanation drift where answers start easy and then rebound into internal wording
• synchronize the touched communication-owner set and runtime rule copies

What changed

Explanation flow

• updated explanation-quality.md with an easy-explanation continuity principle
• added a plain-language re-anchor after dense technical blocks when the user explicitly asked for easier explanation

Communication wording

• updated accurate-communication.md so plain Thai / less-jargon requests stay in the easier register across the whole answer
• added guidance to keep human-meaning-first headings and avoid one-gloss-then-jargon drift

Presentation and style

• updated answer-presentation.md with an easy-explanation pattern that keeps plain-language headings visually primary
• updated natural-professional-communication.md so easy explanations stay in an everyday Thai register instead of drifting back into abstract system language

Governance sync

• updated the touched design companions and per-rule changelogs
• added patch/easy-explanation-continuity-and-plain-thai-register.patch.md
• added phase/phase-059-01-refine-easy-explanation-continuity.md
• added phase/phase-059-02-sync-master-docs-and-runtime-install.md
• synchronized README.md, TODO.md, phase/SUMMARY.md, design/design.md, and changelog/changelog.md

Verification

• checked the wave diff for whitespace issues
• refreshed the installed runtime copies in ~/.claude/rules/
• parity-checked the touched runtime rules against source copies
• verified the wave artifacts and links, excluding the long-standing generic placeholder references inside design/design.md