Skip to content

chore(infra): retire alpha-engine-friday-shell-run cron rule (L4055)#348

Merged
cipher813 merged 2 commits into
mainfrom
chore/retire-friday-shell-run-cron-l4055
May 29, 2026
Merged

chore(infra): retire alpha-engine-friday-shell-run cron rule (L4055)#348
cipher813 merged 2 commits into
mainfrom
chore/retire-friday-shell-run-cron-l4055

Conversation

@cipher813
Copy link
Copy Markdown
Owner

What

Removes the superseded fixed-time Friday cron rule alpha-engine-friday-shell-run from CloudFormation. Closes ROADMAP gate L4055.

Why now — gate cleared (verified live)

The cron was replaced by the event-driven alpha-engine-eod-success-friday-shell-trigger Lambda (#282, merged 2026-05-21), which fires the Saturday SF in shell_run mode on the Friday EOD-SF SUCCEEDED transition (trading_day-bound, not wall-clock). The cron ran DISABLED from the 5/21 cutover. Gate L4055 required the event-driven path to confirm across two Fridays — done:

Fire Date Trigger Shell-run SF
1st 2026-05-22 ✅ fired correctly FAILED (preflight/transient, same week as the known SF-blocker workstream)
2nd 2026-05-29 ✅ fired correctly SUCCEEDED (28 min, clean)

Verified live before deletion: cron State=DISABLED; trigger Lambda Active; both friday-shell-* Saturday-SF executions present.

Changes

  • CFN alpha-engine-orchestration.yaml — remove the FridayShellRunTrigger AWS::Events::Rule (deploying the stack removes the rule + its single target). No other resource references the logical ID.
  • step_function.json — update the shell_run-gate comment to point at the event-driven Lambda. The gate itself is unchanged (strict superset; the Lambda still supplies {"shell_run": true}).
  • index.py (trigger Lambda) — restore pipeline_role: "shell-run" in the shell-run input. Audit finding: the Lambda dropped the tag the cron carried, so since the 5/21 cutover Friday shell-runs ran without the page-25 role-filter surface tag. Fixed here so the event-driven path is a faithful replacement, not a surface regression.
  • deploy.sh — comment updated (cron retired, not just disabled).
  • TestsTestFridayEventBridgeRule (4 rule-presence tests) → one inverted regression guard asserting the rule stays removed; _TRIGGER_SUCCESSORS map + the Friday-Input test updated for the removed block; the trigger Lambda test now asserts pipeline_role="shell-run".

Verification

  • aws cloudformation validate-template OK; step_function.json valid JSON.
  • Full suite: 1683 passed, 1 skipped. Trigger Lambda suite: 13 passed.

Deploy (operator, on merge)

  1. aws cloudformation deploy the orchestration stack → removes the cron rule + target.
  2. Redeploy the trigger Lambda (infrastructure/lambdas/eod-success-friday-shell-trigger/deploy.sh) so the pipeline_role tag takes effect on the next Friday shell-run.

🤖 Generated with Claude Code

cipher813 and others added 2 commits May 29, 2026 16:18
The fixed-time Friday cron rule was superseded by the event-driven
alpha-engine-eod-success-friday-shell-trigger Lambda (#282), which fires the
Saturday SF in shell_run mode on the Friday EOD-SF SUCCEEDED transition
(trading_day-bound, not wall-clock). The cron ran DISABLED from the 2026-05-21
cutover; the event-driven path has now confirmed across two Fridays:

  - 2026-05-22 (1st): trigger fired correctly; shell-run SF FAILED (preflight/
    transient, same week as the known SF-blocker workstream).
  - 2026-05-29 (2nd, today): trigger fired correctly; shell-run SF SUCCEEDED
    end-to-end (28 min). Gate L4055 cleared.

Verified live before deletion: cron rule State=DISABLED; trigger Lambda Active;
both friday-shell-* Saturday-SF executions present.

Changes:
- CFN alpha-engine-orchestration.yaml: remove the FridayShellRunTrigger
  AWS::Events::Rule resource (deploying the stack removes the rule + its target).
- step_function.json: update the shell_run gate comment to point at the
  event-driven Lambda (the gate itself is unchanged — strict superset).
- index.py: restore pipeline_role="shell-run" in the Lambda's shell-run input.
  AUDIT FINDING: the Lambda dropped the tag the cron carried, so since 5/21
  Friday shell-runs ran WITHOUT the page-25 role-filter surface tag. Fixed here
  so the event-driven path is a faithful replacement, not a surface regression.
- deploy.sh: comment updated (cron retired, not just disabled).
- Tests: TestFridayEventBridgeRule (4 rule-presence tests) → one inverted
  regression guard asserting the rule stays removed; _TRIGGER_SUCCESSORS map +
  Friday-Input test updated for the removed block; trigger Lambda test asserts
  pipeline_role="shell-run".

CFN validate-template OK; step_function.json valid; suite 1683 passed, 1
skipped; trigger Lambda suite 13 passed.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@cipher813 cipher813 merged commit 6193d18 into main May 29, 2026
1 check passed
@cipher813 cipher813 deleted the chore/retire-friday-shell-run-cron-l4055 branch May 29, 2026 23:24
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