[criptogus]

Summary

playbook step
  deliver original inputs + prior outputs to the gateway
  reject empty/truncated generation
  require available guard implementation and boolean decision
  contain guard exceptions
  exclude blocked output from returned results and later context

The CLI previously omitted workflow context and accepted incomplete model output. The runtime silently skipped unavailable guards and retained blocked content in both the public result and subsequent step context. The built-in output privacy guard now uses the existing leak scanner; additional names still require host implementations. Its coverage remains the scanner's documented patterns.

Evidence

• Before: actual CLI transport tests reproduced missing source/prior-step data and success on empty/truncated responses; runtime tests reproduced skipped guards, leaked blocked output and uncaught guard exceptions.
  After: real CLI loopback regressions and runtime tests pass, including malformed guard decisions and the real built-in scanner.
• npm run check:project: 240 tests and all 11 checks passed on this production-based branch, including strict lint, types, build, dependencies, generated content and navigation.
• No model inference, database migration or registry publication is part of this change. The separately unqualified Jev candidate and four solution playbook versions are excluded.

Merge Danger

Door: two-way

Code-only rollback; no migration or evidence/approval change.

Blast Radius: runtime

Hosts that relied on missing guards being ignored now receive a recorded failure. Blocked content is intentionally unavailable to later steps, including continue-on-error flows. Scan matches can reject output rather than silently redact it. Publication of new model/package compatibility still requires its own full qualification.