@kolisachint/hoocode-agent 0.5.39 → 0.5.41

package/CHANGELOG.md

@@ -1,5 +1,103 @@
 # Changelog
 
+## [0.5.41] - 2026-08-31
+
+### Added
+
+- Sessions record the git branch they started on, and the resume list shows it.
+
+  A session you never named, that opened with "look at this", was unfindable in
+  the list — the first message said nothing and there was nothing else to go on.
+  The branch usually says exactly what the work was, and it is the rare piece of
+  meaning that can be written down safely: unlike a derived title it is a fact,
+  so it is still true a month later.
+
+  It has to be recorded rather than derived, because by the time anyone reads the
+  list the working tree has moved on. One optional field on the session header,
+  read from `.git/HEAD` at session creation — a walk up to the repo and one file
+  read, no subprocess outside the reftable case, sharing the footer's
+  implementation so the branch a session remembers is the string the footer was
+  showing at the time.
+
+  Shown in the picker only where it adds something: a session with a chosen name
+  already says what it is, and `main` names no particular work. Also in
+  `/session`. Sessions recorded before this simply have no branch and read as
+  they did.
+
+- A session chip: the session's name, filled with its colour, laid into the
+  top-right of the input box.
+
+  The name used to live at the tail of the footer's busiest line — after the
+  brand mark, the mode, the path and the git branch, in `dim`, the quietest
+  colour a theme has. It answered *which session is this*, and it was the least
+  visible thing on screen. The chip puts the same fact where the cursor already
+  is, and gives it a colour so it can be recognised rather than read.
+
+  Every session now carries a name and a colour without anyone setting one. Both
+  are pure functions of the session id: a two-word slug from a 32x32 vocabulary
+  (`amber-harbor`), and a slot in the six-colour identity palette the agent tags
+  already use. Because they derive from the id, a resumed session comes back
+  wearing the same chip and a fork gets its own, with nothing to store. `/name`
+  and the new `/color` override either, and those choices are written to the
+  session's `session_info` entry, which now resolves its two fields
+  independently — setting a colour cannot clear a name, and renaming keeps the
+  colour you have already learned. `/color` on its own opens a swatch picker
+  that repaints the live chip as you move through it.
+
+  The chip is laid into border cells the box was already drawing, so it costs no
+  screen row, and it yields where it should: to the `↑ N more` scroll indicator
+  on the same border, and to the box itself below 48 columns, where the footer
+  takes the name back rather than leaving it nowhere. The editor's border colour
+  is untouched — it still carries thinking level and bash mode, so identity and
+  agent state never fight for the same pixels.
+
+  The fill's ink is picked from its own luminance, which is what lets one code
+  path render on a dark theme's bright hues and a light theme's deep inks alike.
+  `theme.fill()` is the new primitive for that: the palette lives on the
+  foreground side, where `theme.bg()` could not reach it.
+
+  The session picker shows the same colour as a swatch per row, and the slug for
+  sessions nobody has named, so a session recognised by its chip is found the
+  same way in the list.
+
+## [0.5.40] - 2026-08-30
+
+### Added
+
+- A `solarized-light` / `solarized-dark` pair: Ethan Schoonover's palette kept
+  as it was designed rather than corrected to a contrast floor.
+
+  Solarized is one palette read from both ends — eight monotones on a symmetric
+  CIELAB lightness ramp, and eight accents that are the *same hex* on either
+  ground. The two themes are that ramp with the roles mirrored (`base03`↔`base3`
+  for the page, `base02`↔`base2` for the highlight, `base01`↔`base1` for
+  comments, `base00`↔`base0` for body), and nothing is retuned per mode:
+  `success` is `green` `#859900` and `error` is `red` `#dc322f` on cream and on
+  slate alike. `test/theme-contrast.test.ts` checks the two files against each
+  other for exactly that, because a theme that drifts an accent between modes
+  has stopped being this palette.
+
+  Each mode has three content tones rather than a ramp of grays, and the tokens
+  are mapped onto them: `text`/`toolTitle` emphasized, `muted`/`toolOutput`
+  body, `dim` and the quotes, rules and syntax comments in the comment tone at
+  2.0-2.8:1. That is where Solarized puts its comments, so this pair is neither
+  AAA like the accessible themes nor AA like `vox-*` — it holds the contrast
+  Solarized actually has, tier by tier (content 3.2:1, accents 2.3:1, comments
+  1.9:1), on every surface it paints and on both Solarized terminal stops.
+  Anyone who needs a guaranteed floor still wants `warm-*`, `colorsafe-*` or
+  `high-contrast-*`, and the theme docs say so.
+
+  Two things the TUI needs that sixteen colors do not cover. The transcript
+  wants a surface per tool state where Solarized ships two background stops, so
+  each sheet is mixed from the accent that already means that state and then
+  pulled back to the highlight's own lightness — a state reads through hue
+  instead of by getting louder, which is what keeps the ink on a tool box at the
+  contrast it has on the page. And position gets no hue at all: `selectedBg` and
+  the radar mark are neutrals on the `base03`→`base01` axis, one step off the
+  page. Those surfaces are the only colors in either file that are not
+  canonical, and they are named in `vars`; the test rejects a non-canonical
+  *ink*.
+
 ## [0.5.39] - 2026-08-28
 
 ### Fixed

package/dist/core/agent-session.d.ts

@@ -272,6 +272,10 @@ export declare class AgentSession {
     get sessionId(): string;
     /** Current session display name, if set */
     get sessionName(): string | undefined;
+    /** What to show for this session: the chosen name, else its auto-assigned slug */
+    get displayName(): string;
+    /** The session's colour slot (1-6), chosen or auto-assigned */
+    get sessionColorSlot(): number;
     /** Scoped models for cycling (from --models flag) */
     get scopedModels(): ReadonlyArray<{
         model: Model<any>;
@@ -519,6 +523,12 @@ export declare class AgentSession {
      * Set a display name for the current session.
      */
     setSessionName(name: string): void;
+    /**
+     * Set the colour slot (1-6) the session's chip is filled with. Written as its
+     * own field so it survives a later rename, and so setting it never disturbs
+     * the name.
+     */
+    setSessionColor(slot: number): void;
     /**
      * Navigate to a different node in the session tree.
      * Unlike fork() which creates a new session file, this stays in the same file.