[yi-ge]

核心 Agent 缺少开发工作台、可信预览、个人发布和目录分发的统一指引。本变更新增按需加载的 app-developer，衔接 app-install-manager、文件化 Plan、Task/Run 和唯一安装 writer；Core 为 1.16.0，安装管理技能为 1.8.0。

作者能力、草稿、发布、预览、源码/容器纳管和运行改用原 AppManage 的 19 个有限动作及真实 fileRoots/完整 DTO，不依赖普通 HttpRequest 自动注入平台凭据。知识覆盖固定 release 与三类摘要、原源码开发服务器/HMR 合同、真实 Docker prepare/enroll、候选/正式/预览数据隔离、设备偏好 CAS、原 Agent/request 查询、Task 成果 locator，以及 GitHub/Gitea 和 Registry 分发。两份通用教学示例支持笔记保存、显式记住所选位置和按真实请求定位成果；声明、提案和导航接纳均不冒充执行或业务完成。普通运行动作进入当前审批，私有临时预览回收只补偿原批准的 owned 资源。外部 Node/Docker、托管、Git 服务和数据库的实际环境、条款及可能费用按所选技术栈披露。

分发：export_release 可按原 Agent 写权限将 ZIP 交付到显式 FileResourceRef，以 expected_absent/etag 核验目标并返回实际 archiveFile；distribution_prepare 读取真实 export 和能力返回的 Registry 目标生成三文件草稿。上传、目录 PR 和准入仍需各自原工具回执，不读取实例 token 或绕过认证。

验证：Agent seed 与 persona/principles 分层检查、两个 Skill frontmatter、19 项实际动作及参数包络、两份清单的实际 payload/规范 digest、页面 DOM 引用与 JS 语法、公开信息和元数据检查通过。教学材料检查不代替主仓真实模型、GUI、Docker 或第二用户分发验收。

依赖状态：主仓 #4785/#4793/#4802 已受保护合入，fresh027f真实AppWork→AppData→Task/精确binding→Inspector/返回/切换已通过。发行 #4794 final60e经31/31门禁成功/CLEAN/零threads合入实际R d0de23b67e36d36df7a82f6fe27b734727402500；原流程已打不可变 v10.0.181，真实peeled同R。Build38485185504正按同R构建三平台；六架构安装包、上传完整摘要、ReleaseManager与beta实际feed仍待验收，因此知识/正式4.3/seed依赖尚未满足。

配套依赖：Registry 候选 PR #12 与 Market PR #214。

发布顺序：先完成后续候选的审阅、CI 与实际使用验收，发行兼容 reader／app-authoring-v1 客户端并验收，再从各外仓 reviewed main 提交通过单独交付同步正式 seed；Registry 4.3 和新条目激活另行提交 PR。正式 Registry 4.2 继续保留，Core/Market seed 尚未同步，本次仅关联状态更新。

验收范围：原真实模型空目录开发发布与14d Mac/Windows163秒授权、CRUD/CAS、设备偏好和冷恢复分别保留在其原产物范围；027f新Mac AppWork/Task成果链已实际通过，原20文件和fixture字节不变、自有进程清理。当前材料/源码审阅、unit及既有运行证据不替代新发行包、生产更新feed或第二用户市场安装；没有真实来源和目录目标不假称上架。

实际执行仍须探测 app-authoring-v1 与各功能，10.0.180 仅为代码基线。外仓候选知识不表示客户端、正式 seed 或市场条目已发行。

English: The core Agent needs a coherent guide for workbench development, trusted preview, personal publication and distribution. This change adds the on-demand app-developer skill, connects it to app-install-manager, and reuses Plan, Task/Run and the single installation writer. Core becomes 1.16.0; installation-management knowledge becomes 1.8.0.

Authoring capabilities, drafts, publication, previews, enrollment and runtime operations prefer the original 19 finite AppManage actions with real fileRoots and complete DTOs, without assuming automatic credentials in ordinary HttpRequest. Guidance covers fixed material and separate digests, original source-server/HMR contracts, real Docker prepare/enroll, candidate/formal/preview data isolation, device view-state CAS, exact Agent/request lookups, Task result locators and GitHub/Gitea/Registry distribution. Two generic examples demonstrate note persistence, explicitly remembered selection and authorized output navigation. A declaration, proposal or navigation request does not prove execution or business completion. Normal runtime actions re-enter current approval; private transient preview disposal compensates only originally approved owned resources. External runtime/service readiness, terms and possible costs are disclosed according to the selected stack.

Distribution: export_release can materialize ZIP bytes at an explicit FileResourceRef under the original Agent write authority, guarded by expected_absent/etag and returned as archiveFile. distribution_prepare uses the real export and registered capability targets to generate three catalog drafts. Upload, catalog PR and admission still require their original tools and real receipts; no token extraction or authentication bypass is taught.

Validation: seed/prompt structure, both Skill schemas, all 19 actual action names/envelopes, both actual example payload/manifest digests, DOM references, JS syntax and public information/metadata checks passed. These material checks do not establish autonomous-model, GUI, Docker or second-user distribution acceptance.

Dependency status: #4785/#4793/#4802 are merged and the fresh027f real application work/data/Task-binding/Inspector flow passed. Release #4794 passed all31 gates and merged as d0de23b67e36d36df7a82f6fe27b734727402500. The original flow created immutable v10.0.181 at that exact source. Build38485185504 is building all three platforms; six-architecture packages, complete upload digests, owner receipts and beta feed acceptance are still pending before knowledge/Registry/seed activation.

Companion dependencies: Registry candidate PR #12 and Market PR #214.

Release order: finish review, CI and actual usage validation for the follow-up candidate, release and validate a compatible reader/app-authoring-v1 client, then synchronize official seeds from reviewed external main commits through a separate delivery. Activate Registry 4.3 and new entries through another PR. Formal Registry 4.2 remains in place; Core/Market seeds are not synchronized. This update only reconciles linked status.

Evidence scope: the original autonomous-development and14d Mac/Windows grant-renewal, CRUD/CAS, preferences and cold-restore evidence retains its recorded artifact scope. The fresh027f Mac AppWork and Task-object flow passed with protected bytes unchanged and owned processes cleaned up. Material checks, unit fixtures and source review do not establish acceptance of new release packages, production update feeds or actual second-user distribution.

Execution still requires actual app-authoring-v1 and feature negotiation; 10.0.180 is a code baseline only. Candidate knowledge does not establish a shipped client, official seed or catalog activation.

示例增量：四份清单新增readResource声明（不自动grant），fallback补自身controlWork/openResource/saveViewState；原生成器重建材料，root按最终主Schema及真实字节/c14n验证四清单32payload。Node MessageChannel隔离unit证明旧三方法拒、新四fallback三方法往返且任意invoke仍拒；两仓材料镜像、完整及增量独立源码审阅通过。新head CI需实时核查；Market等待Copilot超时不当独立审阅。本候选知识只有兼容客户端实际发行验收后才合main/同步固定reviewed seed。

Example follow-up: declare readResource without granting it, cover all three actual fallback calls, and regenerate fixed releases. Current main Schema, canonical digests and32 payload byte checks pass. Isolated MessageChannel fixtures confirm prior rejection and current roundtrips while arbitrary invoke remains denied. Independent complete and incremental source review passes; fresh-head CI and compatible-client release acceptance remain separate merge/delivery requirements.