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:
@@ -48,7 +48,7 @@ typedef enum {
|
||||
* NET_MSG_UDP_RECVFROM - buf/len=载荷 + timeout_ms=等待预算 + flags
|
||||
* ⚠ 源地址出参(src_addr / addrlen 两个指针)**不走本结构**:结构按值拷入
|
||||
* 队列,指针若在 int 字段里过桥,64 位主机单测构建会被截断,且违反
|
||||
* AGENTS「勿给 net_msg_t 加回传用字段」。改走 net_udp.c 的 per-fd 挂起槽
|
||||
* 禁止给 net_msg_t 加回传用字段。改走 net_udp.c 的 per-fd 挂起槽
|
||||
* (调用方在入队前登记自己的指针,netTask 完成后写进调用方内存 + 通知值回码),
|
||||
* 与 TCP 挂起 recv 把数据直接写进调用方 buf 是同一个模型。
|
||||
* 详见 docs/网络/BSD_Socket_API_使用指南.md §6 */
|
||||
@@ -366,7 +366,7 @@ int net_recv_to(int sockfd, void *buf, int len, uint32_t timeout_ms);
|
||||
* netTask 内直接执行不入队——自投递给自身 = 死锁)
|
||||
* 函数说明:1. 目的地址是**入参**,按值拷进 net_msg_t.addr 随消息进 netTask,
|
||||
* 与 net_connect 传地址同一条通道;结果(已发字节数/错误码)
|
||||
* 搭任务通知值回来(AGENTS「勿给 net_msg_t 加回传字段」)。
|
||||
* 搭任务通知值回来(勿给 net_msg_t 加回传字段)。
|
||||
* 2. 带显式目的地址 = 芯片 DesIP/DesPort 切到该对端 → 本 Socket 记账进入
|
||||
* **UDP 客户端形态**(p_sock->udp_mode = NET_UDP_MODE_CLIENT):此后
|
||||
* `dest_addr = NULL` 的发送就发往它。**收包帧格式不受影响**——信息头是
|
||||
@@ -506,7 +506,8 @@ int net_close(int sockfd);
|
||||
* 见函数说明 2;含幂等:无活动会话),-1 失败
|
||||
* 限定条件:非 netTask 上下文(经消息队列委托,同其它 net_* API)
|
||||
* 函数说明:1. 适用场景=应用层放弃会话(对时 30s 预算耗尽、协议超时等):
|
||||
* 单连接模型禁止对监听 fd net_close(连监听一起毁,AGENTS 约定),
|
||||
* 单连接模型禁止对监听 fd net_close(连监听一起毁 →
|
||||
* docs/网络/网络自愈架构设计.md §4.10),
|
||||
* 而挂起但 TCP 仍活的客户端会永久占住单连接监听(PC 内核自动
|
||||
* ACK keepalive,芯片僵尸判不死——《网络自愈架构设计》§5.2 E13 定案缺口)
|
||||
* 2. 实现(2026-10-25 探针窗口心跳缺口修复起):auto_relisten fd = 登记 QUARANTINE 隔离
|
||||
|
||||
Reference in New Issue
Block a user