Skip to content

Commit 515defb

Browse files
committed
docs: record v57 release gates
1 parent 8719dff commit 515defb

5 files changed

Lines changed: 11 additions & 0 deletions

File tree

‎README.md‎

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -154,6 +154,8 @@ v56 本地发布门禁已通过全仓普通/race 测试(178.5 秒/181.3 秒)
154154
schema v57 在 v56 容器保持停止状态时增加独立的 `sandbox_docker_host_input_staging.v1` 演练。Linux 实现使用 `openat2` 的 `RESOLVE_NO_SYMLINKS`、`RESOLVE_NO_MAGICLINKS`、`RESOLVE_BENEATH` 与 `RESOLVE_NO_XDEV` 固定工作区根和每个只读输入树。每个条目先以 `O_PATH` 预检,再只对同一 inode 的普通文件或目录执行内容打开,因此 FIFO 和其他特殊文件会在潜在阻塞前失败;目录和单文件 mount 均支持,符号链接、硬链接、跨挂载点、越界、过深或超限输入全部拒绝。完成 descriptor pin 后再次核对 inode、大小、时间戳和链接数,再将规范化只读树与已按 Run/Session/Workspace/摘要复核的 Artifact 组成确定性 tar;目录的文件系统相关 inode 大小不进入内容摘要。包只存在于 `memfd`,随后施加 `F_SEAL_WRITE/GROW/SHRINK/SEAL` 并重新读取核对摘要。SQLite 在当前 v56 attempt、container-ID 指纹、计划、输入摘要和 lease generation 下先保存不可变 intent,再保存不含路径、正文、fd 或原始容器 ID 的计数与摘要;未完成 v57 的 attempt 由 SQL 禁止 completion。`--stage-host-inputs` 还要求独立的 `--confirm-host-input-staging`,失败会先尝试清理停止容器,重启后可由新 generation 恢复且不重复 create。当前密封包尚未交给 Docker daemon,`daemon_consumed=false`、`execution_evidence=false`;因此它只关闭 descriptor-capture 内的路径偷换窗口,不是未来容器实际消费输入的生产证据,也没有开放 start、exec、网络、输出导出或 Artifact 提交。
155155
v57 本地发布门禁已通过最终代码的全仓普通/race 测试(155.0 秒/168.1 秒)、vet、零告警 staticcheck、module verify、零可达漏洞 govulncheck、17 项前端测试、OpenAPI 无漂移、生产构建、零漏洞 npm audit、凭据/运行产物/进程入口扫描、diff 检查和隔离真实二进制 schema-v57 smoke。Application staging 连续 10 轮、双 Store 独立 ID 并发 20 轮及 race 10 轮通过,Linux test binary 交叉编译通过。定向覆盖 rename/replace/delete/symlink/hard-link/FIFO/单文件 mount、有界目录枚举、取消、重放、租约接管、迁移和隐私。审计修复了单文件报告/SQL 约束、目录摘要跨文件系统稳定性、特殊文件预打开阻塞、超大目录预分配、读取取消延迟、随机 ID 幂等冲突和漏确认消耗失败账本等问题,未发现未解决高/中风险。已知低风险恢复缺口是 v57 opt-in 尚未在 v56 stage 前持久化:若进程恰好在 stage checkpoint 后、v57 intent 前退出,恢复时遗漏 staging flags 可能完成可选的 v56-only 演练,但不会启动容器或扩权;v58 必须先关闭该窗口。
156156

157+
首次 GitHub Actions run `29395980413` 只暴露 Linux 单文件测试夹具错误:夹具把唯一 mount 目标改成文件路径,却保留目录工作目录,Manifest 正确拒绝该状态;生产实现未失败。修复后的测试保留覆盖工作目录的只读目录 mount,并增加独立单文件 mount,从而真实覆盖 `directory_count < read_only_mount_count`。run `29396264276` 已通过提交 `8719dff`,Go/Linux 与 TypeScript 作业分别用时 3 分 55 秒和 23 秒。
158+
157159
v47 发布复核进一步加固了 Supervisor 并发恢复与预算边界:阶段切换重放会在观察到目标状态后重新核对幂等操作,取消测试会等待 Provider 真正进入调用后再触发取消;任何已经持久化 `model.started` 的 root 模型调用至少计入 1ms,避免 `999/1000ms` 的 deadline 边界被重复进入。该修复不改变 schema、不开放新能力,也不重解释旧 Specialist 账本。GitHub Actions run `29325171043` 已通过 Go 与 TypeScript 全部门禁。
158160

159161
当前版本已经提供 Run 级结构化 Work Board 与 Notes:工作项负责可执行计划,Note 负责观察、假设、决策、摘要和来源引用,所有变更都与 Run 事件在同一事务提交。Supervisor 使用 8192 token 的独立记忆预算选择摘要、活跃工作项和当前 root 可见 Note,并把来源 ID 与 token 估算记录在 `model.started`;Note 正文不会写入模型事件。仍有活跃工作项时,模型不能自行 `finish`。
@@ -291,6 +293,8 @@ The v56 local release gate passed full ordinary/race suites (178.5s/181.3s), vet
291293
Schema v57 adds a separate `sandbox_docker_host_input_staging.v1` rehearsal while the v56 container remains stopped. On Linux, `openat2` pins the workspace root and every read-only source tree with no-symlink, no-magic-link, beneath-only, and no-cross-device resolution. Each entry is preflighted with `O_PATH`, then only a matching regular file or directory is opened for content, so FIFOs and other special files fail before a potentially blocking open. Directory and single-file mounts are supported; symlinks, hard links, nested mounts, traversal, excessive depth, and bounded-resource violations fail closed. After all descriptors are pinned, inode, size, timestamps, and link counts are rechecked before a deterministic tar is assembled from sanitized source entries and exactly revalidated Run/Session/Workspace Artifacts. Filesystem-specific directory inode sizes are excluded from the content digest. The archive exists only in a `memfd`, receives write/grow/shrink/seal kernel seals, and is read back for digest verification. SQLite first stores an immutable intent bound to the current v56 attempt, container-ID fingerprint, plan, input digest, and lease generation, then stores counts and digests without paths, content, file descriptors, or raw container IDs. SQL blocks attempt completion while a v57 intent lacks evidence. `--stage-host-inputs` requires a separate `--confirm-host-input-staging`; failure performs best-effort stopped-container cleanup, and takeover can resume without another create. The sealed bundle is not yet handed to the Docker daemon, so `daemon_consumed=false` and `execution_evidence=false`: v57 closes the descriptor-capture race but is not production proof of bytes consumed by a future container and grants no start, exec, network, export, or Artifact authority.
292294
The v57 local release gate passed the final code's full ordinary/race suites (155.0s/168.1s), vet, zero-warning staticcheck, module verification, zero-finding govulncheck, 17 frontend tests, OpenAPI drift, production build, zero-vulnerability npm audit, credential/runtime-artifact/process-entry scans, diff checks, and an isolated real-binary schema-v57 smoke. Ten Application staging rounds, twenty two-Store independent-ID contention rounds, and ten race contention rounds pass; the Linux test binary cross-compiles. Focused coverage includes rename/replacement/deletion/symlink/hard-link/FIFO/single-file mounts, bounded directory enumeration, cancellation, replay, lease takeover, migration, and privacy. The audit fixed single-file report/SQL constraints, cross-filesystem directory-digest stability, special-file pre-open blocking, pre-limit directory allocation, read cancellation latency, random-ID idempotency conflicts, and failure-ledger consumption after omitted confirmation, with no unresolved high- or medium-severity issue. One known low-risk recovery gap remains: v57 opt-in is not durable before v56 stage, so a process exit after that checkpoint but before the v57 intent requires the staging flags to be resubmitted and can otherwise finish an optional v56-only rehearsal. This cannot start a container or widen authority; v58 must close the window first.
293295

296+
Initial GitHub Actions run `29395980413` exposed only an invalid Linux single-file test fixture: it changed the sole mount target to a file while retaining a directory working directory, which the Manifest correctly rejected; production code did not fail. The corrected fixture retains one read-only directory mount covering the working directory and adds a separate file mount, exercising the intended `directory_count < read_only_mount_count` case. Run `29396264276` passed commit `8719dff`; Go/Linux and TypeScript completed in 3m55s and 23s.
297+
294298
The v47 release audit also hardens Supervisor concurrency recovery and budget accounting. Phase-transition replay rechecks the idempotency operation after observing the target state, cancellation tests wait for the Provider call to begin, and every root model call with a durable `model.started` fact is charged at least 1ms so a `999/1000ms` deadline cannot be entered repeatedly. This changes no schema, grants no capability, and preserves the interpretation of historical Specialist ledgers. GitHub Actions run `29325171043` passed every Go and TypeScript gate.
295299

296300
The current build includes a structured, Run-scoped Work Board and durable Notes. WorkItems hold executable plans, while Notes hold observations, hypotheses, decisions, summaries, and source references. Every mutation commits with its Run event. The Supervisor selects summaries, active work, and root-visible Notes under a separate 8,192-token memory budget, then records source IDs and token estimates in `model.started` without persisting Note bodies there. Model-driven `finish` remains blocked while active work exists.

‎docs/PROGRESS_BOOK.md‎

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -630,6 +630,8 @@ Application 在 v56 stage 后、cleanup 前持久化 v57 intent,并绑定 oper
630630

631631
定向测试已覆盖独立确认、默认关闭、自定义 stager 报告复核、rename/replace/delete/symlink/hard-link/FIFO/单文件 mount、有界目录枚举、取消、确定性重放、失败清理、重启/第二代 lease 恢复、stale generation fencing、completion SQL 门禁、不可变 SQL、路径/正文隐私和 v56 原地迁移。最终全仓普通/race 分别用时 155.0 秒/168.1 秒;应用 staging 10 轮、双 Store 独立 ID 并发 20 轮及 race 10 轮通过。vet、零告警 staticcheck、module verify、零可达漏洞 govulncheck、17 项前端测试、OpenAPI 无漂移、生产构建、零漏洞 npm audit、凭据/运行产物/进程入口扫描、diff 与隔离真实二进制 schema-v57 smoke 均通过。Linux test binary 交叉编译通过;`openat2`/seal 运行测试由 GitHub Actions 执行。本轮审计补强了公开报告构造器、Artifact payload/字节二次复核、根路径父级 symlink 拒绝、stage→intent 时间顺序、超限错误语义、歧义确认、单文件报告约束、目录摘要稳定性、特殊文件预打开阻塞、有界分批目录读取、分块取消、随机 ID 语义收敛和漏确认不消耗 failure/lease。未发现未解决高/中风险。密封包当前没有交给 Docker daemon,持久事实固定 `daemon_consumed=false`、`execution_evidence=false`,因此 v57 只关闭 descriptor-capture 内的路径偷换,不证明未来容器实际消费了这些字节。架构完成度暂保持约 98%,产品可用度约 45-50%。
632632

633+
首次 GitHub Actions run `29395980413` 仅暴露 Linux 单文件测试夹具与 Manifest 工作目录覆盖规则冲突,生产实现未失败。夹具已改为一个目录 mount 覆盖工作目录并增加独立单文件 mount,真实验证 `directory_count < read_only_mount_count`;run `29396264276` 已通过提交 `8719dff`,Go/Linux 3 分 55 秒,TypeScript 23 秒。
634+
633635
Docker/Local 真实进程执行继续关闭,直到 v51 每项检查都有独立可复核的生产证据,且 Sandbox input handoff、资源、网络、取消与原子 Artifact 导出全部通过单独审计;v52 的模拟通过、v53 的元数据观测、v54 的编译/假写、v55-v56 的未启动容器演练/恢复和 v57 的 daemon-unconsumed sealed bundle 都不能满足该要求。已知低风险恢复缺口是:v57 opt-in 选择尚未在 v56 stage 前持久化,若进程恰好在 stage checkpoint 后、v57 intent 前退出,恢复时遗漏 staging flags 可能完成可选的 v56-only 演练;它不会启动容器或扩权。下一切片 schema v58 必须先关闭该窗口,再完成 daemon-owned immutable input handoff,仍不开放 start。
634636

635637
## 八、仓库同步与恢复约定

‎docs/PROJECT_MEMORY.md‎

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -78,6 +78,8 @@ Application verifies returned Artifact bytes and payload digest, stores only bou
7878

7979
Focused tests cover separate confirmation, default-disabled and unsupported behavior, deterministic replay, rename/replace/delete detection after pin, symlink/hard-link/FIFO rejection, single-file mounts, bounded directory enumeration, cancellation, report mismatch, cleanup-first failure, restart/takeover without a second create, stale-generation fencing, SQL completion gating, immutability, privacy, and v56-to-v57 migration. Final ordinary/race suites pass in 155.0s/168.1s; vet/staticcheck/module/govulncheck, 17 frontend tests, OpenAPI/build/npm audit, repository scans, isolated schema-v57 binary smoke, focused repetition, and Linux test-binary cross-compilation pass. GitHub Actions supplies the Linux runtime proof. The audit tightened root-parent symlink rejection, public report construction, Artifact byte/digest revalidation, stage-to-intent chronology, resource-limit errors, ambiguous confirmation, file-mount SQL/report constraints, filesystem-independent directory digests, special-file preflight, bounded/cancellable reads, independent-ID semantic convergence, and pre-acquire rejection of missing resume confirmation. No high/medium issue is currently known. The bundle is deliberately not passed to Docker, so this slice adds no execution usability and does not satisfy a future start gate.
8080

81+
GitHub Actions run `29396264276` passed commit `8719dff` with Go/Linux in 3m55s and TypeScript in 23s, providing the Linux runtime proof. The preceding run `29395980413` failed only because the single-file test fixture no longer covered its directory working path; the corrected mixed directory/file fixture now exercises the intended report constraint.
82+
8183
## Next Slice
8284

8385
Continue P6 through a separately gated schema-v58 daemon-owned immutable input handoff; do not reinterpret v57 capture evidence as bytes consumed by Docker:

‎docs/PROJECT_STATUS.md‎

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -692,6 +692,8 @@ Expected context behavior:
692692

693693
- Schema v57 adds a separately confirmed, default-disabled descriptor-pinned host-input capture between v56 stage and cleanup. Linux `openat2` pins no-symlink/no-magic-link/beneath/no-cross-device trees; `O_PATH` preflight rejects FIFO/special files before content open, and both directory and single-file mounts are supported. Descriptor metadata is rechecked before a deterministic sanitized tar is sealed in `memfd` and reread. Exact Artifact payload metadata is independently rechecked by Application. SQLite binds immutable intent/result rows to attempt, container fingerprint, plan, input digest, requester, and generation; generated row IDs are excluded from semantic fingerprints, pending intent blocks completion, and missing resume confirmation is rejected before lease acquisition. Failure cleans the stopped container before releasing the lease, and takeover resumes without another create. Tests cover rename/replacement/deletion/symlink/hard-link/FIFO/single-file, bounded enumeration, cancellation, replay, report mismatch, cleanup-first recovery, stale-generation fencing, migration, immutability, privacy, CLI, and Linux cross-compilation. Final ordinary/race suites pass in 155.0s/168.1s; vet/staticcheck/module/govulncheck, 17 frontend tests, OpenAPI/build/npm audit, repository scans, focused repetitions, and isolated schema-v57 binary smoke are green. The audit additionally fixed single-file report/SQL constraints, filesystem-dependent directory digest input, special-file pre-open blocking, unbounded directory allocation, cancellation latency, independent-ID convergence, and failure-ledger consumption on omitted confirmation. No unresolved high/medium issue is known. The sealed bundle remains local and daemon-unconsumed, so no process or production authority has been added.
694694

695+
- GitHub Actions run `29396264276` passed commit `8719dff` with Go/Linux in 3m55s and TypeScript in 23s. Initial run `29395980413` exposed only an invalid single-file test fixture whose file target did not cover the retained directory working path; the corrected mixed directory/file fixture now validates the intended report constraint. Production behavior was unchanged.
696+
695697
## Recommended Next Slice
696698

697699
Continue P6 with a separately gated schema-v58 daemon-owned immutable input handoff. First persist the staging choice before v56 daemon stage, closing the low-risk crash window where a post-stage/pre-v57 exit currently requires the operator to resubmit both staging flags and can otherwise finish an optional v56-only rehearsal. Then choose a closed Docker mechanism that consumes the exact v57 bundle without making the target input writable, broadening the fixed endpoint/API allowlist, accepting arbitrary archive destinations, pulling/building unreviewed images, or starting the target container. Bind a daemon-consumption receipt to the v57 digest and current generation, prove crash/retry/cleanup/collision behavior, and keep every execution/backend/Artifact flag false. Only after that gate should termination, running-container orphan recovery, output collection, and atomic Artifact commit be designed. HTTP/React mutation, Rust analyzers, broader network/secret support, real end-user execution, and CTF solving remain deferred.

‎docs/TASK_BOOK.md‎

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -214,6 +214,7 @@ P7 已推进到 schema v47:schema v41 为每个 Run 固定 `code|cyber` 工作
214214
- [x] v56 定向测试覆盖未知 create 后恢复、单次 create、already-absent、无关同名保护、释放/过期接管、旧 generation fencing、双 Store 竞态、原子 v55/v56 completion、隐私、不可变 SQL、v55 升级和 CLI。全仓普通/race、vet/staticcheck、模块/漏洞、17 项前端测试、OpenAPI/构建/audit、仓库隐私/链接/编码扫描、diff 和隔离真实二进制 smoke 均通过;高频 transport/Store/Application 恢复回归通过。GitHub Actions run `29388724727` 已通过功能提交 `e1710bb`,Go 与 TypeScript 作业分别用时 2 分 32 秒和 23 秒。
215215
- [x] schema v57 增加独立宿主输入捕获门禁:Linux 使用 `openat2` 固定工作区根与只读树,`RESOLVE_NO_XDEV` 禁止跨挂载点,`O_PATH` 在内容打开前拒绝 FIFO/特殊文件;目录和单文件 mount 均支持,symlink/magic-link/hard-link 与资源越界失败关闭。重新核对 descriptor 后生成确定性 tar,在 sealed `memfd` 中复读校验,并把 metadata-only evidence 绑定当前 v56 attempt、计划、container-ID 指纹、输入摘要和 lease generation。
216216
- [x] v57 的 intent/result、事件与 CLI 保持路径/正文/fd/raw container ID/私有 lease 不落库;SQL 禁止 pending intent 绕过 completion,失败先清理停止容器,接管恢复不重复 create。随机 row ID 不参与语义指纹,跨 Store 独立重试收敛;漏交恢复确认在 acquire 前拒绝且不消耗 failure slot。定向测试覆盖 rename/replace/delete/symlink/hard-link/FIFO/单文件、有界目录枚举、取消、重放、generation fencing、迁移和隐私;全仓普通/race、静态/漏洞、前端与隔离二进制门禁通过。
217+
- [x] v57 GitHub Actions run `29396264276` 已通过提交 `8719dff`,Go/Linux 3 分 55 秒、TypeScript 23 秒。首次 run `29395980413` 仅暴露单文件测试夹具未覆盖目录工作路径,修复为合法目录+单文件混合 mount 后 Linux 运行测试通过,生产实现未变。
217218
- [ ] schema v58 先把“必须捕获宿主输入”的选择持久化到 v56 daemon stage 之前,再设计并实现 daemon-owned immutable handoff,让 Docker 实际消费 v57 固定的字节且不放宽只读根/输入、固定端点和闭合 API;在 handoff 证据完成前,v57 必须保持 `daemon_consumed=false`、`execution_evidence=false`。
218219
- [ ] 完成 v58 后再单独实现并审计 per-run start/wait/kill/orphan 生命周期。
219220
- [ ] 本地代码默认只读挂载,输出目录独立可写。

0 commit comments

Comments
 (0)