# Hacker Bob v1.3.2 Release Notes

## Highlights

`v1.3.2` fixes recon-agent compatibility with the session read/write guards. Normal and deep recon now keep bulky collection captures in temporary scratch outside the Bob session directory while continuing to produce compact artifacts for routing, summaries, and later phases.

## Recon Guard Compatibility

- Replaced session-local temp files such as `subdomains.tmp` with `mktemp` scratch outside `~/bounty-agent-sessions`.
- Removed `family_raw.txt`, `js_raw.txt`, and deep recon `[SESSION]/raw/*` capture paths from the generated recon contracts.
- Kept compact derived artifacts in the session directory, including `attack_surface.json`, `recon-summary.json`, `deep-summary.json`, and bounded `.txt` summaries.
- Preserved the seven-step recon contract and the MCP-free recon-agent boundary.

## Session Guard Boundaries

- Allowed compact recon summary reads for `recon-summary.json`, `deep-summary.json`, and `surface-leads.json`.
- Allowed direct writes only for compact recon-owned summaries such as `recon-summary.json` and `deep-summary.json`.
- Kept `surface-leads.json` write-protected so normal lead handling remains MCP-owned.
- Kept raw/proof/body/dump-style session reads blocked.

## Verification

- `npm run test:hooks` passes.
- `npm run test:prompts` passes.
- Rendered normal and deep recon Bash blocks pass both session guards with a concrete session path.
- `npm run release:check` passes.
