fulcra-agent-review

# Fulcra Agent Review Enhances the [`fulcra-agent-teams`](https://github.com/fulcradynamics/agent-skills) skill with a lightweight **review handshake**: an author requests review of an artifact, one or more reviewers leave verdicts, and the overall state is folded deterministically. The single-file actions (request, verdict) are prose over `fulcra-api file` + the teams inbox; the **verdict tally** is a `coord-engine` command (folding multiple reviewers is a derived state — code, not eyeballing). ## Where to start — the re-entrancy probes Before requesting a review or leaving a verdict, probe where the handshake already stands. Enter at the **first probe that fails** (per the repo's skill-quality pattern, `docs/skill-quality-pattern.md`); requesting is a single-file write and a verdict is an overwrite (re-uploading your verdict file just supersedes it), so re-entry never corrupts the tally: | Probe (run in order) | Command | Passes when | If it fails, enter at | |---|---|---|---| | Engine + auth usable? | `coord-engine doctor <team>` | exits 0 and the last line is exactly `doctor: healthy` | fix engine/auth first (see fulcra-agent-reconcile) — do NOT tally against a broken engine | | Any reviews owed me? | `coord-engine needs-me <team> --agent <me>` | NO `[REVIEW] pending verdict:` row prints for you — no `pending_required` entry names you (NON-mutating read) | **Leave a verdict** — each printed `[REVIEW] pending verdict: <slug> (required: …)` row is an open obligation on ...