fix(rectification): keep invite collect CHECK-legal after kind mapping (BUG-656)
Independent Staging Quality Gate / validate (push) Successful in 9m14s
Independent Staging Quality Gate / publish (push) Successful in 2m12s

Full TAP failed because invite_more is not a target_kind enum value, and
exhaustion re-decide after skipped targeted persist must reuse decideAfterInferenceChange.

Co-authored-by: Cursor <cursoragent@cursor.com>
This commit is contained in:
Jesse_Chen
2026-09-12 06:34:35 +08:00
co-authored by Cursor
parent eae049d0ea
commit 529fcc097f
6 changed files with 52 additions and 6 deletions
@@ -23,7 +23,14 @@
- `rectification-server-focus.test.ts` + `rectification-probe-pool-exhausted-20260911.test.ts` + `rectification-surface-state.test.ts` + `rectification-replay-20260911.test.ts`**51 / 51**
- Python`test_candidate_discriminator_contract.py` + `test_rectification_event_probes.py`fail=0`.venv/bin/python -m pytest`
## 门禁跟进(2026-09-12
- Independent Staging Quality Gate run 2568 / SHA `eae049d0`validate 失败,`npm test --prefix frontend` **fail 4 / 3132**
- 原因不是基础设施:全量 TAP 才跑到的既有用例被 CHECK 映射和第三次 `decideFromDossier` 打坏
- `invite_more` 不再写入 `target_kind`CHECK 不允许),改断言 `null` + `collect_kind=invite_more`
- `persistExhaustionCollect` 定向 persist skipped 后改走已有的 `decideAfterInferenceChange`idle 源码切片仍是两次 `decideFromDossier`BUG-653
- 本机补跑上述 4 个失败套件后再推 staging
## 未做
- 未 commit / 未 push
- 未部署后按场景 0c 真机走一遍