Repository navigation
Preserve PostgreSQL checkpoint history and recover backups beyond 20,000 commits - #8759
Conversation
Signed-off-by: LoopX Agent <337587101+loopx-agent@users.noreply.github.com>
Signed-off-by: LoopX Agent <337587101+loopx-agent@users.noreply.github.com>
Signed-off-by: LoopX Agent <337587101+loopx-agent@users.noreply.github.com>
Signed-off-by: LoopX Agent <337587101+loopx-agent@users.noreply.github.com>
Signed-off-by: LoopX Agent <337587101+loopx-agent@users.noreply.github.com>
Signed-off-by: LoopX Agent <337587101+loopx-agent@users.noreply.github.com>
Signed-off-by: LoopX Agent <337587101+loopx-agent@users.noreply.github.com>
Signed-off-by: LoopX Agent <337587101+loopx-agent@users.noreply.github.com>
Signed-off-by: LoopX Agent <337587101+loopx-agent@users.noreply.github.com>
Signed-off-by: LoopX Agent <337587101+loopx-agent@users.noreply.github.com>
Signed-off-by: LoopX Agent <337587101+loopx-agent@users.noreply.github.com>
…rk-source-image-return-20261114 Signed-off-by: LoopX Agent <337587101+loopx-agent@users.noreply.github.com>
Signed-off-by: LoopX Agent <337587101+loopx-agent@users.noreply.github.com>
…rk-source-image-return-20261114 Signed-off-by: LoopX Agent <337587101+loopx-agent@users.noreply.github.com>
…-pg-seed exporter - Add authority_checkpoints table DDL and tenant-scoped RLS policies. - Store incremental delta in authority_commits and bounded checkpoints every 64 commits and on genesis cursor 1, resolving table bloat and the 20,000 commit recovery ceiling. - Implement scanCommitted bounded delta replay from covering checkpoint via AuthorityStateReplay. - Add setupPostgreSqlAuthoritySchemaAndRole for explicit schema installation and least-privilege restricted role assembly. - Add exportLocalToPgGenesisSeed with sanitization (expired leases, local absolute paths, .local/ references, Feishu IDs, private materials) and fail-closed privacy boundary scan. - Add loopx postgres setup and loopx postgres local-to-pg-seed CLI commands. - Add test suites for checkpoints, sanitization, role assembly, and CLI invocation. Signed-off-by: LoopX Agent <337587101+loopx-agent@users.noreply.github.com>
…rk-source-image-return-20261114 Signed-off-by: LoopX Agent <337587101+loopx-agent@users.noreply.github.com>
Signed-off-by: LoopX Agent <337587101+loopx-agent@users.noreply.github.com>
loopx-agent
left a comment
There was a problem hiding this comment.
Reviewer: model_agent · gpt-6.1-sol · OpenAI · runtime_reported · reasoning_effort=max
Request changes conclusion (author-owned PR; GitHub blocks formal self-review)
审阅提交 bda7463f66f39324960fb9f468d7f8ef3b43c818,GitHub 目标基线 859a23ee9534539536343206e23452253528dd07,实际合并基点 859a23ee9534539536343206e23452253528dd07。
[P1] 新格式写入后无法重建已提交的历史。 对隔离 PG 16.15 同一 Goal 提交三笔,用生产 scanCommitted 读回;再在旧库升级一次、新写一笔后重试。 旧库历史在迁移后、新写入之前可读,写入第四笔后返回 provider_read_unavailable;新库三笔同样无法扫历史。真实 store suite 旧版 397/397,新版 386/397。共享 AuthorityStateReplay 只提供 apply,当前调用了不存在的 applyDelta;最新 head/原回执仍存在,所以只核对 latest 会误判。 改为调用现有 apply 并补上原有完整游标、缺行拒绝与迁移/恢复测试。运行 npm run typecheck:control-plane 和 npm run test:postgresql-authority-store;覆盖旧库升级后新写入,再从原游标回放。 代码位置
[P1] 按新 setup 建成的受限角色无法提交第一笔事务。 实际运行 loopx postgres setup --execute 创建受限运行角色;使用该角色给空 Goal 提交首笔,游标 1 会写检查点。 setup 显示 installed,角色对检查点只有 SELECT/INSERT。首笔 SQL 使用 ON CONFLICT DO UPDATE,即使没有冲突也需要 UPDATE,PostgreSQL 返回 42501,事务回滚且没有 head。 复用现有锁和唯一约束,检查点走只追加的 INSERT,避免给普通运行角色修改过去检查点的权限。让真实 setup 生成的受限角色完成首次写入、普通更新和跨检查点写入,并确认跨租户与改删历史仍被拒绝。 代码位置
动机 / Motivation
管理员在隔离 PostgreSQL 中准备用最小权限运行共享权威存储,并要在更新后读回历史工作和回执。 一个已有三笔提交的 Goal 升级后还能读回原有历史,但以新格式写入第四笔时,提交成功,整段历史却读不出来。 迁移和恢复依赖可读的历史;如果只核对当前 head 或只读当前回执,会把不可恢复的状态当成已经交付。 引入有界检查点能减少重复存储;实测现有 seed 的正常提交可读回,但新格式历史回放和受限角色首笔提交仍失败。 本轮只评估 PG 检查点、管理员设置、隔离种子导出和受影响的现有读写;部署、切流及整组三切片验收仍待独立工作。
改动思路 / Approach
PostgreSqlAuthorityStore 持有事务与租户过滤;AuthorityStateReplay 管增量格式;仅显式管理员准备 schema。 CLI 校验管理员或导出参数 → effect router → PostgreSQL 事务读写/File 导出 → 同事务 head、历史与回执;恢复阅读旧或新记录。 迁移只变数据库存储格式;检查点、增量、事件和回执同时提交。种子 preview 不连接目标数据库。 维持现有全投影可保读回但存储继续增长;复用共享回放和现有事务 owner 可达到目标。独立发布紧耦合的写入与读回会留下不可恢复的存量。 让 PostgreSQL 直接沿用 File 和 SQLite 的现有回放接口,并把普通写入保持为追加;管理员设库应与运行时种子提交拥有不同权限。 本轮只评估 PG 检查点、管理员设置、隔离种子导出和受影响的现有读写;部署、切流及整组三切片验收仍待独立工作。
具体改动 / Changes
规范依据:docs/architecture/rfcs/shared-goal-authority-state-provider-v0.md,修订 859a23ee9534539536343206e23452253528dd07。按已有存储与服务约束核对,不把隔离 PG 中的局部成功当成部署资格。 +1538/-21(7 个运行时文件、3 个测试文件)。 四个 CLI/facade 文件走同一 effect handler;两个 TS owner 承担设库、授权、检查点回放、种子导出;三个文件是单测和 CLI 回归。
- history_exact 未满足。每笔已提交的历史投影和回执可完整读回,迁移前后同语义。 对应代码或规范
- restricted_runtime 未满足。管理员建库,受限 runtime 可以提交但不能改历史或跨租户。 对应代码或规范
- service_isolation 已验证。现有服务继续按租户和数据库身份拒绝错配。 对应代码或规范
关键代码讲解
installPostgreSqlAuthorityStoreSchema:安装或升级检查点表、RLS 和增量字段。事务中核实原 incarnation,旧历史行保留;不匹配回滚。commitAuthority:受限事务在首个游标写检查点。首笔即命中 ON CONFLICT UPDATE 所需权限;SQL 42501 时首笔整事务回滚。scanCommitted:从近处检查点向前重建历史。共享回放接口名错误,任何新的非检查点 delta 无法处理;TypeError 被包装为 provider_read_unavailable。setupPostgreSqlAuthoritySchemaAndRole:创建受限的 NOLOGIN 组角色和表级授权。检查点表只有 SELECT/INSERT;保持追加语义,而非赋予改历史权限。handle_postgres_command:导出或显式提交种子。未要求写入时不向目标传 URL;无需自动迁移或配置变更。
对主干的风险 / Risks
- PASS · 旧版真实 PG 权威契约。基线 397/397,0 skip。
- PASS · 服务鉴权 / 轮转 / 远程事务和正常 CLI。11+40 项真实 PG 服务与远程测试、19 项 Python、21 项 Node 单测通过;Node 单测含一项独立跳过。普通 seed preview、显式提交和重复目标拒绝实测。
- FAIL · 历史 Todo、迁移、扫描、受限调用。386 通过、11 失败,0 skip。另用真实旧库与新库重现;当前 head 可读但历史 unavailable。
- FAIL · 仅用 setup 生成角色的首笔写入。42501 权限错误,零 head;最小权限合同未达。
- FAIL · 共享回放和 effect runtime 类型。基线通过;当前 4 处类型错误,包括不存在的回放方法和 handler 输入类型。
- FAIL · 差异空白。两个新增测试在 EOF 有空行。
语义与 CI 对齐
本地类型检查另报四处新错误:回放接口不存在、缺少事务类型、seed 局部收窄丢失,以及 effect handler 入参不满足通用边界。请修类型而非把未知输入直接断言成 seed 请求。 在同一 PG 16.15 服务器中,旧版 397 项全部通过,新版 386 通过、11 失败;首次新格式写入后历史扫描 unavailable,且受限角色首笔写入因缺少检查点 UPDATE 权限失败并回滚。 在现有回放 owner 改用实际接口,验证游标连续和历史恢复;检查点使用单次 INSERT,由同事务、主键和原有回执处理重复;再让管理员 setup 和受限连接分开验收。 仅隔离 PostgreSQL 16.15 与源码 CLI;未验证已安装分发、生产部署、三切片联合、20,000+ 历史容量或托管 CI。当前实测失败足以保留合入阻断。
我的整体评价 / Verdict
REQUEST_CHANGES。当前新历史会阻断长期恢复,受限运行角色会阻断用户首次写入。两项都有真实 PG 反例。回放修复与最小权限写入通过后再做联合 PG 检查。 已有 PostgreSQL 部署执行 schema 更新后会写入新历史格式;旧版对新格式的读取与回滚未建立。PR 描述覆盖新功能,但低估了既有 PG 恢复调用面。 让 PostgreSQL 直接沿用 File 和 SQLite 的现有回放接口,并把普通写入保持为追加;管理员设库应与运行时种子提交拥有不同权限。 本轮只评估 PG 检查点、管理员设置、隔离种子导出和受影响的现有读写;部署、切流及整组三切片验收仍待独立工作。
English verdict: REQUEST_CHANGES at bda7463. On PostgreSQL 16.15 the new delta path cannot replay committed history, and the role created by setup cannot append its first checkpoint. Repair both on the real store and keep runtime privileges append-only.
Signed-off-by: LoopX Agent <337587101+loopx-agent@users.noreply.github.com>
…ge-return-20261114 Signed-off-by: LoopX Agent <337587101+loopx-agent@users.noreply.github.com>
Signed-off-by: LoopX Agent <337587101+loopx-agent@users.noreply.github.com>
Signed-off-by: LoopX Agent <337587101+loopx-agent@users.noreply.github.com>
…ge-return-20261114 Signed-off-by: LoopX Agent <337587101+loopx-agent@users.noreply.github.com>
Signed-off-by: LoopX Agent <337587101+loopx-agent@users.noreply.github.com>
…ge-return-20261114 Signed-off-by: LoopX Agent <337587101+loopx-agent@users.noreply.github.com>
Signed-off-by: LoopX Agent <337587101+loopx-agent@users.noreply.github.com>
Signed-off-by: LoopX Agent <337587101+loopx-agent@users.noreply.github.com>
Signed-off-by: LoopX Agent <337587101+loopx-agent@users.noreply.github.com>
Signed-off-by: lusendong.6789 <lusendong.6789@bytedance.com> Co-authored-by: TRAE CLI <traecli@bytedance.com>
…reviewed-20261115 test(core): require installed provenance before qualification
Signed-off-by: lusendong.6789 <lusendong.6789@bytedance.com> Co-authored-by: TRAE CLI <traecli@bytedance.com>
Load the optional PR reconciler only after the invocation-time observation permission check, inside the existing provider failure boundary. Preserve original permission, cadence, result and unknown-effect owners, and document the bounded default-closure and timing-window change. Signed-off-by: lusendong.6789 <lusendong.6789@bytedance.com> Co-authored-by: TRAE CLI <traecli@bytedance.com>
Signed-off-by: lusendong.6789 <lusendong.6789@bytedance.com> Co-authored-by: TRAE CLI <traecli@bytedance.com>
* Skip automatic usage observers for supported opt-outs Signed-off-by: lusendong.6789 <lusendong.6789@bytedance.com> Co-authored-by: TRAE CLI <traecli@bytedance.com> * Record installed Core and C1 observer qualification Signed-off-by: lusendong.6789 <lusendong.6789@bytedance.com> Co-authored-by: TRAE CLI <traecli@bytedance.com> --------- Signed-off-by: lusendong.6789 <lusendong.6789@bytedance.com> Co-authored-by: TRAE CLI <traecli@bytedance.com>
…comparison (#8760) * docs(blog): add EdgeBench controlled Context ON vs OFF 10-task score comparison Signed-off-by: LoopX Agent <337587101+loopx-agent@users.noreply.github.com> * docs(blog): use declarative mechanism-led opening in zh context-delivery score section Signed-off-by: LoopX Agent <337587101+loopx-agent@users.noreply.github.com> --------- Signed-off-by: LoopX Agent <337587101+loopx-agent@users.noreply.github.com>
Signed-off-by: LoopX Agent <337587101+loopx-agent@users.noreply.github.com>
* Package the manager discovery projection Signed-off-by: lusendong.6789 <lusendong.6789@bytedance.com> Co-authored-by: TRAE CLI <traecli@bytedance.com> * Record selected manager discovery distribution qualification Signed-off-by: lusendong.6789 <lusendong.6789@bytedance.com> Co-authored-by: TRAE CLI <traecli@bytedance.com> --------- Signed-off-by: lusendong.6789 <lusendong.6789@bytedance.com> Co-authored-by: TRAE CLI <traecli@bytedance.com>
…ontract (#8816) Signed-off-by: LoopX Agent <337587101+loopx-agent@users.noreply.github.com>
Signed-off-by: LoopX Agent <337587101+loopx-agent@users.noreply.github.com>
…moke-20261115 Keep creation-only intent in the saved Goal browser check
…s into one owner (#8826) reviewer_recommendation.py restated the trust and freshness sets that repository_context.py already owns. Import both as aliases of the owner objects so the decision has a single source, and add an architecture guard that pins single ownership by value, by identity, and by wiring through both public builders. REVIEWER_SOURCE_KINDS stays local (deliberately narrower). Signed-off-by: psychologister <230141834+psychologister@users.noreply.github.com> Co-authored-by: psychologister <230141834+psychologister@users.noreply.github.com>
…llow-up route (#8708) * fix(scheduler): reject superseded heartbeat receipts on the Python follow-up route The Python compatibility route for scheduler-ack-current/scheduler-fail-current checked only that the receipt for --turn-instance-id exists; a receipt already superseded by a newer heartbeat Turn still committed scheduler state, while the native TypeScript transaction rejects it as heartbeat_receipt_stale. Thread the Turn from build_scheduler_followup_payload through record_quota_scheduler_ack / record_quota_scheduler_ack_for_decision / record_quota_scheduler_failure_for_decision into _run_native_followup, which now sends turn_instance_id with require_heartbeat_receipt=true. The TypeScript transaction remains the single owner of the missing/stale/superseded fence (it also rechecks under the scheduler state lock); optional parameters keep the in-process API, which has no Turn, unchanged. Fixes #8605 Signed-off-by: Lihua <1017343802@qq.com> * Keep scheduler follow-up hint reads out of legacy migration Signed-off-by: LoopX Agent <337587101+loopx-agent@users.noreply.github.com> --------- Signed-off-by: Lihua <1017343802@qq.com> Signed-off-by: LoopX Agent <337587101+loopx-agent@users.noreply.github.com> Co-authored-by: LoopX Agent <337587101+loopx-agent@users.noreply.github.com>
* fix(replan): resume settlement after lifecycle review writeback Signed-off-by: LoopX Agent <337587101+loopx-agent@users.noreply.github.com> * Recover committed replan settlement before rebuilding its review Signed-off-by: LoopX Agent <337587101+loopx-agent@users.noreply.github.com> --------- Signed-off-by: LoopX Agent <337587101+loopx-agent@users.noreply.github.com>
Signed-off-by: LoopX Agent <337587101+loopx-agent@users.noreply.github.com>
Signed-off-by: LoopX Agent <337587101+loopx-agent@users.noreply.github.com>
* Recheck captured work before launching an external Turn host Signed-off-by: LoopX Agent <337587101+loopx-agent@users.noreply.github.com> * Keep complete-source metadata assembly outside Turn planning Signed-off-by: LoopX Agent <337587101+loopx-agent@users.noreply.github.com> --------- Signed-off-by: LoopX Agent <337587101+loopx-agent@users.noreply.github.com>
…-upgrade-8759-20261115 Signed-off-by: LoopX Agent <337587101+loopx-agent@users.noreply.github.com>
Signed-off-by: LoopX Agent <337587101+loopx-agent@users.noreply.github.com>
Signed-off-by: LoopX Agent <337587101+loopx-agent@users.noreply.github.com>
loopx-agent
left a comment
There was a problem hiding this comment.
Reviewer: model_agent · gpt-6.1-sol · OpenAI · runtime_reported · reasoning_effort=max
Approval conclusion (author-owned PR; GitHub blocks formal self-approval)
评审提交 2aae8f435ea8dabfb745c1d92923afb7e327e009。GitHub 记录目标 6dfd1c90c4c1a186c43de0a2c05243fa14b5a76e。相对本地核定的实际合并基点 f7e3f427197bab6c66ab535e26613a7f9c2fdbe0 检查差异和复现。
动机 / Motivation
需要升级或从备份恢复长期运行 Goal 的 PostgreSQL 管理员与运行方,需要在受限账号下继续写入,并能核对旧提交的原回执。 v0 保留每笔提交的完整投影。旧备份检查在超过 20,000 笔历史时拒绝导出,长历史的恢复因此停在导出阶段。 管理员显式升级后,运行角色可追加 checkpoint 与 delta。既有提交仍可核验,超过 20,000 笔的历史也能导出并恢复到独立存储。
让仍持有 v0 日志权限的运行角色跨版本读取并继续写入。对长期运行的合成 Goal,导出 20,001 笔历史,恢复到另一独立数据库,再验证原回执和最终状态。 在真实 PostgreSQL 16.15 上,旧角色直授及组继承、跨 checkpoint 页和损坏拒绝均通过。20,001 笔历史恢复后,完整归档审计一致,抽检游标 1、64、65、20,000、20,001 的原回执一致。 本轮使用隔离 PostgreSQL 16.15、真实 TLS 和合成 Goal。只覆盖 PG1 的存储、恢复和显式管理 CLI。 PG2、PG3 与 PG1 还需用精确组合验证 App 业务、恢复和并发写入,再确认部署资格。
改动思路 / Approach
沿用既有存储事务、归档导入与审计。历史成功读回通过同一个重放器恢复,而 seed 仅复制合成头到空目标,使用原事务回执恢复重试。 运行角色沿用 schema setup 的同一锁和事务迁移;历史页从覆盖页首的 checkpoint 或旧完整投影重放。归档保留原事务,seed 路径仅用于合成目标。 File 和 SQLite 分别以两个真实 CLI 并发 seed,均复用同一 cursor 1 回执并只提交一次。第三次调用保持输出文件身份、权限和字节。 本轮使用隔离 PostgreSQL 16.15、真实 TLS 和合成 Goal。只覆盖 PG1 的存储、恢复和显式管理 CLI。
默认 File/SQLite 仍走同样的本地准入。新增 seed 在显式调用时可预览,目标必须由管理员显式配置并执行。共享恢复检查允许分段核验长历史,命令帮助列出新增入口。 主干验收 候选说明 相关评审或宿主接线
具体改动 / Changes
20 个文件,新增 1,869 行、删除 132 行。生产变化集中于 PostgreSQL 日志与权限、显式 seed 命令和共享恢复,另有双语规范和回归测试。
关键代码讲解
- 在已有 store identity 与写锁下完成 v0→v1 的 schema 和 checkpoint 权限准备。 installPostgreSqlAuthorityStoreSchema
- 从恰当的覆盖 checkpoint 重放到请求页,对缺失、错误摘要及不完整前缀拒绝读。 scanCommitted
- 校验 seed 内容与已存在的文件,在空目标落下合成记录,并在重跑时恢复原回执。 exportLocalToPgGenesisSeed
- 以固定页验证归档的全部历史、末尾游标、身份和投影摘要。 authority history verification
- 核对语义捕获字段,区分归档末端 seal 与文件 bytes 的 witness。 decodeAuthorityBackupCapture
对照 f7e3f427197bab6c66ab535e26613a7f9c2fdbe0 的验收。 规范
- PG1-原回执与历史。跨格式的每个提交保持原事件、原回执与可核验投影。 在真实 PostgreSQL 16.15 上,旧角色直授及组继承、跨 checkpoint 页和损坏拒绝均通过。20,001 笔历史恢复后,完整归档审计一致,抽检游标 1、64、65、20,000、20,001 的原回执一致。
- PG1-管理员与隔离。setup 显式发生,普通运行角色在事务和租户边界内续写。 实际受限角色写入通过。缺失或损坏 checkpoint 拒绝读;同存储恢复拒绝且目标仍为空;错误文件与符号链接在目标提交前拒绝。
- PG1-独立恢复。完整历史按独立存储身份恢复且可审计。 在真实 PostgreSQL 16.15 上,旧角色直授及组继承、跨 checkpoint 页和损坏拒绝均通过。20,001 笔历史恢复后,完整归档审计一致,抽检游标 1、64、65、20,000、20,001 的原回执一致。
- PG1-合成 seed。重复调用恢复原回执,拒绝覆盖不匹配的输出或非空目标。 File 和 SQLite 分别以两个真实 CLI 并发 seed,均复用同一 cursor 1 回执并只提交一次。第三次调用保持输出文件身份、权限和字节。
对主干的风险 / Risks
运行角色从旧表 ACL 继承权限后跨 checkpoint 续写;随后尝试损坏历史、同存储恢复、重复 seed 或指定已存在的错误输出文件。 实际受限角色写入通过。缺失或损坏 checkpoint 拒绝读;同存储恢复拒绝且目标仍为空;错误文件与符号链接在目标提交前拒绝。 先静止旧写入方并保留可验证的 v0 备份。自定义列级权限通过受限角色显式配置;升级后复验读历史和续写。
本地双语/差异/边界 canary 6 项直接检查和 4 项选择检查全过,TypeScript 类型检查通过。源码 Python 67 项、实际 PG Store 398 项、远端协议 47 项、归档 18 项通过。服务套件 10 项通过(含 2 项实库),1 项独立 DSN 占位跳过。 全树 digest owner 检查在实际合并基点与候选各有同一失败。匹配器在不受本 PR 修改的 Chat/Lark 路径;本 PR 的历史摘要、归档语义摘要与回执另有独立实库验证。保留这项仓库合并检查失败。
我的整体评价 / Verdict
APPROVE。 PG1 具备这一独立增量的技术通过条件。仓库合并门槛和其余 PG 子项仍需各自验收。 PG2、PG3 与 PG1 还需用精确组合验证 App 业务、恢复和并发写入,再确认部署资格。 检查 postgres setup、seed 与 state recovery CLI 的入口。候选无页面渲染改动,无需截图。
English verdict: APPROVE at 2aae8f4. PostgreSQL 16.15 retained restricted-role access and restored 20,001 commits to an independent database with matching receipts and a full archive audit. Concurrent seed replay committed once. The identical base/head digest-owner failure remains a repository check.
PostgreSQL v1 retains a complete, verifiable journal with append-only checkpoints for restricted runtime roles. The offline backup verifier also reads through a captured frontier above 20,000 commits.
Review fixes
SELECTandINSERTgrants, including group grants, into the checkpoint table. Optional runtime-role provisioning and the format change share the existing PostgreSQL transaction. The released v0 client can still read its original receipt after an intentionally failed role provision, and the same restricted worker can cross cursor 65 after the successful upgrade. History changes and schema changes remain denied to the runtime role.The retained journal and recovery archive continue to carry history, events and receipts. The administrative seed command operates on a sanitized synthetic head. See the exact-head review and schema upgrade, rollback and seed instructions.
Same-workload local PostgreSQL run
PostgreSQL 16.2, 20,001 actual commits per format, an 8,312-byte projection, one original event and one original receipt per commit. The same native archive owner exported and audited both formats through cursor 20,001 and obtained the same final projection digest.
An isolated target restored all 20,001 commits from the 10.9 MiB archive through ordinary writes in 50.22 s, then independently matched the full journal and original receipts in 5.70 s. The entire client run used 55.61 CPU-seconds and 291.9 MiB maximum RSS. This was one local sample. Database process CPU and RSS, multi-tenant throughput, deployment capacity, and the earlier PostgreSQL 16.15 sample have separate measurement boundaries.
Validation at
2aae8f435ea8398 real PostgreSQL store tests, 11 service tests, 47 remote authority tests, 4 real archive interchange tests, 73 Python CLI and recovery tests, and 17 diff-selected premerge validators passed. The exact-head TypeScript typecheck, Ruff, mypy, bilingual RFC and public-diff checks also passed. The 73 Python cases include full SQLite backup verification at 20,001 commits. Manifest counts retain exact positive-decimal validation, and the independent archive audit verifies the claimed history.
The full TypeScript suite passed 6,544 tests with 89 expected skips and one duplicate digest-owner failure. The full Python suite reported a similar architecture failure after 4,327 passes and was stopped for diagnosis. The same failing checks reproduce at the unchanged base
f7e3f427197b: one native child result matcher in TypeScript and duplicate Chat/Lark matchers in Python. These failures hold the managed quality gate. The Python suite beyond that point remains unverified.Fresh independent review and hosted CI are pending. Joint PostgreSQL service and cutover qualification remains with the related delivery program.