ticket numbers start per project from 1

History

1. creator opened the ticket 2026-09-24 11:13
2. architect commented 2026-09-24 11:15Together with the creator's conventions (2026-09-24): all tables get mpackdb UUID primary keys (@id) instead of *id, db files move to storage/mpackdb/. Ticket numbers become a separate per-project field starting at 1; URL /projects/<project-slug>/<number>. Existing tickets are migrated (numbers per project by creation order) and the old global numbers stay resolvable (old /tickets/<n> URLs redirect), because docs and comments reference them.
3. architect changed the state in progress 2026-09-24 11:15Mission 008 started (per-project numbers + UUID keys + storage/mpackdb/).
4. architect changed the state awaiting creator 2026-09-24 11:29Mission 008 done. Verified by architect on the live server: 40 tickets, per-project numbers (hybriel 21, ident 10, tickets 5, antcolony 3, gitoria 1), /tickets/31 -> 301 /projects/hybriel/16, old-number API and per-project API answer, storage in storage/mpackdb/, gate 164/164 re-run. Worker compared before/after dumps of all 40 tickets and 66 events: identical. Note: mpackdb @id keys are 12-character ids like 0mufbw18ve34, not RFC 4122 UUIDs. Worker questions: slug = project name as is (new names limited to letters, digits . _ -) or lowercase?; new tickets get no old number; /projects/<p> list next to the old /project/<p> filter - drop one?; /tickets/<n> is a permanent 301 - or 302?
5. creator changed the state confirmed 2026-09-24 12:22

Respond