Skip to content

Complete failed S3 runner retirement and production MailOut binding #283

Open

Description

@lweberru

Production users still cannot inspect an S3 checkpoint after a reported native Apply failure: the one-shot worker exits, but its CF application can remain desired STARTED. The new stopped-process recovery gate correctly refuses it; waiting alone does not retire that worker.

Add narrowly scoped background retirement for explicitly reported apply_failed S3 runs after a completion grace period. Verify exact app/space/immutable source before issuing CF Stop; record maintenance completion only after independent process/task termination proof. Preserve the recovery hold and all State, and keep the owner checkpoint/confirmation checks independent. Exclude timeouts, ambiguous failures, bootstrap/pending migration and separate recovery data. Related: #280, #279.

Also finish production email availability: v2.2.1 has no production SMTP binding, and its workflow does not pass one to runtime preparation. Add the reviewed separate Prod MailOut manifest, validated DNS and sender, protected-environment binding, actual CF binding verification and a missing-binding preflight. Dev credentials must not be reused. No real message or credential values belong in this issue.

Activity

  1. lweberru commented on Nov 20, 2026

    @lweberru
    CollaboratorAuthor

    Delivered in v2.2.3.

    • Dev run 44791689081 and the actual production deploy job in 44803957213 completed successfully using the same immutable application/Runner packages.
    • Production runtime binding verification reports MailOut enabled; the connection task, including SMTP verification, and the isolated Runner checks completed successfully. Independent SMTP TLS/authentication verification also passed without sending a test email.
    • Workflow follow-ups fix(ci): retain production project context for MailOut preparation #287 and fix(ci): deploy existing releases after skipped publication #288 fix the missing application-preparation project context and the skipped deployment when installing an existing release. The earlier failed/skipped attempts remain recorded in those PRs. Both fixes have green CI and targeted regression coverage.

    Source-verified retirement of explicitly reported failed S3 Apply runners is deployed. Checkpoint inspection and owner confirmation remain required; this release does not itself reconcile a customer Apply or remove Audit resources.

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions