Preserve current support contact requests through the handoff workflow

ROADMAP.md

@@ -1,6 +1,8 @@
 # Mira roadmap
 
-**Current October28:** #91 merged a461f86. Its exact rollout c42efc65 passed startup and the normal how-to smoke. The broken-device reply preserved earlier restarts and delivered the full case privately, but applied Limitless-specific guidance without identifying the hardware. Independent review classified that as failed source applicability; rollback toa9c9508/a6ef6b22 is verified healthy and the third smoke held. #90 integrates #91:1,258/offline8 and independent240-check review pass; final-head review/CI precede merge. This does not fix unknown source applicability or produce a new generated score. Hold further releases while #83 receives a general offline repair and required review; no paid run, memory enablement or customer-resolution claim. Scores64/100 implementation and56/100 delivery remain unchanged.
+**October29 current checkpoint:** Main cffb46b; successful rollback baseline a9c9508/a6ef6b22, one active and auto-deploy off on the fresh read. #90 metadata provenance does not enforce hardware applicability; do not deploy it as the failed smoke’s repair. Three open drafts: #92 bounded current-contact actor, #93 production metadata trace (1,266 full/8 offline, independent review, exact-head CI40918151890 PASS), #94 evidence policy/adversarial checks (1,266 full/8 policy groups and independent scoped review pass, but refund-approval and hardware-applicability probes remain genuinely red). #94 policy is not installed or required on main yet; branch protection/rule reads show no effective requirements. The master plan records installation/accuracy limits. No paid run, merge, deployment, optional enablement or new Discord test; third smoke held. Scores64/56 unchanged. Older checkpoints below are history where superseded.
+
+**Current October28:** #91 merged a461f86, then its rollout failed source applicability despite passing context preservation/private delivery. Rollback baseline a9c9508/a6ef6b22 is verified healthy. #90 merged cffb46b after1,258 tests,8 no-model checks, independent integration/final review and exact-head/merged-main Node20/24/PostgreSQL CI; it is not deployed. The earlier PR queue is closed; one new current-contact draft is being prepared under #83. #83 now has three red synthetic reviewer diagnostics plus a passing ordinary-answer control, and an actual-handler unresolved-FAQ failure plus useful-detail control. These are offline injected diagnostics, not an implemented applicability repair or live-model accuracy. The October29 draft preserves a bounded current contact next actor through the existing redirect owner and shared escalation policy; no new model field, prompt or store. Its final review/CI and applicable quality gate remain. Trustworthy source applicability and arbitrary contradiction resolution are still open; this draft does not repair the failed hardware smoke. Further releases and the third smoke remain held; no paid run or memory enablement. Scores64/100 implementation and56/100 delivery unchanged.
 
 **Earlier October26 checkpoint:** #86 merged647b549 after1202/no-model8, exact-head hosted Node20/24/real PostgreSQL, independent review and merged-main CI. [Lifecycle details](docs/GITHUB_NOTICE_LIFECYCLE.md). The old PR backlog is cleared; new work is Mira repository presentation and local #83 source provenance/conflict handling. #62 stays open for reproduced narration/context loss despite merged diagnostics. Production stays c6f482d; no paid run, public Omi test issue or memory enablement. Main implementation64/100; delivery56/100;44 left. Technical identifiers remain unchanged under the Mira product name.
 

docs/ANSWER_QUALITY_CONTRACT.md

@@ -1,10 +1,13 @@
 # Customer answer quality: repair checklist
 
+**October30 status clarification:** Older dated diagnostics below describe their tested commits, not current refund-filter implementation. #95 financial filtering is merged on main9b7154d and not deployed; #96 device applicability and #94 acceptance/enforcement remain pending. #92 is a narrow current-contact handoff repair, not general #83 completion. Use SUPPORT_MASTER_PLAN.md for current gates and avoid treating historical probe results as present implementation.
+
+
 Updated October 26, 2026. This is an implementation contract, **not a claim that these checks are all built or live**. It extends A1/A2/A4, B2 and E2 in the [master plan](SUPPORT_MASTER_PLAN.md); memory and the reviewed improvement loop keep their existing gates.
 
 ## Priority and status
 
-The [master plan](SUPPORT_MASTER_PLAN.md) takes precedence. The old PR queue is cleared; #71/#75/#82 closed unmerged with unresolved requirements retained. #91 context preservation is merged at a461f86; its rollout failed source applicability and was rolled back. Context/delivery passed, but that does not waive the failed grounding check. #90 provenance integrates that main and awaits final review/CI; the frozen staff-flagging defect is rejected by both integrated #90 and current main. Shared unresolved-next-step/applicability weaknesses remain #83; no new paid run is authorized by these implementation checks. Preserve the maximum of three open PRs.
+The [master plan](SUPPORT_MASTER_PLAN.md) takes precedence. The old PR queue is cleared; #71/#75/#82 closed unmerged with unresolved requirements retained. #91 context preservation is merged at a461f86; its rollout failed source applicability and was rolled back. Context/delivery passed, but that does not waive the failed grounding check. #90 provenance is merged as cffb46b after final review/CI; the frozen staff-flagging defect is rejected by both integrated #90 and current main. Shared unresolved-next-step/applicability weaknesses remain #83; no new paid run is authorized by these implementation checks. Preserve the maximum of three open PRs.
 
 | Order | Customer failure to prevent | Required regression / acceptance | State |
 | --- | --- | --- | --- |
@@ -45,3 +48,8 @@ One customer problem per draft PR. Record baseline failure, passing checks at th
 ### Relative merge gate — Aryan's October 26 direction
 
 Require no material final-answer failure absent from main, no tested protected-handoff regression, and a candidate pass count at least as high as main. Zero material failures is not the gate; track inherited weaknesses separately. Compare final replies/decisions, not a main draft later corrected by review. Preserve frozen grades. Reusing earlier generated evidence requires demonstrated relevant source/runtime/config identity and full saved results; review the restored diff and pass current checks. This grants no new provider quota, deployment, optional enablement or risk waiver.
+
+
+## October29 diagnostic coverage, not accuracy completion
+
+#90 is merged but remains unreleased because declared provenance is not an enforced device-applicability verdict. New draft #94 adds six original fictional no-model boundary stress probes through production owners. Customer instruction role separation, off-topic suppression/person protection, invented staff receipt and ordinary sourced-answer controls pass. Refund-approval text and unidentified-hardware guidance remain actual acceptance failures; CI must stay blocked until a general repair makes those assertions pass with relevant controls/review. Injected hostile replies test application acceptance, not live-model injection resistance or protected-set coverage. #93’s metadata trace is a separate observation-only draft; no customer/model text is logged and no quality point is earned. #92 remains a partial next-actor repair. The maximum of three open PRs is reached and the third smoke/release remain held.

docs/ARCHITECTURE.md

@@ -1,6 +1,8 @@
 # Mira architecture
 
-**Current October28:** #91 merged a461f86. Its exact rollout c42efc65 passed startup and the normal how-to smoke. The broken-device reply preserved earlier restarts and delivered the full case privately, but applied Limitless-specific guidance without identifying the hardware. Independent review classified that as failed source applicability; rollback toa9c9508/a6ef6b22 is verified healthy and the third smoke held. #90 integrates #91:1,258/offline8 and independent240-check review pass; final-head review/CI precede merge. This does not fix unknown source applicability or produce a new generated score. Hold further releases while #83 receives a general offline repair and required review; no paid run, memory enablement or customer-resolution claim. Scores64/100 implementation and56/100 delivery remain unchanged.
+**October29 current checkpoint:** Main cffb46b; successful rollback baseline a9c9508/a6ef6b22, one active and auto-deploy off on the fresh read. #90 metadata provenance does not enforce hardware applicability; do not deploy it as the failed smoke’s repair. Three open drafts: #92 bounded current-contact actor, #93 production metadata trace (1,266 full/8 offline, independent review, exact-head CI40918151890 PASS), #94 evidence policy/adversarial checks (1,266 full/8 policy groups and independent scoped review pass, but refund-approval and hardware-applicability probes remain genuinely red). #94 policy is not installed or required on main yet; branch protection/rule reads show no effective requirements. The master plan records installation/accuracy limits. No paid run, merge, deployment, optional enablement or new Discord test; third smoke held. Scores64/56 unchanged. Older checkpoints below are history where superseded.
+
+**Current October28:** #91 merged a461f86, then its rollout failed source applicability despite passing context preservation/private delivery. Rollback baseline a9c9508/a6ef6b22 is verified healthy. #90 merged cffb46b after1,258 tests,8 no-model checks, independent integration/final review and exact-head/merged-main Node20/24/PostgreSQL CI; it is not deployed. The earlier PR queue is closed; one new current-contact draft is being prepared under #83. #83 now has three red synthetic reviewer diagnostics plus a passing ordinary-answer control, and an actual-handler unresolved-FAQ failure plus useful-detail control. These are offline injected diagnostics, not an implemented applicability repair or live-model accuracy. The October29 draft preserves a bounded current contact next actor through the existing redirect owner and shared escalation policy; no new model field, prompt or store. Its final review/CI and applicable quality gate remain. Trustworthy source applicability and arbitrary contradiction resolution are still open; this draft does not repair the failed hardware smoke. Further releases and the third smoke remain held; no paid run or memory enablement. Scores64/100 implementation and56/100 delivery unchanged.
 
 **Earlier October26 checkpoint:** #86 merged647b549 after1202/no-model8, exact-head hosted Node20/24/real PostgreSQL, final independent review and merged-main CI. Its30-day subject-time replay guard, customer erasure and non-starvable cleanup are on main, awaiting release. [Lifecycle details](GITHUB_NOTICE_LIFECYCLE.md). Production stays c6f482d; no paid run, public Omi test issue or memory enablement. The product name is Mira; technical identifiers are stable. Separate #83 source-provenance work is local and not an accuracy claim.
 

docs/RUNBOOK.md

@@ -1,6 +1,11 @@
 # Mira operations runbook
 
-**Current October28 operator receipt:** #91 mergeda461f868ad097ec93512aeaf111d63f4e4c96997 and was deployed asc42efc65-0efb-4ca2-adca-f5f93627b37f, created20:05:37IST. Exact merged-main CI, rollback availability/cadence/source/off-state preflight, startup/health/schema/login and one running instance passed. Normal phone-only how-to smoke passed. The second smoke preserved the symptom/earlier attempts and delivered one matching private staff card, but improperly applied Limitless-specific guidance to unidentified hardware. Independent review called this a grounding failure. Under Aryan's failure rule, deploymentRollback of verified914a38f0/a9c9508 returnedtrue. Replacementa6ef6b22-26b3-4744-ab8d-e067311ff7da/a9c9508, createdOctober28 at20:27:42IST, is SUCCESS/latest/one running; health/schema/login pass with zero matched startup failures and optional/automatic deployment controls off. Earliest cadence-only window isOctober29 at20:27:42IST; applicability repair/review remains a separate release hold. Third smoke and further releases are held. #90 is not deployed. No environment/settings changes, paid rerun, memory enablement or agent Discord posts. [Master plan](SUPPORT_MASTER_PLAN.md) controls current status.
+**October30 current checkpoint:** GitHub main9b7154d includes #90 provenance, #93 trace and #95 financial-outcome filtering. Live remains verified rollback a9c9508/a6ef6b22; nothing from that newer main is deployed. #92 current-contact integration passes local1,290/8 plus independent runtime review; current-head CI and final docs disposition precede merge. #96 device applicability is draft for deterministic/accuracy gates; reviewer requires a specifically approved paid comparison after repairs. #94 remains draft until fixes and exact-current checks pass; required-check installation is reserved to Aryan. Three open PRs are #92/#94/#96. No quota, deployment, optional feature or Discord input is activated by this checkpoint. [Master plan](SUPPORT_MASTER_PLAN.md) controls current status; earlier checkpoints retain history only.
+
+
+**Historical October29 checkpoint (superseded below and by the master plan):** Main cffb46b; successful rollback baseline a9c9508/a6ef6b22, one active and auto-deploy off on the fresh read. #90 metadata provenance does not enforce hardware applicability; do not deploy it as the failed smoke’s repair. Three open drafts: #92 bounded current-contact actor, #93 production metadata trace (1,266 full/8 offline, independent review, exact-head CI40918151890 PASS), #94 evidence policy/adversarial checks (1,266 full/8 policy groups and independent scoped review pass, but refund-approval and hardware-applicability probes remain genuinely red). #94 policy is not installed or required on main yet; branch protection/rule reads show no effective requirements. The master plan records installation/accuracy limits. No paid run, merge, deployment, optional enablement or new Discord test; third smoke held. Scores64/56 unchanged. Older checkpoints below are history where superseded.
+
+**Historical October28 operator receipt:** #91 mergeda461f868ad097ec93512aeaf111d63f4e4c96997 and was deployed asc42efc65-0efb-4ca2-adca-f5f93627b37f, created20:05:37IST. Exact merged-main CI, rollback availability/cadence/source/off-state preflight, startup/health/schema/login and one running instance passed. Normal phone-only how-to smoke passed. The second smoke preserved the symptom/earlier attempts and delivered one matching private staff card, but improperly applied Limitless-specific guidance to unidentified hardware. Independent review called this a grounding failure. Under Aryan's failure rule, deploymentRollback of verified914a38f0/a9c9508 returnedtrue. Replacementa6ef6b22-26b3-4744-ab8d-e067311ff7da/a9c9508, createdOctober28 at20:27:42IST, is SUCCESS/latest/one running; health/schema/login pass with zero matched startup failures and optional/automatic deployment controls off. Earliest cadence-only window isOctober29 at20:27:42IST; applicability repair/review remains a separate release hold. Third smoke and further releases are held. #90 merged cffb46b after all review/CI gates and remains not deployed. The previous PR queue is cleared; the separate new #83 current-contact draft is not merged or deployed. #83 source-applicability investigation and the narrow current-contact draft are in [SOURCE_APPLICABILITY_BOUNDARY.md](SOURCE_APPLICABILITY_BOUNDARY.md); no third-smoke input or automatic release is scheduled. No environment/settings changes, paid rerun, memory enablement or agent Discord posts. [Master plan](SUPPORT_MASTER_PLAN.md) controls current status.
 
 Do not delete receipt/cutoff rows to force webhook replay. The candidate ignores stale payload subject times, holds uncertain outcomes and retains a minimal customer/time cutoff after owner erasure; cleanup is mandatory even with optional features off. Fixed notice-retention errors mean pending cleanup, not erased records. An unexpected populated pre-lifecycle schema fails closed for review. Use an existing linked synthetic issue/thread for the next approved-release smoke; no new public issue.