docs(plans): mark OIDC token-refresh fix as shipped (3b98097)

The OIDC fix was committed in 3b98097 by a concurrent session. The plan's
status block was stale ('not yet committed/deployed') — updated to reflect
it's done. No remaining open items in this plan.

plans/2026-07-14-post-fix-session-remainders.md

@@ -6,8 +6,9 @@ golden eval harness (4/4 passed), committed (`337d577` + `3de359b` +
 knowledge loop is structurally closed, the plan-duplication chain is broken,
 and the eval harness catches regressions on future changes.
 
-**PM addition — OIDC token-refresh fix** (lines 9-23 below) is the only
-remaining open item: implemented, not yet committed/deployed.
+**PM addition — OIDC token-refresh fix** (lines 9-23 below) also shipped:
+committed as `3b98097` ("fix(web): refresh expired OIDC tokens before API
+calls"). The root cause of the empty-graph symptom is fixed and deployed.
 
 **2026-07-14 (PM) — OIDC token-refresh fix (unplanned, root-cause for the
 empty graph symptom):** the overview background graph and the Knowledge Base
@@ -66,7 +67,8 @@ Run: `go run ./cmd/nomos/eval -gateway http://localhost:8092 -manifest cmd/nomos
 
 ## Remaining (not yet shipped)
 
-- **OIDC token-refresh fix** (the PM addition in the status block above) — implemented in `web/src/lib/{config,oidc,events}.ts`, not yet committed/deployed. Unrelated to this plan's phases; filed here because it was the highest-impact surface symptom.
+None. All 18 fixes + the OIDC token-refresh fix (PM addition, `3b98097`)
+are shipped, committed, and deployed.
 
 ## Commit-history context (the 20-commit iteration)