# Changelog

## 0.8.1

- **plans hand off to implementation without a second gate**: an approved plan deliverable now offers `Use → Implement`, which resolves `worker.implementKind` (default `implementer`), seeds the task from the plan's goal, inherits parent model/thinking, and carries the plan as the byte-exact launch sidecar. Approving a plan and handing it off no longer produces a worker that immediately asks you to approve a plan.
- **plan gate discharge is recorded, not skipped**: only a reviewed handoff can discharge a gate. `task.md` names the approval and decision that satisfied it, tells the worker to publish the plan's steps with `docket_todos`, and re-arms the gate for unnamed files, destructive/external writes, dependency changes, scope growth, or a step that proves wrong. `planAuthorized` without a source deliverable is ignored.
- **two bundled kinds for the loop**: `architect` (read-only, shared workspace) publishes an approvable plan through `docket_done outcome: proposal` instead of parking it in a `docket_wait` question; `implementer` keeps its plan gate and scopes rights to the files the approved plan names.
- **plan contract**: `## Goal`, `## Constraints`, `## Steps` (numbered, each optionally `files: a.ts, b.ts`), `## Verification`, `## Risks`. Markdown headings and bare `Plan:` label lines both parse. A body with no numbered step simply does not parse and reviews as an ordinary proposal — no publish-time validation anywhere.
- **plan coverage on the verdict card and Report**: a ready deliverable that executes an approved plan is compared against the launch sidecar, showing `plan <ref> · N steps · X/Y planned files touched · … off-plan · … untouched`, warning-colored when either drift figure is non-zero. Derived at card-open from data already on disk: no new storage, no decision type, zero model context.
- **kind-aware handoffs**: `Use → Worker` now selects a kind instead of silently landing on the default one. Worker and stored-deliverable handoffs share one path.
- **no new plan object**: a plan is a Worker Deliverable, reusing immutability, versions, generation-bound approval, review notes, and provenance unchanged. See [docs/adr/0007-plan-to-implementation-handoff.md](docs/adr/0007-plan-to-implementation-handoff.md).
- **release notes**: see [docs/releases/0.8.1.md](docs/releases/0.8.1.md).

## 0.8.0

- **human-started workers only (breaking)**: workers no longer receive `docket_spawn_child`; `can_spawn` is ignored with a migration diagnostic, persisted hierarchy fields are ignored, and `worker.maxSpawnDepth` has no effect. Workers are independent: list/respawn are flat and delete/prune removes only requested worker.
- **kind intent separated from execution**: public `WorkerKind` now contains authority/output intent only. `/docket spawn` adds `--model <provider/model>` and `--thinking <level>` (including `--flag=value` and `--` delimiter forms). Read-only kinds derive shared workspace; writable kinds derive isolated workspace.
- **one validated launch policy**: kind, model/thinking, context, workspace, and compatibility layout resolve once with source attribution. Models must exactly match Pi's available `provider/model`; invalid execution aborts, inherited thinking on non-reasoning models resolves visibly to `off`, and launch without any parent/explicit/legacy model aborts.
- **conditional execution confirmation**: interactive changed spend and contributing legacy kind defaults show one resolved launch summary before any worker files/window are created. Bare same-parent spawn stays low-friction; JSON/print mode never waits. Launch details and heartbeat status record canonical model plus effective thinking.
- **legacy kind migration**: `model`, `thinking`, `parent_seed`, `default_worktree`, and `layout` remain launch-compatible through next major release but are hidden from normal kind presentation and explicitly deprecated. Use → Worker routes reviewed choices through same resolver, remains always confirmed/fresh, and rechecks exact approval before launch.
- **immutable Worker Deliverables**: every accepted `docket_done` freezes one versioned primary body, provenance record, evidence/ref projection, and optional patch before `ready`. Verdict, Report, diff/Hunk, overlap checks, promotion, and decision logging bind to that exact generation; revision notes publish later versions without changing earlier sidecars.
- **explicit approved handoffs**: approval remains separate from use. Reopen an approved deliverable and press `u` to queue its exact body for the parent's next prompt or start one human-confirmed fresh worker with selected model/thinking, byte-exact `source-deliverable.md`, and approving-decision provenance.
- **durable deliverable store**: `/docket save` now writes immutable, inspectable deliverable versions from an exact approved worker generation or explicit parent authorship. `/docket load` mounts them at zero model-context cost and `Use` explicitly queues the exact body or starts a fresh confirmed handoff worker. Existing bundles remain compatibility data; new saves no longer use bundle selection, session markers, consume-on-use flags, or model summaries.
- **deliverable schema drift is survivable**: stored records route through a read-time upgrade chain, and a record this build cannot load is surfaced by `/docket list` as `deliverable:unreadable` with its reason and path instead of vanishing from `list`/`read`/`find`. Save refuses such a slot with an explicit message, and validation failures now name the exact failing invariants.
- **tmux back behind the substrate boundary**: core removes split-event layouts, status-right rendering, terminal `pipe-pane` capture, and their configuration paths while retaining shared windows, literal/paste input, peek, durable dead-pane tails, and attach. Stable pane IDs protect core targeting, and one exclusive non-blocking `registerTmuxAdapter` seam lets an optional companion own operator layouts without delaying workers.
- **handoff and review hardening**: long verdict cards compact their preview instead of clipping actions, queued approved versions survive newer mounts, mismatched sidecars are rejected without overwriting claimed version files, and worker retries preserve selected model/thinking and isolated agent directory.
- **arrow keys work in every Docket overlay**: raw terminal key sequences were lowercased before lookup, so `↑`/`↓` (and Home/End/PgUp/PgDn) never resolved and only the `j`/`k` aliases the footer advertises alongside them worked. Sequences now match case-sensitively, application-cursor (SS3) forms are recognized, and anything a terminal negotiates through the Kitty or modifyOtherKeys protocols is decoded by pi-tui.
- **liveness is separate from progress**: workers heartbeat every 15s, but `updatedAt` only moves when something changes, so a healthy worker reasoning through one long turn was shown as `stale` after 90s. Statuses now carry `heartbeatAt`, staleness reads that, and a heartbeat with nothing new refreshes liveness without inflating the dock's "time since progress".
- **a verdict card cannot resolve in the wrong family**: a plan-gated worker can answer its own `docket_wait` and publish while the human is still reading the card. Answering it then delivered the reply to a finished worker — demoting `ready` to `active`, and later to `idle`/`stale` — or landed the same verb id as an unreviewed approval. Docket now detects that the worker changed families, sends nothing, and reopens the current state.
- **worker protocol nudge no longer errors**: the end-of-turn reminder to call a protocol tool is queued as a follow-up instead of failing with `Agent is already processing` when a parent message arrives at the same moment.
- **`/docket kinds` is readable**: kinds are grouped by source with one block each — name and authority as the heading, description, decision rights, and migration warnings hanging under it — plus the spawn hint and which kind `--as` defaults to.
- **release notes**: see [docs/releases/0.8.0.md](docs/releases/0.8.0.md).

## 0.7.3

- **provider-safe worker model inheritance**: workers now receive the parent's canonical `provider/model` reference instead of a bare model id, preventing newly ambiguous ids from resolving to an unauthenticated provider. Nested worker spawns preserve the same provider identity.
- **release notes**: see [docs/releases/0.7.3.md](docs/releases/0.7.3.md).

## 0.7.2

- **metadata-only parent flow**: automatic worker → parent traffic is dock/widget metadata only (state, progress, questions, readiness/failure, compact change stats, attachable refs). `worker.autoEmbedSummary` is removed; existing JSON keys are ignored as legacy. Ready/blocked watcher events refresh widgets and extension subscribers but never call `pi.sendMessage` with worker summaries. Full completion content stays on disk until you open Report or otherwise load/attach evidence.
- **evidence-first verdict + Report**: ready verdict cards show Evidence → Worker says → Actions. Press `r` for a zero-context Report overlay (full `docket_done` summary, evidence, recommendations, checks, change metadata, refs) that closes back to the same unresolved verdict without recording a decision or injecting model context. `d`/`h` still open full diff / Hunk on every change set. Attach stays available as a secondary debug action in the worker lens. `docket_done` keeps its public fields; summaries no longer append a generated `Recommended:` block (recommendations stay in the structured field; legacy combined summaries normalize at display time).
- **worker activity controls**: loading evidence adds a visible `loaded` marker without resolving verdict attention. Dashboard actions now distinguish verdict/details, tell, peek, load, and direct tmux control.
- **plan-gated default worker**: the built-in `default` kind now uses a fresh isolated workspace and asks before its first edit or mutating command. Configured `worker.defaultKind` remains an explicit power-user override with its declared rights.
- **first-use story**: README, package description, primary help, and empty states lead with safe delegation — spawn → watch → verdict → Report — with evidence bundles as supporting infrastructure. Compact empty copy: `docket · no workers yet · /docket spawn <task>`.
- **release notes**: see [docs/releases/0.7.2.md](docs/releases/0.7.2.md).

## 0.7.1

- **attach back to parent from workers**: `/docket attach parent` now returns a worker to the parent tmux target recorded at spawn. Top-level workers store the spawning tmux session/window/pane, child workers can fall back to their parent worker window, and non-tmux launches get a clear warning instead of a bogus attach command.
- **release notes**: see [docs/releases/0.7.1.md](docs/releases/0.7.1.md).

## 0.7.0

- **Hunk worker-diff review**: ready-worker verdict cards can open the exact worker patch in Hunk with `h`. Docket pauses Pi's TUI while Hunk owns the terminal, harvests user comments while the live Hunk session is open, and then offers to send those comments to the worker for revision, copy them, or ignore them. Missing Hunk still falls back to the built-in full diff viewer.
- **cleaner worker dashboard**: `f8` / `/docket workers` now uses compact status badges, a stronger selected-row rail/background, fixed `work/status/task/result` columns, full task text in the detail pane, a simplified footer, and softer headings so yellow is reserved for attention/action-needed states.
- **release notes**: see [docs/releases/0.7.0.md](docs/releases/0.7.0.md).

## 0.6.1

- **diff-colored artifact previews**: Docket now treats file diffs and worker change sets as diff-like everywhere they are previewed or inspected. Inline `+N/-M` stats stay green/red in review cards, selected-item previews render patch bodies with Pi's diff palette, and opening a diff-like artifact uses the colored text viewer instead of plain text.
- **release notes**: see [docs/releases/0.6.1.md](docs/releases/0.6.1.md).

## 0.6.0

- **workers spawn fresh by default**: `/docket spawn` no longer forks the parent session JSONL into the worker, so spawned workers do not inherit the parent's full conversation and context bloat. `--seed` opts back into parent-session seeding (reuses the prompt cache prefix); `--fresh` is now explicit and overrides a kind with `parent_seed: full`. The bundled `default` kind and any kind without `parent_seed` now start fresh. Kinds that need parent context should set `parent_seed: full`. **Breaking** for users who relied on inherited parent context — add `worker.parentSeedPolicy: "full"` in `docket.json`, pass `--seed`, or set `parent_seed: full` on the kind.
- **reviewed workers go dim**: acknowledging or dismissing a ready/failed worker (verdict `accept`/`reject`) now stamps `reviewedAt` on the worker. The dock shows it dim with a `✓` chip and stops counting it as waiting/failed/ready, so an acknowledged worker no longer keeps begging for review. Reviewed workers stay listed (dim) until `worker.dockIdleHideMinutes` hides them and `worker.pruneAfterHours` eventually prunes them. New activity clears `reviewedAt` automatically: telling the worker, respawning it, or a new protocol transition (`docket_wait`/`docket_done`/`docket_fail`) re-surfaces it. `needs_input` replies, failed retries, and chat-back-for-revision do not mark a worker reviewed — only terminal verdicts do.
- **colored diffs in review**: the verdict card now shows `+N` green and `-M` red in the stat line and per-file lines (was plain dim text). Pressing `d` for the full diff opens a colored viewer: added lines green, removed lines red, `@@` hunk headers accent, `diff --git`/`index`/`---`/`+++` metadata muted, context dim — matching pi's editor diff palette (`toolDiffAdded`/`toolDiffRemoved`/`toolDiffContext`).
- **release notes**: see [docs/releases/0.6.0.md](docs/releases/0.6.0.md).

## 0.5.1

- **attach switches inside tmux**: `/docket attach [w<N>]` now uses `tmux switch-client -t docket-workers[:wN]` when Pi is already running inside tmux. Outside tmux it still copies the equivalent attach command.
- **loaded worker state**: `/docket load w<N>` marks a ready worker as `loaded` in the dock so it stops demanding review attention without recording an accept verdict.
- **progress board semantics**: `docket_todos` remains the worker progress tool, but `docket_done` is authoritative. Stale progress no longer creates a `ready/open todos` attention state.
- **worker overlap radar**: Docket detects workers editing the same path, surfaces `overlap w<N>: <path>` hints, and asks for confirmation before promoting an overlapping change set.
- **command surface cleanup**: `workers` remains the fleet/operator dashboard; `answers` remains an advanced response lens. An unreachable dashboard answers action was removed.
- **worker pre-flight briefs**: `task.md` now starts with kind, workspace, decision rights, and plan-gate policy so workers know their authority before they act.
- **plan-gated patcher**: worker kinds can set `plan_gate: true` and `decision_rights`. The bundled `patcher` now does read-only discovery first, then asks through `docket_wait` before its first edit or mutating command.
- **passive worker warnings**: the dock shows `silent Nm` when a running worker has no recent tool/progress event and `waiting Nm` when a parent question ages. No auto-kill, no auto-respawn.
- **tmux docs**: README now spells out the tmux API boundary: shared session spawn, literal reply, paste-buffer multiline tell, capture-pane peek, dead-pane harvest, optional `pipe-pane`, and status-line HUD.
- **release notes**: see [docs/releases/0.5.1.md](docs/releases/0.5.1.md).

## 0.5.0

- **post-mortem terminal tails**: worker windows now run with `remain-on-exit on`, so a crashing worker leaves its dead pane behind. The parent captures the last lines to `pane-tail.txt`, then cleans the window up. The capture shows up in review as a `terminal tail` artifact and the failed verdict card prints the final lines. You see why a worker died, not just its exit code.
- **peek**: in `/docket workers`, `p` shows a live read-only view of the selected worker's tmux pane inside the dashboard, refreshing about once a second. Check on a worker without attaching and without spending model context. `p` or `Esc` closes it.
- **two-pane review**: on terminals around 120 columns and wider, `/docket` renders the item list on the left and the selected item's card plus evidence preview on the right. Narrower terminals keep the stacked layout.
- **decision ledger**: every resolved verdict (accept, reject, reject & stop, chat, option-send) is appended to `~/.pi/agent/docket/decisions.ndjson` with the verb, option text, any risk shown, and the evidence refs that were on the card. `/docket log decisions` (or `/docket decisions`) renders the ledger: a last-7-days headline, a per-verb breakdown, and the recent entries. When a terminal worker is pruned with no verdict ever recorded, that counts as decision debt and shows up as "N workers evicted unreviewed this week" so automation bias stays visible instead of silent.
- **safer verdict keys**: the verdict card now numbers worker-proposed options so you can pick one directly with `1`..`9`, and sets `Reject & stop` apart with a blank line and warning color since it kills the worker and removes its workspace. Number keys only reach the offered options, never the destructive verb.
- **docket key cleanup**: in `/docket`, reply and save are split off the old overloaded `c` into `r` (reply to worker) and `b` (save bundle), and the duplicate `c`/`t`/`i` aliases are gone. `a` is the single attach key. Footer and `?` help updated to match.
- **multiline replies**: `/docket tell` and the verdict chat reply now preserve line breaks. A multiline message is delivered through a tmux paste buffer (bracketed paste) so the worker reads the whole block at once instead of running it on the first newline; one-liners keep the existing send-keys path.
- new tests cover the decision ledger (summary/render/eviction debt), the verdict number keys and destructive-verb guard, the navigator key cleanup, the multiline input classifiers, and the `decisions` grammar.
- **release notes**: see [docs/releases/0.5.0.md](docs/releases/0.5.0.md).

## 0.4.0

- **rename to pi-docket**: product, package, repo title, command, storage paths, worker tools, tmux session, and extension surface now use Docket. Package is `@roodriigoooo/pi-docket`; GitHub repo title should be `pi-docket`; command is `/docket`; extension surface is `globalThis.__docket`; worker tmux session is `docket-workers`.
- **no compatibility command aliases**: old `/trail` commands are intentionally not retained. Removed public grammar for `/docket checkpoint`, `/docket continue`, `/docket resume`, short aliases (`ckpt`, `r`, `s`, `v`), worker-result aliases (`w<N>`, `result`, `use`), and `inject` alias. The command surface now favors explicit verbs.
- **evidence bundles replace checkpoint-first UX**: use `/docket save` to save selected evidence as a durable zero-token bundle and label the current Pi tree leaf; use `/docket load` to mount bundle or worker artifacts. Pi's native `/tree`, `/fork`, `/clone`, `/compact`, `/new`, and `/resume` remain responsible for session movement and context topology.
- **worker protocol renamed**: workers now call `docket_todos`, `docket_wait`, `docket_done`, `docket_fail`, and `docket_spawn_child`. Worker-side `/docket wait|done|fail` remains only a fallback for prompt entry mistakes.
- **release notes**: see [docs/releases/0.4.0.md](docs/releases/0.4.0.md) for rationale, migration notes, and repository rename checklist.

## 0.3.2

- **bundle-first checkpoints**: a checkpoint is now a frozen artifact bundle (`<id>.artifacts.json`) plus a small deterministic orientation header — git state, files touched, errors, and your note — not a model summary. `continue` and `load` both *mount* the bundle at zero model-context tokens; `continue` injects only the header, and artifacts are chipped on demand. The model summarizer becomes an opt-in `--summarize` layer (`--model` / `--max-output` imply it), off the default path. The four mode flags (`--handoff` / `--compact` / `--debug` / `--review`) and `--raw` are dropped in favour of one default selection that the interactive selector prunes. Checkpoints written by older versions still read and continue (`CheckpointMode` kept for back-compat reads). Rationale in [ADR-0001](docs/adr/0001-bundle-first-checkpoints.md); a new `CONTEXT.md` glossary fixes the "checkpoint = bundle, not summary" ambiguity.
- **verdict card**: a focused per-worker decision surface. Open it with `ctrl+shift+d` (jumps to the highest-attention decision), `/docket v` / `/docket verdict [w<N>]`, or `enter` on a worker row. It reads only status fields and the deterministic change set — the worker's intent line, its question, or the diffstat (`+/-` with a proportional bar) — never the transcript or artifacts, so it costs zero model-context tokens. `d` opens the full diff in an overlay without injecting it.
- **worker-proposed decisions**: `docket_wait({ risk?, options?, recommend? })` lets a blocked worker propose discrete branches. The card renders them as the menu (sent back to the worker verbatim), pre-selects the recommended option, and surfaces `risk` as a warning — ADR-0001's human-authored-note lesson applied to the question side.
- **verdict queue**: opening the card without a target now walks every pending decision in attention order instead of resolving only the top one — the footer counts what's left and `esc` stops the walk. It re-ranks after each resolution so new arrivals and dismissals stay current. Verbs name the outcome: **promote** / **discard** when a change set exists, **acknowledge** / **dismiss** when it doesn't, plus **reject & stop** and **chat**; a cancelled sub-action returns to the verb menu instead of closing the card.
- **live dock dot**: the frozen `[o  ]` worker chip becomes a breathing dot that animates only while a worker is active; static mascot frames are stripped from one-shot spawn messages.
- **cross-project worker views**: `/docket workers --all` and `/docket list --all` surface workers from other projects, and the dock breadcrumb summarizes their attention state (`N waiting · N failed · N ready`) instead of a bare count.
- new tests cover verdict verbs/queue, the change-set card, structured `docket_wait`, bundle-first checkpoint selection + orientation header, and cross-project worker ranking.

## 0.3.1

- **auto-embed ready summary**: when a worker reaches `ready`, docket appends a short summary (outcome + one-line headline + up to five recommended bullets) to the parent pi session via `pi.sendMessage({ triggerTurn: false })`. The parent assistant sees it on its next turn without manual `/docket inject`, and any worker spawned afterwards inherits it through session seeding — so sibling findings cross-pollinate without a dedicated channel. Full artifacts still live on disk; `/docket load w<N>` remains the path for the long-form detail. Gated by `worker.autoEmbedSummary` (default true) for users who prefer the pure-ledger behavior. New pure formatter `formatReadyEmbedMessage` in `extensions/worker-summary-embed.ts` is fully testable without pi.
- **kind visibility in the UI**: the worker kind now shows in three surfaces that previously only labelled the worker by index. Dock row renders `● w1·scout …` next to the label; the spawn announce chip becomes `w3·patcher[o  ] · starting`; the spawn-detail and the `/docket w<N>` mini-report both gain an explicit `kind:` line. The implicit `default` kind is suppressed everywhere to keep the common case clean. Model badge keeps its existing brackets so kind and model are visually distinct.

## 0.3.0

Included:
- **worker kinds**: frontmatter MD presets that tune one worker's posture without changing the protocol contract. Bundled `scout` (fast read-only recon) and `patcher` (edits in worktree, can dispatch scout) under `extensions/worker-kinds/`; user overrides in `~/.pi/agent/docket/worker-kinds/*.md` and `<project>/.pi/docket/worker-kinds/*.md`. Fields: `name`, `description`, `model`, `thinking`, `read_only`, `default_worktree`, `parent_seed`, `max_artifacts`, `max_duration_sec`, `can_spawn`, `layout`, `guardrails_append`, plus a markdown body that is *appended* to the universal guardrails (never replaces them).
- **`/docket spawn --as <kind>`**: pick a kind per spawn. `/docket kinds` lists registered kinds.
- **fleet + depth caps**: `worker.maxActive` (default 8) rejects spawns past the cap with a clear error rather than queuing. `worker.maxSpawnDepth` (default 2) bounds how deep child spawns can recurse.
- **cascade delete**: `/docket delete w<N>` now purges children dispatched via `docket_spawn_child` along with the parent.
- **`docket_spawn_child` tool**: only registered for workers whose kind has a `can_spawn` allowlist and only when current depth is below the cap. Child status carries `parentWorkerId`/`depth`; child outcome surfaces in the parent worker's inbox, not directly to the human user.
- **stable tmux window id**: `tmuxWindowId` (`@N`) captured at spawn time. kill, send-keys, and pipe-pane target the id first with name fallback, so renamed/recycled windows no longer misroute parent input.
- **per-kind tmux layout**: `layout: split-events` opens a right pane showing `tail -F events.ndjson` so the user can watch tool activity live without context switching.
- **optional tmux status-line dock**: `worker.tmuxStatusLine: true` writes a compact `docket ?N ✗N ✓N ●N` summary to the shared session's `status-right` so the dock survives even when you're attached to a pane.
- **optional terminal capture**: `worker.captureTerminal: true` enables `tmux pipe-pane` to `pane.log` inside each worker dir for post-hoc debug.
- **`/docket respawn <w<N>|all>`**: relaunch workers whose tmux window died (orphan reconciliation no longer means losing the session dir).
- **`globalThis.__docket` extension surface**: `registerWorkerKind`, `listWorkerKinds`, `onWorkerEvent`. Other pi extensions can contribute kinds at runtime and subscribe to worker events without coupling to docket internals.
- **worker event subscription**: `WorkerSnapshotCache.snapshot()` now returns `newEventsByWorker` (events read this tick) alongside the existing sticky `eventsByWorker` ring. The parent dock pipes new events through the extension surface on every refresh.
- new tests cover worker-kinds parsing + registry, extension surface, grammar (`--as`, `kinds`, `respawn`), cascade purge, and `countActive`.
- **docs cleanup**: README slimmed (587 → ~400 lines) and points at new `docs/configuration.md` for the full config reference, worker-kind frontmatter table, and worked kind examples. `docs/architecture.md` rewritten as a module map + worker lifecycle + storage + extension surface. `docs/stress-test.md` moved out of `scripts/` and inlined the sampler so it has no external dependency. `docs/design-decisions-tmux-and-events.md` removed; same content now lives in much shorter form in `docs/architecture.md`. `scripts/` removed from the package and gitignored. npm-pack leak of personal stress-test results closed by moving the file to a hidden, gitignored path.
- **README banner**: npm version badge.

## 0.2.2

Included:
- shared `docket-workers` tmux session: one server hosts every worker window instead of N servers
- worker NDJSON event stream at `workers/<id>/events.ndjson` for state, todo, and tool-call events
- dock sub-line under thinking workers showing the latest non-protocol tool call (file path, command, etc.)
- `WorkerSnapshotCache` keeps a sticky recent-event buffer so sub-lines survive across refresh ticks
- `fs.watch`-driven dock refresh in place of the 500 ms polling timer, with mtime-cached status + artifacts reads
- heartbeat dedup: workers skip `writeArtifacts` when their artifact list signature is unchanged
- session JSONL seeding (`SessionManager.forkFrom`) so spawned workers resume from the parent's prefix and hit the provider's prompt cache. Opt out with `/docket spawn --fresh`
- `/docket attach [w<N>]` first-class command that copies the tmux attach incantation, optionally pinned to one worker
- idle eviction: ended workers auto-hide from the dock after `worker.dockIdleHideMinutes` (default 30) and auto-prune after `worker.pruneAfterHours` (default 24)
- worker guardrails note that the tmux session is shared; workers must not invoke `tmux` directly
- README simplified, outdated demo gifs removed
- stress-test runbook + sampler under `scripts/`
- architecture doc resynced (storage layout, shared topology, event stream, eviction)

## 0.2.1

Included:
- README rewrite with a more direct, personal tone
- note that current GIFs are outdated and need refreshing

## 0.2.0

Included:
- compact worker dock above the prompt for live worker state without context injection
- worker protocol tools (`docket_wait`, `docket_done`, `docket_fail`) plus bash fallback interception for accidental `/docket wait|done|fail` calls
- `/docket tell w<N> [text]` for explicit worker input/follow-up, with modal input when text is omitted
- simplified Navigator modes: Review, Answers, All
- hard rename from Memory to Answers and Catalog to All
- numeric mode keys (`1` Review, `2` Answers, `3` All) and `t` for telling workers
- `/docket workers` positioned as a debug/power view with clearer labels
- docs and tests for updated worker/mode UX

## 0.1.4

Included:
- soft-consume for `--once` checkpoints: marked consumed at session end (not on inject), files retained for `consumedRetentionDays` (default 7) so accidental cancels are recoverable
- `/docket load [id|last|w<N>] [--include-consumed]` — lazy carryover of checkpoint or worker artifacts into the navigator with **zero** model-context cost; injected only when user creates a chip with `/docket ref` or `/docket inject-full`
- unified `/docket load` picker for checkpoints and workers, with preview for checkpoints before loading
- `/docket unload <id|w<N>|all>` — drop loaded checkpoint/worker artifacts from the session and cancel pending checkpoint consume contracts
- tmux-backed `/docket spawn <task>` workers, plus `/docket list --workers`, `/docket load w<N>`, and `/docket delete w<N>`
- worker artifact snapshots so parent sessions can inspect and reference worker findings via loaded slots
- JSONL-backed checkpoint event log with legacy index backfill
- navigator `s` key cycles source filter (current / all / `c1` / `w1` / ...); default view is `current`
- carryover artifacts namespaced as `<slot>.<displayId>` (e.g. `c1.f12` or `w2.c3`), refs unchanged
- `/docket list [--include-consumed]` shows soft-consumed checkpoints
- `/docket delete` permanently purges checkpoints (bypasses soft-consume) and kills workers when targeting `w<N>`
- internal deepening: Loaded Artifact Context, Checkpoint Commands, and Worker Commands concentrate reference/carryover and command-flow logic behind tested Modules

## 0.1.3

Included:
- ranked artifact search index backing `/docket search`, with ripgrep-backed candidate scoring and in-memory fallback
- npm trusted publishing pipeline for releases
- README demo videos / gif walkthroughs

## 0.1.2

Included:
- cleaner checkpoint reference lists with single file guidance note
- hidden checkpoint context loading for `/docket continue` to avoid editor prompt bloat
- loaded checkpoint chip above the editor
- `/docket delete [id|last]` command
- checkpoint selector delete action with confirmation

## 0.1.1

Included:
- centered Docket command-center overlay with stronger island borders
- denser artifact rows with filter chips, relative time, and preview toggle
- interactive `/docket resume` / `/docket continue` checkpoint selector
- checkpoint preview and edit-before-continue flow
- checkpoint summaries with file, error, command, and token estimates

## 0.1.0

Initial package scaffold.

Included:
- `/docket` artifact navigator
- artifact search via ripgrep-backed temp docs
- compact artifact references
- full artifact injection
- summarized/raw checkpoints
- one-off `--once` checkpoints
- checkpoint sidecar artifacts