Skip to content

chore: drop dead ALPHA_ENGINE_LIB_TOKEN PAT plumbing#148

Merged
cipher813 merged 3 commits into
mainfrom
feat/drop-pat-plumbing
May 3, 2026
Merged

chore: drop dead ALPHA_ENGINE_LIB_TOKEN PAT plumbing#148
cipher813 merged 3 commits into
mainfrom
feat/drop-pat-plumbing

Conversation

@cipher813
Copy link
Copy Markdown
Owner

Summary

alpha-engine-lib was flipped public 2026-05-03. PAT auth machinery is now dead weight — removed across 6 files (net −87 lines).

Changes

File What changed
.github/workflows/ci.yml Drop "Configure git auth" step
.github/workflows/deploy.yml Drop the secondary actions/checkout for cipher813/alpha-engine-lib + the LIB_REPO_DIR env on the deploy step
Dockerfile Replace COPY vendor/alpha-engine-lib + local pip install with pip install "alpha-engine-lib[flow_doctor] @ git+https://...@v0.3.0". [flow_doctor]-only install for Lambda preserved (Lambda doesn't need [arcticdb] or [rag]).
infrastructure/deploy.sh Drop vendor/alpha-engine-lib staging + cleanup_lib_staging trap
infrastructure/spot_data_weekly.sh Drop SSM PAT fetch + insteadOf rewrite from DEPS step + inline comment cleanup (3 spots)
infrastructure/spot_drift_detection.sh Same removal

Companion follow-ups (not in this PR)

  • Delete ALPHA_ENGINE_LIB_TOKEN GitHub Actions secret on this repo
  • Delete /alpha-engine/lib-token SSM SecureString (us-east-1)
  • vendor/alpha-engine-lib local checkout can be removed (gitignored, not in any commit)

Test plan

  • CI passes on this PR (validates pip install works without the PAT)
  • deploy.yml runs cleanly on next push to main (validates Docker build with git+https install)
  • Spot data weekly + drift detection runs cleanly on next launch

Per ROADMAP follow-up "P3 Drop ALPHA_ENGINE_LIB_TOKEN PAT plumbing" added 2026-05-03. Second of 6 consumer-repo PRs in this cleanup arc; prototype: alpha-engine PR #128.

🤖 Generated with Claude Code

cipher813 and others added 3 commits May 3, 2026 15:30
Caught 2026-05-03 in SF eval-pipeline-validation-5: Research succeeded
and wrote new-format captures to S3, but the eval-judge state silently
never fired because the operator had passed skip_backtester=true to
skip the long-running backtester for validation purposes.

PR 4c (#140) wired the eval-pipeline states between Backtester success
and SaturdayHealthCheck:

  CheckBacktesterStatus.Success
    → CheckSkipEvalJudge → ComputeEvalCadence → CheckMonthlyCadence
        → EvalJudgeFirstSaturday or EvalJudgeWeekly → EvalRollingMean
    → SaturdayHealthCheck

But CheckSkipBacktester.skip routed directly to SaturdayHealthCheck,
bypassing the eval-pipeline entirely. Production Sat 5/9 won't hit
this (skip_backtester defaults false; Backtester runs and routes
through eval-judge correctly), but operator manual skips for any
non-eval validation purpose silently dropped the eval state.

Fix: route skip_backtester=true → CheckSkipEvalJudge instead of
SaturdayHealthCheck. Eval pipeline now fires on every SF execution
where the operator hasn't explicitly skip_eval_judge'd it.

tests/test_sf_eval_judge_wiring.py — TestSkipBacktesterPreservesEvalJudge:
  pins the routing so a future "simplification" can't re-introduce
  the silent bypass.

Tests 433 → 434 (+1 wiring assertion).

Pairs with alpha-engine-research PR #104 (RubricEvalLLMOutput
defense + judge max_tokens to strategic tier — closes the 5/32
remaining failure class observed in this same SF run).

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
alpha-engine-lib was flipped public 2026-05-03; PAT auth machinery
that existed to install from a private repo is now dead weight.
Removed across 6 files (net −87 lines).

CI:
- .github/workflows/ci.yml — drop "Configure git auth" step
- .github/workflows/deploy.yml — drop the secondary
  actions/checkout for cipher813/alpha-engine-lib + the LIB_REPO_DIR
  env on the deploy step

Docker / deploy:
- Dockerfile — replace `COPY vendor/alpha-engine-lib` + local pip
  install with `pip install "alpha-engine-lib[flow_doctor] @
  git+https://github.com/cipher813/alpha-engine-lib@v0.3.0"`. The
  [flow_doctor]-only install for Lambda is preserved (Lambda doesn't
  need [arcticdb] or [rag]); requirements.txt's
  [arcticdb,flow_doctor,rag] extras still apply for the EC2 install
  path.
- infrastructure/deploy.sh — drop the vendor/alpha-engine-lib
  staging block + cleanup_lib_staging trap. Replace with one-line
  comment explaining lib comes from public git+https now.

EC2 spot scripts:
- infrastructure/spot_data_weekly.sh — drop SSM PAT fetch + insteadOf
  rewrite from the DEPS step. Update inline comments referencing the
  old mechanism (3 spots).
- infrastructure/spot_drift_detection.sh — same removal.

Companion follow-ups (not in this PR):
- Delete ALPHA_ENGINE_LIB_TOKEN GitHub Actions secret on this repo
- Delete /alpha-engine/lib-token SSM SecureString (us-east-1)
- vendor/alpha-engine-lib local checkout can be removed (gitignored,
  not in any commit)

Per ROADMAP follow-up "P3 Drop ALPHA_ENGINE_LIB_TOKEN PAT plumbing"
added 2026-05-03. Second of 6 consumer-repo PRs in this cleanup arc;
prototype landed in alpha-engine PR #128.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@cipher813 cipher813 merged commit 3c9cb35 into main May 3, 2026
1 check passed
@cipher813 cipher813 deleted the feat/drop-pat-plumbing branch May 3, 2026 22:52
cipher813 added a commit that referenced this pull request May 12, 2026
…#222)

PR #221 bumped requirements.txt to v0.12.0 (alpha_engine_lib.secrets)
but missed the Dockerfile, which strips alpha-engine-lib from
requirements.txt before pip install (via `grep -vE ...alpha-engine-lib`)
and installs from a hardcoded `pip install "alpha-engine-lib@v0.3.0"`
line — so a requirements-only bump never propagates to the Lambda
image.

Data Lambda canary failed at 2026-05-12 17:22 UTC after PR #221
auto-deployed on merge to main:

    WARNING: Canary returned 'No module named 'alpha_engine_lib.secrets''

Live alias unchanged (canary refusal). Same drift class hit the
predictor Lambda 2 minutes earlier and prompted the predictor hotfix
(alpha-engine-predictor #148). Two stale pins shipped to canary the
same hour.

Adds tests/test_lib_pin_lockstep.py — re-greps both deploy artifacts
on every CI run and fails if they drift. Same antipattern as
2026-05-06 (research v0.4.0 → v0.5.1 / image kept v0.3.0 /
agent_schemas ModuleNotFoundError) and the predictor canary same
hour. Comments warning about lockstep weren't enough — locking it in
test.

Suite: 801/801 (was 800 + 1 lockstep test).

Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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