diff --git a/.dev/STATE.md b/.dev/STATE.md
index fe4135b..532902b 100644
--- a/.dev/STATE.md
+++ b/.dev/STATE.md
@@ -7,7 +7,7 @@ Roadmap detail lives in the work-plan tracker **#257**, not here (PLAN.md predat
 
 ## In flight
 
-- **v0.28.1 release cut 2026-09-14** (#308 `aae38d1`) — patch: sync mode fires only for PRs
+- **v0.28.1 release cut 2026-09-14** (fix #308 `aae38d1`; release PR #309 `3de9024`) — patch: sync mode fires only for PRs
   merged into the default branch. Trigger: QuantEcon/lecture-python-programming#629 (theme
   v3.0.0) merged into the long-lived `jb2` branch on 2026-09-12 and all three deployed sync
   workflows fired — `types: [closed]` has no base-branch filter and neither the job `if:`
@@ -16,8 +16,11 @@ Roadmap detail lives in the work-plan tracker **#257**, not here (PLAN.md predat
   now requires it) + `mergedIntoDefaultBranch` in `validatePREvent` and the resync path,
   compared against `repository.default_branch`. Tidy-up outside the repo, same day: the
   three downstream PRs closed unmerged; `branches: [main]` PR'd into the deployed workflows
-  (lecture-python-programming ×3, lecture-python-intro, lecture-python.myst). §4a gate
-  status is recorded on the release PR. W1 (#259) still targets v0.29.0.
+  (lecture-python-programming#630, lecture-python-intro#846, lecture-python.myst#1056 —
+  open, awaiting merge). §4a gate **completed 2026-09-14**:
+  84/84 sync runs, 28/28 delivery + 28/28 verdicts per lane at `engineVersion: 0.28.1`;
+  `@v0` = `v0.28` = `3de9024`, alias smoke (scenario 01) reports `engineRef: v0` on all
+  three lanes; GitHub release published. W1 (#259) still targets v0.29.0.
 - **v0.28.0 released 2026-09-03** (#303 `07e7c64`; release #304 `9284fbc`; §4a gate **completed**:
   84/84 sync runs, 28/28 delivery + 28/28 stamped verdicts per lane; `@v0` = `v0.28` = `9284fbc`,
   smoke-verified on all three lanes) — headline: the
diff --git a/.dev/log/2026-09-14-jb2-sync-fallout.md b/.dev/log/2026-09-14-jb2-sync-fallout.md
index c5b953e..079540a 100644
--- a/.dev/log/2026-09-14-jb2-sync-fallout.md
+++ b/.dev/log/2026-09-14-jb2-sync-fallout.md
@@ -12,3 +12,5 @@
 **Tidy-up outside the repo**: fr#79 / fa#166 / zh-cn#105 closed unmerged with a note; `branches: [main]` PRs opened in lecture-python-programming (3 workflows), lecture-python-intro, lecture-python.myst. The harness source repo (test-translation-sync) re-renders from the template on the next run and needs no PR.
 
 **Gate**: §4a on `v0.28.1` per the checklist; tally recorded on the release PR. Note for the tally: the harness fires the `labeled` trigger on open fixture PRs against `main`, so the new filter is exercised on every run — a lane that fails to start is the filter misbehaving, not the fixture.
+
+**Addendum, same day — released.** Release PR #309 merged `3de9024`; tag `v0.28.1`. §4a gate on the tag: 84/84 sync runs (3 non-matching-trigger skips), 28/28 translation PRs + 28/28 verdicts per lane at `engineVersion: 0.28.1` / `engineRef: v0.28.1`; the harness's `labeled` trigger on `--base main` fixture PRs exercised the new `branches: [main]` filter on every run. `v0.28` + `v0` moved to `3de9024`; alias smoke on scenario 01 delivered test-translation-sync.zh-cn#876 / .fa#260 / .ml#160 with `engineRef: v0`. GitHub release published. Deployed-workflow PRs open: lecture-python-programming#630 (Copilot asks for an `issue_comment` base-branch guard in the workflow itself — judgement call pending with the owner; the action-side check now covers it at `@v0`), lecture-python-intro#846, lecture-python.myst#1056. Tally recipe from the 09-03 log held; the `created` filter picked up the harness's own PR-close runs as `skipped`, which is the expected noise.