Please cut a release: v1.2.1 is broken against current beads schema (depends_on_id) — fixes already merged on main

Summary

v1.2.1 (2026-06-06) is the latest tagged release, but it is effectively broken against any beads database on the current (post column-split) schema: its embedded SQL and embedded beads library still reference wisp_dependencies.depends_on_id / dependencies.depends_on_id, which beads split into depends_on_issue_id / depends_on_wisp_id / depends_on_external.

On a production town running v1.2.1 with migrated databases we observed:

• Reaper: gt reaper scan fails on every migrated DB with Error 1105 (HY000): table "wd" does not have column "depends_on_id" — stale-wisp reaping impossible (wisp backlog grew to ~8.6k before manual intervention).
• Wisp compaction: the orphaned wisp_dependencies cleanup step fails with the same error on every compaction cycle.
• Daemon convoy feeder: Convoy: <db> beads store unavailable: failed to initialize schema: failed to create ready_issues view: Error 1105 ... depends_on_id, ending in Convoy: no beads stores available, event polling disabled — event polling silently dead town-wide (64,000+ log lines over ~6 weeks in our case). This is the embedded old beads library; main now embeds beads v1.0.5 which fixes it.

The fixes already exist on main

Current main (649b832, 2026-07-23) resolves all three paths — we've been running a source build of it in production since 2026-08-19: convoy opens all stores, reaper scans migrated DBs cleanly, compaction cleanup no longer errors.

Ask

Please cut a tagged release (and brew bottle) from current main. There is a long tail of open duplicates that a release would close: #4678, #4495, #4210, #4229, #4284, #4205, #4224, #4328, #4382, #4304, #4702, #4553, #4718. Related release-pipeline issue: #4179.

If main is not releasable due to #4272 (CI red), a patch release of v1.2.1 + cherry-picked schema fixes would equally unblock users on migrated beads schemas.