Sync Boatstack from Intelligence Flow Labs @ e5dbf426e441

[operator-stack-publisher]

What this sync releases

Plan-approved visual scenarios now ship with require semantics

When the approved plan declares pr_visual_evidence relevance relevant with scenarios, the configured suggest policy escalates to require semantics for that feature: publication blocks until current PASS evidence exists, even when no capture capability is registered yet. A plan that promises pixels can no longer ship with a NOT_VERIFIED gap. The escapes stay explicit: off globally, or a per-feature not_relevant decision with a reason for genuinely nonvisual changes. Because Boatstack now captures registered scenarios automatically during ship, provisioned repositories will not notice the escalation. One-time effect after upgrading: an existing suggest preview for a feature with declared scenarios reports a changed context fingerprint — regenerate the preview with pr-context before publishing.

The flow now prescribes the owed visual-evidence attachment

A published PR whose Boatstack evidence comment failed to attach (visual_pending) or needs manual attachment (manual_required) no longer goes dark in flow next. The new attach-evidence --repo --feature verb retries exactly the operator-confirmed evidence package against the recorded PR — publication authority is never re-asked, and an already attached comment is a no-op. flow next prescribes the retry as the agent's step for a transient publisher failure, and prescribes record-pr-visual-publication (owing the observed comment URL) as the operator's step when no automatic publisher is available. Both fire under the published and merged terminals, because attaching evidence completes the publication itself.

Projection provenance

Generated from operatorstack/intelligence-flow@e5dbf426e4417f4f2f73c9f855d34808f7fa8f9a.
Review provenance, tests, and examples before merging.