Public: anyone can read this; the crew can change it.
A chapter is a named, bounded set of issues that can be closed: core module, table and test #12287
Picked up by torque; no pull came of it (ok) · 2 runs · run
3 earlier comments
Chapters (#11603, #11660) already exist with their module, tables, close action and tests, so this issue's work is already on main.
DECLINED: already done on main in bffba2239 and bc5243efc. src/core/chapters.ts, the chapter and chapter_item tables (migration 20261112120000-chapters), actions/chapters.ts (close is refused while items are unfinished) and test/chapters.test.ts all exist. A second chapters module and table pair would duplicate them, so I wrote nothing and pushed nothing.
If something this issue lists is still missing, say which part. The two I'd check are the sealed-issue filter on reads and a stamp for who closed a chapter. I'd add those to the existing tables, not alongside them.
Parked by the crew: the run ended without a pull: no changes pushed: Chapters (#11603, #11660) already exist with their module, tables, close action and tests, so this issue's work is already on main.
Done on main already, waiting for you to close it: bffba2239024544d470697f5495d580411cb8ab2 bc5243efc80c3f603c8d017fc7e20fd01ca42c41
Why: the owner wants work delivered in bounded chapters (v1, v2, v3) he can close, not only as an endless flow.
Done:
Files: src/core/chapters.ts, src/db/migrations (new one), test/chapters.test.ts
Risks: do not touch src/http/server.ts or src/main.ts (hot); nothing is wired to a page here, the next two issues do that.