git:20260508.6dedfb6 to git:20261003.aaf3bb0

12 added, 20 removed. Audit A to A.

What this update changes in the checks

No check changed: every fixed check gives the same answer before and after this update.

A tripped check is a label, not a verdict: read the matched text and the lines below. This week's updates that newly trip a check.

# Agent setup
- This is a deepsec scanning workspace. Each registered project has its
- own setup prompt at `data/<id>/SETUP.md` — open the relevant one when
- asked to set a project up.
-
- ## Common tasks
-
- - **Set up a project for scanning**: read `data/<id>/SETUP.md` and
- follow it (read `node_modules/deepsec/SKILL.md`, then fill
- `data/<id>/INFO.md` from the target codebase).
- - **Add a new project**: run `deepsec init-project <root>` — it
- scaffolds `data/<id>/` and prints/writes the setup prompt for the
- new project.
- - **Write a custom matcher** (only after a real true-positive shows you
- a pattern worth keeping): read
- `node_modules/deepsec/dist/docs/writing-matchers.md`.
-
- ## Reference
+ This is a DeepSec scanning workspace. Read `README.md` for the configured
+ project and `node_modules/deepsec/SKILL.md` for commands matching the installed
+ version. The full docs ship at `node_modules/deepsec/dist/docs/`.
- The deepsec skill is at `node_modules/deepsec/SKILL.md` (after
- `pnpm install`). The full docs ship at
- `node_modules/deepsec/dist/docs/`.
+ - For a scan session, check `deepsec setup --status --output json`, then run
+ `deepsec scan` and `deepsec process` from this directory. The process command
+ resumes pending files.
+ - For changes to the target codebase or matcher set, run `deepsec setup` to
+ reconcile the surface inventory and coverage before processing.
+ - For a new project, run `deepsec init-project <root>` and then follow its
+ `data/<id>/SETUP.md` prompt.
+ - Review generated matchers before committing. Write a hand-authored matcher
+ only after a confirmed finding warrants one; read `writing-matchers.md` first.