test: verify conversational birth-time rectification

2026-07-21 14:40:43 +08:00
parent de9a687779
commit ffaa7dc9c5
9 changed files with 1138 additions and 22 deletions
@@ -0,0 +1,27 @@
+# User-reported birth-time flow issues — 2026-07-20
+
+This ledger records the five reported product failures and the evidence needed
+to close them. It contains no copied authentication header, cookie, token,
+email, user UUID, or real birth record. The original plan described this file as
+an existing modification target; it did not exist in this checkout, so Task 12
+created it.
+
+`verified-local` means deterministic contract tests and the equivalent local
+PostgreSQL 14 workflow pass. It is deliberately not `closed`: closure also
+requires an authenticated synthetic production smoke whose health Git SHA is
+the tested deployment SHA.
+
+| Issue | Reported failure | Current status | Local evidence | Production closure artifact |
+| --- | --- | --- | --- | --- |
+| ISSUE-BT-001 | A chat appeared impossible to delete, or a late response could recreate it. | verified-local | `20260720000000_chat_delete_and_dynamic_candidate_confirmation.sql`; `frontend/tests/chat-session-delete-contract.test.ts`; Task 12 synthetic flow deletes the chat while retaining the account case. | Authenticated synthetic delete plus account-case reload, tied to `/api/health` deployment SHA. |
+| ISSUE-BT-002 | A new chat could not establish a fresh rectification interaction and unfinished progress was coupled to chat state. | verified-local | `20260720010000_conversational_rectification_schema.sql`; account-level resume in `frontend/tests/conversational-rectification-e2e.test.ts` across two route clients; Task 9 current-chat consent tests. | Authenticated new-device/new-chat resume smoke tied to the deployed SHA. |
+| ISSUE-BT-003 | Confirming a candidate such as `17:15` surfaced `The string did not match the expected pattern`. | verified-local | Atomic v3 confirmation in `20260720030000_conversational_rectification_transitions.sql`; client retry/fallback and mismatched-then-exact confirmation in `frontend/tests/conversational-rectification-e2e.test.ts`; PG14 confirmation/rollback runtime suite. | Authenticated production exact-candidate confirmation with old-time preservation, plus transient deployment-error probe. |
+| ISSUE-BT-004 | Choosing `都不符合` surfaced the same raw English pattern error. | verified-local | The actual orchestrator treats `都不符合` as a normal direction change; Task 12 E2E advances the durable turn and preserves the single fee; client maps terminal 502/non-JSON failures to stable Chinese copy. | Authenticated production `都不符合` action followed by reload/resume, tied to the deployed SHA. |
+| ISSUE-BT-005 | Initialization used generic broad-year choices and lost the rich card/chat rectification analysis. | verified-local | Task 9 onboarding soft gate; v3 narrative grounding rejects broad-year questionnaires; Task 12 asserts candidate boundary, D1/D9/D10 layers, three domain rationales, free text, and year/month event request; `20260721010000_conversational_legacy_import_projection.sql` imports old unfinished work once with `migration_waived`. | Authenticated synthetic first-turn snapshot and one legacy import smoke tied to the deployed SHA. |
+
+## Release decision
+
+All five issues remain `verified-local` until the production closure artifacts
+above are attached. A public 200 response, an unverified browser session, or a
+local in-memory test cannot change them to `closed`. The deployment sequence and
+non-destructive rollback are defined in `deploy/README.md`.