v0.6.4

Fixed

• /rite:pr:open branch creation is now worktree-isolated as a hard invariant under multi_session.enabled: true — branch creation re-resolves multi_session from rite-config.yml immediately before the branch is created (instead of relying on a [CONTEXT] marker that can be lost across resume / context compaction / mid-flow entry), so the git switch -c legacy path is reachable only when multi_session.enabled: false. After EnterWorktree, an invariant check verifies the repository top-level matches the worktree path and halts on mismatch instead of silently continuing on the main tree; flow-state.sh set --require-worktree emits a loud warning when a branch/PR phase would be recorded without a worktree. (#1596)

v0.6.3

Docs

• Restructured the README into a bilingual layout: README.md (English, with the English intro video) and a new README.ja.md (Japanese, with the Japanese intro video), cross-linked by a language switcher at the top of each (#1585, #1587)

v0.6.2

Docs

• Added a Demo section with an introductory video (Japanese subtitles) near the top of the README (#1580)

v0.6.1

Fixed

• EnterWorktree failure under harness git misdetection now points to a restart remedy — when multi_session.enabled: true (default), /rite:pr:open Step 2.3-W and /rite:resume re-entry detect the harness git repository misdetection (.git present and git CLI healthy, but the startup check reports false) and recommend restarting Claude Code from the repository root so the already-created worktree is reused (WT_CASE=reuse), instead of offering only the prior "abort / git switch -c" fallback. Documented in getting-started.md and git-worktree-patterns.md. (#1574)

v0.6.0

Added

• Canon TDD cycle for the implementation phase — when tdd.enabled: true (default on), /rite:issue:implement drives implementation through a Canon TDD loop: pick one behavior from the test list → confirm Red → minimal Green → Refactor → repeat until the list is empty. Falls back gracefully: commands.test: null runs in "Degraded TDD" mode (test-list discipline kept, auto-run skipped with a warning), and tdd.enabled: false restores the prior non-TDD flow. (#1567)
• tdd: configuration section, default-on (opt-out) — distributed rite-config.yml ships a tdd: section with enabled: true; /rite:init --upgrade back-adds it to existing projects via the same active-section mechanism as wiki / multi_session. (#1566)
• Canon TDD documentation and test-list framing — the Issue template Section 6 "Test Specification" is now framed as the Canon TDD test list (one T-xx row = one Red→Green→Refactor cycle), reflected across skills/rite-workflow, docs/SPEC.md, getting-started, and pr/open.md. (#1568)

v0.5.5

Fixed

• bang-backtick-check.sh no longer hard-blocks consumer repos — a new --skip-if-no-target flag makes --all return a clean skip (rc=0) instead of an rc=2 invocation error when there is no plugins/rite/ markdown to scan (marketplace-only consumer repos), removing the forced manual gate bypass in /rite:pr:ready and /rite:pr:create. Self-host repos keep the original rc=2 misconfiguration diagnostic. (#1551)
• Active-but-idle session worktrees protected from lazy reap — pr-cycle-cleanup.sh keeps a worktree whose issue claim holder is active=true even when the claim heartbeat has gone stale (idle past CLAIM_STALE_SECONDS), preventing the /clear "Path does not exist" error from recurring on resume. (#1553)
• Read-only commands relay their real output again — removed context: fork from /rite:issue:list, /rite:investigate, /rite:workflow, and /rite:skill:suggest so their output is shown inline instead of being replaced by the harness control wrapper. (#1556)
• orphan-reference-check.sh --all works inside session worktrees — the --all scan now walks paths relative to REPO_ROOT, so running from a .rite/worktrees/issue-N worktree no longer excludes every file and exits 2; orphan detection is restored under the default multi_session.enabled: true. (#1557)

v0.5.4

Added

• OKF v0.1 minimal conformance for Wiki concept pages — concept page frontmatter now carries type and okf_version fields, aligning Wiki pages with Open Knowledge Format v0.1.
• OKF v0.1 sync and upstream visualizer integration guide — documentation now covers OKF v0.1-conformant synchronization and connecting the upstream visualizer.

Changed

• /rite:pr:run defaults to draft-only — the command runs open → iterate (stopping at draft) by default, and ready → merge → cleanup is opt-in via the --merge flag.
• Wiki index.md reshaped to OKF bullet form with two-pass query — index.md adopts an OKF bullet structure and wiki:query resolves in two passes.
• Wiki log.md reshaped to OKF form — log.md adopts an OKF structure and the ingest:skip state moves into raw frontmatter.

Fixed

• wiki:close heredoc write-failure guard — close.md Phase 4.4.W guards against heredoc write failure, mirroring the review/fix path.
• /rite:pr review/fix $trigger_exit defensive default — Step 3 assigns a defensive default to $trigger_exit.
• Live-process worktrees protected from /clear "Path does not exist" — worktrees with a live process are protected so the /clear "Path does not exist" error does not recur.

v0.5.3

Added

• /rite:pr:run — a batch PR lifecycle command that runs open → iterate → ready → merge → cleanup sequentially and autonomously across multiple Issues.
• /rite:lint number-reference guard — a number-reference-check.sh lint (non-blocking warning) that detects Issue/PR number references (#NNN, Issue #NNN, PR #NNN) re-introduced into the number-free surface (CHANGELOG.md, CHANGELOG.ja.md, lint.md), guarding the cleaned surface against recurrence.

Fixed

• Parallel sessions no longer contaminate each other's flow state — session_id resolution is now env-first, so concurrent sessions resolve distinct identifiers instead of clobbering a shared flow_state.
• /rite:pr:cleanup reclaims temporary branches and worktrees name-independently — cleanup no longer relies on branch or worktree naming to find and remove the artifacts it created.
• In-use session worktrees are protected from reap — lazy reap skips worktrees owned by active sessions, and /clear self-repairs dangling session state.
• drift-check over-detection removed — eliminated false-positive drift findings and aligned the document-missing reason emitted by the check.
• decompose-issues.sh no longer crashes on an empty labels_csv — Sub-Issue creation handles an empty label set instead of failing.
• /rite:pr:merge success path terminates with a fixed exit 0 — a trailing no-op prevents the merge success path from inheriting a non-zero exit status.

Changed

• wiki:ingest write-failure handling — the write-failure path now emits a dedicated content_write_failed reason instead of a generic failure reason.
• Documentation surface made number-free and present-tense — removed implicit history-dependent phrasing (e.g. "the previous behavior", "the old way") and Issue/PR number references across user-facing config and docs, spec and design docs, command/skill/hook/script comments, and tests, stating the rationale directly in prose. The CHANGELOG history-dependent-phrasing policy is now documented in the file header.
• Account migration — updated B16B1RD references to asakaguchi following the repository account transfer.

Removed

• README v0.4.0 Breaking Changes section — dropped the now-historical upgrade notice from the README.

v0.5.2

Fixed

• /rite:init --upgrade short-circuit path no longer drops drift back-adds (#1461) — when no pending drift was detected, the --upgrade short-circuit path skipped the back-add step that the full path performs, so projects taking the short-circuit could miss newly added config sections and sub-keys. The short-circuit now applies the same drift back-add logic, covered by an added drift-detection test.
• Fixed broken references to the non-existent _resolve-flow-state-path.sh (#1466) — updated stale script references in the hooks documentation to the actual flow-state.sh path.

Changed

• Unified flow state on the per-session model (#1460) — removed the legacy flow_state.schema_version=1 (single-file) path from the hooks (session-start, session-end, post-compact, pre-compact, post-tool-wm-sync), init.md, and the config template, consolidating on per-session flow state. Stale schema_version test fixtures/labels were neutralized (#1465), commit.contextual was added to the SPEC Deprecated key list (#1469), and SPEC.md / getting-started.md were updated to follow the --upgrade drift back-add behavior change (#1467).

v0.5.1

Fixed

• /rite:init --upgrade now converges to the latest config defaults (#1447) — the --upgrade path previously dropped newly added top-level sections, new sub-keys inside existing sections, and the multi_session block, producing a two-tier behavior where upgraded projects drifted from what a fresh /rite:init produces. --upgrade now back-adds multi_session with enabled: true (an explicit false is preserved; idempotent), fills only the missing sub-keys from the template default while preserving existing sibling values, and tracks newly added top-level sections via a drift anchor. Covered by a new sub-key-merge drift-detection test (T-12, #1451), which was unified onto the shared _test-helpers.sh harness (#1453). commands/getting-started.md documents the --upgrade multi_session back-add behavior (#1452).

Full Changelog: v0.5.0...v0.5.1