test(freeze-guard): keep the sync8 freeze paths in the forbidden list (issue #159)
The sync9b edit replaced the two sync8 entries in IDENTITY_FORBIDDEN_PREFIXES instead of appending after them, so the guard covered two records instead of four while still passing. Restore the sync8 pair under its own comment and keep the sync9b pair after it. The freshness test passes again (9) and the frontend confirmation-gate test for the moved sealed report passes (8). Co-Authored-By: Grok (agent loop)
This commit is contained in:
jesse-ux
co-authored by
Grok (agent loop)
Grok (agent loop)
parent
8015e8efb7
commit
cbe665107f
@@ -45,7 +45,7 @@ Python 快速门、前端 tsc / lint / build、`npm test`、`test:db` 没跑：
|
||||
| --- | --- | --- | --- |
|
||||
| `tests/test_varga_bphs.py::test_22nd_drekkana_counts_forward_from_lagna_drekkana` | `expected = (drekkana_ref(asc_lon) + 21) % 12` | 固定 `3`（巨蟹），保留 `offset_from_lagna_drekkana == 22` | 旧断言把「+21」的错口径抄进了测试；换成书上的固定反例（射手 D3 起，第 8 宫为巨蟹） |
|
||||
| `tests/test_cli_smoke.py::test_full_reading_exposes_sensitive_point_modules` | `definition == "Cancer-2, Scorpio-1, Pisces-3"` | `definition == "Cancer-2, Cancer-3, Scorpio-1, Scorpio-2, Pisces-3"` | BUG-1494 改的就是这个定义字符串；仍逐字比对，没有放宽 |
|
||||
| `tests/test_sealed_holdout_contract_freshness.py` 排除前缀 | 排除到 `upstream_sync8_2026_10_18` | 增加 `upstream_sync9b_2026_10_28` 两条 | ERR-110 另存新冻结，旧记录留在清单外 |
|
||||
| `tests/test_sealed_holdout_contract_freshness.py` 排除前缀 | 排除到 `upstream_sync8_2026_10_18` | 新增 `upstream_sync9b_2026_10_28` 两条，原有条目全部保留 | ERR-110 另存新冻结，旧记录留在清单外；第 1 次打回时补回被误删的 sync8 两条 |
|
||||
| `frontend/tests/rectification-confirmation-gate.test.ts` 读取与断言路径 | `…upstream_sync8_2026_10_18.json` | `…upstream_sync9b_2026_10_28.json` | 合同当前指针移到新报告；注释补第 11 条三栏 |
|
||||
| `scripts/research/sealed_holdout_rerun.py`、`reported_offset_sweep.py` 的 `FREEZE` / `REPORT` | `…upstream_sync8_2026_10_18` | `…upstream_sync9b_2026_10_28` | 同上，ERR-110 |
|
||||
|
||||
@@ -58,3 +58,11 @@ Python 快速门、前端 tsc / lint / build、`npm test`、`test:db` 没跑：
|
||||
|
||||
- Windows 跑 Python 测试要 `PYTHONUTF8=1`，否则子进程按 GBK 编码，遇到警告符号会 `UnicodeEncodeError`，看起来像引擎崩了。
|
||||
- 前端测试没跑（任务书不要求，且本单没改前端产品代码）。
|
||||
|
||||
## 第 1 次打回（2026-10-28）
|
||||
|
||||
- 被验 SHA：`5c5f333d4d93fb691c10790988d3d4c986ac1bd3`；修复单 `docs/tasks/TASK-upstream-sync9b-fix-20261028.md`
|
||||
- 错在哪：改 `IDENTITY_FORBIDDEN_PREFIXES` 时把第八轮的两条**替换**掉了，清单从 4 条变成 2 条；测试照样通过，但守门变弱（第八轮的冻结记录混进打分身份也不会再被发现）
|
||||
- 改了什么：把第八轮两条加回原来的注释下面，第九轮乙批两条保留 —— 现在清单同时含 sync8 与 sync9b 共 4 条；本文件「断言三栏」对应行改成「新增两条、原有全部保留」
|
||||
- 跑过：`tests/test_sealed_holdout_contract_freshness.py` 9 passed；`frontend/tests/rectification-confirmation-gate.test.ts` 8 passed（`node node_modules/tsx/dist/cli.mjs --test tests/rectification-confirmation-gate.test.ts`，工作树里 `frontend/node_modules` 已存在，没有重跑 `npm ci`）
|
||||
- 没有重跑上游两个测试文件和校正 20 / 900：本次不改计算代码
|
||||
|
||||
@@ -51,8 +51,10 @@ IDENTITY_FORBIDDEN_PREFIXES = (
|
||||
# 原值: 排除到 scoring_perf_2026_10_13
|
||||
# 新值: 再排除 upstream_sync8_2026_10_18 两份冻结路径
|
||||
# 原因: sync8 改了冻结身份文件，输出不变，ERR-110 另存新记录
|
||||
"docs/research/sealed_holdout_rerun_upstream_sync8_2026_10_18",
|
||||
"docs/research/reported_offset_upstream_sync8_2026_10_18",
|
||||
# 原值: 排除到 upstream_sync8_2026_10_18
|
||||
# 新值: 再排除 upstream_sync9b_2026_10_28 两份冻结路径
|
||||
# 新值: 再排除 upstream_sync9b_2026_10_28 两份冻结路径（追加，不替换上面的）
|
||||
# 原因: sync9b 改了扩展身份里的 scripts/varga.py，回放输出不变，ERR-110 另存新记录
|
||||
"docs/research/sealed_holdout_rerun_upstream_sync9b_2026_10_28",
|
||||
"docs/research/reported_offset_upstream_sync9b_2026_10_28",
|
||||
|
||||
Reference in New Issue
Block a user