Skip to content

ref(seer): Use lifecycle locking for workflow configuration - #129092

Draft
trevor-e wants to merge 5 commits into
masterfrom
telkins/codex/ref/seer-workflow-locking
Draft

trevor-e wants to merge 5 commits into
masterfrom
telkins/codex/ref/seer-workflow-locking

Conversation

@trevor-e

@trevor-e trevor-e commented Oct 28, 2026 •

Copy link
Copy Markdown
Member

Apply the SeerWorkflowRunLifecycle pattern to SeerWorkflow: retain only config and organization IDs, read fresh configuration, and acquire a row lock within each mutation.

Metric-breach admission owns its transaction and calls the public get_or_create_run(), accepting a second locked config read. Config-list serialization reuses bulk-loaded models.

Validation: 95 relevant tests passed, including freshness, organization scoping, rollback, and query coverage. Lint and type checks passed.

Store workflow identity as IDs and load fresh configuration for reads and locked mutations. Update callers and preserve batched config serialization.
@github-actions github-actions Bot added the Scope: Backend Automatically applied to PRs that change backend components label Oct 28, 2026

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Scope: Backend Automatically applied to PRs that change backend components

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant