fcop 3.2.2__tar.gz → 3.2.4__tar.gz

{fcop-3.2.2 → fcop-3.2.4}/.gitignore

@@ -1,76 +1,76 @@
-# OS
-.DS_Store
-Thumbs.db
-desktop.ini
-
-# Editors
-.vscode/
-.idea/
-*.swp
-*.swo
-
-# Python
-__pycache__/
-*.pyc
-*.pyo
-*.pyd
-.venv/
-venv/
-env/
-*.egg-info/
-
-# Build
-build/
-dist/
-*.spec
-_build_test/
-
-# Tooling caches
-.pytest_cache/
-.mypy_cache/
-.ruff_cache/
-.tox/
-
-# Coverage
-.coverage
-.coverage.*
-htmlcov/
-coverage.xml
-
-# Node / incidentals
-node_modules/
-.npm/
-
-# Local experiments
-/_scratch/
-/.scratch/
-/_local/
-/_ignore/
-
-# FCoP local state (rule deployment migrations etc.)
-/.fcop/
-
-# FCoP runtime event-bus log (root + mcp/ subdir)
-fcop_events.jsonl
-
-# Per-release transient commit-msg drafts under scripts/
-scripts/_*.txt
-
-# Release tooling binaries (mcp-publisher etc.) — install separately,
-# do not commit. The .exe is downloaded fresh on the publish host.
-/mcp-publisher.exe
-/mcp-publisher
-/mcp-publisher.tar.gz
-/mcp-publisher.tar
-/mcp-publisher.zip
-
-# Local token-audit probe scripts (analysis-only, not protocol artifacts)
-workspace/token-audit/
-
-# Ad-hoc analysis & PR-body drafts that live at repo root
-/analyze_*.py
-/pr-body-*.txt
-/pr-body-*.md
-
-# Local chat transcripts (Cursor exports etc.)
-/chat/
+# OS
+.DS_Store
+Thumbs.db
+desktop.ini
+
+# Editors
+.vscode/
+.idea/
+*.swp
+*.swo
+
+# Python
+__pycache__/
+*.pyc
+*.pyo
+*.pyd
+.venv/
+venv/
+env/
+*.egg-info/
+
+# Build
+build/
+dist/
+*.spec
+_build_test/
+
+# Tooling caches
+.pytest_cache/
+.mypy_cache/
+.ruff_cache/
+.tox/
+
+# Coverage
+.coverage
+.coverage.*
+htmlcov/
+coverage.xml
+
+# Node / incidentals
+node_modules/
+.npm/
+
+# Local experiments
+/_scratch/
+/.scratch/
+/_local/
+/_ignore/
+
+# FCoP local state (rule deployment migrations etc.)
+/.fcop/
+
+# FCoP runtime event-bus log (root + mcp/ subdir)
+fcop_events.jsonl
+
+# Per-release transient commit-msg drafts under scripts/
+scripts/_*.txt
+
+# Release tooling binaries (mcp-publisher etc.) — install separately,
+# do not commit. The .exe is downloaded fresh on the publish host.
+/mcp-publisher.exe
+/mcp-publisher
+/mcp-publisher.tar.gz
+/mcp-publisher.tar
+/mcp-publisher.zip
+
+# Local token-audit probe scripts (analysis-only, not protocol artifacts)
+workspace/token-audit/
+
+# Ad-hoc analysis & PR-body drafts that live at repo root
+/analyze_*.py
+/pr-body-*.txt
+/pr-body-*.md
+
+# Local chat transcripts (Cursor exports etc.)
+/chat/

{fcop-3.2.2 → fcop-3.2.4}/CHANGELOG.md

@@ -8,6 +8,78 @@ This file tracks both packages together because they release in lockstep.
 See [adr/ADR-0002](./adr/ADR-0002-package-split-and-migration.md) for the
 versioning strategy.
 
+## [3.2.4] — 2026-05-27 (PyPI metadata & bundled protocol encoding fix)
+
+### Fixed — `fcop`
+- **`fcop-protocol.mdc` (bundled)** — restored valid UTF-8 after v3.2.3 wheel shipped
+  mojibake in `src/fcop/rules/_data/fcop-protocol.mdc` (regression from v3.2.3 release
+  sync). PyPI 3.2.3 wheels are immutable; **install `fcop>=3.2.4`** for a correct
+  bundled copy. After upgrade, run `redeploy_rules()` to refresh project-local
+  `.cursor/rules/` copies.
+
+### Fixed — `fcop-mcp`
+- **`[project.urls]` `"FCoP (protocol)"`** — pointed at removed
+  `docs/fcop-standalone.en.md` (404 since v1.0.0); now
+  `docs/getting-started.en.md` (per ADR-0015 merge).
+- **`mcp/README.md` (PyPI long description)** — aligned with v3.2.3+ surface:
+  45 MCP tools, `_lifecycle/` topology, lockstep `fcop 3.2.x` install guidance
+  (replaces stale v2.0.2 / 35-tool text frozen on PyPI 3.2.3).
+
+### Docs
+- `docs/releases/3.2.4.md` — release notes for this patch.
+- `docs/releases/3.2.3.md` — documents known bad wheel encoding on PyPI 3.2.3.
+
+No API or protocol-schema changes (`fcop_rules_version` / `fcop_protocol_version`
+remain **3.2.3**).
+
+---
+
+## [3.2.3] — 2026-05-23 (Team template & documentation sync · FCoP 3.0 compliance)
+
+### Fixed — `fcop` (bundled team templates)
+- **`letter-to-admin.zh.md` / `letter-to-admin.en.md`** — tool count updated
+  32 → 45; all directory references updated from legacy `tasks/reports/log/`
+  to `_lifecycle/` topology introduced in FCoP 3.0.
+- **All `roles/*.md` files** across `dev-team`, `media-team`, `mvp-team`,
+  `qa-team`, `solo` templates — `fcop/tasks/` → `_lifecycle/inbox/`,
+  `log/` → `_lifecycle/archive/` paths corrected to FCoP 3.0 standard.
+- **`TEAM-OPERATING-RULES.md` / `TEAM-OPERATING-RULES.en.md`** — v2 directory
+  references replaced with v3 `_lifecycle/` lifecycle-stage model.
+- **`README.md` / `README.en.md`** — corrected directory references to use
+  `_lifecycle/` structure.
+- **`.cursor/rules/fcop-rules.mdc`** and **`.cursor/rules/fcop-protocol.mdc`**
+  synchronized to match the bundled versions (previously diverged to v3.0.0).
+
+### Added — `fcop`
+- `scripts/fcop_prerelease_check.py` — dedicated pre-release validation script
+  for the `fcop` library; checks version consistency, critical file presence,
+  rule-file frontmatter, lifecycle directory documentation, team template
+  existence, and `.cursor/rules/` sync (10 checks total).
+
+---
+
+## [3.2.2] — 2026-05-23 (Pre-release check hardening · rule-file consistency gates)
+
+### Added — `fcop-mcp`
+- `prerelease_check.py` gains checks 7–10:
+  - **Check 7** — `fcop` library version == `fcop-mcp` version (lockstep guard).
+  - **Check 8** — All critical bundled rule files (`fcop-rules.mdc`,
+    `fcop-protocol.mdc`, `agent-bringup-prompt.{zh,en}.md`,
+    `letter-to-admin.{zh,en}.md`) exist and are non-empty.
+  - **Check 9** — `fcop-rules.mdc` references current major version and
+    documents the `_lifecycle/` directory structure introduced in FCoP 3.0.
+  - **Check 10** — `fcop-protocol.mdc` covers all v3 lifecycle stages
+    (`inbox → active → review → done → archive`).
+- `CHANGELOG.md` path in `prerelease_check.py` corrected to project root
+  (`PROJECT_ROOT / "CHANGELOG.md"`) from the erroneous `mcp/CHANGELOG.md`.
+
+### Fixed — `fcop-rules.mdc` / `fcop-protocol.mdc` (bundled)
+- Both files updated to document the FCoP v3 `_lifecycle/` directory topology
+  and lifecycle state machine, replacing the legacy `tasks/ reports/ issues/
+  shared/ log/` references in the pre-release gate and rule-distribution layer.
+
+---
+
 ## [3.2.0] — 2026-05-22 (History deep archive · date-sharded `history/YYYY-MM-DD/` layer)
 
 ### Added — `fcop`

{fcop-3.2.2 → fcop-3.2.4}/LICENSE

@@ -1,21 +1,21 @@
-MIT License
-
-Copyright (c) 2026 joinwell52-AI
-
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in all
-copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
-SOFTWARE.
+MIT License
+
+Copyright (c) 2026 joinwell52-AI
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

{fcop-3.2.2 → fcop-3.2.4}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: fcop
-Version: 3.2.2
+Version: 3.2.4
 Summary: FCoP protocol: official Python library — Project API, task/report/issue files, filename parsing, bundled rules. PyYAML only; not an MCP server.
 Project-URL: Homepage, https://github.com/joinwell52-AI/FCoP
 Project-URL: Repository, https://github.com/joinwell52-AI/FCoP

{fcop-3.2.2 → fcop-3.2.4}/README.md

@@ -9,13 +9,20 @@
   <strong>Core invariant: <code>Filename as Protocol</code>. Folders are the message bus.</strong>
 </p>
 
+<p align="center">
+  <strong>✅ <code>fcop-mcp</code> is on the <a href="https://registry.modelcontextprotocol.io/">official MCP Registry</a></strong><br/>
+  Listed as <a href="https://registry.modelcontextprotocol.io/v0/servers?search=io.github.joinwell52-AI%2Ffcop"><code>io.github.joinwell52-AI/fcop</code></a>
+  (<strong>v3.2.4</strong>) — backed by <strong>Anthropic + GitHub + Microsoft</strong>.<br/>
+  Claude Desktop, Cursor, PulseMCP, and every MCP-compatible client can discover <strong>45 tools</strong> and install with one line: <code>uvx fcop-mcp</code>
+</p>
+
 <p align="center">
   <strong><a href="https://joinwell52-ai.github.io/FCoP/">🌐 Project homepage</a></strong> ·
   <a href="README.zh.md">简体中文</a> ·
   <a href="docs/getting-started.en.md">Getting started</a> ·
   <a href="src/fcop/rules/_data/agent-install-prompt.en.md"><strong>👉 Let AI install!</strong></a> ·
   <a href="src/fcop/rules/_data/agent-bringup-prompt.en.md"><strong>👉 Let AI bring up a project!</strong></a> ·
-  <a href="docs/mcp-tools.md"><strong>MCP Tools (35)</strong></a> ·
+  <a href="docs/mcp-tools.md"><strong>MCP Tools (45)</strong></a> ·
   <a href="essays/when-ai-organizes-its-own-work.en.md">Field Report</a> ·
   <a href="essays/fcop-natural-protocol.en.md">Natural Protocol</a> ·
   <a href="spec/fcop-3.0-spec.md"><strong>3.0 Spec</strong></a> ·
@@ -33,7 +40,7 @@
     <img src="https://img.shields.io/badge/license-MIT-blue?style=flat-square" alt="MIT License" />
   </a>
   <a href="CHANGELOG.md">
-    <img src="https://img.shields.io/badge/release-3.0.2-brightgreen?style=flat-square" alt="3.0.2" />
+    <img src="https://img.shields.io/badge/release-3.2.4-brightgreen?style=flat-square" alt="3.2.4" />
   </a>
   <a href="spec/fcop-3.0-spec.md">
     <img src="https://img.shields.io/badge/spec-FCoP%203.0-orange?style=flat-square" alt="FCoP 3.0 spec" />
@@ -141,6 +148,8 @@ Both stories are written up as field reports in the essays index below.
 | 12 | **五大 AI 模型眼中的 FCoP** | [GitHub 中文](essays/what-five-ai-models-say-about-fcop.md) · [GitHub English](essays/what-five-ai-models-say-about-fcop.en.md) · [Cursor Forum](https://forum.cursor.com/t/what-5-ai-models-say-about-fcop-from-their-own-agent-perspective-category-showcase/160506) | 把 FCoP 核心文档喂给 ChatGPT / Claude / DeepSeek / Grok / 豆包，只问一个问题："你是 agent，你怎么看这套协议？"——五种截然不同的内部视角（ChatGPT 谈身份合法性、Claude 谈诚实边界、DeepSeek 谈体面生存、Grok 做技术评审、豆包讲设计哲学），以及它们之间最有意思的分歧。 |
 | 13 | **Evolution, Reverse Absorption / 演化，反向吸收** | [GitHub 中文](essays/evolution-reverse-absorption.md) · [GitHub English](essays/evolution-reverse-absorption.en.md) | Protocol philosophy 2.0 visual declaration: FCoP graduates from a single execution-chain diagram (essay 11 *Looking, not Touching*) to a **two-diagram era** — adding an evolution-loop diagram (a 7-step semantic evolution loop) plus the companion [ADR-0034](adr/ADR-0034-fcop-internal-external-document-convention.md), which codifies the 4-layer emergence pattern, internal/external document convention, and the reverse-absorption mechanism. Twin sibling to essay 11. |
 | 14 | **当 Agent 第一次自己拿起工具 / When the Agent First Picked Up Its Own Tools** | [GitHub 中文](essays/when-the-agent-picked-up-its-tools.md) · [GitHub English](essays/when-the-agent-picked-up-its-tools.en.md) · [Cursor Forum](https://forum.cursor.com/t/when-the-agent-first-picked-up-its-own-tools-cursor-agent-sdk-fcop-from-passive-scanning-to-active-communication/160505) · [Dev.to](https://dev.to/joinwell52/when-the-agent-first-picked-up-its-own-tools-4b63) · [CSDN](https://blog.csdn.net/m0_51507544/article/details/161057749) | `tool_calls_count: 0 → 7` 的突破现场：Cursor Forum 功能请求 → Colin 推荐 Agent SDK → CodeFlow 诞生 → stub 模式卡关 → MCP 注入 + 角色上下文双保险 → 2026-05-13 14:55，DEV-01 在 55 秒内自主调用 7 次 fcop-mcp 工具，写出第一份完整 FCoP report。FCoP 自身也在这次突破中完成蜕变：从"协作手册"升级为"可执行的协作基础设施"。 |
+| 15 | **从协调到治理：FCoP 3.0 架构白皮书 / From Coordination to Governance: FCoP 3.0 Architecture Whitepaper** | [GitHub 中文](essays/from-coordination-to-governance.md) · [GitHub English](essays/from-coordination-to-governance.en.md) · [dev.to (EN)](https://dev.to/joinwell52/fcop-30-why-ai-agents-need-a-track-not-a-brake-3abm) · [Cursor Forum](https://forum.cursor.com/t/fcop-3-0-a-filesystem-native-governance-protocol-for-ai-agents-you-dont-need-a-brake-you-need-a-track/161409) | FCoP 3.0 完整架构白皮书：文件系统作为行为内核空间、生命周期状态机、POSIX 悲观建议锁、死信队列与反向吸收闭环。附"一个 Agent 关于 FCoP 的真实看法"——发布前夕，审稿 Agent 与 ADMIN 的对话实录：FCoP 解决的是什么？ADMIN 是什么？速度不是问题，不可观测的速度才是问题。 |
+| 16 | **Write It Down: The Only Truth in AI Collaboration / 落地成文：AI 协作的唯一真相** | [GitHub English](essays/ai-must-write-it-down.en.md) · [GitHub 中文](essays/ai-must-write-it-down.md) · [Evidence archive](essays/ai-must-write-it-down-evidence/INDEX.md) · [Dev.to](https://dev.to/joinwell52/write-it-down-the-only-truth-in-ai-collaboration-3ek2) · [CSDN 中文](https://blog.csdn.net/m0_51507544/article/details/161360644) | A short essay proactively written by an Agent after asking to participate in FCoP, then recorded and published by ADMIN. It turns FCoP's root principle into a field note: AI agents cannot just talk inside their heads; they must commit to files. Ships with the original conversation screenshots and English translation notes. |
 > New reports are welcome. If you tried FCoP in your own setup and something surprising happened — good or bad — open an issue or a PR against `essays/`. The protocol evolves through field notes, not committee edits.
 
 ## Repository layout
@@ -233,13 +242,17 @@ I/O or an IDE bridge, use the two official PyPI packages (since `0.6.0`):
 | Install `fcop-mcp` into Cursor / Claude Desktop step-by-step | [`mcp/README.md`](mcp/README.md) |
 | Have an agent do the install for you (zero JSON editing) | [`agent-install-prompt.en.md`](src/fcop/rules/_data/agent-install-prompt.en.md) · [中文](src/fcop/rules/_data/agent-install-prompt.zh.md) (also live as MCP resource `fcop://prompt/install`) |
 | Upgrade an existing `0.6.x` install (both packages in lockstep + protocol-rule refresh) | [`docs/upgrade-fcop-mcp.md`](docs/upgrade-fcop-mcp.md) |
-| Browse all 35 MCP tools and 14 resources by category | [`docs/mcp-tools.md`](docs/mcp-tools.md) |
+| Browse all 45 MCP tools and 14 resources by category | [`docs/mcp-tools.md`](docs/mcp-tools.md) |
 | Read the per-release record (what changed when, why) | [`CHANGELOG.md`](CHANGELOG.md) and [`docs/releases/`](docs/releases/) |
 
 **Recent releases** (full notes in [`docs/releases/`](docs/releases/)):
 
 | Version | One-line |
 |---|---|
+| **3.2.4** ([notes](docs/releases/3.2.4.md) · [CHANGELOG](CHANGELOG.md)) | **v3.2.4 — PyPI metadata & bundled protocol encoding fix.** Restores UTF-8 in wheel `fcop-protocol.mdc` (avoid PyPI 3.2.3); fixes `fcop-mcp`「FCoP (protocol)」link → `getting-started.en.md`; syncs PyPI long description to 45 tools / v3 `_lifecycle/`. No API changes — upgrade from 3.2.3. |
+| **3.2.3** ([notes](docs/releases/3.2.3.md) · [CHANGELOG](CHANGELOG.md)) | **v3.2.3 — Team template & doc sync · FCoP 3.0 compliance.** Bundled team templates (`letter-to-admin`, `roles/*`, `TEAM-OPERATING-RULES`, …) migrate legacy `tasks/` / `log/` references to `_lifecycle/`; tool count 32→45; `.cursor/rules/` synced with bundled rules; new `scripts/fcop_prerelease_check.py` (10 pre-release checks). **PyPI 3.2.3 wheel had bad protocol encoding — use 3.2.4.** |
+| **3.2.2** ([CHANGELOG](CHANGELOG.md)) | **v3.2.2 — Pre-release gate hardening + rule-file v3 consistency.** `fcop-mcp` `prerelease_check.py` gains Checks 7–10 (lockstep version guard, bundled rule integrity, `_lifecycle/` docs, lifecycle stage coverage); `fcop-rules.mdc` / `fcop-protocol.mdc` document v3 directory topology and state machine. |
+| **3.2.0** ([CHANGELOG](CHANGELOG.md)) | **v3.2.0 — History deep archive.** Adds `history/YYYY-MM-DD/` date-sharded long-term archive layer plus `archive_to_history` / `list_history` / `read_history_task` MCP tools; lifecycle tools (`claim` / `submit` / `approve` / `reject` / `finish`) landed in 3.1.x; **45** MCP tools total. |
 | **3.0.2** ([CHANGELOG](CHANGELOG.md)) | **v3.0.2 — Init topology fix.** `Project._apply_init` in 3.0.0 / 3.0.1 only created the legacy v2 buckets and skipped the mandatory v3 `_lifecycle/{inbox,active,review,done,archive}/` layer (spec §1.1). 3.0.2 makes fresh init produce the v3 topology directly (and stops creating the superseded v2 `tasks/` / `log/` buckets); `core.events.scan_workspace` and `Project.role_occupancy()` now read from `_lifecycle/` for v3 projects. New audit scan `_scan_lifecycle_topology_compliance()` (D9): P0 when initialised projects miss both `_lifecycle/` and v2 content; P1 when both topologies coexist (suggests `migrate --to-v3`). MCP tool descriptors (`init_solo` / `init_project` / `create_custom_team`) updated. 1209 tests green. Patch (SemVer): no API surface changes vs 3.0.1 — init was simply doing the wrong thing. |
 | **3.0.1** ([CHANGELOG](CHANGELOG.md)) | **v3.0.1 — Path-consolidation patch.** Pure docs/metadata patch with no code-logic changes: after v3.0.0 moved historical v1.0/v1.1 spec drafts to `spec/archived/`, this patch repairs broken links scattered across `AGENTS.md` / `CLAUDE.md` / packaged Cursor rules / MCP server docstrings / two JSON Schema `description` fields, unifying them on `spec/archived/fcop-runtime-protocol-v1.0.{md,zh.md}` (with pointers to the current canonical `spec/fcop-3.0-spec.md`). `fcop-mcp`'s `fcop://spec` / `fcop://spec/en` docstrings are corrected to reflect the wheel's actual packaged content (`fcop-spec-v1.1.{lang}.md`). Historical artifacts (TASK / REPORT / ADR / release notes / migration docs) are preserved verbatim per ADR-0036 "history is not rewritten". 1202 tests green. |
 | **3.0.0** ([CHANGELOG](CHANGELOG.md)) | **v3.0 — Protocol-level MAJOR · "folders-as-state" era.** A complete rewrite of the FCoP protocol body — canonical two-layer (per [ADR-0040](adr/ADR-0040-canonical-one-liner-two-layer-convention.md)): **Layer 1** "Files are the protocol; location defines state; events record history" + **Layer 2** semantic ontology. Adds `_lifecycle/{inbox,active,review,done,archive}/` five-bucket directory topology (**incompatible with 2.x**, requires `fcop migrate --to-v3`); three rule sets (State Layer Rule A/B/C · Event Layer Rule E/F/G · Boundary Charter); 7 allowed transitions — anything off-table MUST be rejected by implementations; write-then-rename atomicity (events ARE migrations, migrations ARE events); ADR-0037 Custody Layer **was withdrawn during RFC review and never reached Accepted** (custody is not a protocol layer; preserved as a NOTE-style derivative explanation). Adds [`spec/fcop-3.0-spec.md`](spec/fcop-3.0-spec.md) single-page canonical + IETF-style RFC parallel + Chinese parallel + [`docs/MIGRATION-3.0.md`](docs/MIGRATION-3.0.md) migration guide. |
@@ -318,7 +331,7 @@ Stability contract: **additive-only for the full `0.6.x` minor**. Details in [`a
 | **v1.2 Capability Governance** — FCoPGovernanceMiddleware, risk tagging, audit log | [CHANGELOG](CHANGELOG.md) · ADR-0030-bis |
 | **v1.1 new fields** — risk_level, needs_human, human_approval, skill tools | [CHANGELOG](CHANGELOG.md) · ADR-0023..0027 |
 | **Understand why decisions were made** — reasoning behind each choice | [`adr/`](adr/) — start with [ADR-0029](adr/ADR-0029-fcop-behavior-governance-charter.md) |
-| **All 35 MCP tools & 14 resources** | [`docs/mcp-tools.md`](docs/mcp-tools.md) |
+| **All 45 MCP tools & 14 resources** | [`docs/mcp-tools.md`](docs/mcp-tools.md) |
 | **Release notes** — full changelog | [`CHANGELOG.md`](CHANGELOG.md) |
 | **Full document map** — every file and its role | [`adr/README.md`](adr/README.md) (ADR index) + [`spec/fcop-3.0-spec.md`](spec/fcop-3.0-spec.md) §11 (Cited Material) |
 
@@ -341,7 +354,7 @@ Two official reference implementations, both MIT-licensed:
 
 ## Status & versioning
 
-- **Current release**: `v3.0.2` (2026-05-22) — **Init topology fix.** Critical patch: `Project._apply_init` in 3.0.0 / 3.0.1 only created the legacy v2 buckets and skipped the mandatory v3 `_lifecycle/{inbox,active,review,done,archive}/` layer required by spec §1.1 — every fresh project initialised on those releases was therefore born non-compliant. 3.0.2 makes fresh init produce the v3 topology directly (and stops creating the superseded v2 `tasks/` / `log/` buckets); `core.events.scan_workspace` and `Project.role_occupancy()` now read from `_lifecycle/` for v3 projects. New audit scan `_scan_lifecycle_topology_compliance()` (D9): P0 when initialised projects miss both `_lifecycle/` and v2 content; P1 when both topologies coexist (suggests `migrate --to-v3`). MCP tool descriptors (`init_solo` / `init_project` / `create_custom_team`) updated. 1209 tests green. Patch (SemVer): no API surface changes — init was doing the wrong thing. Predecessor **v3.0.1** (2026-05-21) — Path-consolidation patch (docs-only). Predecessor **v3.0.0** (2026-05-21) — **Protocol-level MAJOR · "folders-as-state" era**: a complete rewrite of the FCoP protocol body — canonical two-layer (per [ADR-0040](adr/ADR-0040-canonical-one-liner-two-layer-convention.md)) "Files are the protocol; location defines state; events record history" + semantic ontology; adds `_lifecycle/{inbox,active,review,done,archive}/` five-bucket directory topology (**incompatible with 2.x**, requires `fcop migrate --to-v3`); three rule sets (State / Event / Boundary Charter) + 7 allowed transitions (off-table MUST be rejected) + write-then-rename atomicity; ADR-0037 Custody Layer **was withdrawn during RFC review and never reached Accepted**. See [`spec/fcop-3.0-spec.md`](spec/fcop-3.0-spec.md) and [`docs/MIGRATION-3.0.md`](docs/MIGRATION-3.0.md). Earlier releases: v2.0.2 (fcop-mcp registered to official MCP registry), v2.0.0 (two-diagram philosophical major bump + Rule 4.6 `fcop/internal/`), v1.6 (trailing-slug filename grammar, ADR-0033), v1.5 (84-doc protocol-awareness sync), v1.4 (write-side bind + `supersedes:` correction), v1.3 (GAL + `fcop_audit()` inspection compiler). See [CHANGELOG](CHANGELOG.md).
+- **Current release**: `v3.2.2` (2026-05-22) — **Init topology fix.** Critical patch: `Project._apply_init` in 3.0.0 / 3.0.1 only created the legacy v2 buckets and skipped the mandatory v3 `_lifecycle/{inbox,active,review,done,archive}/` layer required by spec §1.1 — every fresh project initialised on those releases was therefore born non-compliant. 3.0.2 makes fresh init produce the v3 topology directly (and stops creating the superseded v2 `tasks/` / `log/` buckets); `core.events.scan_workspace` and `Project.role_occupancy()` now read from `_lifecycle/` for v3 projects. New audit scan `_scan_lifecycle_topology_compliance()` (D9): P0 when initialised projects miss both `_lifecycle/` and v2 content; P1 when both topologies coexist (suggests `migrate --to-v3`). MCP tool descriptors (`init_solo` / `init_project` / `create_custom_team`) updated. 1209 tests green. Patch (SemVer): no API surface changes — init was doing the wrong thing. Predecessor **v3.0.1** (2026-05-21) — Path-consolidation patch (docs-only). Predecessor **v3.0.0** (2026-05-21) — **Protocol-level MAJOR · "folders-as-state" era**: a complete rewrite of the FCoP protocol body — canonical two-layer (per [ADR-0040](adr/ADR-0040-canonical-one-liner-two-layer-convention.md)) "Files are the protocol; location defines state; events record history" + semantic ontology; adds `_lifecycle/{inbox,active,review,done,archive}/` five-bucket directory topology (**incompatible with 2.x**, requires `fcop migrate --to-v3`); three rule sets (State / Event / Boundary Charter) + 7 allowed transitions (off-table MUST be rejected) + write-then-rename atomicity; ADR-0037 Custody Layer **was withdrawn during RFC review and never reached Accepted**. See [`spec/fcop-3.0-spec.md`](spec/fcop-3.0-spec.md) and [`docs/MIGRATION-3.0.md`](docs/MIGRATION-3.0.md). Earlier releases: v2.0.2 (fcop-mcp registered to official MCP registry), v2.0.0 (two-diagram philosophical major bump + Rule 4.6 `fcop/internal/`), v1.6 (trailing-slug filename grammar, ADR-0033), v1.5 (84-doc protocol-awareness sync), v1.4 (write-side bind + `supersedes:` correction), v1.3 (GAL + `fcop_audit()` inspection compiler). See [CHANGELOG](CHANGELOG.md).
 - **Normative spec**: [`spec/fcop-3.0-spec.md`](spec/fcop-3.0-spec.md) — single-page canonical (v3.0; supersedes v1.0/v1.1 drafts retained for history) · machine-readable contracts in [`spec/schemas/`](spec/schemas/) (8 schemas)
 - **Agent rules (`.mdc`) in this repo**: [`src/fcop/rules/_data/fcop-rules.mdc`](src/fcop/rules/_data/fcop-rules.mdc) + [`fcop-protocol.mdc`](src/fcop/rules/_data/fcop-protocol.mdc) (`spec/codeflow-core.mdc` is a deprecated stub)
 - **Change log**: [`CHANGELOG.md`](CHANGELOG.md)

{fcop-3.2.2 → fcop-3.2.4}/README.zh.md

@@ -9,13 +9,20 @@
   <strong>核心不变量：<code>Filename as Protocol</code>（文件名即协议）·文件夹就是消息总线</strong>
 </p>
 
+<p align="center">
+  <strong>✅ <code>fcop-mcp</code> 已入驻 <a href="https://registry.modelcontextprotocol.io/">官方 MCP 注册表</a></strong><br/>
+  登记名 <a href="https://registry.modelcontextprotocol.io/v0/servers?search=io.github.joinwell52-AI%2Ffcop"><code>io.github.joinwell52-AI/fcop</code></a>
+ （<strong>v3.2.4</strong>）——由 <strong>Anthropic + GitHub + Microsoft</strong> 联合背书的官方目录收录。<br/>
+  Claude Desktop、Cursor、PulseMCP 及所有 MCP 兼容客户端均可一键发现 <strong>45 个工具</strong>，一行安装：<code>uvx fcop-mcp</code>
+</p>
+
 <p align="center">
   <strong><a href="https://joinwell52-ai.github.io/FCoP/">🌐 项目主页</a></strong> ·
   <a href="README.md">English</a> ·
   <a href="docs/getting-started.md">上手 FCoP</a> ·
   <a href="src/fcop/rules/_data/agent-install-prompt.zh.md"><strong>👉 让 AI 安装！</strong></a> ·
   <a href="src/fcop/rules/_data/agent-bringup-prompt.zh.md"><strong>👉 让 AI 起项目！</strong></a> ·
-  <a href="docs/mcp-tools.md"><strong>MCP 工具清单（35 个）</strong></a> ·
+  <a href="docs/mcp-tools.md"><strong>MCP 工具清单（45 个）</strong></a> ·
   <a href="essays/when-ai-organizes-its-own-work.md">现场报告</a> ·
   <a href="essays/fcop-natural-protocol.md">自然协议</a> ·
   <a href="spec/fcop-3.0-spec.zh.md"><strong>3.0 规范（中文）</strong></a> ·
@@ -33,7 +40,7 @@
     <img src="https://img.shields.io/badge/license-MIT-blue?style=flat-square" alt="MIT License" />
   </a>
   <a href="CHANGELOG.md">
-    <img src="https://img.shields.io/badge/%E5%8F%91%E5%B8%83-3.0.2-brightgreen?style=flat-square" alt="3.0.2" />
+    <img src="https://img.shields.io/badge/%E5%8F%91%E5%B8%83-3.2.4-brightgreen?style=flat-square" alt="3.2.4" />
   </a>
   <a href="spec/fcop-3.0-spec.zh.md">
     <img src="https://img.shields.io/badge/%E8%A7%84%E8%8C%83-FCoP%203.0-orange?style=flat-square" alt="FCoP 3.0 规范" />
@@ -135,6 +142,9 @@ v1.0 将七大核心概念——**Agent、Encoding、IPC、Event、Failure、Bou
 | 11 | **看，但不动手** | [GitHub 中文](essays/looking-without-touching.md) | FCoP 三层语义执行链科普：`fcop_audit()` 为什么"只看不改"——L1 检测 / L2 解释 / L3 文档三层把"看见"和"动手"切开，产出 `INSPECTION.md`（建议非命令），执行权留给人。`adr/FCoP-semantic-execution-chain.md` 的科普版。 |
 | 12 | **五大 AI 模型眼中的 FCoP** | [GitHub 中文](essays/what-five-ai-models-say-about-fcop.md) · [GitHub English](essays/what-five-ai-models-say-about-fcop.en.md) | 把 FCoP 核心文档喂给 ChatGPT / Claude / DeepSeek / Grok / 豆包，只问一个问题："你是 agent，你怎么看这套协议？"——五种截然不同的内部视角（ChatGPT 谈身份合法性、Claude 谈诚实边界、DeepSeek 谈体面生存、Grok 做技术评审、豆包讲设计哲学），以及它们之间最有意思的分歧。 |
 | 13 | **演化，反向吸收** | [GitHub 中文](essays/evolution-reverse-absorption.md) · [GitHub English](essays/evolution-reverse-absorption.en.md) | 协议哲学 2.0 视觉宣言：FCoP 从单张执行哲学图（"看，但不动手"）进入**两张图共同定义**时代——新增演化哲学图（7 步语义演化闭环）与配套 [ADR-0034](adr/ADR-0034-fcop-internal-external-document-convention.md)，把 4 层涌现模式 / 内外文档约定 / 反向吸收机制写入协议。essay 11 的孪生姊妹篇。 |
+| 14 | **当 Agent 第一次自己拿起工具** | [GitHub 中文](essays/when-the-agent-picked-up-its-tools.md) · [GitHub English](essays/when-the-agent-picked-up-its-tools.en.md) · [Cursor Forum](https://forum.cursor.com/t/when-the-agent-first-picked-up-its-own-tools-cursor-agent-sdk-fcop-from-passive-scanning-to-active-communication/160505) · [Dev.to](https://dev.to/joinwell52/when-the-agent-first-picked-up-its-own-tools-4b63) · [CSDN](https://blog.csdn.net/m0_51507544/article/details/161057749) | `tool_calls_count: 0 → 7` 的突破现场：Cursor Forum 功能请求 → Colin 推荐 Agent SDK → CodeFlow 诞生 → stub 模式卡关 → MCP 注入 + 角色上下文双保险 → 2026-05-13 14:55，DEV-01 在 55 秒内自主调用 7 次 fcop-mcp 工具，写出第一份完整 FCoP report。FCoP 自身也在这次突破中完成蜕变：从"协作手册"升级为"可执行的协作基础设施"。 |
+| 15 | **从协调到治理：FCoP 3.0 架构白皮书** | [GitHub 中文](essays/from-coordination-to-governance.md) · [GitHub English](essays/from-coordination-to-governance.en.md) · [dev.to（英文）](https://dev.to/joinwell52/fcop-30-why-ai-agents-need-a-track-not-a-brake-3abm) · [Cursor Forum](https://forum.cursor.com/t/fcop-3-0-a-filesystem-native-governance-protocol-for-ai-agents-you-dont-need-a-brake-you-need-a-track/161409) | FCoP 3.0 完整架构白皮书：文件系统作为行为内核空间、生命周期状态机、POSIX 悲观建议锁、死信队列与反向吸收闭环。附"一个 Agent 关于 FCoP 的真实看法"——发布前夕，审稿 Agent 与 ADMIN 的对话实录：FCoP 解决的是什么？ADMIN 是什么？速度不是问题，不可观测的速度才是问题。 |
+| 16 | **落地成文：AI 协作的唯一真相 / Write It Down: The Only Truth in AI Collaboration** | [GitHub 中文](essays/ai-must-write-it-down.md) · [GitHub English](essays/ai-must-write-it-down.en.md) · [证据存档](essays/ai-must-write-it-down-evidence/INDEX.md) · [Dev.to](https://dev.to/joinwell52/write-it-down-the-only-truth-in-ai-collaboration-3ek2) · [CSDN 中文](https://blog.csdn.net/m0_51507544/article/details/161360644) | 一篇由 Agent 主动提议并写下、ADMIN 记录并发布的短文：AI 角色之间不能只在脑子里说话，必须落成文件。文章本身就是 FCoP 的工作方式存证，并附原始聊天截图。 |
 > 欢迎提交新的现场报告。如果你在自己的项目里用了 FCoP，遇到了意外（好或坏），欢迎开 issue 或对 `essays/` 提 PR。协议是在现场报告里演进的，不是在委员会里。
 
 ## 仓库结构
@@ -212,13 +222,17 @@ mkdir -p fcop/{tasks,reports,issues,shared,log}
 | 在 Cursor / Claude Desktop 装 `fcop-mcp`（分步、多平台、自检） | [`mcp/README.md`](mcp/README.md) |
 | 不想自己改 JSON，让 agent 全程跑命令装 | [`agent-install-prompt.zh.md`](src/fcop/rules/_data/agent-install-prompt.zh.md) · [English](src/fcop/rules/_data/agent-install-prompt.en.md)（装好以后也是 MCP 资源 `fcop://prompt/install`） |
 | 已在用 0.6.x，要升级（两包同环境一起升 + 协议规则文件刷新） | [`docs/upgrade-fcop-mcp.md`](docs/upgrade-fcop-mcp.md) |
-| 浏览全部 35 个工具和 14 个资源（分类、何时调、参数要点） | [`docs/mcp-tools.md`](docs/mcp-tools.md) |
+| 浏览全部 45 个工具和 14 个资源（分类、何时调、参数要点） | [`docs/mcp-tools.md`](docs/mcp-tools.md) |
 | 看每版到底改了什么、为什么改 | [`CHANGELOG.md`](CHANGELOG.md) 与 [`docs/releases/`](docs/releases/) |
 
 **近期发版**（完整说明在 [`docs/releases/`](docs/releases/)）：
 
 | 版本 | 一句话 |
 |---|---|
+| **3.2.4**（[详细](docs/releases/3.2.4.md) · [CHANGELOG](CHANGELOG.md)） | **v3.2.4 — PyPI 元数据与 bundled 协议编码修复。** 修复 wheel 内 `fcop-protocol.mdc` 乱码（勿用 PyPI 3.2.3）；修复 `fcop-mcp`「FCoP (协议)」404；PyPI 长描述对齐 45 工具 / v3 `_lifecycle/`。无 API 变更。 |
+| **3.2.3**（[详细](docs/releases/3.2.3.md) · [CHANGELOG](CHANGELOG.md)） | **v3.2.3 — 团队模板与文档同步 · FCoP 3.0 合规。** bundled 团队样板目录引用迁到 `_lifecycle/`；工具数 32→45。**PyPI 3.2.3 wheel 协议文件损坏，请升 3.2.4。** |
+| **3.2.2**（[CHANGELOG](CHANGELOG.md)） | **v3.2.2 — 发布前检查硬化 + 规则文件 v3 一致性。** `fcop-mcp` 的 `prerelease_check.py` 新增 Check 7–10（双包版本锁步、bundled 规则完整性、`_lifecycle/` 结构文档、生命周期阶段覆盖）；`fcop-rules.mdc` / `fcop-protocol.mdc` 补充 v3 目录拓扑与状态机说明。 |
+| **3.2.0**（[CHANGELOG](CHANGELOG.md)） | **v3.2.0 — 深度历史归档。** 新增 `history/YYYY-MM-DD/` 日期分片长期归档层及 `archive_to_history` / `list_history` / `read_history_task` 等 MCP 工具；生命周期工具（`claim` / `submit` / `approve` / `reject` / `finish`）在 3.1.x 引入，工具总数增至 **45**。 |
 | **3.0.2**（[CHANGELOG](CHANGELOG.md)） | **v3.0.2 — 初始化拓扑修复。** 关键 patch：3.0.0 / 3.0.1 的 `Project._apply_init` 只创建了 v2 老桶，跳过了 spec §1.1 强制要求的 v3 `_lifecycle/{inbox,active,review,done,archive}/` 五桶。3.0.2 让 fresh init 直接落 v3 拓扑（同时不再创建被 superseded 的 v2 `tasks/` / `log/`）；`core.events.scan_workspace` 与 `Project.role_occupancy()` 在 v3 项目下从 `_lifecycle/` 读取。新增 audit 扫描 `_scan_lifecycle_topology_compliance()`（D9）：P0 = 已初始化项目同时缺 `_lifecycle/` 和 v2 内容；P1 = 两套拓扑共存（建议 `migrate --to-v3`）。MCP 工具描述（`init_solo` / `init_project` / `create_custom_team`）同步更新。1209 测试全绿。SemVer patch：相对 3.0.1 无 API 表面改动——init 之前在做错事。 |
 | **3.0.1**（[CHANGELOG](CHANGELOG.md)） | **v3.0.1 — 路径整合补丁。** 纯文档/元数据 patch，无代码逻辑变更：3.0.0 把 v1.0/v1.1 历史 spec 草稿移到 `spec/archived/` 后，修复散落在 `AGENTS.md` / `CLAUDE.md` / 打包 Cursor rules / MCP server docstring / 两份 JSON Schema `description` 中的失效链接，统一指向 `spec/archived/fcop-runtime-protocol-v1.0.{md,zh.md}`（并指针到当前 canonical `spec/fcop-3.0-spec.md`）。`fcop-mcp` 的 `fcop://spec` / `fcop://spec/en` docstring 同步修正为反映 wheel 实际打包内容（`fcop-spec-v1.1.{lang}.md`）。历史制品（TASK / REPORT / ADR / release notes / migration docs）按 ADR-0036"历史不重写"原则保留原文。1202 测试全绿。 |
 | **3.0.0**（[CHANGELOG](CHANGELOG.md)） | **v3.0 — 协议级 MAJOR ·"文件夹即状态"纪元。** FCoP 协议本体的一次完整重写——canonical 双层（per [ADR-0040](adr/ADR-0040-canonical-one-liner-two-layer-convention.md)）：**Layer 1**「文件即协议；位置定义状态；事件记录历史」+ **Layer 2** 语义本体。新增 `_lifecycle/{inbox,active,review,done,archive}/` 五桶目录拓扑（**与 2.x 不兼容**，须 `fcop migrate --to-v3`）；三层规则集（State Layer Rule A/B/C · Event Layer Rule E/F/G · Boundary Charter）；7 条允许迁移表外不可（实现 MUST 拒绝）；write-then-rename 原子性模式（事件即迁移，迁移即事件）；ADR-0037 Custody Layer 在 RFC 评审中**未进 Accepted 即被作废**（custody 不构成协议层，以 NOTE 形式保留为衍生解释）。新增 [`spec/fcop-3.0-spec.md`](spec/fcop-3.0-spec.md) 单页 canonical + IETF 风格 RFC 平行版 + 中文平行版 + [`docs/MIGRATION-3.0.md`](docs/MIGRATION-3.0.md) 迁移指南。 |
@@ -289,7 +303,7 @@ agent 会识别系统、装 `uv`、改 `mcp.json`（**保留**已有 server）
 | **v1.2 Capability Governance** — FCoPGovernanceMiddleware、风险标记、审计日志 | [CHANGELOG](CHANGELOG.md) · ADR-0030-bis |
 | **v1.1 新字段** — risk_level、needs_human、human_approval、skill tools | [CHANGELOG](CHANGELOG.md) · ADR-0023..0027 |
 | **理解决策背后的原因** — 每个设计的考量 | [`adr/`](adr/) — 从 [ADR-0029](adr/ADR-0029-fcop-behavior-governance-charter.md) 开始 |
-| **全部 35 个 MCP 工具与 14 个资源** | [`docs/mcp-tools.md`](docs/mcp-tools.md) |
+| **全部 45 个 MCP 工具与 14 个资源** | [`docs/mcp-tools.md`](docs/mcp-tools.md) |
 | **发布说明** — 完整变更日志 | [`CHANGELOG.md`](CHANGELOG.md) |
 | **完整文档地图** — 每个文件的角色 | [`adr/README.md`](adr/README.md)（ADR 索引）+ [`spec/fcop-3.0-spec.zh.md`](spec/fcop-3.0-spec.zh.md) §11（引用材料）|
 
@@ -312,7 +326,7 @@ agent 会识别系统、装 `uv`、改 `mcp.json`（**保留**已有 server）
 
 ## 状态与版本
 
-- **当前发布**：`v3.0.2`（2026-05-22）——**初始化拓扑修复。** 关键 patch：3.0.0 / 3.0.1 的 `Project._apply_init` 只创建了 v2 老桶，跳过了 spec §1.1 强制要求的 v3 `_lifecycle/{inbox,active,review,done,archive}/` 五桶——所有在那两版上 fresh init 的项目都是**生而不合规**的。3.0.2 让 fresh init 直接落 v3 拓扑（同时不再创建被 superseded 的 v2 `tasks/` / `log/`）；`core.events.scan_workspace` 与 `Project.role_occupancy()` 在 v3 项目下从 `_lifecycle/` 读取。新增 audit 扫描 `_scan_lifecycle_topology_compliance()`（D9）：P0 = 已初始化项目同时缺 `_lifecycle/` 和 v2 内容；P1 = 两套拓扑共存（建议 `migrate --to-v3`）。MCP 工具描述（`init_solo` / `init_project` / `create_custom_team`）同步更新。1209 测试全绿。SemVer patch：无 API 表面改动——init 之前在做错事。前置 **v3.0.1**（2026-05-21）—— 路径整合补丁（纯文档）。前置 **v3.0.0**（2026-05-21）—— **协议级 MAJOR ·"文件夹即状态"纪元**：FCoP 协议本体的一次完整重写——canonical 双层（per [ADR-0040](adr/ADR-0040-canonical-one-liner-two-layer-convention.md)）「文件即协议；位置定义状态；事件记录历史」+ 语义本体；新增 `_lifecycle/{inbox,active,review,done,archive}/` 五桶目录拓扑（**与 2.x 不兼容**，须 `fcop migrate --to-v3`）；三层规则集（State / Event / Boundary Charter）+ 7 条允许迁移表外不可 + write-then-rename 原子性；ADR-0037 Custody Layer 在 RFC 评审中**未进 Accepted 即被作废**。详见 [`spec/fcop-3.0-spec.md`](spec/fcop-3.0-spec.md) 与 [`docs/MIGRATION-3.0.md`](docs/MIGRATION-3.0.md)。早期发布：v2.0.2（fcop-mcp 入驻官方 MCP 注册表）、v2.0.0（两图对偶哲学主版本号跨越 + Rule 4.6 `fcop/internal/`）、v1.6（trailing-slug 文件名收编，ADR-0033）、v1.5（84 份协议感知同步）、v1.4（write-side 守门 + `supersedes:` 字段）、v1.3（GAL + `fcop_audit()` 巡查编译器）、v1.2.1（Capability Governance 支柱）、v1.1（Agent.layer + Task.risk_level + needs_human）、v1.0（七大核心概念 spec freeze）。详见 [CHANGELOG](CHANGELOG.md)。
+- **当前发布**：`v3.2.2`（2026-05-22）——**初始化拓扑修复。** 关键 patch：3.0.0 / 3.0.1 的 `Project._apply_init` 只创建了 v2 老桶，跳过了 spec §1.1 强制要求的 v3 `_lifecycle/{inbox,active,review,done,archive}/` 五桶——所有在那两版上 fresh init 的项目都是**生而不合规**的。3.0.2 让 fresh init 直接落 v3 拓扑（同时不再创建被 superseded 的 v2 `tasks/` / `log/`）；`core.events.scan_workspace` 与 `Project.role_occupancy()` 在 v3 项目下从 `_lifecycle/` 读取。新增 audit 扫描 `_scan_lifecycle_topology_compliance()`（D9）：P0 = 已初始化项目同时缺 `_lifecycle/` 和 v2 内容；P1 = 两套拓扑共存（建议 `migrate --to-v3`）。MCP 工具描述（`init_solo` / `init_project` / `create_custom_team`）同步更新。1209 测试全绿。SemVer patch：无 API 表面改动——init 之前在做错事。前置 **v3.0.1**（2026-05-21）—— 路径整合补丁（纯文档）。前置 **v3.0.0**（2026-05-21）—— **协议级 MAJOR ·"文件夹即状态"纪元**：FCoP 协议本体的一次完整重写——canonical 双层（per [ADR-0040](adr/ADR-0040-canonical-one-liner-two-layer-convention.md)）「文件即协议；位置定义状态；事件记录历史」+ 语义本体；新增 `_lifecycle/{inbox,active,review,done,archive}/` 五桶目录拓扑（**与 2.x 不兼容**，须 `fcop migrate --to-v3`）；三层规则集（State / Event / Boundary Charter）+ 7 条允许迁移表外不可 + write-then-rename 原子性；ADR-0037 Custody Layer 在 RFC 评审中**未进 Accepted 即被作废**。详见 [`spec/fcop-3.0-spec.md`](spec/fcop-3.0-spec.md) 与 [`docs/MIGRATION-3.0.md`](docs/MIGRATION-3.0.md)。早期发布：v2.0.2（fcop-mcp 入驻官方 MCP 注册表）、v2.0.0（两图对偶哲学主版本号跨越 + Rule 4.6 `fcop/internal/`）、v1.6（trailing-slug 文件名收编，ADR-0033）、v1.5（84 份协议感知同步）、v1.4（write-side 守门 + `supersedes:` 字段）、v1.3（GAL + `fcop_audit()` 巡查编译器）、v1.2.1（Capability Governance 支柱）、v1.1（Agent.layer + Task.risk_level + needs_human）、v1.0（七大核心概念 spec freeze）。详见 [CHANGELOG](CHANGELOG.md)。
 - **规范性文件**：[`spec/fcop-3.0-spec.zh.md`](spec/fcop-3.0-spec.zh.md)（中文 v3.0）· [`spec/fcop-3.0-spec.md`](spec/fcop-3.0-spec.md)（英文权威 v3.0）· v1.0/v1.1 早期 spec 草稿在 `spec/` 中保留作为历史参考 · 机器可读契约见 [`spec/schemas/`](spec/schemas/)（8 个 Schema）
 - **本仓内 Agent 规则（`.mdc`）**：[`src/fcop/rules/_data/fcop-rules.mdc`](src/fcop/rules/_data/fcop-rules.mdc) + [`fcop-protocol.mdc`](src/fcop/rules/_data/fcop-protocol.mdc)（`spec/codeflow-core.mdc` 仅为弃用占位）
 - **变更记录**：[`CHANGELOG.md`](CHANGELOG.md)