# Review protocol

This protocol defines how a roadmap stage is reviewed by a local DSH
DeepSeek Pro profile without turning private runtime state into public project
content.

## Review pack

Create the pack outside the public package, under the ignored `.reviews/`
directory. It may contain:

- relative file names;
- sanitized diffs;
- package manifests with credentials and private paths removed;
- test and dry-run summaries;
- the stage's acceptance questions;
- the DSH version and plugin contract evidence used for the change.

It must not contain raw chats, full Sessions, credentials, cookies, `.env`
values, real `DSH_HOME` paths, private knowledge, or unredacted diagnostics.

## Isolated review runtime

The review must use an isolated DSH Profile and a temporary review home. The
review prompt should explicitly restrict the model to the Review Pack and the
listed public files. The review profile must not use a production Profile or
mount the new plugin into a user workspace.

Credentials may be supplied through the approved local DSH credential service
or an explicitly approved process environment. Values must never be written to
the repository, Review Pack, shell transcript, test fixture, or final report.

The exact `agentworkos.local.toml` filename and the
`agentworkos.local.*.toml` pattern must be present in `.gitignore`. Verify both
with `git check-ignore` and verify that neither appears in `npm pack --dry-run`.

## Review questions

Ask DeepSeek Pro to classify findings as `pass`, `needs-change`, or
`not-reviewed` for:

1. project purpose, public audience, and non-goals;
2. Runtime, Profile, Preset, Session, Host, and Client ownership;
3. DSH Bundle and Client contract claims for the pinned version;
4. Runtime adapter allowlisting and arbitrary-command prevention;
5. JSON-safe Host/Client data boundaries;
6. Slot, Service, disposer, unload, reload, and recovery behavior;
7. private-path, credential, raw-chat, and private-knowledge leakage;
8. tests and evidence supporting public documentation claims;
9. whether the stage has accidentally claimed a later stage as complete.

## Maintainer decision

DeepSeek Pro is an advisory reviewer. The parent agent or maintainer must
compare the review with the actual diff, test output, runtime evidence, and
privacy scan. A model response alone cannot close a roadmap stage.

The final sanitized record must state:

- the DSH version and isolated Profile used;
- the Review Pack identifier;
- findings and dispositions;
- unresolved risks;
- whether the stage passed its exit criteria;
- whether any commit, push, Release, or PR occurred.