docs: 0.5.0 → 1.0 roadmap (per RFC-0036) - #197
Merged
Merged
Conversation
issue 驱动的排期总览，单项设计仍在各 issue / RFC： - 0.6.0 收缩+体积止血：#166 A2–A5/E1、#185、#170/#171(前半)、 B1+C2 解锁项、S1 桌面 .a 切 staticlib profile、S2 体积门禁 - 0.7.0 protocol registry + auth：#166 B2–B9、#174/#175、#171(后半)、 S3 体积审计（gating 仅可选路径，默认 API 不变） - 0.8.0 FFI ops + bindings：#166 C/D 轨 - 1.0 锚点：#167 transport replay、#179/#181/#180 清尾、API 冻结 - §6 横切：产物体积预算（瘦身不改变对外 API 的约束）与 协议/生态定期跟踪节奏（扩展 #170 为三条流水）
- re-staged around RFC-0036: 0.6 gates + protocol groundwork, 0.7 L1 + auth, 0.8 ops protocol (FFI + stdio), 0.9 governance, 1.0 freeze only - moved out of docs/plan/ (archived by the E1 docs reorg) - A2 flagged as binding source-level breaking, with migration note - C1 in 0.8 with old exports coexisting; C4 at 1.0; D1/D5 can go early - #167/#179 moved to 0.9 so 1.0 carries no large feature - RFC-0031/0032/0033 landing is an explicit 0.6 item - S1 limited to the staticlib job; S2 gets concrete thresholds; perf gate P - refreshed facts: FFI 123 exports, #164 merged, A1 done; 0.6 re-estimated Co-Authored-By: Claude <noreply@anthropic.com>
eric8810
changed the title
3 tasks done
eric8810
added a commit
that referenced
this pull request
Sep 29, 2026
…199) stream_abort_mid_session started its 100ms abort timer before do_stream. On a slow runner the abort fired during the connect, do_stream returned Aborted, and the unwrap panicked (seen on #197's CI). Start the timer once the session is up so the abort is always mid-session. Co-authored-by: Claude <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Issue-driven roadmap for 0.5.0 → 1.0, rewritten against RFC-0036 (positioning and layered architecture). Sequencing only — design details stay in the issues/RFCs. Moved to
ROADMAP.mdat the repo root, sincedocs/plan/is archived by the E1 docs reorg.Stages
.a→ staticlib LTO-off profile (staticlib job only); S2 size gates with concrete per-artifact thresholds; P perf regression gate; A2–A5, E1, Tool-call input boundary: type the raw/parsed distinction, drop the unused StreamingToolCallTracker #185, Registry maintenance: weekly models.dev diff report and monthly reachability probe #170/Registry triage: 27 base_url disagreements and 116 missing providers vs models.dev #171 (first half); B1 + C2 unlock items; ops protocol schema; L0 native passthroughRaw/provider_metadatawiring, S3 size audit, L2 data-model evaluation RFCaimux probe / replay / diff(aimux-cli follow-ups (RFC-0025): online mode and replay subcommand #179, Session aggregation follow-ups (RFC-0024): partial-match merging and debug CLI #181 folded in)Not scheduled (direction set in RFC-0036): UDS/HTTP transports,
aimux-proxy. De-prioritized: B9, #171 second half.Changes vs the first draft
ProviderNameremoved in 7 bindings), with a migration note🤖 Generated with Claude Code