# pi-docket v0.5.1

A patch release focused on worker attention flow: less command friction, clearer tmux movement, progress that stays informational, and better mediation when parallel workers touch the same files.

## Highlights

### Attach switches when already inside tmux

`/docket attach [w<N>]` now does the thing you usually mean from inside a tmux client: it runs `tmux switch-client -t docket-workers[:wN]` and moves directly to the worker session/window.

Outside tmux, Docket keeps the safer old behavior and copies the equivalent `tmux attach` command instead. The distinction is deliberate and visible in the notification.

### Loaded workers stop demanding attention

Loading a ready worker with `/docket load w<N>` now marks it `loaded` in the parent dock. The worker remains visible and its artifacts stay mounted at zero model-context tokens, but it no longer counts as unresolved review work.

This does not record an accept verdict. `loaded` means "I pulled this evidence into view," not "I accepted the work."

### Progress boards are no longer completion gates

`docket_todos` is now treated as a progress board: useful parent visibility, not a durable task manager and not a completion signal.

`docket_done` is authoritative. If a worker forgets to republish progress before finishing, stale `0/4` progress remains informational and no longer forces a noisy `ready/open todos` state.

### Worker overlap is surfaced before promotion

Docket now detects when two workers edited the same path in their isolated workspaces. The dock/dashboard can show hints like:

```text
overlap w2: src/auth.ts
```

Promotion asks for confirmation when overlap exists. Docket still does not lock files or auto-merge workers; it surfaces the conflict so the parent can mediate.

### Command surface cleanup

The workers dashboard remains the fleet/operator surface. `/docket answers` remains an advanced response-artifact lens, not a second worker dashboard. An unreachable dashboard answers action was removed.

## Compatibility

No breaking changes. Command names, worker protocol tool names, storage paths, and extension surface remain compatible. The visible language around `docket_todos` changes from todos to progress, but the tool name stays the same.

## Upgrade

```bash
npm install -g @roodriigoooo/pi-docket@0.5.1
```

Publishing is handled by the `Release` GitHub Actions workflow. It reads the version from `package.json`, verifies the requested version matches, publishes to npm with provenance, packs the npm artifact, and creates the GitHub Release from this file.