refactor(docs): point entry-file references at their new homes
AGENTS.md stopped being the store of record for build steps, Python env, hardware pins, doc conventions, log cost and task ownership. Those facts already live in docs, skills and role files; the entry file now only points at them. This commit moves every reference that used to name the entry file to the authoritative landing point, so a reader who follows a link arrives at the fact instead of at a sentence that no longer exists. What changed is links and prose, not behaviour. Code, scripts and tests only have comment and docstring lines touched; the only non-comment edit in the whole changeset is one note string inside the generated pin table JSON, and its generator was changed in the same step so the two stay byte-identical. New landing points created before the references were retargeted: - The console single-writer log design doc, section 7.1, is now the single authority for log cost: about 90 B flash and 216 B stack per DBG_ line, and the rule that deep call chains must predefine DBG_LINE_BUF_MAX. It also carries the full list of the twelve translation units that have tightened it, plus the grep command that decides the truth if the list and the code ever disagree. - The document writing standard, section 2, now holds the BOM list. - keil-build skill gains an exit code table: 0 success, 1 build failure, 2 BuildEnvError, 3 usage, 4 build lock held. This corrects a belief that was never actually written down anywhere: exit 2 does not simply mean environment error, argparse also exits 2 and the wrapper script was remapped so the two no longer collide. Regenerated and checked byte for byte: - The end-to-end architecture SVG in docs/images from its generator. - tools/netlist_semantics/pinout_kb.json from gen_kb.py. Both are idempotent; running the generators again produces no diff. Deliberately not touched, because machines read them: - scripts/check_bom_drift.py joins every line containing BOM and asserts four paths are present, so the entry file BOM line must stay one line. - scripts/gen_task_table.py reads the TASK_TABLE anchors directly. - scripts/rename_maps and scripts/archive keep their historical wording; they describe what happened, not what is true now. Verified: doc links report the same six pre-existing findings as the base commit and no new ones, generated-fresh passes, bom drift is clean across 101 files, and AGENTS.md itself is unchanged in this commit.
This commit is contained in:
@@ -1289,7 +1289,7 @@ def cmd_log(args):
|
||||
"""读日志:**先过滤、后截尾**。
|
||||
|
||||
旧实现先 tail 后 grep → `log --grep "App init OK"`(--tail 默认 50)只在末 50 行
|
||||
里找,开机标记必然查无此 marker——这就是 AGENTS.md 里"log --grep 实测不可信"的
|
||||
里找,开机标记必然查无此 marker——这就是历史上"log --grep 实测不可信"的
|
||||
根因(2026-10-09 实测复现并修复)。返回带 scanned/matched 计数,便于判定。
|
||||
"""
|
||||
log_path, gen = resolve_log_paths()
|
||||
@@ -1334,7 +1334,7 @@ def cmd_wait_idle(args):
|
||||
# wait-idle 是同步阻塞的长操作:CLI 超时按等待上限自动推导。旧实现固定 5s
|
||||
# 硬超时会在 daemon 还在等的时候先掐断 → CLI 报 exit 2、daemon 侧
|
||||
# ConnectionAbortedError traceback(本机 daemon.log 实测 16 次)。
|
||||
# AGENTS.md 抓开机日志铁律②"必须带 --timeout"就是这个坑的手工补丁。
|
||||
# 抓开机日志必须带 --timeout(CLI 侧默认不推导时的护栏),否则就是下面这个坑的手工补丁。
|
||||
args.timeout = args.max_ms / 1000.0 + 5.0
|
||||
return call_daemon(args, "POST", "/wait-idle", body)
|
||||
|
||||
@@ -1514,7 +1514,7 @@ def run_selftest():
|
||||
check("T5c 持续吐数判 timeout + 返回增量字节",
|
||||
r["reason"] == "timeout" and r["rx_bytes"] > 0, repr(r))
|
||||
|
||||
# T6 log 命令:先 grep 后 tail(旧顺序即 AGENTS.md"log --grep 不可信"的根因)
|
||||
# T6 log 命令:先 grep 后 tail(旧顺序即"log --grep 不可信"的根因)
|
||||
saved_log, saved_meta = LOG_FILE, load_meta
|
||||
saved_resolve = globals()["resolve_log_paths"]
|
||||
fd2, lpath2 = tempfile.mkstemp(prefix="serial_tool_selftest_log_", suffix=".log")
|
||||
|
||||
Reference in New Issue
Block a user