# Hacker Bob v1.1.6 Release Notes

## Highlights

`v1.1.6` finishes the evidence-pack flow by making evidence readiness visible from `/bob-status`.

The core pipeline still uses the same persisted FSM phases:

```text
RECON -> AUTH -> HUNT -> CHAIN -> VERIFY -> GRADE -> REPORT
```

Evidence collection happens after final verification and before grading. Final reportable findings must have valid bounded evidence packs before Bob can grade or report them.

## Changes

- `/bob-status` now reports evidence readiness as `valid`, `missing/invalid`, `skipped`, or `unknown`.
- Missing or invalid evidence packs for final reportable findings are shown as blocking issues so operators can resume the run instead of discovering the blocker later in grading or reporting.
- README now documents the evidence-pack gate while keeping the FSM phase names unchanged.
- Prompt-contract tests now assert that `/bob-status` can read evidence packs for confirmation while remaining read-only and non-networked.

## Install

```bash
npx -y hacker-bob-cc@1.1.6 install /path/to/your/project
```

After installing, fully restart Claude Code in that project so `/bob-status` reloads.

## Verification

- `npm test` passes.
- `npm run release:check` passes.
