# pi-docket v0.6.0

A release focused on worker review polish and lower-context worker launches. Workers now start from a clean session by default, acknowledged workers visually recede, and review diffs use the same color language as Pi's editor diff view.

## Highlights

### Workers spawn fresh by default

`/docket spawn` no longer forks the parent session JSONL into each worker by default. Fresh workers avoid inheriting the parent's full conversation, reduce context bloat, and make worker prompts easier to reason about.

Use `--seed` when a worker should inherit the parent session prefix and reuse the provider prompt cache. `--fresh` remains explicit and overrides a kind configured with `parent_seed: full`.

Kinds that need parent context should declare it directly:

```yaml
parent_seed: full
```

Project-level configs can also opt back into seeded workers with `worker.parentSeedPolicy: "full"`.

### Reviewed workers go dim

Accepting or rejecting a ready/failed worker now stamps it as reviewed. Reviewed workers stay visible but dim, show a `✓` chip, and stop counting as waiting/failed/ready review work.

New activity clears the reviewed state and brings the worker back into attention: telling the worker, respawning it, or a fresh protocol transition (`docket_wait`, `docket_done`, or `docket_fail`). Terminal verdicts mark review complete; chat-back-for-revision, failed retries, and `needs_input` replies do not.

### Colored review diffs

The verdict card now colors diff statistics and per-file rows: additions green, removals red. The full diff viewer follows Pi's editor diff palette too: added lines green, removed lines red, hunk headers accented, metadata muted, and context dim.

## Compatibility

This release changes the default worker seed policy. Users who relied on workers inheriting the parent session should choose one of these migration paths:

- pass `--seed` for one-off seeded workers,
- set `worker.parentSeedPolicy: "full"` in `docket.json`, or
- add `parent_seed: full` to worker kinds that require parent context.

Existing worker protocol tool names, storage paths, command names, and extension surface remain compatible.

## Upgrade

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

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.