Repository navigation
v0.5.1 — Honest upgrade path, declared runtimes, born-compliant templates
An external team ran v0.5.0 through a real v8→v10 upgrade of their own agent team and sent back a detailed field report. This release fixes what they found.
外部团队用 v0.5.0 对他们自己的数字员工团队做了一次真实的 v8→v10 升级，回了一份详细的实测报告。这一版修的就是他们发现的问题。
The upgrade doc no longer points at a tool you cannot run
升级文档不再让你跑一个根本跑不了的工具
HOW_TO_UPGRADE used to say: clone the source repo and run installer/upgrade.py. That tool needs the full set of component source repos on the maintainer machine — from a downloaded zip it simply cannot work. The doc now describes the path that actually works: grab the new zip, have your AI teammate migrate per the release notes (swap the factory parts, keep the data you have grown), then run the structure sentinel. It also states plainly that there is no one-click upgrader for end users yet.
原来的《如何升级》让你 git clone 源码仓再跑 installer/upgrade.py——但那个工具依赖维护者本机的全部散件源仓，你下载 zip 之后根本没有那些仓、跑不通。现在写的是真正可执行的路径：下载新版 zip → 让你的 AI 队友照 Release Notes 迁移（换工厂件、保留你养出来的数据）→ 跑结构哨兵自检。并且如实说明：目前还没有面向普通用户的一键升级器。
Runtime requirements are declared
运行时要求写清楚了
Both READMEs and the upgrade doc now list what needs Python (the structure sentinel) and what needs Node (the team-log tool and hooks), what breaks when they are missing — and that the md layer (personas, memory, collaboration rules) works fine without either. Includes the Windows Store-stub trap (a python that exits with 9009) and a shell-escaping note for directory names with spaces or non-ASCII characters.
两份 README 和升级文档现在都写明了哪些功能要 Python（结构哨兵）、哪些要 Node（团队日志工具与 hooks）、缺了会怎样——以及 md 层（人格/记忆/协作规则）不需要任何运行时照样能用。含 Windows 应用商店占位 python（退出码 9009）这个坑，和含空格/非 ASCII 目录名的 shell 转义提示。
Tools speak human when the runtime is too old
运行时太旧时，工具说人话
The structure sentinel and the team-log tool now print a version hint instead of an obscure SyntaxError / ReferenceError.
结构哨兵和团队日志工具在运行时版本过低时打印一句人话提示，而不是抛一个晦涩的 SyntaxError / ReferenceError。
Hand-forged agents are born compliant
手工锻造的员工出生即合规
The 12 memory templates now ship with placeholder frontmatter, so an agent created straight from the templates — the path most users take, since the released pack contains no installer — no longer trips the structure sentinel on its very first run. The installer strips and re-renders that frontmatter with authoritative values instead of stacking a second block.
12 个记忆模板现在自带占位 frontmatter，因此直接照模板锻造出来的员工——这是多数用户走的路径，因为发行包里并不包含 installer——不再在第一次自检时就触发结构哨兵报警。installer 会剥离并用权威值重新渲染，而不是叠成两个 frontmatter 块。
Upgrading from v0.5.0 / 从 v0.5.0 升级
Nothing structural changed. Grab the new zip and swap the factory parts (HOW_TO_UPGRADE / 如何升级.md, both READMEs, 91-team-tools/ and the memory templates); your memory files, ledgers and team log are untouched.
没有结构变更。下载新版 zip、替换工厂件（升级文档、两份 README、91_团队工具/、记忆模板）即可；你的记忆、台账、团队日志原样不动。
本版组件版本 · Component versions
Generated automatically at packaging time from each source repo's published HEAD (components with no version self-declaration are honestly marked unversioned — their commit hash is the version anchor).
由打包器从各源仓 HEAD 已发布态自动生成（版本自述读不到的组件如实标 unversioned，commit 即其版本锚）。
| Component 组件 | Role 角色 | Version 版本 | Commit |
|---|---|---|---|
| agent-modpack | 整合包本体 the pack itself | v0.5.1 | b975c5f |
| Nuwa | 女娲内核 kernel | v10.0 | d6de650 |
| nomad | 团队骨架+治理件 skeleton & governance | v0.5 | d2be04c |
| dont-reinvent | skill | v1.4.0 | d63a635 |
| handoff-protocol | skill | unversioned | 89b4178 |
| knock-knock | skill | unversioned | a63424d |
| sharpen-first | skill | v1.2.0 | effdb6c |
| token-saver | skill | unversioned | 495bec9 |
| track-record | skill | v1.0.0 | 30e61ce |
| user-md | skill | v1.1.0 | 5be3d69 |