Repository navigation
extdeps: anchor cache_purity in external-authority backfill (fleet-red keystone) - #5465
Merged
Merged
Conversation
…y backfill (fleet-red keystone fix) #5429 added the cache_purity module but did not register it in external_authority_backfill_pending.txt (its 4 realization siblings are listed), so #5418's live-clean-tree lens fail-closes — fleet-wide main-red since cdd1421 (#5429); prior commit ac9a7e7 (#5449) was green. Same floor-skew class as #5445/#5453. One-line backfill anchor; diagnosed by bright-stag-194, delegated by sunny-bee-667 (lane owner) for the urgent fleet-unblock. Also unblocks stern-otter's P3 branch. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
briansrls
added a commit
that referenced
this pull request
Jun 21, 2026
…ag (§3 cleanup) (#5466) #5464 added a Wikipedia-anchor to `extdeps.realization.cache_purity` as an incorrect fix for the fleet-red; #5465 then landed the correct fix (backfill entry). The anchor is stranded: §3 forbids an internal machinery module from claiming an external URI it does not ground on, and the backfill entry (#5465) already satisfies the gate. Remove the three import lines and the dead `data extdeps_external_authority_anchor` declaration; the module stays backfill-listed (its four realization siblings share that classification). Co-authored-by: Brian Searls <briansrls@gunb.ai> Co-authored-by: Claude Sonnet 4.6 <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.
Fleet-wide main-red keystone fix. One line.
Root cause
#5429 (cdd1421) added module `extdeps.realization.cache_purity` (`dsl/extdeps/realization/cache_purity.dag`) but did not register it in `dsl/extdeps/external_authority_backfill_pending.txt` — its four siblings (`hermetic_fixture`, `parse_table_memo`, `resolved_graph`, `v1_handler`) are all listed. So #5418's external-authority live-clean-tree lens fail-closes on the unanchored module:
Main has been red since #5429; the prior commit (#5449, ac9a7e7) was green. Same floor-skew class as #5445/#5453 — the branch was green pre-merge, reds main on landing.
Fix
Add `extdeps.realization.cache_purity` to the backfill list (alphabetical slot). The sanctioned pending-anchor mechanism; exactly the #5453 reconciliation pattern.
Why this PR (not #5429's owner)
Diagnosed by bright-stag-194; delegated by sunny-bee-667 (the §2 lane owner) for the urgent fleet-unblock (a fresh PR from their side would still wait on review+merge). Blocks every PR (all inherit the red) and unblocks stern-otter's P3 branch.
🤖 Generated with Claude Code