internal/

Package buildinfo resolves the version string printed by `wt -version` / `wtd -version`.

Package client is the one shared thin HTTP client every wt-cockpit frontend — the CLI (cmd/wt) and the TUI (internal/tui) — uses to talk to wtd.

Package config loads wtd's optional TOML config file (~/.config/wtcockpit/config.toml by default).

Package diffparse turns `git diff` unified output into structured model.DiffFile values.

Package discovery scans root directories for git repositories.

Comment operations: validation lives here (the trust boundary; handlers stay thin), along with the stale/orphaned computation against the worktree's current cached diff and the comment.changed delta emission.

Package gitbackend abstracts all git access behind an interface.

Package guardrail evaluates declarative rules over a worktree diff and returns the tripped rules.

Package model holds the core domain types shared across the engine and clients.

Package notify is wtd's desktop-notification subscriber: a plain registry- bus subscriber (Notifier.Run) that fires an OS notification on danger- severity guardrail.tripped events, via a fixed-argv exec — osascript on darwin, notify-send on linux, never a shell (P5-design.md §1.5).

Package registry is the in-memory source of truth for tracked worktrees plus a small pub/sub event bus.

open.go implements store.Open (P6-design.md §7/§4): extension-based backend dispatch (".json" → the JSON escape hatch, forever; anything else → SQLite), the one-time JSON→SQLite import that runs only when a SQLite db is being created (§4.2), and the corrupt-db move-aside safety net (§4.3) that sqlite.go's OpenSQLite deliberately leaves to this layer.

Package tui is the Bubble Tea program: a thin client exactly like cmd/wt — it speaks only through internal/client (HTTP+SSE over wtd's Unix socket), holding zero git logic and importing nothing from internal/engine or below (docs/02-stack-decision.md's constitution).

Package watcher triggers engine refreshes.

comments.go builds the reading room's comment view-models: the per-file "strip" of threads (P4-design.md §1.5's fallback placement for stale/ orphaned comments, generalised here to every comment — see room.tmpl's own doc comment for why the side-by-side grid can't safely host a variable- height thread inline) and the page-bottom section for comments whose file left the diff entirely.