Skip to content

fix: agent-registry 可见性申报修正 private→public（ADR-0019） #62

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
randypanding wants to merge 1 commit into from
Closed

fix: agent-registry 可见性申报修正 private→public（ADR-0019） #62

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion governance/REPOS.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -33,7 +33,7 @@ repos:

- name: agent-registry
layer: L1
visibility: private
visibility: public

@qodo-code-review qodo-code-review Bot Aug 19, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Remediation recommended

1. agent-registry entry remains local 📘 Rule violation § Compliance

This change modifies the organization repository registry entry in governance/REPOS.yaml, while
the checklist requires ADR and registry entries to reside in the designated agent-registry
repository. Keeping the agent-registry registry record here leaves a local registry entry in the
prohibited repository.
Agent Prompt 
## Issue description
The PR modifies a repository-registry entry in `governance/REPOS.yaml`, but the compliance rule requires registry entries to be maintained in the designated `agent-registry` repository.

## Issue Context
The changed line is the `agent-registry` registry record whose visibility is being changed from private to public. Preserve the intended visibility correction in the designated registry repository and remove or replace the local registry entry according to the repository layout required by the organization.

## Fix Focus Areas
- governance/REPOS.yaml[34-39]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

@qodo-code-review qodo-code-review Bot Aug 19, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Remediation recommended

2. Stale private-visibility documentation 🐞 Bug ⚙ Maintainability

Changing agent-registry to public leaves the user-facing repository map labeling it “私有” and
leaves gate/drift-check comments explaining behavior on the premise that the repository is private.
This contradicts the authoritative declaration and can mislead maintainers about the access model
and the reason ADR existence validation is deferred.
Agent Prompt 
## Issue description
`agent-registry` is now declared public, but repository documentation and validation comments still describe it as private.

## Issue Context
Update the user-facing repository table and the ADR-validation rationale so they reflect public visibility. Preserve the security rationale if it remains applicable, but do not claim that cross-repository reads are unavailable solely because the repository is private.

## Fix Focus Areas
- profile/README.md[21-21]
- .github/workflows/gate.yml[77-82]
- governance/drift-check.sh[271-276]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

status: active
role: 注册层——agent/skill/tool/team 声明 + 模型注册表(models.yaml) + ADR；AR-2 状态门禁校验器
key_paths: [registry/, decisions/, scripts/validate.py]
Expand Down