Milestones
List view
One coherent release: operator boundary re-worded and tested, api() contract hardened, providers audited against written conventions, two deployment shapes, operator UI rebuilt, core guides filled. Cross-cutting principle: keep the model that interacts with connecta as efficient as possible — every surface is judged by the tokens and round trips it costs an agent.
No due date•12/12 issues closedAgent-efficiency and recovery hardening derived from the issue #177 current-version model/tool audit: improve lexical discovery, reduce duplicate result payloads, make optional surfaces conditional, unify credential recovery, and establish a repeatable release eval gate.
No due date•8/8 issues closedConsolidation before capability growth: unify invocation semantics, make code mode lazy, bound catalog discovery, extract oversized modules, harden the dev loop, and settle the pre-1.0 design decisions surfaced by the executor-comparison audit.
No due date•16/16 issues closed