diff --git a/active.md b/active.md
index fb25a165..6b188a9d 100644
--- a/active.md
+++ b/active.md
@@ -13,3 +13,15 @@
- registered: 2026-08-19 by the wake_up session — the issuing session (claude/autofit-priors-messages-audit-ylvenv)
filed the prompt + issue but not this entry, tripping Lifecycle Drift on main.
- repos-none-claimed: this entry claims NO repos — one line deliberately, not 2-space bullets.
+
+## jax-stall-shared-preloads-retime-refutation
+- issue: https://github.com/PyAutoLabs/PyAutoMind/issues/328 (issued 2026-08-25)
+- issued: 2026-08-25
+- prompt: active/jax_stall_shared_preloads_retime_refutation.md
+- epic: jax-compile-stall (evidence-recording only; not a phase)
+- status: library-dev
+- worktree: ~/Code/PyAutoLabs-wt/jax-stall-shared-preloads-retime-refutation
+- repos:
+ - PyAutoMind (branch claude/weekly-smoke-timings-naming-012fuj)
+- note: web-github session — no local worktree created. Mind-only record change; parks nothing.
+
diff --git a/active/jax_stall_shared_preloads_retime_refutation.md b/active/jax_stall_shared_preloads_retime_refutation.md
new file mode 100644
index 00000000..77e759f2
--- /dev/null
+++ b/active/jax_stall_shared_preloads_retime_refutation.md
@@ -0,0 +1,119 @@
+# The 2026-08-24 retime returned `shared_preloads.py` to coverage; it stalled the next day
+
+Type: bug
+Target: ci
+Repos:
+- @PyAutoMind
+Epic: jax-compile-stall
+Difficulty: small
+Autonomy: safe
+Priority: medium
+Status: issued
+Filed: 2026-08-25
+Issued: 2026-08-25
+
+Evidence-recording task against the jax-stall ledger
+[`jax_vmap_jit_compile_stall.md`](jax_vmap_jit_compile_stall.md). Surfaced
+2026-08-25 by the `weekly-smoke-timings-naming` verification sweep
+(PyAutoHeart#182), which dispatched a full `workspace-smoke.yml` run and turned
+up a stall the ledger does not know about.
+
+## What was observed
+
+PyAutoHeart `Workspace Smoke` run **32902243623** (2026-08-25, `workflow_dispatch`),
+job `smoke / run_scripts (3.12, autolens_test, multi_dataset)` (97978549465).
+16 of 17 scripts passed:
+
+```
+scripts/multi_dataset/jax_likelihood/shared_preloads.py ... TIMEOUT (300s)
+```
+
+Its siblings in the same job, same commit, same runner:
+
+| Script | Result |
+|---|---|
+| `jax_likelihood/mge.py` | PASS 11.7s |
+| `jax_likelihood/rectangular_mge.py` | PASS 20.7s |
+| `jax_likelihood/mge_group.py` | PASS 49.3s |
+| `jax_likelihood/delaunay_mge.py` | PASS 20.2s |
+| `jax_likelihood/rectangular.py` | PASS 15.8s |
+| `jax_likelihood/shared_preloads.py` | **TIMEOUT (300s)** |
+
+A >6x outlier against the slowest sibling, with every other member of the family
+completing comfortably — the bimodal signature the ledger already uses to
+separate a stall from slowness.
+
+## Why this is not just another occurrence
+
+**The 2026-08-24 retime refuted this entry's SLOW marker and put it back in
+coverage. It hung on the next weekly run.**
+
+`shared_preloads.py` sat in the PyAutoHeart#74 "flakes at the 1800s cap" SLOW
+family. On 2026-08-24 that family was retimed (5 repeats per Python leg, 300s
+cap; runs 32741371308 + 32741386752) and eight entries "completed 5/5 on both
+legs (slowest 54.5s) and were removed — marker refuted, scripts back in mega-run
+coverage" (`autolens_workspace_test/config/build/no_run.yaml`, and
+`complete/2026/08/smoke-surface-retime-sweep.md`).
+
+Verified 2026-08-25 against `autolens_workspace_test` at `7fc497d`:
+
+- `config/build/no_run.yaml` — **no `shared_preloads` entry**. It is in mega-run
+ and weekly coverage.
+- `smoke_tests.txt` line 15 — still **commented out**, "disabled 2026-07-22:
+ exceeds the 300s smoke cap (measured 300s+ in CI, autolens_workspace_test#196)
+ … it is the heaviest entry here and does not belong in the fast PR gate."
+
+So the two exclusion lists now disagree about this script, and the list that
+readmitted it did so on ~10 executions at ≤54.5s. **A 10-execution sample at
+~50s cannot exclude a low-probability hang** — which is exactly the claim the
+retime's "marker refuted" conclusion rests on. The retime was right that the
+script is not *slow*; it was not powered to see that it *stalls*.
+
+That is the ledger's own phase-2 question (§ Task step 1: "a slow script has a
+tight timing distribution, a stalling one is bimodal") landing on the other side
+from where the retime put it.
+
+## Also new: the channel
+
+Every occurrence in the ledger comes from a workspace repo's own `Smoke Tests`
+gate or from `release-integrate`. This is its **first from the weekly
+`workspace-validation.yml` sweep** — a different harness (PyAutoHeart-owned,
+`script_matrix.py`-driven, honouring `no_run.yaml` and *not* `smoke_tests.txt`)
+reproducing the same signature. That is corroboration the stall is not an
+artifact of one repo's runner configuration.
+
+It also means the weekly channel runs scripts the PR gate deliberately excludes,
+which is how a script disabled in `smoke_tests.txt` since July was still able to
+burn a 300s cap in CI.
+
+## Task
+
+Record this in the ledger — do not park the script.
+
+1. Append a `## New occurrence — 2026-08-25, multi_dataset/jax_likelihood/shared_preloads.py`
+ section to [`jax_vmap_jit_compile_stall.md`](jax_vmap_jit_compile_stall.md),
+ in the shape of the existing § "New occurrence — 2026-08-24" section: run and
+ job ids, the sibling timing table, and the affected-set consequence.
+2. State the retime refutation explicitly, so phase 2's written answer is not
+ left contradicting the evidence: this entry was readmitted to coverage on a
+ sample too small to exclude a stall, and the readmission is now falsified.
+3. Extend the ledger's affected-set shape to name `shared_preloads.py`, and note
+ the `smoke_tests.txt` / `no_run.yaml` disagreement about it.
+4. Add the "first occurrence on the weekly `workspace-validation` channel" point,
+ with the cross-harness corroboration it gives.
+
+**Deliberately out of scope:** re-adding `shared_preloads.py` to `no_run.yaml`.
+The ledger's own § "This is why quarantining is the wrong end state" argues
+against whack-a-mole parking that strips coverage of the heaviest JAX paths, and
+the 2026-08-24 precedent for `multi_dataset/jax_likelihood/mge.py` was to record
+and deliberately **not** park. Any re-marking is phase 3's call with a root cause
+in hand, not this task's.
+
+## Acceptance
+
+- The ledger names `shared_preloads.py` in its affected set, with the run/job
+ evidence and the sibling timings.
+- The 2026-08-24 retime refutation for this entry is recorded in writing, so a
+ reader of phase 2's conclusion sees the counter-evidence beside it.
+- No script is parked, disabled, or re-marked by this task.
+- `lifecycle.py check` clean; PyAutoMind is the only repo touched.
diff --git a/dashboard.html b/dashboard.html
index 401dcefc..3b6eb0d6 100644
--- a/dashboard.html
+++ b/dashboard.html
@@ -185,7 +185,7 @@
PyAutoMindDashboard
Intent. Priority. Flow.
Every task the Mind is holding. Tap a task's 📋 and its /start_dev command is on your clipboard — paste it into a Claude Code chat to route Claude straight to that task. Recent is the same work by date — what has been happening rather than what to do next.
-
1In flight
3Parked
5Planned
137Backlog
+
2In flight
3Parked
5Planned
137Backlog
Last updated 2026-08-25. This page is generated from active/, draft/ and the registry files, so it is only as current as they are. dashboard_refresh.yml re-renders it on every push to main — that heals a stale page, but not a stale prompt: a task that shipped without its prompt advancing to complete/ keeps rendering here as pickable backlog. Reconciling those is the refresh below.