per-story-delivery lacks a lightweight verify-Green checkpoint between implementer and adversary

## Summary
The per-story-delivery flow proceeds implementer → adversary → demo → push → PR-manager. There is no orchestrator-owned inspection step between implementer and adversary. If the implementer overclaims completion (tests-only green but lint/format failures, stray `todo!()`/`unimplemented!()` outside declared out-of-scope surfaces, unsigned commits, unpushed branch, workspace divergence), the orchestrator cannot detect this without spawning ad-hoc verification. Real cost: manually-spawned verification burns tokens; without it, defects surface during the more expensive adversarial pass and can trigger extra convergence cycles.

## Proposed remediation
Define a lightweight `verify-green` sub-step in per-story-delivery that runs (inspection-only, no writes):
- The language-native full-suite test invocation across the whole workspace (not just the story's target file).
- The language-native lint at deny-warnings level.
- The language-native format check.
- Commit signature verification across the story's commit range.
- A grep for `todo!()`/`unimplemented!()`/equivalent that reports every hit and cross-checks against the story's declared out-of-scope surfaces.
- `git status --porcelain` + branch parity vs origin.

## Impact
~1-minute inspection dispatch catches overclaims cheaply, avoids consuming adversarial convergence passes on fixable-lint defects, and gives the orchestrator a formal handoff artifact between implementer and adversary. Also complements a companion issue on implementer final-gate lint enforcement.