docs: record project-wide scaffold activation

This commit is contained in:
brother7 committed 2026-09-05 12:39:18 +08:00
1 parent 6710527e8f
commit 5e0a091955
11 files changed
+147 -133

No files matched your search

+9 -4
View File
@@ -7,7 +7,10 @@
later consume Token Points, and system-included Data Service remains zero-charge.
- Account Library, Device Installation, project enablement, Agent assignment, runtime
authorization, and billing are separate states. No read, install, acquisition, or
assignment may silently advance another state.
assignment may silently advance another state. The sole code-owned activation-scope
exception is `makelore.project-scaffold`: Account acquisition and project enablement
remain separate, but project enablement intentionally makes its Skills available to
every parent Agent without creating or requiring assignment state.
- Marketplace packages become effective only after closed manifest/descriptor parsing,
canonical archive and client-compatibility checks, Ed25519 verification, immutable
Package Store selection, project enablement, Agent projection, and current server
@@ -64,9 +67,11 @@
Store, Release, Channel, Admission, project enablement, Agent assignment, or server
billing state.
- Code-owned official bundled Plugins may be `platform_hosted` or `skill_only`.
`makelore.project-scaffold` retains Account Library, project enablement, Agent
assignment, Release, and Admission state while its exact Skill/templates/`.mjs`
ship only in the signed client. Downloadable Marketplace artifacts remain P0
`makelore.project-scaffold` retains Account Library, project enablement, Release, and
Admission state while its exact Skill/templates/`.mjs` ship only in the signed client.
It is project-wide: once acquired and enabled for a project, every parent Agent receives
the Skill without partner assignment; child Agents remain empty. Downloadable
Marketplace artifacts remain P0
text/image-only and must reject `.mjs`; official bundled authority is not inferred
from provider metadata or an uploaded ZIP.
- 面向用户的 AI 编程新建流程必须在 `interactive_ai_app`(“交互式 AI 应用”)和 `custom` 中选择;`ProjectType` 是产品类型,创建后不能通过 UI 或 Host API 修改。历史 `mini_game` / `mini_program` 仅在读取边界归一为 `interactive_ai_app`,读取本身不改写配置;未传类型的兼容 API 调用按 `custom` 处理。