test: prove durable authority, effect accounting, and cleanup residuals

[szmyty]

Flow's durable lifecycle suite covered interruption and recovery but lacked observable effect counts and cleanup-residual qualification. This PR supplies the remaining synthetic proof for #31.

• Adds 15 safety recipes, bringing the lifecycle corpus to 49; every recipe runs twice in fresh workspaces.
• Proves seven authority-denial categories, zero denied/descendant launches and effects, and a working independent positive control.
• Proves persisted authority before launch, completed reuse without relaunch, stale-authority invalidation, matching recovery approval, and rejection of replayed recovery decisions.
• Exercises cancellation and a real filesystem error after partial synthetic cleanup; preserves source bytes, unaccepted candidates, unfinished evidence, and typed failure history.
• Extends strict receipts and privacy canaries, reconciles all [FLO-13.4] Prove interruption, retry, resume, and authority state transitions #31 criteria, and records the maintainer's instruction to hand back work after focused local checks without waiting for hosted CI.

Runtime APIs and schemas are unchanged. All effects are harmless local witnesses. Upload uses network permission; paid-service requests use AI-provider permission. The explicitly acknowledged retry demonstrates a second uncertain effect—there is no exactly-once, sandbox, automatic cleanup, or real external-action claim.

Validation:

• Rust 1.85: all targets passed, including 81 acceptance recipes and 49 lifecycle recipes, twice each.
• Stable Rust (Cargo 1.98.1): all 49 lifecycle recipes passed twice.
• Formatting, focused Clippy with warnings denied, documentation tests, contract/repository validators, deterministic fixture checks, and negative receipt checks passed.
• Hosted CI and macOS/Windows were not checked or awaited for this handoff.

Evidence: immutable acceptance reconciliation and local validation record. The record pins the tested code commit, source identities, report/receipt digests, and remaining limits; the follow-up commit only retains documentation and evidence.

Closes #66.
Closes #31.

#13/#11 remain open for real-provider integration and later gates. After maintainer merge, the agreed next checkpoint is Optiflow #88. No automatic merge.

[devactivity-app]

Pull Request Summary by devActivity

Metrics

Achievements

• @szmyty
  Earned XP: 15⭐
  Check Your Progress