Skip to content

fix: require explicit live lifecycle authority - #267

Merged
Pigbibi merged 1 commit into
mainfrom
feat/canonical-lifecycle-view
Aug 23, 2026
Merged

fix: require explicit live lifecycle authority#267
Pigbibi merged 1 commit into
mainfrom
feat/canonical-lifecycle-view

Conversation

@Pigbibi

@Pigbibi Pigbibi commented Aug 23, 2026

Copy link
Copy Markdown
Contributor

Summary

  • make incomplete strategy metadata fail closed instead of defaulting to live-capable
  • require explicit runtime_enabled, can_switch_live, live execution mode, and live lifecycle status in backend and Worker checks
  • accept canonical live_enabled while preserving legacy runtime_enabled deployments
  • document canonical lifecycle names and the catalog-versus-deployment authority boundary

Compatibility

  • existing fully configured live profiles remain unchanged
  • legacy runtime_enabled is accepted only when every independent deployment gate is explicitly present
  • no strategy, broker, account, or live permission is modified

Validation

  • 114 Python tests passed
  • Worker validation passed
  • config check, Ruff, py_compile, and diff check passed

Co-Authored-By: Codex <noreply@openai.com>
@Pigbibi
Pigbibi enabled auto-merge (squash) August 23, 2026 16:50
@Pigbibi
Pigbibi merged commit 5f59363 into main Aug 23, 2026
6 checks passed
@Pigbibi
Pigbibi deleted the feat/canonical-lifecycle-view branch August 23, 2026 16:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant