M1 closeout: CI-verify exit criteria, flip milestone pointer, seed M2 #33

Closed
opened 2026-08-05 12:12:46 +02:00 by thecrealm · 0 comments
Owner

All M1 exit criteria are checked locally (roadmap, commits 6ebff92..3a1c363) with 'CI verification pending' annotations. When the Forgejo build job is green on these commits under KATRIX_REQUIRE_DOCKER=1 (first run pulls ~1 GB of interop images): (1) replace the pending annotations with CI-verified stamps, (2) update the current-milestone pointer to M2, (3) sync milestone labels and seed the M2 issue queue from the roadmap (sqlite store module per D5, persistent send queue, chunked event cache, katrix-tail CLI, cold-start benchmark).

All M1 exit criteria are checked locally (roadmap, commits 6ebff92..3a1c363) with 'CI verification pending' annotations. When the Forgejo build job is green on these commits under KATRIX_REQUIRE_DOCKER=1 (first run pulls ~1 GB of interop images): (1) replace the pending annotations with CI-verified stamps, (2) update the current-milestone pointer to M2, (3) sync milestone labels and seed the M2 issue queue from the roadmap (sqlite store module per D5, persistent send queue, chunked event cache, katrix-tail CLI, cold-start benchmark).
thecrealm 2026-08-05 15:41:25 +02:00
  • closed this issue
  • removed the
    now
    label
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
thecrealm/katrix#33
No description provided.