chore(policy): adopt organization instruction routing - #570
Merged
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
Deliver the generated organization routing block in
AGENTS.mdand add the immutable reusable Org Routing workflow onnext. The caller uses organization revision1becebb7b98dab717d82897428afafd792d4fb97; declared vendored skills match the approved inventory at that revision. Repository-specific instructions are preserved.Refs z-shell/.github#665. This pull request covers this repository's initial delivery; the wider rollout and enforcement remain open.
Verification
scripts/org-routing.py checkpassed against a clean source snapshot forz-shell/zi.trunk check --no-fix, workflow actionlint and Git diff hygiene passed.Agent handoff
Ready for hosted validation and review of record. After landing and observing a successful caller, verify the exact hosted check name before requiring it in branch rules. Delivery does not by itself prove runtime selection or semantic compliance.