Restore the full canary registry - #90
Merged
Merged
Conversation
Trimming the registry to iamkayleb/bukay alone broke every sync run: select_consumer_sync_phase rejects a config outside 2..3 canaries with canary_config_requires_two_or_three_repos, so Maint 68 failed in its first job before reaching any repository. The trim was aimed at two consistently red matrix legs for repositories this fork cannot write to. Those legs were noise, not the blocker — the run that prompted the change failed on all three legs, including bukay, for an unrelated missing read:org PAT scope. Removing them bought nothing and cost the whole sync. Relaxing the lower bound was considered and rejected: the checked-in config is also asserted to cover six distinct consumer capability shapes, which a single-consumer fork cannot satisfy without inventing capabilities. The two unowned legs stay red until this fork either gains access to them or registers a second consumer it owns. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01FC8XoyssN5v6hQCTtcjoB5
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
2 participants
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.
Trimming the registry to iamkayleb/bukay alone broke every sync run: select_consumer_sync_phase rejects a config outside 2..3 canaries with canary_config_requires_two_or_three_repos, so Maint 68 failed in its first job before reaching any repository.
The trim was aimed at two consistently red matrix legs for repositories this fork cannot write to. Those legs were noise, not the blocker — the run that prompted the change failed on all three legs, including bukay, for an unrelated missing read:org PAT scope. Removing them bought nothing and cost the whole sync.
Relaxing the lower bound was considered and rejected: the checked-in config is also asserted to cover six distinct consumer capability shapes, which a single-consumer fork cannot satisfy without inventing capabilities. The two unowned legs stay red until this fork either gains access to them or registers a second consumer it owns.
Claude-Session: https://claude.ai/code/session_01FC8XoyssN5v6hQCTtcjoB5
Workflow Source
Started from:
Automation intent:
Notes:
Summary
Testing