From fde001a9c959880e11868b6cc7082b491e6c90ac Mon Sep 17 00:00:00 2001 From: YokiiroBW Date: Mon, 27 Jul 2026 14:58:54 +0800 Subject: [PATCH] docs: record D5 D6 deployment verification --- docs/运维记忆错题本.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/运维记忆错题本.md b/docs/运维记忆错题本.md index 573c245..e6088bf 100644 --- a/docs/运维记忆错题本.md +++ b/docs/运维记忆错题本.md @@ -318,7 +318,7 @@ - Root cause: the calendar event type and its private Bot-memory ownership were conflated with a second, non-queryable domain. - Fix or workaround: retain `bot_calendar_event` as a Bot-private event with reality level `calendar_event`; retire the direct calendar writer; remove the domain constant, migration target, historical injection marker, and archive flag. - Prevention rule: a contract type may remain supported only through its real producer; do not preserve a second storage domain when the public write path rejects it. -- Validation evidence: targeted D5/D6 regressions and `pytest -q --ignore=tests/test_security_cache.py` passed 325 tests plus 8 subtests. +- Validation evidence: targeted D5/D6 regressions and `pytest -q --ignore=tests/test_security_cache.py` passed 325 tests plus 8 subtests; commit `e884138` is deployed, VM hashes match, D5 is true, no D6 core references remain, service is active, and `NRestarts=0`. - Supersedes: the 2026-07-24 Q4.2 calendar-history write path. ## 2026-07-27 - Default user-fact session isolation @@ -328,4 +328,4 @@ - Root cause: two bridge entrypoints used contradictory defaults for the same `strict_session_only` policy. - Fix or workaround: `bridge_query_user_facts` now defaults the omitted flag to `True`; callers can only relax it by explicitly supplying `false`. - Prevention rule: every user-fact lookup must inherit the same default isolation policy as archive search; cross-session negative tests must exercise the public bridge path. -- Validation evidence: the D5 bridge-to-visibility negative test, focused migration/contract tests, and 325 pytest tests plus 8 subtests passed. \ No newline at end of file +- Validation evidence: the D5 bridge-to-visibility negative test, focused migration/contract tests, and 325 pytest tests plus 8 subtests passed; commit `e884138` is deployed with matching VM hashes, active service, and `NRestarts=0`. \ No newline at end of file