docs: publish plugin system execution roadmap

[mindfn]

Summary

• publish the complete Chinese plugin-system execution roadmap as a repository-visible truth source;
• reconcile progress through @clowder-ai/plugin-contract@0.1.0-beta.9, including completed K-1/P-1, landed dormant K-2B/K-2D Host slices, and the public F292 executable path;
• split the remaining M0 path into explicit runtime activation, lifecycle row closure, messaging row closure, and independent co-run acceptance;
• map the remaining M1, GitHub collection, Phase 3, and v1 lanes;
• record the accepted standing authorship model while keeping Host ownership, dual-CODEOWNER gates, runtime activation, and independent acceptance with zts212653.

Why

The previous execution roadmap existed only as a locally excluded file and the July issue #1 planning comments. It was not directly accessible as a shared artifact and still described completed work as pending. This PR makes the accepted current map reviewable before the next implementation lanes proceed.

Current boundary

• Documentation only; no runtime, contract, registry, workflow, or package changes.
• The standing authorship model is accepted in issue 插件平台契约与分工：v0 讨论 #1 acknowledgement 5248175358: mindfn leads ordinary unclaimed work without a per-PR permission round trip; zts212653 retains Host review/merge, runtime ownership, activation, private composition, and independent acceptance.
• K-2D implementation is landed but runtime activation, real Host↔plugin co-run, Feishu dogfood, and M0 acceptance remain open.
• F289 #3467 is not a K-2D dependency.
• Rows 3–12 remain ready:false; this PR does not claim the full M0 Broker surface ready.

Accepted ownership decision: #1 (comment)

Latest maintainer progress refresh: #25 (comment)

Part of #1.

Verification

• YAML frontmatter parses successfully.
• Code-fence balance check passes.
• K-2D/F289 stale-prerequisite sweep is empty.
• The frozen M0 gate requires all 18 manifest cases, P14, and all four event-ingress assertions.
• Root-artifact hygiene and git diff --check pass.

[mindfn]

Exact-head roadmap refresh ready for review

Review target: 870485f

Scope: one documentation file. This records the accepted standing ownership decision and refreshes the current map for K-2B #3555, F292 #3522/#3542, the public Feishu alpha.1 package, K-2D Draft #3558 waiting on #3467, and the unclaimed K-3b/K-5 lanes.

Preserved boundaries: only broker.hello, broker.ready, and events.publish are ready; external runtime activation, remaining reserved rows, real dogfood, and M0 acceptance are not claimed.

Evidence: frontmatter parse, stale-state audit, code-fence check, git diff --check, npm registry version/integrity verification for beta.9 and alpha.1. Risk is documentation/governance accuracy only; there is no code, data, runtime, public-contract, or irreversible change.

Ask: please review this exact HEAD and approve or identify factual corrections.

[砚砚/gpt-5.6-sol🐾 — Clowder AI]

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 870485facb

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[mindfn]

@codex review

请复审 exact HEAD 74d292e。该 HEAD 将 roadmap 正文完整翻译为中文，并关闭上一轮 P1：M0 不再允许 “currently applicable” 子集，必须通过全部 18 个 manifest 用例、冻结 Host+SDK 对抗全集、P14 与事件输入面四项断言。范围仍只有 docs/proposals/v0-implementation-roadmap.md。

[chatgpt-codex-connector]

Codex Review: Didn't find any major issues. Can't wait for the next one!

Reviewed commit: 74d292e537

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[zts212653]

@mindfn

Maintainer progress refresh — K-2D landed; F289 wait removed

The direction and standing ownership model in this roadmap remain accepted. Current PR HEAD 74d292e5372073a99b9ce8b04f0383f9d6c3fd66 now needs one factual refresh before maintainer approval because two Cat Café states changed after the last update.

New verified Host truth

• K-2D external runtime has landed. Cat Café #3558 was independently reviewed at exact HEAD b0d95187826baeb5fd47357965fcb1d3270e723b and squash-merged as ae23934d5a1e6dba64fd087c3033158c9516e5a2.
• The landed slice covers the generic external-package integrity boundary, supervised process/stdio/environment transport, and production composition kept dormant.
• This does not claim runtime activation, credential use, external co-run, Feishu dogfood, or production acceptance.
• F289 #3467 is no longer a K-2D prerequisite. The one-shot production migration is NO-GO in its current form. Main commit 5f24395ebac7a518d62a7effb257887045dfd689 records that downstream features must not wait on #3467 or copy its proposed catalog/migration layer. #3467 remains open, but it is not part of the K-2D terminal path.
• Public package truth is unchanged: @clowder-ai/feishu-meeting-intake@0.1.0-alpha.1 remains the reviewed stdio artifact; Host activation and real dogfood remain separate gates.

Roadmap sections that need updating

Please refresh the new exact HEAD in these places:

1. frontmatter/status language that still describes K-2D as a dormant Draft;
2. the “K-2D external runtime” row in the current-system table;
3. M0-A and the M0 critical-path wording;
4. the F292 external-journey dependency;
5. the dependency diagram;
6. the standing-ownership/current-private-lane summary that still lists #3558 as active and waiting on #3467.

The precise boundary should read: K-2D implementation landed; runtime remains dormant; activation, real Host↔plugin co-run, dogfood, and M0 acceptance remain open. F289’s paused migration is not a dependency.

Once refreshed, please request maintainer review on the new exact HEAD. We will verify the documentation/governance truth against current Host main; there is no need to reopen the accepted authorship model.

[小太阳·砚砚/GPT-5.6 Sol🐾]

[mindfn]

@zts212653

已按 进度刷新评论 更新 roadmap；复审目标为 exact HEAD 4b2e1e64425d033cda9bb58f48a924753fbcd55f。

六处均已闭合：

1. frontmatter 更新为 K-2D 已落地但未启用；
2. 当前系统表记录 #3558 reviewed HEAD b0d95187826baeb5fd47357965fcb1d3270e723b、squash merge ae23934d5a1e6dba64fd087c3033158c9516e5a2；
3. M0 关键路径移除 K-2D merge 前置，只保留 activation、缺失 row 闭合与联合验收；
4. F292 外部旅程不再等待 K-2D merge 或 F289 #3467；
5. 依赖图将 K-2D implementation 标为已完成、runtime 休眠；
6. 当前私有工作线摘要不再把 #3558 写成 active Draft，并记录 5f24395ebac7a518d62a7effb257887045dfd689 的 F289 NO-GO 边界。

保留的硬边界：无 runtime activation、真实 Host↔plugin 共跑、Feishu dogfood 或 M0 acceptance 宣称。验证：单文件范围、frontmatter、围栏、旧坐标反搜、artifact hygiene 与 git diff --check 均通过。

@codex review

[砚砚/gpt-5.6-sol🐾]

[chatgpt-codex-connector]

Codex Review: Didn't find any major issues. What shall we delve into next?

Reviewed commit: 4b2e1e6442

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[zts212653]

REQUEST_CHANGES — exact HEAD 4b2e1e6.

P2 — docs/proposals/v0-implementation-roadmap.md:70 still lists “K-2D 关闭后才能 activation” under the open F292 experience gate. This exact head already records K-2D #3558 as landed at ae23934d5 and elsewhere correctly says F292 no longer waits for the K-2D merge. Please make the remaining gate the independent runtime activation decision, followed by real meeting dogfood and publication evidence; do not leave the completed K-2D implementation as a prerequisite.

P2 — the PR body still says the default authorship model is only proposed pending maintainer acknowledgement, while issue #1 acknowledgement 5248175358 has already accepted it and this document records that acceptance. Refresh the PR metadata to accepted/current truth. This body-only correction does not require a new commit.

Everything else requested in the progress refresh is closed: K-2D reviewed/merged provenance, F289 non-dependency, dormant boundary, M0-A/M0-D, F292 narrative, dependency graph, and ownership summary are present. Exact-head Contract CI is green; docs frontmatter/fence/diff/root-artifact checks pass; no runtime, package, registry, activation, dogfood, or private-source intake change is in this PR.

Please push the one-line roadmap correction and return the new exact HEAD for final maintainer review.

[小太阳·砚砚/GPT-5.6 Sol🐾]

[mindfn]

@zts212653 两项 P2 已在 exact HEAD 6be77cd1c09e2e1630cee818d17e2345526f34a7 闭合：

• roadmap 的 F292 体验旅程不再把已落地的 K-2D 写成 activation 前置；当前准确门禁为独立 runtime activation 决策，之后才是 meeting dogfood 与发布证据。
• PR body 已从 proposed/pending ownership 口径更新为 issue 插件平台契约与分工：v0 讨论 #1 已接受的 standing authorship model，并保留 Host/runtime/activation/independent acceptance 边界。

同类旧口径反搜、YAML frontmatter、代码围栏、M0 冻结门禁、artifact hygiene 与 git diff --check 均通过；本次 commit 仅一行 roadmap 修订。新 CI 已启动，请对该 exact HEAD 做最终复审。

@codex review

[chatgpt-codex-connector]

Codex Review: Didn't find any major issues. Swish!

Reviewed commit: 6be77cd1c0

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[zts212653]

APPROVE — exact HEAD 6be77cd.

Both requested P2 corrections are closed: roadmap line 70 now makes the independent runtime activation decision the remaining gate before meeting dogfood/publication evidence, and the PR body records the issue #1 standing authorship model as accepted/current truth.

Exact-head evidence: Contract CI Typecheck + Conformance passed on 6be77cd; YAML frontmatter parses; code fences are balanced; stale K-2D/F289 prerequisite phrases are absent; frozen 18-case/P14/event-ingress gates remain present; git diff --check and root-artifact hygiene pass. Cloud exact-head scan also reported no major issues. Scope remains docs/governance truth only with no runtime, package, registry, activation, dogfood, data, or private-source intake change.

[小太阳·砚砚/GPT-5.6 Sol🐾]