Files
CyberGril/docs/requirements/handoff-HEL-896.json
T
zonggongandmultica-agent c121c42e39 HEL-896 release completion: the A/B/C budget becomes an executable two-instance split, the real-browser false positive is fixed precisely (product untouched), the SDK gap list is corrected to the honest 41-distribution closure with the pip-download erratum, and release archiving becomes a consistency snapshot - (1) budget split: the manager's independent review reproduced on a temp store that writing A's total_requests=55 into the shared product ledger blocks B's mem0_extract and C's dialogue_main with budget_total_requests_exhausted:55/55 while budget_total/request_usage/token_usage have no stage or authorization-source column; docs/budget-package-hel895.md gains §6 making the split executable: A lives ONLY on the isolated 8360 team-test instance with its own DB and models.yaml (55/500000 one-shot totals plus same-value daily category caps), the user instance NEVER carries one-shot totals (its budget_total rows are record-only, no gate), A is sealed by stop+consistent-snapshot archiving with budget_total never zeroed and restart/archive proving the seal holds, old test data has no import path into the user instance (release checklist forbids copying the 8360 data dir), B starts only after baiqizhi approval writes llm_cap/embed_cap per the 500+180 formula with the authority frozen prefix, the real-Mem0 smoke is counted INSIDE B's 60/180, B cap-hit queues batches (no retry burn, no lost rows, FTS fallback, chat uninterrupted) and first-week end requires a fresh approval to continue, and §6.4 gives one responsible limited recommendation (A 55/500k isolated, B 60 LLM/180 embeds, C daily table) plus errata for the two unsafe original claims ('A shares C's daily account' and 'WAL single file copies whole'); tools/verify_budget_split_hel896.py 8/8 on temp stores and stand-ins only (S0 exact-shape repro of the manager's finding, S1 team instance consumes the §1 step plan to 55 then hard-stops with the tightest gate winning - life daily 8/8 rejects before the total, S2 seal survives restart and backup-API archive, S3 user instance B/C unblocked after A with dialogue 60/semantic 40/daily-token stacking and rejections booking nothing, S4 the misconfigured-total guard on the user instance, S5 repo configs and authoritative facts untouched, real caps all stay 0); (2) browser false positive fixed without touching any product file: web/tests/hel895_real.mjs B3 used '!!stage || any visible button' and clicked the FIRST button containing 回 which is the 日子与回忆 home nav button, so stage=false still PASSed and the screenshot stayed on days - the verbatim original rerun reproduces the false 7/7 with B3 stage=false (docs/rework/hel896/browser-before/), and the revised test passes 9 checks by precise interaction: B2 asserts the letter card carries her exact words plus the talk-nav unread aria-label, B3a waits for the VISIBLE reach card (aside.reach.show, aria-hidden=false, non-zero box, exact words) over days, B3b clicks only THAT card's 回她 button and strictly asserts the conversation stage .conversation .sr contains the reach-out text with the unread mark cleared, B4/B5 prove dedup by server message id (data-mid in the record panel: zero duplicates, gap and live reach-outs each exactly once), B5 asserts /api/health epoch bumps exactly +1 (1->2) before rechecking, B6 counts the page's OWN permissions.query/getUserMedia calls from first document load (0/0, instrumented via Page.addScriptToEvaluateOnNewDocument after Page.enable), B7 runs the service under a temp loopback models config (CYBERGRIL_MODELS, all caps 0) plus a sitecustomize socket guard that REJECTS and eagerly reports non-loopback connects (0 attempts, 0 non-loopback DNS lookups, report survives signal death) - under precise interaction the stage really plays, unread really clears, dedup and epoch semantics really hold: it was a test defect, not a product defect, so no interface change and nothing to escalate; (3) SDK honesty: tools/audit_sdk_offline_hel896.py (read-only, zero downloads/installs/inference) computes the 3.11-Linux closure from the installed 3.10 pinned metadata - 55 dists, 41 missing from the product venv (28 pure + 13 native incl. grpcio/numpy/onnxruntime/tokenizers/sqlalchemy/protobuf), all three top-level pins are py3-none-any (no 'cp311 wheel' needed for them), mem0ai's installed direct_url is the local fixed source hel857-src and hel857-data/mem0-2c81af3.tar.gz hashes exactly to the lock's 9dcef930...dda23 (an index mem0ai==2.2.1 wheel proves nothing), the wheel built during hel857 lived only in an ephemeral cache and hatchling is not offline-available, exactly 3 of the 41 are cache-reusable today for 3.11 (greenlet 3.5.6 cp311, pillow 12.3.0 cp311, truststore 0.10.5 py3-none-any - version+tag verified), the fastembed model cache is measured (Qdrant/bge-small-zh-v1.5 + bm25, ~92MB, placement = instance data dir copy), and the seq48-51 pip event is settled by cache forensics: uv's pip-26.2.2 wheel entry (files.pythonhosted.org, sha256 fd7f4dfa...) was CREATED 2026-10-27 02:10:04 inside the HEL-895 run window as the ONLY new cache entry, so that step DID fetch from the network - the prior card's zero-download claim is corrected to 'download' by the conservative reading (byte-level download vs conditional request is indistinguishable from cache evidence) while the lock install itself added no new cache entries; deploy/hel895-release-candidate.md §4 is rewritten to this accurate list, all future installs forced offline/no-index; (4) release archiving: tools/release_snapshot_hel896.py implements the two safe modes (stop+wal_checkpoint(TRUNCATE)+copy, or online SQLite backup API), writes per-file sha256 manifests carrying the exact code commit, per-table row-count verification and a verify-mode rollback drill; its selftest reproduces the manager's WAL finding (online naive copy of the main .db: 'no such table: companion') and proves both fixed modes complete (backup API and checkpoint copies both hold companion=1/chat_message=1, archive hashes+rows verify, commit 04eff61 recorded); §5 of the release doc now carries the copy-paste commands covering the product DB, semantic vector root, history root and the authoritative embed ledger, archives are never deleted, and the section explicitly does NOT claim R6 complete backup; regression on this head: pytest 299/299 (3.11.16 venv + requirements.lock offline), ruff clean (src/tests/tools), web typecheck 0 errors / lint 0 errors 1 pre-existing warning / vitest 55/55 / build passes with CSS still index-DdDYzR5S.css, pinned-SDK reruns all green (close-ownership 16/16, shutdown-queued 12/12, inflight 6/6, semantic-recovery 7/7, mem0-real 12/12, reports in docs/rework/hel896/regression/), check_release_offline R1-R7 passes, real-HTTP pagination 7/7 rerun saved as docs/rework/hel896/http-pagination-rerun.json with the original hel895 evidence byte-untouched, requirement checks 6/6 (origin/main, de8874a3803b, 152479b, each with and without handoff-HEL-896.json); handoff-HEL-896.json written; zero real LLM, zero real embeddings, zero new downloads beyond existing caches, authoritative ledgers and freezes (39/60, 498/500, 2 frozen, HEL-835 gate) untouched, not deployed, PR#11 appended-not-merged, no visual changes, R5/R6/R7 honestly deferred
Co-authored-by: multica-agent <github@multica.ai>
2026-10-27 03:06:23 +08:00

58 lines
9.4 KiB
JSON
Raw Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
{
"baseline_version": "1.11",
"read_commit": "04eff611e7d85e539d43717711172441420ac853",
"task": "HEL-896 发布补齐:按总管独立复审(附件 HEL-895-总管独立复审.md 及证据 zip)一次修正四项发布工程与如实记载——①A/B/C 可执行分账与阶段切换(临时库复现共库误配、独立团队测试实例+全新用户实例方案、封账/授权来源/叠加口径/停续语义、一次有限推荐);②修真实浏览器验证误报(精确点击可见留言卡回她、严格断言舞台文本/未读变化/消息ID去重/重启epoch+1、权限API调用计数0、临时回环配置+拒绝非回环连接,保留原误报证据+勘误+修后证据,不改视觉产品);③SDK 离线可复用部分与准确余缺(41 项闭包逐项分类、mem0 固定源码身份哈希核验、fastembed 模型缓存实测、seq48–51 pip 26.2.2 下载事件缓存取证与勘误);④发布归档/回退改一致性快照(WAL 丢失复现、停服+checkpoint 与 backup API 双口径、可审核产物/哈希/命令/代码提交对应,不冒充 R6 完成)。零真实 LLM、零真实嵌入、除既有缓存外零新增下载、不部署、不合并 PR、不交体验地址、不触 8300–8350 与共享语音口型、不访问 4080、不写权威账、真实 cap 保持 0、不改任何队员运行时/模型/认证、不导入测试档案为用户伴侣",
"requirement_ids": [
"CG-006",
"CG-008",
"CG-009",
"CG-011",
"CG-012",
"CG-013",
"CG-014",
"CG-015",
"CG-018",
"CG-021",
"CG-023",
"CG-029",
"CG-030",
"CG-031",
"VIS-013",
"AM-001",
"AM-002",
"AM-003",
"UX-001",
"UX-005",
"UX-006",
"GOV-001",
"GOV-002",
"GOV-003",
"GOV-004",
"GOV-005",
"GOV-006",
"DEL-001"
],
"deliverable": "分支 hel-870-assembly 正常追加 PR#11(不强推不合并):1) docs/budget-package-hel895.md 增 §6 可执行分账(独立团队测试实例 8360 独库独配置承载 A 的 55/500000 一次性总量、全新用户实例永不配置一次性总量、A 封账=停服+一致性快照归档+budget_total 永不清零、旧测试数据无导入用户库路径、B/C 开始的配置与授权来源、B 真实 Mem0 冒烟计入 60/180、B 到顶 queued 不丢行不耗重试、首周结束凭实际用量报告定停续、一次负责的有限推荐 A55/500k+B60/180+C 逐日顶),并勘误原文『A 当天同时受 C 类日顶约束』与『WAL 单文件整体归档』两处不安全表述;新增 tools/verify_budget_split_hel896.py 8/8(S0 共库误配复现与总管同形、S1 团队实例 55 硬顶+日顶取最紧、S2 封账跨重启跨归档、S3 用户实例 B/C 放行+日顶叠加+拒绝不落账、S4 误配守门、S5 仓库配置与权威事实零改动),证据 docs/rework/hel896/budget-split/budget-split.json;2) web/tests/hel895_real.mjs 修订(B2 信件卡精确断言+未读标记、B3a/B3b 导航日子→可见留言卡 aside.reach.show→只点该卡『回她』→严格断言 .conversation .sr 舞台原文+未读清零、B4/B5 服务器消息 ID data-mid 去重 0 重复、B5 epoch 恰 +1 实测 1→2、B6 页面自身 Permissions API/getUserMedia 调用计数 0、B7 临时回环 models.yaml+sitecustomize socket 守卫拒绝并计数非回环连接=0 且非回环 DNS=0);勘误前证据 browser-before/(原脚本逐字重跑 7/7 含 B3 stage=false 误报 PASS)、修后 browser/ 9/9;docs/rework/hel896/README.md 勘误说明;未改任何 web/src 产品代码,精确交互下舞台/未读/去重/epoch 语义真实成立,未发现产品行为缺陷;3) tools/audit_sdk_offline_hel896.py 只读审计:闭包 55 项/缺 41(纯 28+原生 13)逐项分类(立即可复用仅 greenlet cp311/pillow cp311/truststore py3-none-any 三项)、mem0ai 固定源码 direct_url+tarball SHA256 与 mem0-stack.lock 一致、索引同名 wheel 不作数、hel857 构建轮在临时缓存未持久、hatchling 离线构建待发布卡、fastembed 真实模型缓存 92MB 实测(bge-small-zh-v1.5+bm25)、pip 26.2.2 事件缓存取证(uv 条目创建于 2026-10-27 02:10:04、files.pythonhosted.org、窗口内唯一新增→该步发生了网络获取,前卡零下载不成立,按保守口径记为下载;requirements.lock 装机全部命中既有缓存);deploy/hel895-release-candidate.md §4 勘误为准确清单、后续安装强制 offline/no-index;4) tools/release_snapshot_hel896.py 一致性快照/回退工具(停服+checkpoint 与 backup API 双口径、逐文件 SHA256 MANIFEST、代码精确提交、逐表行数核对、verify 回退演练)自测 4/4:在线裸复制主 .db 复现 no such table: companion、backup API 与 checkpoint 两口径均完整、归档哈希与行数全过;§5 改一致性快照口径含照抄命令与覆盖范围(产品库/向量/推导史/权威账),不冒充 R6 完成;deploy/hel895-release-candidate.md 增 HEL-896 修订头与交付物表更新",
"acceptance": [
"分账方案可执行且经临时库+替身验证:tools/verify_budget_split_hel896.py 8/8 全过(共库误配复现与总管独立复现同形;团队实例 55 硬顶跨重启跨 backup API 归档不失效;用户实例无总量闸时 B/C 放行、日顶逐项到顶拒绝且拒绝不落账;误配总量守门;仓库配置与权威账零改动)",
"docs/budget-package-hel895.md §6 明确 A 封账步骤、B/C 开始配置与授权来源、旧测试数据不会转成用户伴侣(无导入路径+发布检查单禁复制)、全局累计与日顶叠加口径、B 到顶与首周结束的停/续授权语义、A stub 检查/真实 Mem0 冒烟/B 首周/C 日常关系、一次负责的有限推荐;原文两处不安全表述已勘误标注",
"浏览器验证误报修正:原脚本逐字重跑复现误报(B3 stage=false 仍 PASS,7/7 作废口径);修订版 9/9 全过——精确点击可见留言卡的回她、舞台 .conversation .sr 含留言原文、未读标记真实清零、记录 data-mid 全无重复且缺口/现场留言各恰一次、/api/health epoch 恰 +1(1→2)、页面自身权限 API 调用计数 0、非回环连接尝试 0 且非回环 DNS 0(回环配置+socket 守卫强制拒绝);产品代码零改动,原证据保留+勘误+修后证据三件齐",
"SDK 余缺准确清单:闭包 55/缺 41 与总管独立计算一致;三个顶层包 WHEEL 均 py3-none-any;mem0ai 固定源码身份(direct_url+tarball SHA256 与 lock 注释一致)核实;缓存可复用仅 3 项、其余 37 项+离线构建依赖准确留给发布卡不阻塞;fastembed 模型缓存实测 92MB 两模型;pip 26.2.2 事件取证明确(该步发生网络获取,前卡零下载勘误不成立,保守记为下载;lock 装机无新增缓存条目);本卡零下载零安装零推理",
"发布归档/回退一致性:在线裸复制丢 WAL 已提交行复现(no such table: companion);停服+checkpoint 与 backup API 双口径快照完整;归档含逐文件 SHA256+代码精确提交+逐表行数核对;verify 回退演练全过;§5 命令与覆盖范围(产品库/语义向量/推导史/权威账)可照抄,不删档,不冒充 R6 完整备份完成",
"全量回归在本 head 实跑:3.11.16 venv + requirements.lock 离线 pytest 299/299、ruff 干净(src/tests/tools);web typecheck 0 错、lint 0 错 1 条既有警告、vitest 55/55、build 通过 CSS 仍 index-DdDYzR5S.css;固定 SDK 回归(hel857-venv 3.10.12 替身+回环)verify_close_ownership_hel894 16/16、verify_shutdown_queued_hel889 12/12、verify_inflight_lifecycle_hel886 6/6、verify_semantic_recovery_hel885 7/7、verify_mem0_real_hel874 12/12、check_release_offline_hel882 R1–R7 15/15;真实 HTTP 分页合同 7/7;三目标需求检查各含/不含 handoff-HEL-896 共 6/6"
],
"deferred": [
"R5 语音仍由 HEL-878/879 接续;R6 天气/素材/完整备份(CG-009 每日自动备份与手动导出)未接入,本卡一致性快照只是发布归档/回退要求,不冒充完成",
"R7 有条件视觉观察继续保留;手机真机与 Safari 未验证",
"真实部署、体验地址、PR 合并、真实预算写入、SDK 41 项缺口的授权下载与离线并入、真实 Mem0 激活(B)与团队整体检查(A)执行:全部留给发布卡经总管向白栖知一次申请批准后执行;A/B/C 批准前所有 cap 保持 0 fail-closed",
"视觉方向讨论与整套界面验收仍由视觉总监线承接;本卡未改任何界面文件"
],
"requirement_changes": [],
"verification": [
"docs/rework/hel896/budget-split/budget-split.json(8/8)、docs/rework/hel896/browser-before/(误报复现)与 docs/rework/hel896/browser/(修后 9/9 + netguard 报告 + 截图 + run-commands.txt)、docs/rework/hel896/sdk-audit/sdk-audit.json+summary.md(含 pip 事件缓存取证)、docs/rework/hel896/release-snapshot/selftest.json(4/4)",
"HEL-895 原始证据 docs/rework/hel895/ 原样保留未改;总管复审附件与其独立证据 zip 引用见 docs/rework/hel896/README.md",
"回归命令与需求检查输出见交付评论;人工核对原话:GOV-006(01a1734c)、完整体验委托(01a1780e 原话『我觉得这是工程问题…直奔核心』)已由本卡阅读并在方案中落实为『不再问用户选择算法、直接接续已授权工程』",
"未验证:真机/Safari/手机、真实 LLM 与真实嵌入行为(本卡零真实调用)、目标发布机的实际归档执行(工具已自测,发布卡照抄)"
]
}