Parent issue: 0.1 alpha readiness

[jillesvangurp]

Summary

This parent issue groups the work required to make the first public alpha release operationally credible and properly documented by the end-of-April 2026 target.

Sub-issues

• Add production observability and readiness baseline for the 0.1 alpha #1 Add production observability and readiness baseline for the 0.1 alpha
• Establish baseline performance checks for CRUD, ingest, MQTT publication, and RPC #2 Establish baseline performance checks for CRUD, ingest, MQTT publication, and RPC
• Expand boundary-focused coverage for runtime edges and auth-enabled WebSocket flows #3 Expand boundary-focused coverage for runtime edges and auth-enabled WebSocket flows
• Define and document MQTT operational behavior for publish failures, reconnect storms, and overload #4 Define and document MQTT operational behavior for publish failures, reconnect storms, and overload
• Publish a runtime and operations guide for the alpha release #5 Publish a runtime and operations guide for the alpha release
• Publish an ingest and CRS guide for accepted inputs and georeferencing behavior #6 Publish an ingest and CRS guide for accepted inputs and georeferencing behavior
• Expand MQTT and RPC documentation for the public alpha surface #7 Expand MQTT and RPC documentation for the public alpha surface
• Publish a data and behavior model guide for current storage and event semantics #8 Publish a data and behavior model guide for current storage and event semantics
• Decide the 0.1 alpha scope for fence timeout and tolerance semantics #9 Decide the 0.1 alpha scope for fence timeout and tolerance semantics
• Decide the 0.1 alpha scope for collision-event behavior #10 Decide the 0.1 alpha scope for collision-event behavior

Done when

• the alpha milestone has a coherent release-readiness tracker
• operational hardening, documentation, and scope decisions can be reviewed as one release slice

[jillesvangurp]

Status update after reviewing the April 1-2 merged work against the alpha-readiness backlog:

Addressed

• Expand MQTT and RPC documentation for the public alpha surface #7 is now closed as addressed by PRs [codex] Add GTFS MQTT connector and connector docs #34 and Add OTLP observability and SigNoz demo runtime #35.

Partially addressed, with remaining work split into narrower follow-up issues

• Add production observability and readiness baseline for the 0.1 alpha #1 observability/readiness advanced materially in PR Add OTLP observability and SigNoz demo runtime #35; remaining readiness surface tracked in Add dependency-aware readiness reporting for Postgres, MQTT, auth, and metadata reconcile #36
• Establish baseline performance checks for CRUD, ingest, MQTT publication, and RPC #2 performance work advanced materially in PRs Add replay connector, shared capture scripts, and replay throughput improvements #32 and Improve replay throughput and asynchronous event fan-out #33; repeatable published baseline tracked in Publish a repeatable alpha performance baseline for CRUD, ingest, MQTT, and RPC #37
• Document downstream consumer delivery and reconnect semantics for WebSocket and MQTT event streams #26 downstream consumer semantics has partial doc/runtime coverage from PRs Add connector demos and fix WebSocket keepalive handling #31, Add replay connector, shared capture scripts, and replay throughput improvements #32, Improve replay throughput and asynchronous event fan-out #33, [codex] Add GTFS MQTT connector and connector docs #34, and Add OTLP observability and SigNoz demo runtime #35; remaining single consumer contract tracked in Write a consumer contract guide for WebSocket and MQTT delivery, ordering, reconnects, and duplicates #39

Not reassessed in this pass

• Expand boundary-focused coverage for runtime edges and auth-enabled WebSocket flows #3, Define and document MQTT operational behavior for publish failures, reconnect storms, and overload #4, Publish a runtime and operations guide for the alpha release #5, Publish an ingest and CRS guide for accepted inputs and georeferencing behavior #6, Publish a data and behavior model guide for current storage and event semantics #8, Decide the 0.1 alpha scope for fence timeout and tolerance semantics #9, Decide the 0.1 alpha scope for collision-event behavior #10, Publish a contributor quality guide for the required just workflow and CI gates #11 remain open without a close recommendation from this review

This keeps the alpha tracker aligned with the work that landed last week while preserving the remaining gaps as explicit child issues.