[agent] Operator-approval workflow (currently stubbed in orchestrator)

[jdev-02]

Surfaced during #5.

In agent/orchestrator.py, the call to security.pipeline.run_pipeline passes:

context={"operator_approved": True, "policy_valid": True, ...}

Both are stubbed to True. In real deployment:

• operator_approved should come from an out-of-band approval workflow (UI button, pre-mission ROE acknowledgment, etc.)
• policy_valid should come from an explicit policy lookup (mission-type/ROE/role matrix)

For MVP these are fine being True (we're driving everything via the operator's request). Post-MVP needs a real flow.

Owner: @aleens-labs + @jdev-02.

[kylemhicks]

Status from current main: partially addressed, not complete. The old always-true operator_approved path has been tightened: /plan now treats plans as provisional and /plan/approve creates an operator approval signature. The remaining post-MVP gap is the full out-of-band approval UX and explicit policy lookup/ROE matrix, so this should stay open as the broader workflow tracker.