docs(config): correct alias-pinned Lambda env-flag flip procedure (L4497)#235
Merged
Merged
Conversation
… (L4497) The `_flag_env_or_yaml` docstring + the XSEC_DEMEAN_ALPHA_ENABLED comment claimed the flag flips "live via update-function-configuration, no redeploy." That is the trap L4497 flags: `alpha-engine-predictor-inference` runs at the `live` alias pinned to a PUBLISHED version, whose env is frozen — a bare `update-function-configuration` only touches `$LATEST` and is a SILENT no-op on the alias. Corrected both comments to document the real procedure (update-function-configuration → publish-version → update-alias live→N; revert = alias rollback) and clarified "no redeploy" = "no container rebuild," not "env change takes effect on the alias immediately." Comment-only; mirrors the already-corrected OBSERVATION_REGISTRY `predictor_xsec_level_neutralization`. 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
1 participant
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.
Closes L4497 (P2, audit finding 2026-06-03) — the only non-gated remnant after this session's API-resilience sweep drained the build queue.
Problem
config.py's_flag_env_or_yamldocstring and theXSEC_DEMEAN_ALPHA_ENABLEDcomment said the flag flips "live viaupdate-function-configuration, no redeploy." That's the exact trap that bit the 6/3 GATE 1 flip:alpha-engine-predictor-inferenceis invoked at thelivealias pinned to a published version, and a published version's env is frozen —update-function-configurationonly mutates$LATEST, so it's a silent no-op on the alias.Fix (comment-only)
Both comments now document the real procedure:
update-function-configuration ($LATEST) → publish-version → update-alias live→<N>(revert =update-alias live→<prior>), and clarify "no redeploy" = "no container rebuild," not "env change takes effect on the alias immediately." Mirrors the already-correctedOBSERVATION_REGISTRY.yaml::predictor_xsec_level_neutralization.No behavior change.
tests/test_level_neutralization.pygreen (6 passed); config.py syntax verified.ROADMAP L4497
[x]write-back will follow in the session config docs PR.🤖 Generated with Claude Code