Why: facts-verify failed closed on first run — the real token file stores keys
as markdown bullets ("- ACCESS_TOKEN=..."), so the ^-anchored sed match in the
registry never fired; the earlier manual probe had used grep (anywhere-in-line)
and passed, which is exactly the drift the registry re-verification exists to
surface.
Evidence: re-run recorded in the task card — [facts-verify] total=4 pass=4
fail=0 (sha256 919401b838d77909), after fixing the sed pattern to
"^[ -]*ACCESS_TOKEN=".
Impact: policy/facts.md F2 command now matches the actual file shape and the
fact text documents the file format; no behavior change elsewhere.
Refs: task card evidence table (failed run sha256 6c61e644395042fa, then pass).
1.8 KiB
1.8 KiB
项目外部事实登记表
规则见 AGENTS.md「证据与验证门禁」与 deps/development-guidelines/standards/verification.md「声明与证据来源」。
- 每条事实 = 陈述 + 验证命令 + last_verified + TTL;引用前必须先执行其验证命令(外部事实零信任)。
- 过期(>TTL)必须重验后更新:
make facts-verify逐条重验,make facts-verify ARGS=--update把 PASS 项的 last_verified 刷新为当天并写回本表(随 PR 合入)。 - 表内验证命令不得含竖线
|(保持表格与解析可核);新增事实先实测再登记,不得凭记忆填日期。 - precheck 的
[facts]行报告过期项;AGENTS.md「Gitea 与 Git 访问事实」节为本表的叙述版。
| ID | 事实 | 验证命令 | last_verified | TTL(天) |
|---|---|---|---|---|
| F1 | Gitea Web/API 可达:https://git-home.u1680832.nyat.app:30319(1.27.3) | curl -fsS -m 10 https://git-home.u1680832.nyat.app:30319/api/v1/version |
2026-10-05 | 30 |
| F2 | API token 存在且可用(值在 ~/.secrets/gitea,文件为 markdown 列表格式 - ACCESS_TOKEN=…,不入仓不回显) |
t=$(sed -n "s/^[ -]*ACCESS_TOKEN=//p" ~/.secrets/gitea); test -n "$t" && curl -fsS -m 10 -o /dev/null -H "Authorization: token $t" https://git-home.u1680832.nyat.app:30319/api/v1/user |
2026-10-05 | 30 |
| F3 | Git over SSH 可达:ssh://git@git-ssh.u1680832.nyat.app:31411/weichen/<Repo>.git(key ~/.ssh/home_gitea) | GIT_SSH_COMMAND="ssh -i ~/.ssh/home_gitea -o BatchMode=yes" git ls-remote ssh://git@git-ssh.u1680832.nyat.app:31411/weichen/Development-Guidelines.git HEAD |
2026-10-05 | 30 |
| F4 | 旧端点 git-panel.u1680832.nyat.app:30319 已失效(TLS 握手失败),不得使用 | ! curl -fsS -m 8 https://git-panel.u1680832.nyat.app:30319/api/v1/version |
2026-10-05 | 180 |