v0.1.0-beta.8 - Core Boundary Contraction Checkpoint

v0.1.0-beta.8 is a fast checkpoint release focused on core Zig boundary
contraction and architecture hygiene while Android remains explicitly beta.

Summary

• Core runtime boundary vocabulary and helper routes were narrowed to canonical
  transport/result paths.
• Refresh/reuse orchestration and transport seams were tightened with
  behavior-neutral helper and integration invariant coverage.
• Linux and Android smoke/deploy guards remained green across the checkpoint.

Platform Position

Linux

• Linux remains an active first-class lane.
• This checkpoint is primarily architecture hygiene and contract tightening; no
  new Linux-only feature surface is introduced.

Android

• Android remains beta by design.
• GLES/harness quality remains strong and continues to validate shared seam
  changes; this release does not claim final Android parity/maturity.

Current Beta Release Notes

• Release tag: v0.1.0-beta.8
• Product version: 0.1.0-beta.8
• Release date: 2026年04月20日
• Previous checkpoint: v0.1.0-beta.7

v0.1.0-beta.7 - Linux/Android Hygiene Checkpoint

v0.1.0-beta.7 is a small release-hygiene checkpoint focused on tightening
release surfaces while Android remains explicitly beta.

Summary

• Android app/package versioning is now aligned to the current beta tag
  (0.1.0-beta.7)
• Android is called out as beta in top-level product docs, with GLES + harness
  maturity acknowledged and ongoing product expansion clearly scoped
• Linux and Android release/discovery docs now point to one current checkpoint
  note instead of stale previous-release links

Platform Position

Linux

• Linux remains an active first-class lane with the existing local install and
  staged-release model unchanged for this checkpoint
• this release does not alter Linux runtime behavior; it is a release-surface
  hygiene update

Android

• Android remains beta by design
• GLES + harness quality is strong enough for continued product expansion work,
  but this release does not claim final Android parity/maturity
• Android focus remains app-shell/tab/userland maturity and production-hardening
  under real workloads

Current Beta Release Notes

• Release tag: v0.1.0-beta.7
• Product version: 0.1.0-beta.7
• Release date: 2026年04月18日
• Previous checkpoint: v0.1.0-beta.6

v0.1.0-beta.6 - Renderer Backend Contract Milestone

v0.1.0-beta.6 is a backend-contract milestone release focused on shrinking
renderer-root ownership and moving startup/global lifecycle orchestration into
backend/runtime helper modules.

Summary

• renderer startup/bootstrap sequencing is now runtime-helper driven instead of
  open-coded in renderer.zig
• global renderer state/query/wake/poll utilities now route through dedicated
  runtime helpers
• backend contract hardening continued across OpenGL/Metal dispatch seams,
  lifecycle ownership, and present-path consistency

macOS Position

• macOS validation is deferred until the maintainer has office Mac access
  again
• once that access is restored, ship a macOS milestone release in one of two
  ways:
  • separate GL/Metal releases if backend choice is compile-time
  • one combined release if backend choice is runtime

Current Beta Release Notes

• Release tag: v0.1.0-beta.6
• Product version: 0.1.0-beta.6
• Release date: 2026年04月06日
• Previous checkpoint: v0.1.0-beta.5

v0.1.0-beta.5 - macOS GL Checkpoint

v0.1.0-beta.5 is a macOS-first checkpoint release on the current SDL/OpenGL
lane.

This is not the long-term macOS renderer direction. Metal + AppKit remain the
destination architecture. The point of this release is to make the current
native macOS path honest, buildable, and smokeable before the renderer
migration starts.

Summary

• native macOS arm64 builds are now green for the main app, editor mode, and
  terminal mode
• zlua-portable package consumption is back on a published pinned dependency
  instead of a sibling checkout override
• macOS PTY bring-up now uses the correct header/layout split and starts the
  default interactive shell as a real login shell

Technical Breakdown

Dependency Graph

• Zide now consumes zlua-portable from the published
  v0.1.0-beta.2 package release
• the temporary local path override used during macOS build bring-up is gone
• the package-side Lua boundary fix now keeps macOS-native consumers on the
  normal Zig package path

macOS Runtime

• src/terminal/io/pty_unix.zig now uses macOS-appropriate PTY headers instead
  of assuming Linux-only includes
• macOS default shell startup now execs the configured shell directly as a
  login shell instead of misusing /usr/bin/login
• terminal-mode startup no longer hits the initial bogus login failure seen in
  earlier bring-up

Release Position

• this is a checkpoint release for the current macOS GL lane, not the final
  native macOS architecture
• Metal/AppKit ownership work is still ahead and remains explicitly tracked in
  docs/todo/macos/implementation.md

Current Beta Release Notes

• Release tag: v0.1.0-beta.5
• Product version: 0.1.0-beta.5
• Release date: 2026年04月05日
• Current authority docs:
  • BOOTSTRAP.md
  • DEPENDENCIES.md
  • DEVELOPMENT_JOURNEY.md
  • macOS implementation queue

Validation Position

• native macOS compile/build truth is green for:
  • zig build
  • zig build -Dmode=editor
  • zig build -Dmode=terminal
• macOS CLI/bootstrap smoke was run from the published dependency graph for the
  release-prep path
• broader native GUI/manual interaction validation is still a follow-up item
  before claiming full first-class macOS maturity

v0.1.0-beta.4 - Editor Runtime And Windows Bootstrap Checkpoint

v0.1.0-beta.4 is a small checkpoint release focused on two things:

• making the editor visible-highlight path more runtime-owned and less draw-path
  driven
• keeping the Zig-managed dependency/bootstrap path viable across Linux and the
  active Windows branch

This is not a large feature release. It is a stabilization checkpoint that
cleans up several recent seams before the next validation and release-quality
push.

It also coincides with a large Windows branch fast-forward and ongoing Windows
font/rendering architecture work. That branch progress is real, but the broader
automated validation surface is not fully green yet, so this beta should be
read as a checkpoint release rather than a "everything closed out" release.

Summary

• visible editor highlight work now runs through a worker-oriented runtime seam
  instead of the earlier frame-driven startup trickle path
• synthetic large-file fallback highlight tokens were removed from the render
  path so highlight output reflects actual runtime/highlighter truth
• visible precompute is now gated on real pending highlight/layout work, which
  materially reduced empty frame churn in the Unicode stress path
• the Windows branch text-stack build path now keeps Linux zlib linkage
  correct while Windows work continues on its own branch

Technical Breakdown

Editor Runtime

• visible highlight scheduling is editor/runtime-owned rather than render-cache
  owned
• request, compute, ready, publish, and redraw now have clearer runtime seams
• the startup 4-line visible highlight throttle is gone; the visible Unicode
  stress file now schedules as one visible-range batch instead of trickling

Render / Cache Cleanup

• synthetic large-file fallback tokens were removed from the render path
• wrap work now tracks completed visible ranges, like line-width work, which
  removed a large amount of layout-only churn after highlight completion
• visible precompute now runs only when highlight scheduling or layout work is
  actually pending

Build / Platform

• repo-local absolute paths were removed from docs and local tooling config
• case-colliding kitty fixture names were normalized so Windows can track the
  fixture set on a case-insensitive filesystem
• the Windows branch now carries the Linux-side zlib linkage fix for the
  Zig-managed FreeType/HarfBuzz text stack
• Windows also moved forward substantially on Zig-managed bootstrap,
  fractional-scaling text rendering, and app/font ownership cleanup, even
  though that lane still needs broader test closure before it can be described
  as fully settled

Current Beta Release Notes

• Release tag: v0.1.0-beta.4
• Product version: 0.1.0-beta.4
• Release date: 2026年03月20日
• Current authority docs:
  • BOOTSTRAP.md
  • DEPENDENCIES.md
  • EDITOR_RUNTIME_CONTRACT.md
  • TERMINAL_BETA_CHECKPOINT.md
• Validation position:
  • primary app builds are green for this checkpoint
  • broader automated test/gate cleanup is still in progress

Keep Out Of The Notes

• do not present this as a full release-readiness claim
• do not imply the broader automated validation surface is fully green yet
• do not turn a checkpoint note into a long commit inventory

v0.1.0-beta.3 - Terminal Cleanup And Host-Contract Beta

v0.1.0-beta.3 is a post-rewrite terminal checkpoint focused on native quality
hardening, tighter host/backend boundaries, and richer terminal-derived host
state on top of the rewritten VT/render architecture.

For current install, compatibility, and architecture notes, prefer the hosted
docs and current terminal authority docs linked below rather than treating
these notes as a full architecture spec.

Summary

v0.1.0-beta.3 keeps the rewrite direction from the earlier betas and turns
recent dogfooding into product-visible cleanup:

• terminal viewport chrome is now host-owned instead of terminal-content-owned
  for the scrollbar path
• native/backend boundaries are tighter after moving paste and close-confirm
  policy out of TerminalSession
• native terminal tabs can surface richer task context, including progress and
  compact foreground command summaries
• recent correctness fixes closed real daily-use issues in tab reorder, copy,
  focus loss, selection anchoring, glyph fallback, and bursty input pressure

Technical Breakdown

Native Path

• Native remains the reference host for terminal contract correctness, but the
  host/runtime split is materially cleaner than the earlier beta checkpoint.
• Terminal scrollbar behavior is now app chrome rather than terminal content
  behavior, which reduces ownership confusion around hover, drag, focus, and
  alt-screen suppression.
• Native terminal tab chips now compose host presentation from backend facts
  such as progress, foreground process state, and compact command summaries.

Hardening Wins

• Terminal tab drag reorder now keeps backend workspace state, live terminal
  widgets, and keyboard navigation aligned.
• Ctrl+Shift+C copying scrollback no longer snaps the viewport back to the
  live cursor.
• Lazydocker box-drawing gaps were fixed by routing unsupported special glyphs
  back through normal font fallback instead of dropping them.
• Focus-loss hover behavior is now cleaner across terminal scrollbar and other
  edge-hover surfaces.
• Threaded PTY sessions now keep active pressure while unread parse-buffer IO
  remains queued, which tightens the held-input / burst-redraw feel in chatty
  TUIs.

FFI / Host Contract

• Metadata v3 now exports the first richer activity/task summary through the
  live terminal bridge:
  • foreground process presence
  • semantic prompt/input/output state
  • semantic prompt kind and exit-code truth
  • optional foreground process label
• The backend now owns a shared ActivityMetadata summary used by both FFI and
  native host paths, instead of duplicating that host-facing reasoning in the
  bridge.
• Progress remains a real backend semantic family in native, while FFI progress
  exposure is still deliberately deferred until the shared contract is widened
  on purpose.

Quality Positioning

This beta is not claimed as feature parity with kitty or ghostty; it is a
cleanup and convergence checkpoint:

• Ghostty is still ahead on engine-centered minimalism and surface cleanliness.
• Zide is now materially stronger on explicit host-contract richness and
  native/FFI convergence than the earlier beta wording implied.
• The remaining terminal risks are increasingly concentrated in narrower redraw
  and contract edge cases, not in broad rewrite instability.

Current Checkpoints

• Native UX
  • terminal scrollbar moved into host chrome
  • native terminal tabs surface progress and richer command context
  • close-confirm and paste policy no longer hide inside terminal-session logic
• Bridge semantics
  • Metadata v3 activity/task export is live
  • shared backend ActivityMetadata now feeds both FFI and native host flows
• Compatibility
  • recent dogfood fixes materially improved behavior for nvim, btop,
    lazydocker, and Codex CLI daily-use workflows

Current Beta Release Notes

• Release tag: v0.1.0-beta.3
• Product version: 0.1.0-beta.3
• Release date: 2026年03月17日
• Authoritative terminal docs:
  • TERMINAL_ARCHITECTURE_COMPARISON.md
  • BRIDGE_DESIGN.md
  • SNAPSHOT_ABI.md
  • TERMINAL_BETA_CHECKPOINT.md

Keep Out Of The Notes

• do not treat this as final parity with kitty / ghostty
• do not list long commit inventories
• do not add internal debug-war-room details unless they materially changed the
  live runtime story

v0.1.0-beta.2 - Terminal Cleanup And Host-Contract Beta

v0.1.0-beta.2 is a post-rewrite terminal checkpoint focused on cleanup,
native/FFI host-contract convergence, and a narrower compatibility hardening set
on top of the rewritten VT/render architecture.

For current install, compatibility, and architecture notes, prefer the hosted docs
and current terminal authority docs linked below rather than treating these notes
as full architecture spec.

Summary

v0.1.0-beta.2 keeps the terminal rewrite direction from the prior release and
adds production-oriented host-contract tightening:

• terminal metadata and snapshot APIs moved to request-based retrieval for cheaper
  hot-path usage
• backend-owned viewport control and pending outbound input are now fully shared
  between native and Flutter-style transport paths
• child-exit reporting reached contract alignment across host modes
• the terminal FFI diff lane is now coherent in first-cut form and now used with
  one-acquire fallback discipline

Technical Breakdown

Native Path

• Native remains the reference host for terminal contract correctness, but it is
  no longer a privileged semantic path.
• The renderer-owned composition/present path remains the baseline architecture,
  with explicit redraw/present acknowledgement and publication sequencing.
• Native debug/bug workaround patterns were reduced in favor of narrower
  ownership-driven flow.

Hardening Wins

• Scrolling and command-visual validation now include a verified host-aware
  snapshot diff boundary:
  • full-refresh fallback on startup/invalid history transitions
  • granular diff after an acked settled baseline
• Metadata and snapshot read paths now avoid unnecessary unconditional string churn by
  requiring explicit request-level inclusion of non-scalar fields.
• Cross-host terminal contract behavior (including child exit, focus, and color
  reporting) remains stable under second-host integration.

FFI / Host Contract

• Request-based metadata and snapshot acquisition are now stable contract points.
• Diff API now carries cursor state directly, removing the prior host-side cursor
  workaround.
• present_ack now advances terminal-hosted publication lineage in line with the
  diff baseline rules.
• The shared redraw -> snapshot/diff -> present flow now has cleaner fallback
  behavior and remains one-acquire one-release in normal hot paths.

Quality Positioning

This beta is not claimed as feature parity with kitty or ghostty; it is a
convergence checkpoint:

• libghostty-vt-style engine-centered cleanliness remains ahead on architecture
  minimalism.
• Zide is materially stronger on explicit host-contract richness and native/FFI
  convergence than the older checkpoint.
• The immediate remaining risk is ongoing performance and edge-case hardening in a
  narrow snapshot-cost lane, not a broad terminal-API rewrite reset.

Current Checkpoints

• Terminal FFI:
  • metadata and snapshot now use request includes for strings
  • first conservative snapshot-diff lane with explicit fallback behavior
  • direct cursor truth in diff payload
• Diff behavior:
  • startup baseline full-refresh remains out of granular guarantee by design
  • settled baseline granular path now coherent after publication-lineage
    retirement fix
• Cross-host:
  • shared widget/controller behavior holds across bridge-owned PTY and Flutter-owned
    PTY transport

Current Beta Release Notes

• Release tag: v0.1.0-beta.2
• Product version: 0.1.0-beta.2
• Release date: 2026年03月16日
• Authoritative terminal docs:
  • TERMINAL_ARCHITECTURE_COMPARISON.md
  • BRIDGE_DESIGN.md
  • SNAPSHOT_ABI.md
  • TERMINAL_FFI_PERFORMANCE_REVIEW_2026年03月15日.md

Keep Out Of The Notes

• do not treat this as final parity with kitty / ghostty
• do not list long commit inventories
• do not add legacy rewrite-war-room debugging details unless they materially affect
  user-facing behavior

v0.1.0-beta.1 - First VT/Render Rewrite Beta

v0.1.0-beta.1 is the first public semver beta built on Zide's rewritten
VT/render path. This is the checkpoint where the terminal stopped treating the
default framebuffer as the normal composition surface and moved to a
renderer-owned scene target with explicit renderer-owned present
acknowledgement. The result is a much cleaner Linux native terminal path, plus
the first serious hardening pass on top of that architecture.

Technical Breakdown

Renderer / Present Path

• Main terminal composition now happens in a renderer-owned scene target.
• The default framebuffer is now just the final present sink or a degraded
  fallback, not the normal architectural path.
• Terminal present retirement is tied to renderer-owned successful submission
  instead of widget-local draw completion.
• Much of the rewrite-era war-room probe and override machinery has now been
  removed from the live runtime, so the shipped path reflects the intended
  architecture more honestly.

Hardening Wins

• Codex inline resumed history now retires into real primary scrollback instead
  of collapsing into the visible pre-viewport band.
• Zig std.Progress redraw now rewrites in place correctly; synchronized redraw
  plus reverse-index handling no longer leave stale blocks appended at the
  bottom.
• Focused native input latency is materially tighter after replacing blind
  focused-idle sleep with event-aware wake waiting, while steady-state CPU stays
  in the good pre-rewrite range.
• Current native validation is holding on the rewritten path for the main
  workload set, including nvim and btop.

FFI / Host Contract

• The FFI redraw/publication/present contract has been tightened to match the
  stronger native ownership model.
• Hosts now have explicit publication truth, acknowledgement truth, and redraw
  truth instead of blurrier wake/event semantics alone.
• This keeps the native GUI as the proving ground while making the eventual
  embedded and Flutter host path more honest.

Current Quality Bar

• This beta is the first public checkpoint of the rewritten terminal
  architecture, not the end of the terminal hardening story.
• The architectural rewrite is coming to an end; the project is now in a
  post-rewrite phase of bug hunting, compatibility hardening, and
  native/embedded contract convergence.
• Zide should still be described honestly as a beta rather than as full
  kitty / ghostty parity.

Zide beta-0.0.2

Highlights:

• focused native input latency improved by replacing blind focused-idle sleep with event-aware wake waiting
• Codex inline resume history now retires into real primary scrollback on the rewritten path
• Zig std.Progress redraw now rewrites in place correctly on the native terminal path

Assets:

• zide-terminal bundle
• zide-editor bundle
• zide-ide bundle
• zide-terminal FFI
• zide-editor FFI
• SHA256SUMS

zide ffi release beta-0.0.1