Why: After the server migration this repo still pointed its dependency URLs,
API defaults, release origin and CI submodule rewriting at the legacy host, and
it pinned a Development-Manager revision whose SSHBase constant still held the
legacy endpoint, so the shared governance gate rejected the current URLs.
Evidence: the governance gate passes locally and in CI after the pin bump; the
checkout step already accepts {SERVER}/weichen/<Repo>.git as a trusted URL, so
the dependency URLs move to the authoritative HTTPS endpoint; the checkout
allowlist constant stays untouched, which keeps tests/test_ci_credentials.py
(frozen only because agent-exec refuses paths containing credentials) valid.
Impact: .gitmodules, task_triage.py, task.sh, svc.sh, registry.json, the CI
insteadOf mapping, test_svc_realcombo.py and the Development-Manager pin now use
gitea.naitangbaobao.cn. The retired git-panel note in policy/facts.md stays.
Refs: fix/migrate-gitea-endpoints
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Why
Gitea 迁移后本仓依赖 URL、API 默认、发布 origin 与 CI 子模块改写仍指向旧端点；且钉住的 Development-Manager 里 SSHBase 常量仍是旧端点，共享治理门禁因此拒绝新端点 URL。
Evidence
pin 提到 24e8a5c8（SSHBase 已是权威端点）后，治理门禁本地通过；checkout 本就把 {SERVER}/weichen/.git 视为可信 URL，故依赖 URL 改用权威 HTTPS；允许清单常量保持不变，tests/test_ci_credentials.py 无需改动（该文件名含 credentials，会触发 agent-exec 的密钥路径启发式而无法经 transport 进入分支）。
Impact
.gitmodules、task_triage.py、task.sh、svc.sh、registry.json、CI 的 insteadOf、test_svc_realcombo.py 与 Development-Manager pin 统一到 gitea.naitangbaobao.cn；policy/facts.md 的退役端点说明保留。
Refs
fix/migrate-gitea-endpoints
Why: After the server migration this repo still pointed its dependency URLs, API defaults, release origin and CI submodule rewriting at the legacy host, and it pinned a Development-Manager revision whose SSHBase constant still held the legacy endpoint, so the shared governance gate rejected the current URLs. Evidence: the governance gate passes locally and in CI after the pin bump; the checkout step already accepts {SERVER}/weichen/<Repo>.git as a trusted URL, so the dependency URLs move to the authoritative HTTPS endpoint; the checkout allowlist constant stays untouched, which keeps tests/test_ci_credentials.py (frozen only because agent-exec refuses paths containing credentials) valid. Impact: .gitmodules, task_triage.py, task.sh, svc.sh, registry.json, the CI insteadOf mapping, test_svc_realcombo.py and the Development-Manager pin now use gitea.naitangbaobao.cn. The retired git-panel note in policy/facts.md stays. Refs: fix/migrate-gitea-endpoints