Milestones
List view
Release-independent operational monitoring and investigation for historical intermittent authenticated Relay route loss (#161). Root cause and responsibility remain unconfirmed; no current recurrence or resolution is asserted. Escalate priority only with verified current impact. No operating changes or release gate are authorized by assignment.
No due date•0/1 issues closedUsability and opt-in integration work: delivery/readiness explanations (#323), local destination presets and address book (#324), explicit trusted SSH configuration (#312), one-time link pairing (#212), bounded metadata watch (#296), and per-release update notice dismissal (#294). Codex side-session and live-steering research (#245/#247; Draft #246/#248) is tracked in Long-term, not this release. Preserve ownership, permissions, no-retarget/no-uncertain-resend and submission-versus-ACK boundaries. Separate native/platform/security acceptance is required; no committed date or publication approval.
No due date•7/13 issues closedTarget release date: 2026-10-18 (end of this week, KST), requested by the owner on 2026-10-13. GitHub stores the due date without a time of day. Safety and delivery foundations after v1.1.2: native target-generation (#180), effective Codex storage/shared-server configuration (#268), scoped first-input Codex transport (#306), handoff observation/receipt/bootstrap/lifecycle acceptance (#181), and bounded Antigravity version/platform acceptance and startup investigation (#304/#307). Preserve embedded/shared-server distinctions and unsupported pre-first-input boundaries. Development and release preparation are authorized; merge, tag, publication, deployment and expanded live-test permissions retain separate approval and acceptance gates. Report scope/deadline conflicts; never relax safety to meet the date.
Overdue by 6 day(s)•Due by October 18, 2026•7/13 issues closedOptional post-1.0 distribution and architecture work without a committed release date. Issues here are proposals, not approval to implement or publish.
No due date•1/9 issues closedPost-1.0 fixes and diagnostics found during RC4 validation (#164). Not release blockers unless re-triaged.
No due date•9/9 issues closedFix-forward from partial RC3 PyPI publication. Require complete wheel and sdist publication, exact-artifact fresh installs, independent real ACKs, and an uninterrupted four-hour five-host campaign before stable promotion. Creating this milestone does not itself approve promotion.
No due date•3/3 issues closedInvestigation-driven candidate for #161 Relay stability. Scope is gated by evidence: receiver lifecycle, sanitized stage diagnostics, affected real ACK routes, and a clean four-hour five-host validation. Creating this milestone does not approve a fix, deployment, or publication.
No due date•3/3 issues closedRC1 multi-host validation fixes. Any runtime, supported-platform, packaging, authentication, or durable-state change requires RC2 and revalidation before v1.0.0.
Overdue by 29 day(s)•Due by September 25, 2026•6/6 issues closedRepository and core-architecture work required before the first stable session-peer release. Alpha behavior remains supported while structure, tests, packaging, and standalone deployment contracts are stabilized.
Overdue by 25 day(s)•Due by September 29, 2026•7/7 issues closed