Skip to content

Deferred: compatibility checks for terminal preservation recovery - #536

Closed
JWThewes wants to merge 1 commit into
fix/blocked-unit-completionfrom
fix/recovery-compatibility-preflight
Closed

JWThewes wants to merge 1 commit into
fix/blocked-unit-completionfrom
fix/recovery-compatibility-preflight

Conversation

@JWThewes

@JWThewes JWThewes commented Oct 14, 2026 •

Copy link
Copy Markdown
Contributor

Deferred with the added preservation-recovery feature for finished incomplete intents.

The immediate safeguards now consist of #534 (prevention and canonical completion), #537 (delivery status/retry) and #539 (bounded read-only audit). Both follow-ups target #534 directly. None retains the terminal-preservation mutation path protected by this PR.

These compatibility protections remain necessary if that preservation feature is resumed: verify the deployed orchestrator/runtime capabilities, preserve original execution pins, and fence mutating recovery dispatch. Deferral is not a recommendation to restore the mutation without its protections.

The source branch is retained at 35737c9d97584c1c0b5370de56777e73263cfba1, and local backup refs preserve this work and the original recovery stack. This PR is closed to make clear that it is outside the current merge sequence. No deployment, production recovery or change to the historical notification PR is included.

@JWThewes
JWThewes added this pull request to stack #551 October 14, 2026 11:17
@JWThewes
JWThewes removed this pull request from stack #551 October 15, 2026 15:36
@JWThewes JWThewes changed the title Verify deployment compatibility before preservation recovery Deferred: compatibility checks for terminal preservation recovery Oct 15, 2026
@JWThewes JWThewes closed this Oct 15, 2026
@JWThewes

Copy link
Copy Markdown
Contributor Author

@jeromevdl Following your scope feedback, this PR is now closed as deferred together with the added preservation-recovery mode for finished, incomplete intents. That mutation path has been removed from the active #534/#537/#539 changes; ordinary repair and rewind remain supported.

The current sequence is #534 prevention first, then #537 delivery retry and #539 read-only audit independently. Neither follow-up depends on this PR.

The source branch is retained at 35737c9, and backups preserve the original recovery work. If we revisit terminal-preservation recovery as a separate product feature, its deployment-compatibility protections need to return with it. No deployment or production recovery was performed.

@jeromevdl jeromevdl added area/frontend React application in frontend/ area/agents AgentCore runtime: CLI drivers, MCP tools, workspace and Git operations area/backend Lambda APIs, lambda/shared, v2-orchestrator area/infra Terraform, installer and deployment area/ci GitHub Actions, hooks, lint, release tooling, E2E harness size/L < 3000 changed lines (lockfiles excluded) labels Oct 30, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area/agents AgentCore runtime: CLI drivers, MCP tools, workspace and Git operations area/backend Lambda APIs, lambda/shared, v2-orchestrator area/ci GitHub Actions, hooks, lint, release tooling, E2E harness area/frontend React application in frontend/ area/infra Terraform, installer and deployment size/L < 3000 changed lines (lockfiles excluded)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants