v3.2.0 Karnak Released #1064
amrmelsayed
announced in
Announcements
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
v3.2.0 Karnak is out. Four threads land in this cycle: the completed VS Code markdown-preview review surface, a hot/cold tier split for the governance documents, terminal correctness wins on both Tower freeze and corrupted-on-open replay, and three substantive contributions from outside contributors.
Foundational
@cluesmith/codev-artifact-canvaspackage shipped (#945), a host-agnostic React canvas for rendering specs / plans / reviews across surfaces. It was then mounted ascodev.openMarkdownPreviewin VS Code (#859): hover a rendered block, click+, type your feedback, and an on-disk<!-- REVIEW: -->marker writes above the block. Same bit format the editor's Comments-API thread uses, so the two surfaces are interchangeable. A second pass (#863) turned overlay cards into in-flow elements anchored below each annotated block, added a right-edge marker minimap for at-a-glance comment density, and pinned multi-block-marker rendering. The same VS Code surface also gained codelens-driven file and hunk injection from the diff editor into the builder PTY (#789), removing the typing-the-path-by-hand bottleneck in architect-to-builder feedback.Governance docs go two-tier (Spec 987 by @waleedkadous, PR #1034).
arch-critical.mdandlessons-critical.mdare now hard-capped and always-injected into every porch phase prompt plus a managed block in CLAUDE.md / AGENTS.md. The deeparch.mdandlessons-learned.mdarchives stay reference-only and on-demand. Two fresh-install fixes build on the same foundation: framework files now reach builders through resolver-aware channels rather than literal paths (#1011), and the matching cold-tier starter files materialize oncodev init/adopt/update(#1012).Terminal correctness saw two coordinated wins. #1047 resolves the oversized-replay reconnect storm that froze builder and architect terminals after hours of Tower uptime: Tower scans only the incoming chunk and brackets catch-up replay with
pause/resume; the VS Code client drops live output under overload, reconnects with?resume=<seq>deltas where the stream has newlines, and forces a guaranteed redraw after attach. #1052 fixes the size-settling timing flaw behind corrupted-on-open replays in VS Code terminals, by holding the bracketed replay until the two-step VS Code size report quiets, then flushing once at the settled width.afx tower startnow waits for/api/statusbefore reporting success, with safely-redacted shellper startup diagnostics on failure (#1031 by @timeleft--). The shellper protocol replaysEXITto clients that connect after the PTY has already exited, fixing a previously-flaky race on Tower restart and on rapid-exit fixtures (#953 by @mohidmakhdoomi).afx statusfinally surfaces architect ↔ builder ownership for multi-architect workspaces, with--architect,--mine, and--jsonflags (#1058 by @waleedkadous, on top of his Spec 987 work).Install:
npm install -g @cluesmith/codev@3.2.0 afx tower stop && afx tower startVS Code extension via the Marketplace:
Codevbycluesmith, version3.2.0. Also published to Open VSX.Full release notes: https://github.com/cluesmith/codev/releases/tag/v3.2.0
Beta Was this translation helpful? Give feedback.
All reactions