Spec #136: Finished belongs to the Series — owner-owned poll gate, Lifecycle bucket dropped (#163)

Closes #136.

Spec #136 end to end: `finished` becomes a fact about the Series, written only by the owner, and the reader-facing Lifecycle bucket is gone.

## What landed

- **#157** — `series.finished_at bigint NOT NULL DEFAULT 0` plus the migration whose statement order is load-bearing (seed from the buckets, then flip them); both Lane queries lose the `HAVING COUNT(*) FILTER (WHERE b.status <> 'finished')` clause and gate on `finished_at = 0` instead, with the due-query/eligible-count force asymmetry kept deliberate and commented; `StatusFinished`, its API special-case 400, the web tab and the templates' Finished bucket deleted.
- **#158** — owner Finish control on the Series detail page: confirm-gated finish, instant un-finish, admin accent (never ember, nothing is destroyed), `Store.SetSeriesFinished`, the two routes behind the owner gate, and the state displayed on the list row without offering the control there.
- **#160** — reader side: derived `finished` bool on the flat Bookmark (`s.finished_at > 0`), rendered as a text-only label in both userscripts and on the web card; read-only inbound by omission from `Upsert`'s explicit `series` column list, same mechanism that already protects `cover`.
- **#161** — glossary and the stale Reader-count divergence note catch up.
- **#159** — `finished` joins the admin filter vocabulary (predicate `finished_at > 0`, label `Finished`, own aggregate count, figure last in the stats block as informational); the four clock-driven hygiene predicates (stale, never-checked, no-cover, no-chapter) exclude finished Series while unpollable, orphan and sighting-raised deliberately do not.

## Verification

`go vet ./...` and `go test ./...` green on the merged branch (Docker-backed, throwaway `postgres:17-alpine` per package). Each ticket also passed a two-axis review (spec + standards) on its own branch before merge.

Reviewed-on: #163
Co-authored-by: Sulthan Zaki <sultankiki05@gmail.com>
Co-committed-by: Sulthan Zaki <sultankiki05@gmail.com>

backend/AGENTS.md

@@ -200,12 +200,16 @@ stored** and clients must adopt that response rather than their own payload.
 
 ### Lifecycle buckets — `status` on each bookmark
 
-`reading` | `archived` | `finished`, orthogonal to `favorite`. Archived and
-finished appear only in their own tab, never in All, Updated, Favourites or the
-recent strip. The poller keeps checking archived series and skips finished ones.
+`reading` | `archived`, orthogonal to `favorite`. Archived rows appear only
+in their own tab, never in All, Updated, Favourites or the recent strip. The
+poller keeps checking archived series; a finished Series (issue #157) is a
+`series.finished_at` fact the Lane gate reads, with every bookmark on it
+archived.
 
-- `finished` is settable only from the web UI; `PUT /bookmarks/{key}` rejects
-  it with 400.
+- `PUT /bookmarks/{key}` accepts only the two values; anything else —
+  `finished` included — is a plain 400, and the web UI's own status control
+  validates the same way. The 0016 migration is the only writer of the flag
+  today; the undo is writing 0.
 - **An empty incoming status means "keep the stored one"**, and it is resolved
   on the `VALUES` side of `Store.Upsert`, not in the conflict clause:
   `excluded.*` is the post-evaluation row, so a default applied there would