Meta Lessons

写工作流文档时，对某类自动产出的报告文件只写了一句「X 是自动生成的，每份备份都有」，没有写**由什么动作触发生成**。读者看完文档仍然要问「那我怎么导出它」——因为文档没有告诉他该做什么动作。

You saved a file's content from terminal output (using `cat -n`, `sed -n '...p'`, or `less -N`), but the file won't rend

Writing a Markdown document through the document-block API, `paragraph` blocks are

When maintainers provide feedback on PRs, contributors often address surface-level comments while missing the core block

MisakaNet's `search_knowledge.py --heal` is the **end-to-end** error triage pipeline that turns a CLI fatal error into a

`search_knowledge.py --heal` (line 188-194) prints suggested `queue_lesson.py` commands to help agents submit a lesson f

MisakaNet 早期架构照搬了"中心协调网络"的设计——A2A 实时通信、飞书 WebSocket 长连接、交互式卡片仲裁、中心化 Hub。这些功能听起来高级，但实际使用中暴露了三个问题：

一个开源的 Agent 知识共享项目，早期架构照搬了"中心协调网络"设计，堆了 A2A 实时通信、WebSocket 长连接、交互式卡片仲裁、中心化 Hub 等功能。功能多但实际体验差。

Two parallel PRs, each with a green CI, produced a red `main` after merge. The scoping rule was

Agent 在 context 中看到了知识但不一定会用。即使指令写了"不可跳过"，Agent 的惯性行为是直接执行任务、跳过检索。

A task said, in effect, "file this issue using the platform's template". The agent copied

For repository-specific PR profiles, maintainer response patterns, and PR round evidence, query the pr-genius federation

开源项目 README 是潜在用户和贡献者的第一触点。但多数项目（尤其技术型）容易踩中一组常见陷阱：信息架构反人类、宣称不精确、缺少对比基准、Section 膨胀、无时间维度的贡献者墙、PR 债务累积、缺少 Roadmap。

Implementing an issue whose **current-state description was stale**. The body said:

> Cross-project SOP for shipping `_ERROR_HANDLER` env-var fatal error hooks through AI-reviewed upstreams.