chore(infra): retire alpha-engine-friday-shell-run cron rule (L4055)#348
Merged
Conversation
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>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Removes the superseded fixed-time Friday cron rule
alpha-engine-friday-shell-runfrom 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-triggerLambda (#282, merged 2026-05-21), which fires the Saturday SF inshell_runmode on the Friday EOD-SFSUCCEEDEDtransition (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:Verified live before deletion: cron
State=DISABLED; trigger LambdaActive; bothfriday-shell-*Saturday-SF executions present.Changes
alpha-engine-orchestration.yaml— remove theFridayShellRunTriggerAWS::Events::Rule(deploying the stack removes the rule + its single target). No other resource references the logical ID.step_function.json— update theshell_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) — restorepipeline_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).TestFridayEventBridgeRule(4 rule-presence tests) → one inverted regression guard asserting the rule stays removed;_TRIGGER_SUCCESSORSmap + the Friday-Input test updated for the removed block; the trigger Lambda test now assertspipeline_role="shell-run".Verification
aws cloudformation validate-templateOK;step_function.jsonvalid JSON.Deploy (operator, on merge)
aws cloudformation deploythe orchestration stack → removes the cron rule + target.infrastructure/lambdas/eod-success-friday-shell-trigger/deploy.sh) so thepipeline_roletag takes effect on the next Friday shell-run.🤖 Generated with Claude Code