From 9d6da53b8f55304fd8c05920cf0f5fdd11c87454 Mon Sep 17 00:00:00 2001 From: "Morten V. Christiansen" Date: Mon, 27 Apr 2026 13:17:58 +0200 Subject: [PATCH] Update Workplan current status: phases 6.5/7/9 all externally gated Co-Authored-By: Claude Sonnet 4.6 --- Workplan.md | 13 +++++++------ 1 file changed, 7 insertions(+), 6 deletions(-) diff --git a/Workplan.md b/Workplan.md index 0e39763..ea39e52 100644 --- a/Workplan.md +++ b/Workplan.md @@ -549,12 +549,6 @@ Exit criteria: ## Current Next Step -- fido2-direct is now the deployed default; keep it as the baseline for regression runs. -- Push the next engineering cycle toward Phase 6.5 limits: - - reproduce and narrow the `~10` in-flight request ceiling on the browser-facing `k_client -> k_proxy` Qubes forward - - separate Qubes forwarding churn from app-level issues with targeted concurrency probes and log capture -- Keep the regression helpers as the fast check that transport, auth, session reuse, and counter semantics still hold after each change. - Status (2026-04-27): - fido2-direct mode confirmed working end-to-end with real card via browser on k_client. - Full register → login → counter → logout flow verified with physical card button presses. @@ -562,6 +556,13 @@ Status (2026-04-27): - 100-test unit suite added for k_proxy (tests/test_k_proxy.py); runs locally without card or VMs. - All three service files refactored and re-deployed. +Phase status (2026-04-27): +- Phase 6.5 (concurrency): deferred. Ceiling (~10 in-flight) is acceptable until multi-card use cases arrive. +- Phase 7 (firmware build/flash): blocked on Chrome Roads (card vendor). No local action until that discussion concludes. +- Phase 9 (phone integration): awaiting go-ahead. When approved: Flutter app (iOS + Android) replaces k_proxy; FIDO2 over WiFi to card; depends on Phase 7 firmware capability. + +No active engineering work is unblocked at this time. Resume when Chrome Roads responds or Phase 9 is approved. + Status (2026-04-26, markdown maintenance): - Re-scanned `Setup.md`, `Workplan.md`, and `PHASE5_RUNBOOK.md` against the current workspace files. - Updated the plan to match the verified state: