5 Commits

Include renames

Author	SHA1	Message	Date
agent-bot	ee1e53b510	fix(tests): per-package test databases + legitimate approval fixtures (issue #2 close) ... Root causes of the remaining 5 CI PG failures (and the hidden flaky set): 1. All PG-integration packages shared ONE database under parallel package execution - migrations/seeds/truncates raced (nondeterministic failure sets, locally and in CI). Fix: RequireTestDatabaseURL/SkipIfNoTestDatabaseURL now derive a per-package database (<base>_<pkgHash>, advisory-lock-guarded CREATE); 9 raw-env straggler tests funnelled through the helpers; db-package tests call it unqualified (no import cycle). 2. Approval-chain fixtures were not production-shaped: freezeReviewSnapshot only honors head_snapshot_id, fake content hashes never froze a snapshot, so ApproverApprove rejected with 'approved requires frozen review_snapshot_id'. Errors were swallowed (_, _ =) hiding this. Fix (ownership-respecting, arch-enforced): - docrevision.SeedContentSnapshotForTest seeds the ledger tables it owns - docgov GovernanceEngine.FreezeHeadSnapshotForTest freezes head/review pointers on document_records (docgov-owned) and clears engine cache - all four integration fixtures use the pair; swallowed errors checked 3. Fixed-name fixtures collide once a package shares one DB (projects uq_projects_name_global): uniquified in projectinstance + server tests. 4. CAS/ctxmgr tests never bootstrapped migrations (relied on other packages having migrated the shared DB): explicit RunMigrationsOnceForTest. Verified: full parallel short suite = 75 packages, 0 failures against an isolated throwaway PG. CI skip list removed - short tests fully required.	2026-09-29 09:54:43 +00:00
weichen	f3f23a3018	feat(errcode): 用稳定错误码记录 HTTP 与异步失败 ... 失败响应此前不写日志，request_id 无法对照原因。注册表不覆盖处理器已经给出的 HTTP 状态。	2026-09-28 02:27:16 +00:00
weichen	aee774b894	fix(ctxmgr): keep displaced deterministic narrative for rollback-safe replace ... Runtime verification found the deterministic generator merges the prior served narrative, so a replaced (semantic) narrative would linger after rollback. Store the displaced deterministic narrative in the shadow report (persisted via shadow_json) and merge that instead when the prior summary source is semantic_replace.	2026-09-25 23:14:07 +00:00
weichen	ffa41d78df	feat(ctxmgr): wire fail-closed gray REPLACE for chat semantic narrative ... Unseal SEMANTIC_SUMMARY_REPLACE under explicit user authorization with a defense-in-depth session allowlist (SEMANTIC_SUMMARY_REPLACE_SESSIONS): swap happens only for allowlisted sessions after result digests and served watermark validation, bounded narrative size; facts/counts stay deterministic and the daily digest stays advisory. Master flag alone replaces nothing.	2026-09-25 22:56:36 +00:00
WeiCHEN	056e4e5c4b	feat(chat): productionize semantic summary shadow path without REPLACE	2026-09-22 21:51:20 +08:00