410 Commits

Author SHA1 Message Date
YeonGyu-Kim
eefcfe159f roadmap: #299 filed (/resume latest workspace-scope gap, cross-ref PR #2811) 2026-04-27 09:38:08 +09:00
YeonGyu-Kim
4621f339a9 roadmap: #298 filed (event/log output unstructured, no machine-readable format) 2026-04-27 09:33:58 +09:00
YeonGyu-Kim
40147e1db3 roadmap: #297 filed (MCP plugin connection crash no mid-session recovery) 2026-04-27 09:02:02 +09:00
YeonGyu-Kim
c014acb787 roadmap: post-merge parity matrix (claw-code vs. anomalyco/opencode reference) 2026-04-27 08:42:38 +09:00
YeonGyu-Kim
1291d9fbc3 roadmap: #296 filed (test brittleness under sustained concurrency) 2026-04-27 08:22:02 +09:00
YeonGyu-Kim
c14a366dfa roadmap: #295 filed (long-running worktree stale-branch detection gap) 2026-04-27 08:01:52 +09:00
YeonGyu-Kim
f84676d534 roadmap: #294 filed (first-run onboarding no guided setup, pairs with PR #2810) 2026-04-27 08:01:29 +09:00
YeonGyu-Kim
ee3d325a0b roadmap: #293 filed (claw doctor lacks provider health/reachability check) 2026-04-27 07:01:39 +09:00
YeonGyu-Kim
6c5f150d68 roadmap: #292 filed (extreme-sustained-degradation user-facing escalation) 2026-04-27 01:02:36 +09:00
YeonGyu-Kim
b8ada4042f docs: ROADMAP.md cluster index for 49+ pinpoints navigation 2026-04-26 23:02:35 +09:00
YeonGyu-Kim
7a0a64beeb roadmap: #291 filed (repeat-failure detection / circuit-breaker) 2026-04-26 22:02:04 +09:00
YeonGyu-Kim
0f389752f0 roadmap: #290 filed 2026-04-26 21:32:04 +09:00
YeonGyu-Kim
096f15506d docs: add ROADMAP.md extended-audit summary header (cycles #388-#415) 2026-04-26 21:17:45 +09:00
Yeachan-Heo
5ee9a00d56 roadmap: #289 filed 2026-04-26 10:30:34 +00:00
Yeachan-Heo
ca6107ab77 roadmap: #288 filed 2026-04-26 10:01:31 +00:00
Yeachan-Heo
9b06c98bd6 roadmap: #287 filed 2026-04-26 09:36:09 +00:00
Yeachan-Heo
79eeaaeaf6 roadmap: #286 filed 2026-04-26 09:30:37 +00:00
Yeachan-Heo
639e1e338e roadmap: #285 filed 2026-04-26 09:26:56 +00:00
Yeachan-Heo
92a598e7e6 roadmap: #284 filed 2026-04-26 09:24:27 +00:00
YeonGyu-Kim
1a7b8ea893 roadmap: #283 filed 2026-04-26 18:08:49 +09:00
YeonGyu-Kim
b05561c6ac roadmap: #282 filed 2026-04-26 18:03:00 +09:00
Yeachan-Heo
fdb149d424 roadmap: #281 filed 2026-04-26 18:03:00 +09:00
YeonGyu-Kim
cc06e4699f roadmap: #280 filed 2026-04-26 18:03:00 +09:00
Yeachan-Heo
d9607068ff roadmap: #279 filed 2026-04-26 18:03:00 +09:00
Jobdori
294b855851 roadmap: #278 filed 2026-04-26 18:03:00 +09:00
Yeachan-Heo
1f9d30fadc roadmap: #277 filed 2026-04-26 18:03:00 +09:00
YeonGyu-Kim
39ce893b9d roadmap: #276 filed 2026-04-26 18:03:00 +09:00
Yeachan-Heo
25164086c0 roadmap: #275 filed 2026-04-26 18:03:00 +09:00
YeonGyu-Kim
27f395aa82 roadmap: #274 filed 2026-04-26 18:03:00 +09:00
Yeachan-Heo
b3af8bdb54 roadmap: #273 filed 2026-04-26 18:03:00 +09:00
YeonGyu-Kim
c7d2c4e47f roadmap: #272 filed 2026-04-26 18:03:00 +09:00
Yeachan-Heo
77c5e4f5cc roadmap: #271 filed 2026-04-26 18:03:00 +09:00
Jobdori
a1b2fed172 roadmap: #270 filed 2026-04-26 18:03:00 +09:00
Yeachan-Heo
28a37fbedd roadmap: #269 filed 2026-04-26 18:03:00 +09:00
YeonGyu-Kim
0f8e633d5f roadmap: #268 filed 2026-04-26 18:03:00 +09:00
Yeachan-Heo
25adb26dd5 roadmap: #267 filed 2026-04-26 18:03:00 +09:00
YeonGyu-Kim
cc14d6edd6 roadmap: #266 filed 2026-04-26 18:03:00 +09:00
Yeachan-Heo
5ccaf34d9d roadmap: #265 filed 2026-04-26 18:03:00 +09:00
YeonGyu-Kim
01b8149e00 roadmap: #264 filed 2026-04-26 18:03:00 +09:00
Yeachan-Heo
e69fe1a7da roadmap: #263 filed 2026-04-26 18:03:00 +09:00
YeonGyu-Kim
3606f589c1 roadmap: #262 filed 2026-04-26 18:03:00 +09:00
Yeachan-Heo
127108c5e7 roadmap: #261 filed 2026-04-26 18:03:00 +09:00
Jobdori
971c1a808e roadmap: #260 filed 2026-04-26 18:03:00 +09:00
Yeachan-Heo
fe10cb39c1 roadmap: #259 filed 2026-04-26 18:03:00 +09:00
YeonGyu-Kim
1c50d946e4 roadmap: #258 filed 2026-04-26 18:03:00 +09:00
Yeachan-Heo
fe7f449de6 roadmap: #257 filed 2026-04-26 18:03:00 +09:00
Yeachan-Heo
8a187634a8 docs: intake hikaMaeng web search fork ideas
Add ROADMAP pinpoint #255 summarizing the safe subset of hikaMaeng/Sigrid Jin's web-search provider work to adopt later.\n\nReviewed fork commits 262405e, bd11289, fa93cd3, 5f2540a, 7f34d91, and 535be97 from https://github.com/hikaMaeng/claw-code. This deliberately preserves attribution and avoids a blind cherry-pick because the cross-crate provider/spec/config/banner changes need a dedicated implementation lane with tests.
2026-04-26 18:03:00 +09:00
YeonGyu-Kim
6fa9196f04 roadmap: #254 filed 2026-04-26 18:03:00 +09:00
Yeachan-Heo
c7ef6f636d roadmap: #253 filed 2026-04-26 18:03:00 +09:00
YeonGyu-Kim
46f3e9cd2c roadmap: #252 filed — /v1/messages/count_tokens typed-taxonomy is structurally absent from the public Provider trait + types + CLI surface (Anthropic ships /v1/messages/count_tokens as a first-class GA endpoint that consumes the SAME MessageRequest shape as /v1/messages but produces a TRUNCATED CountTokensResponse { input_tokens: u32 } only — no message emission, no completion-side tokens, no streaming — the canonical pre-flight cost-estimation primitive where a client constructs the exact request it intends to dispatch, asks the server to count input tokens, and decides whether to send before paying for completion-side tokens; claw-code has zero public typed surface even though a private count_tokens helper exists at rust/crates/api/src/providers/anthropic.rs:522 for internal preflight context-window-exceeded validation, with zero CountTokensRequest/CountTokensResponse typed model in types.rs, zero count_tokens method on the public Provider trait, zero count_tokens dispatch on the ProviderClient enum, zero claw count-tokens CLI subcommand, zero /count-tokens slash command in SlashCommandSpec, zero pre_flight_count_cost_per_million_usd field in ModelPricing, zero CountTokensSubmittedEvent/PreFlightCostEstimatedEvent telemetry events, and zero PreFlightCostEstimator/BudgetGate runtime primitive) — eight-layer fusion shape with the NOVEL same-request-shape-but-different-response-shape axis-class (FIRST audit member where the request shape is IDENTICAL to an existing typed model MessageRequest but the response shape is a TRUNCATED-projection that cannot reuse MessageResponse's shape, distinct from prior fusion-axes which all add NEW request-side fields or NEW response-side blocks) founding THREE new clusters as solo founder (Pre-flight-cost-prediction cluster, Token-accounting-without-message-emission cluster, Server-side-pre-execution-counting cluster) plus introducing the THIRD distinct discovery-pattern in the audit catalog NEW-SOLO-CLUSTER-FOUNDING-WITH-DAILY-DRIVER-IMPACT (distinct from META-cluster-growth and complementary-pinpoint-pair-bundle), grows Two-member-major-provider-only-no-third-party-partner-set sub-cluster from 6 to 7 members (#240+#241+#247+#248+#249+#250+#252) confirming continuing-pattern-status across SIX distinct axis-classes — Jobdori cycle #394 / fast-forward-rebase verified onto gaebal-gajae's #251 cycle ExternalPatchIntake pinpoint at 313c840 before filing (NINTH consecutive concurrent-dogfood rebase cycle, three-way parity confirmed local==origin==fork at HEAD 313c840 with no race detected, directly demonstrating the gaps #239 catalogues at the dogfood-coordination layer and #243 catalogues at the canonical-ordering layer for the NINTH cycle in a row, confirming concurrent-dogfood-rebase as a stable operational pattern that has now held for NINE cycles) — PIVOT-AWAY signal: #252 deliberately PIVOTS AWAY from BOTH Cross-pinpoint-synthesis-fusion-shape META-cluster (intentionally not extending the +1-per-cycle synthesis chain) AND Tool-locality-axis META-cluster (already extended by #250 cycle #393), founding NEW solo clusters with daily-driver-impact instead, demonstrating audit-breadth-across-discovery-pattern-classes alongside audit-balance-across-META-clusters — the audit now spans THREE structurally distinct discovery-patterns (META-cluster-growth + complementary-pinpoint-pair-bundle + new-solo-cluster-founding-with-daily-driver-impact) 2026-04-26 18:03:00 +09:00