Skip to content

feat: 提供固定工作台应用的 Registry 候选格式 - #12

Open
yi-ge wants to merge 3 commits into
mainfrom
work/application-authoring-registry
Open

yi-ge wants to merge 3 commits into
mainfrom
work/application-authoring-registry

Conversation

@yi-ge

@yi-ge yi-ge commented Oct 13, 2026 •

Copy link
Copy Markdown
Member

现有目录不能明确描述固定网页工作台及其应用 release。本变更新增独立 4.3 候选 Schema、静态/原生服务/Docker 合成目录样本,以及严格的摘要、镜像固定引用和字段一致性验证。

正式 SCHEMA_VERSION、manifest 数据版本及当前 registry-entry.schema.json 仍为 4.2;当前 Schema 原字节 SHA-256 保持 ea63d6305ae17994e595aea009a131c41300d2b7fdb07ec83cc2c19c37b32038。候选 4.3 摘要为 29ece0b6ae92d2b31d18bbb288b5ed33220dde125924082e1e38c20ace900200。样本仅为 listing-only 的协议材料,正式目录仍为原 24 个条目。

验证:

  • node --test scripts/application-authoring.test.mjs scripts/native-app.test.mjs:13/13。
  • node scripts/validate-registry.mjs:24 个正式条目通过。
  • node scripts/catalog/validate-registry.mjs --require-sidecars:通过。
  • 完整工作树、路径与提交元数据公共信息检查通过。

未将协议样本称作真实 Docker 运行、外部上传或另一用户安装验收。本 PR 不激活候选协议、不修改客户端内置 seed。

依赖状态:主仓 #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依赖尚未满足。

配套依赖:Core 知识 PR #4 与 Market PR #214。本 PR 的 4.3 仍仅为候选 Schema/fixture,当前正式 4.2 和既有条目保留。私有来源访问依真实 Git ACL,不因团队成员移除假报源端权限已撤销。

发布顺序:先完成后续候选的审阅、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或第二用户市场安装;没有真实来源和目录目标不假称上架。

English: The existing catalog cannot represent fixed web workbenches and portable application releases. This change adds an isolated 4.3 candidate Schema, synthetic static/native-service/Docker listings, and strict digest, immutable image-reference and cross-field checks. The formal 4.2 version and current Schema bytes remain unchanged; the 24 formal entries remain intact.

Validation: 13 focused tests passed; both Registry validators passed for all 24 existing listings; the public-information boundary was checked. No candidate activation or client seed update is included.

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: Core knowledge PR #4 and Market PR #214. Version 4.3 remains a candidate Schema/fixture in this PR; formal 4.2 and existing entries remain intact. Private access follows actual Git ACL, without claiming that team-member removal revokes source access.

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.

依赖正文增量仅明确“兼容客户端实际发行验收→知识main/固定bootstrap→另PR正式4.3激活/seed”,与已合Docs#771一致。独立全diff及增量审阅通过;正式4.2/schema原字节、版本、24entries和信任seed均不变。

The README follow-up aligns activation order with merged Docs#771. Independent full and incremental source review passes; formal4.2 Schema bytes, version,24 entries and seed trust remain unchanged.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant