@kolisachint/hoocode-agent 0.5.58 → 0.5.59

package/CHANGELOG.md

@@ -1,5 +1,23 @@
 # Changelog
 
+## [0.5.59] - 2026-09-05
+
+### Fixed
+
+- **`hoo`, `/new` and `/reload` now leave you looking at the same thing.** All
+  three rebuild the session's resources and repaint the chrome, and they did it
+  from two hand-kept lists, so an edit to `settings.json` reached one and not the
+  other: after `/reload` the footer went on promising auto-compaction that was
+  switched off, and the model count, the subagent indicator and the session chip
+  kept the state of the session before it; after `/new` a changed `theme` never
+  loaded at all. A theme that did load left the banner in the retired theme's
+  colours, on either path — a `Text` holds its string with the escapes already in
+  it, so invalidating it is not repainting it. One list now, applied by every
+  path, and the resource listing is drawn once per session change instead of
+  drawn and immediately wiped. `/reload` also drops the stale view-layer
+  references into the transcript it just replayed, the way a session swap always
+  has.
+
 ## [0.5.58] - 2026-09-04
 
 ### Changed

package/dist/modes/interactive/interactive-mode.d.ts

@@ -3,6 +3,7 @@
  * Handles TUI rendering and user interaction, delegating business logic to AgentSession.
  */
 import type { ImageContent } from "@kolisachint/hoocode-ai";
+import type { Terminal } from "@kolisachint/hoocode-tui";
 import type { AgentSessionRuntime } from "../../core/agent-session-runtime.js";
 import type { TeamViewConnection } from "../../core/team-view.js";
 /**
@@ -21,6 +22,11 @@ export interface InteractiveModeOptions {
     initialMessages?: string[];
     /** Force verbose startup (overrides quietStartup setting) */
     verbose?: boolean;
+    /**
+     * Terminal the TUI draws to. Defaults to the real process terminal; tests
+     * pass a capturing one to mount the whole mode headlessly and screenshot it.
+     */
+    terminal?: Terminal;
 }
 export declare class InteractiveMode {
     private options;
@@ -164,19 +170,51 @@ export declare class InteractiveMode {
      */
     private getDispatchableAgentCount;
     private bindCurrentSessionExtensions;
+    /**
+     * Push the current settings and session onto the chrome: keybindings, footer,
+     * editor, cursor.
+     *
+     * Startup, a session swap (/new, /resume, /fork, /cd) and /reload all rebuild
+     * the same things from disk, so they must all repaint the same way. They used
+     * to do it with two hand-kept copies of this list, and the /reload copy was
+     * missing pieces — a `compaction.enabled` edit left the footer still
+     * promising auto-compaction. One list, called from both paths; the theme is
+     * the second half, in `applySessionTheme`.
+     */
     private applyRuntimeSettings;
+    /**
+     * Load the theme the settings name, and rebuild what holds colour baked in.
+     *
+     * Runs after extensions are bound (and after `session.reload()`), because a
+     * `resources_discover` handler can contribute the very theme directory the
+     * name resolves in — resolving it earlier would fall back to dark for anyone
+     * whose theme ships with an extension.
+     *
+     * The banner is rebuilt rather than invalidated: a `Text` holds its string
+     * with the escapes already in it, so invalidating only drops the line cache
+     * and the old theme's colours come straight back. It also names the working
+     * directory, which `/cd` moves.
+     */
+    private applySessionTheme;
+    private finishRuntimeSettings;
     private rebindCurrentSession;
     private handleFatalRuntimeError;
     /**
-     * Reset the transcript to whatever the (possibly just-swapped) session holds.
+     * Drop every view-layer reference into the transcript that is about to be
+     * rebuilt. Shared by the session swaps and by /reload: a component that
+     * survives the clear is detached, so anything still pointing at it (the open
+     * chain the next tool call would join, the block the unfold key peels back)
+     * would be writing to a frame nobody renders.
+     */
+    private resetTranscriptView;
+    /**
+     * Reset the transcript to whatever the just-swapped session holds.
      *
-     * Every caller — /new, /resume, /fork — reaches here *after* the runtime has
-     * rebound extensions, and rebinding is what renders the loaded-resource
-     * listing. Clearing the chat therefore wiped the listing a moment after it was
-     * drawn, which is why /reload showed skills, agents and plugins and starting a
-     * new session showed nothing. Re-rendering it here is what makes the surface
-     * common: one call site, so a session change of any kind reports the same
-     * capabilities /reload does.
+     * Every caller — /new, /resume, /fork, /cd, /import — reaches here after the
+     * runtime has rebound extensions. Drawing the listing here rather than in the
+     * rebind is what makes the surface common: one call site, so a session change
+     * of any kind reports the same capabilities /reload does, and neither path
+     * draws the listing twice.
      */
     private renderCurrentSessionState;
     /**