You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Phase 2] Extend the repo-local pinning standard to all first-party reusables #671
As a maintainer,
I want broaden the mutable-ref exception in AGENTS.md and versioning.md to cover every first-party same-repo reusable, not just the two agents,
so that the channel-tag standard and its compliance-audit exemption explicitly include ci-failure-analyst, so the repin and the future test are sanctioned.
Acceptance Criteria
AGENTS.md §"Release channel tags & the mutable-ref exception" states the exception applies to all first-party same-repo reusables and names ci-failure-analyst as an in-scope channel namespace.
The doc records that the release-channel-tags ruleset must add target ci-failure-analyst/** for the exception's guarantees to hold, cross-referencing the human-gated ruleset story.
docs/release/versioning.md channel scheme is generalized so it reads correctly for non-agent reusables.
The text makes clear a compliance audit must not flag @ci-failure-analyst/stable as an unpinned action.
AGENTS.md exception is around lines 96-120; the ruleset currently targets only pr-review/** and dev-lead/**.
The CANONICAL org standard lives in petry-projects/.github (cross-repo). This story updates only the repo-local AGENTS.md/docs; the org-wide promotion is the human-gated story id 8 — do not attempt cross-repo edits here.
Keep the documented invariant that agents running as GITHUB_TOKEN cannot move/delete release tags (only admin/automation can).
Project Structure Notes
Edits AGENTS.md and docs/release/versioning.md only.
Activity