From aa1f247d80b0cf48672a2f668b755ce5e2b0e28c Mon Sep 17 00:00:00 2001
From: Mathieu Moran <mathieumoran1@gmail.com>
Date: Tue, 11 Aug 2026 01:23:39 -0400
Subject: [PATCH] docs(bugs): record Phase 26 deploy/verify status for BUG-03
 and BUG-05

Amend the Phase 26 progress note: BUG-03 was deployed to the Pi (pulled to
4f975ad, service active, /api/health ok) and real in-car behavior verification
is still pending; BUG-05 is code-ready but the unraid/server side is not yet
deployed (needs docker compose build api && docker compose up -d api).
---
 PLAN.md | 9 ++++++++-
 1 file changed, 8 insertions(+), 1 deletion(-)

diff --git a/PLAN.md b/PLAN.md
index f72244c..43bba9a 100644
--- a/PLAN.md
+++ b/PLAN.md
@@ -1907,7 +1907,14 @@ each poll, `/api/dtc` falls back to persisted state when OBD is offline, `get_ov
 fixed to use the real `dtc` table, cleared/since tracked via `IS_SET`/`FIRST_SEEN_AT`/
 `LAST_SEEN_AT`, plus a schema migration and `tests/test_dtc_persistence.py`). **BUG-05** ✅ FIXED
 (commit `e2f2314` — server route `speed_source` mirrors the Pi's `obd if speed>0 else gps`).
-Both pending deploy/verify. The remaining items (BUG-01, 02, 04, 06, 07, 08) stay open.
+**Deployment status 2026-08-11 (tested on prod per owner workflow):** BUG-03 was pulled to the Pi
+(`git pull --ff-only` to `4f975ad`, 8 commits fast-forwarded) and `yaris-obd.service` restarted —
+service is **active** and `/api/health` returns `status: "ok"`. The `dtc` table migration runs on
+next DB init; DTC persistence begins on the next successful OBD poll. Real-world verification
+(actual DTC codes from a drive; `/api/dtc` + `/api/stats` reflecting persisted state) is still
+pending an in-car check. **BUG-05** is code-ready but the **server/unraid side has NOT yet been
+deployed** (needs `docker compose build api && docker compose up -d api` after review) and is
+unverified. The remaining items (BUG-01, 02, 04, 06, 07, 08) stay open.
 
 **Acceptance for Phase 26:** every `BUGS.md` entry in scope is fixed, regression-tested, deployed,
 marked resolved, and the corresponding fix recorded here.