feat: include as215932.net in loop scope#3
Merged
Conversation
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.
Summary
Extend the production Engineering Loop managed-repo contract from the prior seven core repos to include the AS/routing identity repo:
AS215932/as215932.nettoCORE_REPOS.as215932.netcheckout name.as215932.netin sibling workspaces alongsidehyrule-*,engineering-loop, and infra checkouts.Safety
as215932.netremains AS/routing identity; no broad domain-policy replacement is implied.Validation
uv run --group dev python -m pytest -q tests/test_phase24_daemon.py tests/test_phase8_repo_adapter.pyuv run --group dev mypy --strict srcuvx ruff check src testsNetwork-operations follow-up
After merge,
network-operations#228should pinengineering_loop_versionto the merged SHA and add theas215932.networkspace checkout/deployment repo entry.