v0.330.7

Changed

• On the variant overview of a design round, the feedback dock now offers the note of the variant in the centre (and follows the carousel), so a remark on a variant no longer requires opening it first (#960).

---

Install: /plugin marketplace add Jerry0022/dotclaude

v0.320.0

The session title now shows the finger whenever the user has to allow something, also while a background agent waits on a tool permission dialog. Before, only the main thread could rename the session, pre.ask.title stayed silent inside subagents and no PermissionRequest hook was registered, so nothing woke the idle main thread and the title kept its ⏳ while work stood still.

Added

• 👉 while a background agent waits on a permission. ⏳ ➜ 🤖 Team ┃ X becomes 👉 ➜ 🤖 Team ┃ X (Solo and Testing alike, a bare ⏳ becomes 👉 Solo) and returns to ⏳ once the dialog is answered. Ship, working concept, batch and outcome titles stay as they are. Main-thread prompts are not covered: the user already sees that dialog.
• PermissionRequest hooks perm.approval.flag / perm.approval.watch. Own hooks.json entries with asyncRewake: true wake the idle main thread with the exact title (the hook itself is the waker; a model-armed background waker was rejected because it needs arming at every turn end). post.approval.clear (PostToolUse + PostToolUseFailure) and substop.approval.clear (SubagentStop) drop the wait. Entry key = agent id + hash of tool name and input; a denied dialog is cleared by the agent's next finished call that started after it, SubagentStop clears all of the agent's entries. Writes run under an exclusive lock file (stale-lock takeover, fail-open after 1 s); an entry counts as answered after 55 min and the watch deadline sits just past that, so a forgotten entry never pins 👉.
• Silent rename-only wake turn. A wake turn that only renames the session renders no card (approval-wake flag read by stop.flow.guard / post.flow.completion, dropped on the next user prompt); a turn with any other tool call keeps every gate.

Changed

• Title rule documented in deep-knowledge/session-title-scheme.md; perm. hook prefix in CONVENTIONS.md; the README/architecture roster generator knows the PermissionRequest event and the "approval" domain.

---

Install: /plugin marketplace add Jerry0022/dotclaude

v0.300.2

A queued ship card no longer asks "weiter in ?". A kept ship whose summary carries do-ship's (Queue n/N) suffix now renders the plain merge heading without a Continue button.

Why: in a /do-run backlog run every ship is --queued and --keep, so each ship card asked to continue on its branch, and the user — who sees only this one thread and background agents — had to type "weiter" for a run that continues on its own. Rejected: a new card field for queue mode — the existing (Queue n/N) suffix already identifies the case.

Fixed

• Queued keep heading. render_completion_card resolves a queued kept ship to the plain ship-successful key; a user-driven keep (no queue suffix) still asks "weiter in ?".
• Docs. do-ship completion-card-payloads.md § Keep-mode variant: "Not for a queued ship".

---

Install: /plugin marketplace add Jerry0022/dotclaude

v0.236.0

Changed

• Rethink decides alone; a concept page only for a real fork. /do-run rethink and the "Rethink vorher" option no longer ask the user anything — no intake question, no question round, no corridor-widening question. Target, success criteria, no-gos and demolition corridor are derived from the evidence (conservative corridor: the named target only) and listed in the brief as assumptions. The run ends in exactly one of two exits: an autonomous pick handed to implementation (default; on a criteria tie the lower risk, then the lower effort wins), or a concept page when a real fork remains that the evidence cannot rank, the strongest approach is over-corridor (picking it on the page is the widening), or the goal stays unclear. A close call on effort alone is not a fork. With Ablauf "Autonom" a page the rethink opens waits for the user's return.
• No plan confirmation after a rethink. The interactive handoff passes --rethink to auto-agents, whose Step 3 treats the rethink pick as the go, like the concept's implement click.

Tests

• New do-run-rethink.test.js (17 contract tests; the 13 core ones fail against the old text). Behavioral check: a subagent played the new mode through 6 scenarios (clear winner, taste fork, over-corridor winner, empty target, effort-only tie, interactive full ceremony) — 6/6 took the expected exit, none asked the user; the four ambiguities of the first round (precedence, tie-breaker, skill name, router args) are fixed.

---

Install: /plugin marketplace add Jerry0022/dotclaude

v0.229.0

Added

• No reachable bridge is no reason to skip the concept (#568). auto-concept states before Step 0 that a concept request always produces the real page — engine, decision panel, gate, docs/concepts/ — and that the bridge stays mandatory wherever it can run. Step 3 gains a fallback for sessions whose owner cannot reach localhost (claude.ai cloud or remote container): Steps 0–2 run in full, the page is committed and pushed, and one line hands off file, branch and how a Desktop session resumes the live loop. Never a hand-built look-alike; a slow bridge, a failed first Edge start or saving tokens is no reason to take it. Publishing the page as a claude.ai artifact is tracked separately (#589).

---

Install: /plugin marketplace add Jerry0022/dotclaude

v0.214.1

Fixed

• A green test line no longer renders as red on the completion card. "7663 grün · 1 Flake (auch auf main rot) behoben · 3 skipped" showed "✗ 7663 Tests rot" and a "Nicht erreicht" line, because any failure word in the line overrode the counted verdict. The verdict word next to a count now decides; a bare failure word counts only when no green count is present.

---

Install: /plugin marketplace add Jerry0022/dotclaude

v0.199.0

Added

• Local links in the card open in your default browser. The Desktop Code tab opens only https links from a widget. An http link, localhost included, was dropped without a trace, so a concept page or dev-server link in the card did nothing. A link to this machine (localhost, *.localhost, 127.x, [::1]) is now a button: a click puts „Im Standardbrowser öffnen: " into the input box, and Enter opens the page in the browser the system has set as default. The new hook prompt.flow.open-url opens it and catches the prompt, so it costs no turn. It acts only on the prefix plus one local URL, starts the browser without a shell, and passes the prompt on to Claude when the browser cannot start. An armed /do-batch never collects the open command. https links stay normal links. completion-card-design.md § 4 records the host's link rules.

---

Install: /plugin marketplace add Jerry0022/dotclaude

v0.192.5

Fixed

• No stray <!-- ✨✨✨ … ✨✨✨ --> line under the completion card on Desktop. The Desktop renderer does not hide HTML comments; it shows them as literal text. So the card-guard marker that #443 moved into a comment appeared as a visible line under the widget on every card. The Desktop marker is now a markdown comment, [//]: # (✨✨✨ title ✨✨✨): a link reference definition, which renders to nothing. Backslash and parentheses in the title are escaped so they cannot close the definition early, and card-guard's extractCardTitle unescapes them. The terminal card and the visible title-line fallback for a failed widget call are unchanged.

---

Install: /plugin marketplace add Jerry0022/dotclaude

v0.192.1

Fixed

• Completion-card buttons no longer prefill slash commands, which the Desktop host refuses. In a live test on 2026-09-23, the Code-tab host refused every ui/message prefill whose text starts with /, with or without a leading space: /compact … and /devops:ship … stayed red, while ship --no-compact and plain sentences landed. That made Ship (ready, test), Promote (ship-successful), Nach stable (released-beta) and Fix (ship-blocked) dead buttons. They now prefill trigger words the hooks and skills already recognise: ship goes through prompt.ship.detect, promote / promote stable reach the promote skill, and Debug den Blocker der letzten Card und behebe ihn. reaches the fix skill. Two new tests pin this: card-widget.test.js rejects any prompt that starts with whitespace plus /, and checks each button's routing against isShipIntent (ship buttons are ship intents, promote and fix are not). The host simulator in card-widget.send.test.js also learned the slash rule, and completion-card-design.md § 4 records it as host rule 4.

---

Install: /plugin marketplace add Jerry0022/dotclaude

v0.182.0

Changed

• Completion card: one page, three result lines, one decision. The old card had to be scrolled to be read — a Changes block with file names, a Geprüft block with five checkmarks, ⚠ OFFEN in the middle, the usage meter between body and footer, a 📌 build line, a state line, a CTA heading, and the clickable verbs above it all. Redesigned on an 11-round /concept page with the user (mock-ups of every state, 16 scenarios on the final layout, 12 adaptations accepted) and specified in deep-knowledge/completion-card-design.md, which the renderer, the widget and the guards now implement. The card is two blocks: what happened — the ### ✨✨✨ title (outcome only, never status), up to three › result lines that answer the prompt (a deviation is line 1, **Nicht erreicht:**), an evidence row of always the same three posts (✓ 3/3 Anforderungen ✓ 3464 Tests grün ✓ 4 Live-Checks ok — deviations first and bright, lint/build/review/the V&V stamp only with a finding, monochrome glyphs ✓ ✗ ◐ ○ ●), a budget line (bar = elapsed time, marker = usage, remaining time as a watermark, omitted while both windows are < 50 % and > 1 h from reset; 🧠 1180 Calls · /compact dim at its end past the threshold) and a pipeline line (○ commit → ○ push → ○ PR → ○ merge · branch · Build 176c57d, continuing → ✓ alpha → ○ beta → ○ stable on ring projects — it replaces the Delivery ladder); what to decide — an H2 heading that is the decision (📦 Shippen trotz fremdem Testfehler?, ⚠ Trotzdem shippen mit 2 roten Tests?, ⛔ … umgehen und trotzdem shippen?, 🚀 Released v0.182.0 alpha — nach beta promoten?, 🎊 Promoted v… BETA — nach stable?, 🎊 Released v… LIVE — stable. as a state when nothing is left to decide), an optional › context line, at most three numbered points (reservations, then manual test steps, then deploy artifacts; more → +N weitere), and — on Desktop — the buttons. Every variant and override (ready, red, blocked, shipped, kept, deploy-pending, released beta/stable, ready-files, test, test-minimal, analysis, aborted, fallback, pending, concept, batch, unverified) maps to one row of the design's § 3 table, de + en; the terminal gets the same card without buttons. Heuristics the concept settled: tests read as number + noun + state (3464 Tests grün, skipped is never a deviation, 0 rot is green), live checks are counted, gates without a lane (preflight, smoke) surface only with a finding and by name, a short reservation is quoted in the heading and a long one becomes the count, an identifier-like area keeps its subject (run-agents nutzt …) while a worded one is dropped (#396), the ring pipeline ticks only the channels this version reached.
• Desktop: the whole card body is one widget (mcp-server/lib/card-widget.js, replaces cta-actions.js): the soft "what happened" panel and the accent-bordered decision box, green/red/yellow evidence posts with tooltips, budget bars with time fill, usage marker (white ≤ 10 pp ahead of time, yellow ≤ 25, red beyond), watermark and a light band inside the fill, a quiet PR link, code spans in the accent lilac instead of the client's red, equal-height buttons with tooltips. [CARD WIDGET — DO NOT OUTPUT THIS BLOCK] replaces [CTA ACTIONS] and still renders before the card markdown; test-minimal never calls it.
• Session title: ⏳ (icon only) while working instead of 🔧 (prompt.flow.title-work 0.3.0); the card's result prefix replaces it at turn end. mode-state.js: work: "⏳ ", the fallback card gets its own 🔧 Done – . The strip lists in the hook and the card cover every state (Shipping/Shipped, Released Alpha/Beta/Stable, Ready, Blocked, Test, Started, Analysis, Aborted, Working, Concept, Batch).
• Guards for the new anatomy (card-guard.js 0.5.0, stop.flow.guard.js 0.5.0): a title with status words (läuft, wartet, pending, agent counts) is blocked once with the reason; more than three › result lines, or one whose first token is a path / hook name, is blocked; more than three points is blocked; the line budget (14 Desktop / 24 terminal rows) is reported; a turn that starts from a background-task notification, wake-up or cron tick carries no card obligation when nothing changed, and an identical second card (same variant, build-id, evidence row) is blocked — the "Hintergrund-Testlauf beendet — Stand bleibt" echo after a card is gone. templates/output-style-quiet.md states the same rule for the style. prompt.flow.appstart names the new test-minimal / test headings; post.flow.completion looks for [CARD WIDGET.
• Docs: README § Completion Cards rewritten to the new anatomy (one full example, a compact variant table instead of thirteen old-format cards), plugin-behavior.md, templates/completion-card.md as a pointer to the spec, deep-knowledge index and architecture roster regenerated, ship/SKILL.md prefix reference. Follow-ups filed from the concept's close-out: #423 (build-id.js fails on a deleted-but-tracked file), #424 (git-sync tests time out under full-suite load). Not covered by Codex review — external usage limit until 2026-10-11; full suite 144 files / 3554 green before the last renderer fixes, ship_build ran the 37 card / guard / title suites (825) under its 120-s ceiling after them, lint clean, six variants rendered through --render-card and read.

---

Install: /plugin marketplace add Jerry0022/dotclaude