Why: establish the authorized task workspace and its initial baseline.
Evidence: preserved precheck receipt in .task/fix-gitea-endpoint-migration.md; R0=3d3474a731f9ef3ee1f41935e63bca3afb70db56.
Impact: task metadata only; the feature workspace starts at 3d3474a731.
Refs: .task/fix-gitea-endpoint-migration.md
Why: record the endpoint migration goal, file scope and completion
conditions before dispatching the unit.
Evidence: NOT_RUN (task card only)
Impact: task card only.
Why: cursor completed the file changes but failed the terminal record
decode; scene preserved, diff exported for the retry.
Evidence: NOT_RUN (task card only)
Impact: task card only.
Why: cursor again completed the work but failed the terminal record;
preparing a routing unit to promote the next candidate.
Evidence: NOT_RUN (task card only)
Impact: task card only.
Why: antigravity promotion landed via worker transport so the endpoint
migration implementation can proceed; revert before final delivery.
Evidence: NOT_RUN (task card only)
Impact: task card only.
Why: antigravity failed at startup on an OAuth endpoint EOF; scene
preserved, retrying with the next candidate.
Evidence: NOT_RUN (task card only)
Impact: task card only.
Why: antigravity OAuth is unreachable and its profile sits first, so
every run fails at launch before any candidate can run; restore the
original order (revert of transport 8441284c, to be re-landed when
agy recovers).
Evidence: NOT_RUN (routing config only)
Impact: routing order only; Codex stays last.
Why: include the current integration baseline before verification.
Evidence: fetched origin/main=cb36b59accd0418c5ca952912d7c181b83038a4c.
Impact: integrate upstream changes without rewriting task history.
Refs: task-sync
Why: include the current integration baseline before verification.
Evidence: fetched origin/main=6ced938a126981ee2a4fab671a2da94f49cb56c5.
Impact: integrate upstream changes without rewriting task history.
Refs: task-sync
Why: modules/backend pin alignment requires Backend code to adopt the
current dependency API generation first; blocker documented on PR #706
and handed to a follow-up Backend integration task.
Evidence: NOT_RUN (vet failures reproduced and documented)
Impact: task card only.
Some required checks failed
ci / svc-realcombo (pull_request) Failing after 1m34s
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.
Gitea 服务器迁移：更新仓内端点引用
.gitmodules（14 URL）、scripts/task.sh、scripts/task_triage.py、scripts/facts-verify.sh、scripts/svc.sh、.gitea/workflows/ci.yaml、plugins/registry.json、policy/facts.md（F1—F3）、policy/delivery.md（队列链接）、相关测试期望值make test-governanceOK（证据见任务卡，SELF）docs/superpowers/reviews/2026-10-22-gitea-endpoint-migration-review.md）阻塞说明（2026-10-22）
端点引用迁移已全部完成并通过独立 Review；组件仓迁移已全部合入（14/14）。本 PR 的组件 pin 对齐被 Backend 依赖 API 漂移阻塞：
make test-pins一致性门禁要求 modules/backend 的嵌套 pin 与 Dev 顶层 pin 完全一致；解除条件：先落地一个 Backend 集成任务——把 Backend 代码升级到当前 agent-command/agent-intent/agent-native/agent-squad 的 API（或由 owner 决定 pin 策略豁免），随后本 PR 重新对齐 pin、重跑
make test与 CI。本 PR 现状：端点迁移 + 13 组件 pin 已就绪；modules/backend pin 保守停留在 main 的 330c1a3（迁移前世代），CI 的 checkout allowlist 将拒绝该 pin（预期红灯），因此暂不等待 CI、不请求合入。
View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.