@kolisachint/hoocode-agent 0.5.6 → 0.5.8

package/CHANGELOG.md

@@ -1,5 +1,74 @@
 # Changelog
 
+## [0.5.8] - 2026-08-12
+
+### Changed
+
+- **Capability listings share one layout.** `/plugin list`,
+  `/plugin marketplace list`, `SearchPlugins` and `ListPlugins` each built their
+  own `name [a, b] — description` line, so the same plugin printed three ways
+  and the model's view never matched the user's. They now go through a single
+  row formatter (`core/format-list.ts`, `core/extensions/plugins/listing.ts`):
+  aligned name column, facts beside it, description wrapped with a hanging
+  indent instead of restarting at column 0, and plugins grouped by the
+  marketplace that offers them. `/plugin list` marks what is already installed.
+- `SearchPlugins` takes a `limit` (default 10). With no query it previously
+  returned every plugin in every registered marketplace — dozens of entries,
+  several lines each — into the chat and the context.
+- The five plugin tools define `renderResult`, as every other built-in tool
+  already did. Results are bounded to 20 lines with an expand hint rather than
+  dumped whole.
+- `ListPlugins` reports the manifest format its description already promised,
+  counts `themes` and `providers` as capabilities (a plugin shipping only a
+  theme reported none), and carries the plugin description through.
+- `[Agents]` in the startup summary is one line per agent, truncated to the
+  terminal, instead of a 200-character summary wrapping into a paragraph.
+- `brand.ts` moved to `core/` so non-interactive surfaces can label capability
+  classes; added a `marketplaces` glyph.
+
+### Fixed
+
+- Status messages carrying their own colors are no longer wrapped in a blanket
+  dim. `theme.fg` closes with `\x1b[39m` (reset, not restore), so the dim died
+  at the first inner span and — because the wrapper carries that state across
+  newlines — every line after it lost the dim too.
+- `InstallPlugin` no longer erases its own announcement. It notified "installing
+  X because Y", then notified the outcome; consecutive info notifications
+  coalesce into one chat line, so the second replaced the first and the
+  transparency the tool guidelines require never reached the screen.
+- Truncation in the new listings does not emit escape codes. The TUI's
+  `truncateToWidth` appends `\x1b[0m` even for plain input — a full reset that
+  would both leak into model-facing text and clear any enclosing style mid-line.
+
+### Added
+
+- `ExtensionUIContext.columns` exposes the terminal width to extensions, so a
+  listing can wrap to the actual terminal. Optional, and undefined outside a
+  terminal (RPC, print), which is the signal to emit unwrapped text rather than
+  wrap to someone else's width.
+
+## [0.5.7] - 2026-08-12
+
+### Added
+
+- **`vox-dark` and `vox-light` themes** — explanatory-journalism styling: one
+  loud yellow used sparingly against a newsprint-quiet palette. The yellow is
+  reserved for four roles (`accent`, `mdHeading`, `selectedBg`, `borderAccent`)
+  and never carries a status, so `warning` is orange rather than the usual
+  yellow — a yellow `◐` or context gauge stops reading as a signal when yellow
+  is already the accent. Both are AA, not AAA, and are not covered by
+  `test/theme-contrast.test.ts`, but they are held to the same standards the
+  default `light` theme gained in 0.5.6: every text token clears 4.5:1 on every
+  surface it paints, rules and inactive chrome clear 2.8:1, and no two tokens
+  that mean different things sit closer than ΔE 11. Rules stay neutral rather
+  than saturated — a separator carries no meaning through hue — which is the one
+  deliberate departure, documented in `docs/themes.md`.
+- Optional `brandBg` / `brandText` theme tokens, honored only as a pair, paint
+  the footer's brand mark as a filled chip instead of accent-colored text.
+  Themes that omit them are unchanged. Added for light themes, where a brand
+  hue vivid enough to be recognizable is rarely legible as text on a light
+  canvas. `vox-light` is the only built-in that sets them.
+
 ## [0.5.6] - 2026-08-12
 
 ### Changed

package/dist/{modes/interactive → core}/brand.d.ts

@@ -11,6 +11,11 @@
  * Glyphs are chosen to be single terminal cell, widely supported, and distinct
  * from the task-panel's own status/owner glyphs (◐ ◆ ◇ ▸ ⧉ ✓ ✗ ○) so the two
  * vocabularies never read as the same signal.
+ *
+ * This lives in `core/` rather than `modes/interactive/` because the `/plugin`
+ * command extension labels the same capability classes, and extensions must not
+ * reach into a mode's internals. The module is pure data — no theme, no
+ * rendering — so it is safe for every surface.
  */
 /** The HooCode mark — a filled hexagon, rendered in the accent colour. */
 export declare const BRAND_MARK = "\u2B22";
@@ -25,6 +30,7 @@ export declare const CATEGORY_GLYPH: {
     readonly agents: "◈";
     readonly mcp: "⧉";
     readonly plugins: "⬡";
+    readonly marketplaces: "⊞";
     readonly themes: "◒";
     readonly context: "❯";
     readonly extensions: "⊹";

package/dist/core/brand.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"brand.d.ts","sourceRoot":"","sources":["../../src/core/brand.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;GAkBG;AAEH,4EAA0E;AAC1E,eAAO,MAAM,UAAU,WAAM,CAAC;AAE9B;;;;GAIG;AACH,eAAO,MAAM,cAAc;;;;;;;;;;CAUjB,CAAC;AAEX,MAAM,MAAM,WAAW,GAAG,MAAM,OAAO,cAAc,CAAC;AAEtD,iEAAiE;AACjE,eAAO,MAAM,WAAW,WAAM,CAAC;AAE/B,yCAAyC;AACzC,eAAO,MAAM,gBAAgB,WAAM,CAAC","sourcesContent":["/**\n * HooCode brand identity — the single source of truth for the product mark and\n * the glyph vocabulary the interactive surfaces share.\n *\n * The brand *colour* is the theme's `accent` token (see theme/dark.json,\n * theme/light.json) so it stays theme-aware and swappable; this module owns the\n * non-colour identity: the mark and the category glyphs used by the footer,\n * the startup resource summary, and anywhere a capability class is labelled.\n * Keeping them here means a future rebrand touches one file, not twenty.\n *\n * Glyphs are chosen to be single terminal cell, widely supported, and distinct\n * from the task-panel's own status/owner glyphs (◐ ◆ ◇ ▸ ⧉ ✓ ✗ ○) so the two\n * vocabularies never read as the same signal.\n *\n * This lives in `core/` rather than `modes/interactive/` because the `/plugin`\n * command extension labels the same capability classes, and extensions must not\n * reach into a mode's internals. The module is pure data — no theme, no\n * rendering — so it is safe for every surface.\n */\n\n/** The HooCode mark — a filled hexagon, rendered in the accent colour. */\nexport const BRAND_MARK = \"⬢\";\n\n/**\n * Glyphs for the capability classes a session can load. Used by the startup\n * \"resources ready\" summary and reusable anywhere a class needs a label. Each is\n * a single cell so counts and columns stay aligned.\n */\nexport const CATEGORY_GLYPH = {\n\tskills: \"✦\",\n\tcommands: \"⌘\",\n\tagents: \"◈\",\n\tmcp: \"⧉\",\n\tplugins: \"⬡\",\n\tmarketplaces: \"⊞\",\n\tthemes: \"◒\",\n\tcontext: \"❯\",\n\textensions: \"⊹\",\n} as const;\n\nexport type CategoryKey = keyof typeof CATEGORY_GLYPH;\n\n/** A soft dot separator used between footer/summary segments. */\nexport const SEGMENT_SEP = \"·\";\n\n/** Fork glyph preceding a git branch. */\nexport const GIT_BRANCH_GLYPH = \"⑂\";\n"]}

package/dist/{modes/interactive → core}/brand.js

@@ -11,6 +11,11 @@
  * Glyphs are chosen to be single terminal cell, widely supported, and distinct
  * from the task-panel's own status/owner glyphs (◐ ◆ ◇ ▸ ⧉ ✓ ✗ ○) so the two
  * vocabularies never read as the same signal.
+ *
+ * This lives in `core/` rather than `modes/interactive/` because the `/plugin`
+ * command extension labels the same capability classes, and extensions must not
+ * reach into a mode's internals. The module is pure data — no theme, no
+ * rendering — so it is safe for every surface.
  */
 /** The HooCode mark — a filled hexagon, rendered in the accent colour. */
 export const BRAND_MARK = "⬢";
@@ -25,6 +30,7 @@ export const CATEGORY_GLYPH = {
     agents: "◈",
     mcp: "⧉",
     plugins: "⬡",
+    marketplaces: "⊞",
     themes: "◒",
     context: "❯",
     extensions: "⊹",

package/dist/core/brand.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"brand.js","sourceRoot":"","sources":["../../src/core/brand.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;GAkBG;AAEH,4EAA0E;AAC1E,MAAM,CAAC,MAAM,UAAU,GAAG,KAAG,CAAC;AAE9B;;;;GAIG;AACH,MAAM,CAAC,MAAM,cAAc,GAAG;IAC7B,MAAM,EAAE,KAAG;IACX,QAAQ,EAAE,KAAG;IACb,MAAM,EAAE,KAAG;IACX,GAAG,EAAE,KAAG;IACR,OAAO,EAAE,KAAG;IACZ,YAAY,EAAE,KAAG;IACjB,MAAM,EAAE,KAAG;IACX,OAAO,EAAE,KAAG;IACZ,UAAU,EAAE,KAAG;CACN,CAAC;AAIX,iEAAiE;AACjE,MAAM,CAAC,MAAM,WAAW,GAAG,IAAG,CAAC;AAE/B,yCAAyC;AACzC,MAAM,CAAC,MAAM,gBAAgB,GAAG,KAAG,CAAC","sourcesContent":["/**\n * HooCode brand identity — the single source of truth for the product mark and\n * the glyph vocabulary the interactive surfaces share.\n *\n * The brand *colour* is the theme's `accent` token (see theme/dark.json,\n * theme/light.json) so it stays theme-aware and swappable; this module owns the\n * non-colour identity: the mark and the category glyphs used by the footer,\n * the startup resource summary, and anywhere a capability class is labelled.\n * Keeping them here means a future rebrand touches one file, not twenty.\n *\n * Glyphs are chosen to be single terminal cell, widely supported, and distinct\n * from the task-panel's own status/owner glyphs (◐ ◆ ◇ ▸ ⧉ ✓ ✗ ○) so the two\n * vocabularies never read as the same signal.\n *\n * This lives in `core/` rather than `modes/interactive/` because the `/plugin`\n * command extension labels the same capability classes, and extensions must not\n * reach into a mode's internals. The module is pure data — no theme, no\n * rendering — so it is safe for every surface.\n */\n\n/** The HooCode mark — a filled hexagon, rendered in the accent colour. */\nexport const BRAND_MARK = \"⬢\";\n\n/**\n * Glyphs for the capability classes a session can load. Used by the startup\n * \"resources ready\" summary and reusable anywhere a class needs a label. Each is\n * a single cell so counts and columns stay aligned.\n */\nexport const CATEGORY_GLYPH = {\n\tskills: \"✦\",\n\tcommands: \"⌘\",\n\tagents: \"◈\",\n\tmcp: \"⧉\",\n\tplugins: \"⬡\",\n\tmarketplaces: \"⊞\",\n\tthemes: \"◒\",\n\tcontext: \"❯\",\n\textensions: \"⊹\",\n} as const;\n\nexport type CategoryKey = keyof typeof CATEGORY_GLYPH;\n\n/** A soft dot separator used between footer/summary segments. */\nexport const SEGMENT_SEP = \"·\";\n\n/** Fork glyph preceding a git branch. */\nexport const GIT_BRANCH_GLYPH = \"⑂\";\n"]}

package/dist/core/extensions/plugins/listing.d.ts

@@ -0,0 +1,34 @@
+/**
+ * Row shapes for the plugin listings, shared by every surface that prints one.
+ *
+ * `/plugin list`, `SearchPlugins` and `ListPlugins` describe the same objects,
+ * and each used to build its own `name [a, b] — description` string, so the same
+ * plugin printed three ways and the model's view never quite matched the user's.
+ * They all go through here now; only the styling and the width differ.
+ */
+import type { ListGroup, ListRow } from "../../format-list.js";
+import type { AvailablePlugin } from "./install.js";
+import type { NormalizedPlugin } from "./manifest.js";
+/** Human-readable source for an available plugin (a URL, a path, an npm spec). */
+export declare function formatPluginSource(source: AvailablePlugin["source"]): string;
+/**
+ * Capability classes a plugin actually ships.
+ *
+ * Covers every capability `NormalizedPlugin` can carry — themes and providers
+ * included, which the old `ListPlugins` inline list omitted, so a plugin that
+ * shipped only a theme or only a provider reported no capabilities at all.
+ */
+export declare function pluginCapabilities(plugin: NormalizedPlugin): string[];
+/**
+ * Available plugins, grouped by the marketplace offering them.
+ *
+ * Grouping is what makes provenance legible: a flat list cannot answer "where
+ * would this come from if I installed it", which is the one question that
+ * matters at a trust boundary. Marketplace order is preserved from the caller.
+ */
+export declare function availablePluginGroups(plugins: readonly AvailablePlugin[], options?: {
+    installed?: ReadonlySet<string>;
+}): ListGroup[];
+/** Installed plugins as rows: id@version, platforms, format, capabilities. */
+export declare function installedPluginRows(plugins: readonly NormalizedPlugin[]): ListRow[];
+//# sourceMappingURL=listing.d.ts.map

package/dist/core/extensions/plugins/listing.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"listing.d.ts","sourceRoot":"","sources":["../../../../src/core/extensions/plugins/listing.ts"],"names":[],"mappings":"AAAA;;;;;;;GAOG;AAEH,OAAO,KAAK,EAAE,SAAS,EAAE,OAAO,EAAE,MAAM,sBAAsB,CAAC;AAC/D,OAAO,KAAK,EAAE,eAAe,EAAE,MAAM,cAAc,CAAC;AACpD,OAAO,KAAK,EAAE,gBAAgB,EAAE,MAAM,eAAe,CAAC;AAEtD,kFAAkF;AAClF,wBAAgB,kBAAkB,CAAC,MAAM,EAAE,eAAe,CAAC,QAAQ,CAAC,GAAG,MAAM,CAI5E;AAED;;;;;;GAMG;AACH,wBAAgB,kBAAkB,CAAC,MAAM,EAAE,gBAAgB,GAAG,MAAM,EAAE,CAUrE;AAED;;;;;;GAMG;AACH,wBAAgB,qBAAqB,CACpC,OAAO,EAAE,SAAS,eAAe,EAAE,EACnC,OAAO,GAAE;IAAE,SAAS,CAAC,EAAE,WAAW,CAAC,MAAM,CAAC,CAAA;CAAO,GAC/C,SAAS,EAAE,CAab;AAED,8EAA8E;AAC9E,wBAAgB,mBAAmB,CAAC,OAAO,EAAE,SAAS,gBAAgB,EAAE,GAAG,OAAO,EAAE,CAWnF","sourcesContent":["/**\n * Row shapes for the plugin listings, shared by every surface that prints one.\n *\n * `/plugin list`, `SearchPlugins` and `ListPlugins` describe the same objects,\n * and each used to build its own `name [a, b] — description` string, so the same\n * plugin printed three ways and the model's view never quite matched the user's.\n * They all go through here now; only the styling and the width differ.\n */\n\nimport type { ListGroup, ListRow } from \"../../format-list.js\";\nimport type { AvailablePlugin } from \"./install.js\";\nimport type { NormalizedPlugin } from \"./manifest.js\";\n\n/** Human-readable source for an available plugin (a URL, a path, an npm spec). */\nexport function formatPluginSource(source: AvailablePlugin[\"source\"]): string {\n\tif (typeof source === \"string\") return source;\n\tif (source.source === \"url\") return source.url;\n\treturn `${source.url}/${source.path}`;\n}\n\n/**\n * Capability classes a plugin actually ships.\n *\n * Covers every capability `NormalizedPlugin` can carry — themes and providers\n * included, which the old `ListPlugins` inline list omitted, so a plugin that\n * shipped only a theme or only a provider reported no capabilities at all.\n */\nexport function pluginCapabilities(plugin: NormalizedPlugin): string[] {\n\treturn [\n\t\tplugin.skillsDir && \"skills\",\n\t\tplugin.commandsDir && \"commands\",\n\t\tplugin.agentsDir && \"agents\",\n\t\tplugin.themesDir && \"themes\",\n\t\tplugin.hooks && \"hooks\",\n\t\tplugin.mcpServers && \"mcp\",\n\t\tplugin.providers?.length && \"providers\",\n\t].filter((value): value is string => typeof value === \"string\");\n}\n\n/**\n * Available plugins, grouped by the marketplace offering them.\n *\n * Grouping is what makes provenance legible: a flat list cannot answer \"where\n * would this come from if I installed it\", which is the one question that\n * matters at a trust boundary. Marketplace order is preserved from the caller.\n */\nexport function availablePluginGroups(\n\tplugins: readonly AvailablePlugin[],\n\toptions: { installed?: ReadonlySet<string> } = {},\n): ListGroup[] {\n\tconst groups = new Map<string, ListRow[]>();\n\tfor (const plugin of plugins) {\n\t\tconst rows = groups.get(plugin.marketplaceName) ?? [];\n\t\trows.push({\n\t\t\tname: plugin.name,\n\t\t\tmarker: options.installed?.has(plugin.name) ? \"✓\" : undefined,\n\t\t\tfacts: [plugin.supportPlatform.join(\"/\"), plugin.sourceKind],\n\t\t\tdetail: plugin.description ?? formatPluginSource(plugin.source),\n\t\t});\n\t\tgroups.set(plugin.marketplaceName, rows);\n\t}\n\treturn Array.from(groups, ([title, rows]) => ({ title, rows }));\n}\n\n/** Installed plugins as rows: id@version, platforms, format, capabilities. */\nexport function installedPluginRows(plugins: readonly NormalizedPlugin[]): ListRow[] {\n\treturn plugins.map((plugin) => {\n\t\tconst capabilities = pluginCapabilities(plugin);\n\t\treturn {\n\t\t\tname: `${plugin.id}${plugin.version ? `@${plugin.version}` : \"\"}`,\n\t\t\t// The manifest format is parenthesised because it is usually the same\n\t\t\t// word as the platform (\"claude/github · claude\" reads as a stutter).\n\t\t\tfacts: [plugin.supportPlatform.join(\"/\"), `(${plugin.format})`, capabilities.join(\", \") || \"no capabilities\"],\n\t\t\tdetail: plugin.description,\n\t\t};\n\t});\n}\n"]}

package/dist/core/extensions/plugins/listing.js

@@ -0,0 +1,69 @@
+/**
+ * Row shapes for the plugin listings, shared by every surface that prints one.
+ *
+ * `/plugin list`, `SearchPlugins` and `ListPlugins` describe the same objects,
+ * and each used to build its own `name [a, b] — description` string, so the same
+ * plugin printed three ways and the model's view never quite matched the user's.
+ * They all go through here now; only the styling and the width differ.
+ */
+/** Human-readable source for an available plugin (a URL, a path, an npm spec). */
+export function formatPluginSource(source) {
+    if (typeof source === "string")
+        return source;
+    if (source.source === "url")
+        return source.url;
+    return `${source.url}/${source.path}`;
+}
+/**
+ * Capability classes a plugin actually ships.
+ *
+ * Covers every capability `NormalizedPlugin` can carry — themes and providers
+ * included, which the old `ListPlugins` inline list omitted, so a plugin that
+ * shipped only a theme or only a provider reported no capabilities at all.
+ */
+export function pluginCapabilities(plugin) {
+    return [
+        plugin.skillsDir && "skills",
+        plugin.commandsDir && "commands",
+        plugin.agentsDir && "agents",
+        plugin.themesDir && "themes",
+        plugin.hooks && "hooks",
+        plugin.mcpServers && "mcp",
+        plugin.providers?.length && "providers",
+    ].filter((value) => typeof value === "string");
+}
+/**
+ * Available plugins, grouped by the marketplace offering them.
+ *
+ * Grouping is what makes provenance legible: a flat list cannot answer "where
+ * would this come from if I installed it", which is the one question that
+ * matters at a trust boundary. Marketplace order is preserved from the caller.
+ */
+export function availablePluginGroups(plugins, options = {}) {
+    const groups = new Map();
+    for (const plugin of plugins) {
+        const rows = groups.get(plugin.marketplaceName) ?? [];
+        rows.push({
+            name: plugin.name,
+            marker: options.installed?.has(plugin.name) ? "✓" : undefined,
+            facts: [plugin.supportPlatform.join("/"), plugin.sourceKind],
+            detail: plugin.description ?? formatPluginSource(plugin.source),
+        });
+        groups.set(plugin.marketplaceName, rows);
+    }
+    return Array.from(groups, ([title, rows]) => ({ title, rows }));
+}
+/** Installed plugins as rows: id@version, platforms, format, capabilities. */
+export function installedPluginRows(plugins) {
+    return plugins.map((plugin) => {
+        const capabilities = pluginCapabilities(plugin);
+        return {
+            name: `${plugin.id}${plugin.version ? `@${plugin.version}` : ""}`,
+            // The manifest format is parenthesised because it is usually the same
+            // word as the platform ("claude/github · claude" reads as a stutter).
+            facts: [plugin.supportPlatform.join("/"), `(${plugin.format})`, capabilities.join(", ") || "no capabilities"],
+            detail: plugin.description,
+        };
+    });
+}
+//# sourceMappingURL=listing.js.map

package/dist/core/extensions/plugins/listing.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"listing.js","sourceRoot":"","sources":["../../../../src/core/extensions/plugins/listing.ts"],"names":[],"mappings":"AAAA;;;;;;;GAOG;AAMH,kFAAkF;AAClF,MAAM,UAAU,kBAAkB,CAAC,MAAiC,EAAU;IAC7E,IAAI,OAAO,MAAM,KAAK,QAAQ;QAAE,OAAO,MAAM,CAAC;IAC9C,IAAI,MAAM,CAAC,MAAM,KAAK,KAAK;QAAE,OAAO,MAAM,CAAC,GAAG,CAAC;IAC/C,OAAO,GAAG,MAAM,CAAC,GAAG,IAAI,MAAM,CAAC,IAAI,EAAE,CAAC;AAAA,CACtC;AAED;;;;;;GAMG;AACH,MAAM,UAAU,kBAAkB,CAAC,MAAwB,EAAY;IACtE,OAAO;QACN,MAAM,CAAC,SAAS,IAAI,QAAQ;QAC5B,MAAM,CAAC,WAAW,IAAI,UAAU;QAChC,MAAM,CAAC,SAAS,IAAI,QAAQ;QAC5B,MAAM,CAAC,SAAS,IAAI,QAAQ;QAC5B,MAAM,CAAC,KAAK,IAAI,OAAO;QACvB,MAAM,CAAC,UAAU,IAAI,KAAK;QAC1B,MAAM,CAAC,SAAS,EAAE,MAAM,IAAI,WAAW;KACvC,CAAC,MAAM,CAAC,CAAC,KAAK,EAAmB,EAAE,CAAC,OAAO,KAAK,KAAK,QAAQ,CAAC,CAAC;AAAA,CAChE;AAED;;;;;;GAMG;AACH,MAAM,UAAU,qBAAqB,CACpC,OAAmC,EACnC,OAAO,GAAwC,EAAE,EACnC;IACd,MAAM,MAAM,GAAG,IAAI,GAAG,EAAqB,CAAC;IAC5C,KAAK,MAAM,MAAM,IAAI,OAAO,EAAE,CAAC;QAC9B,MAAM,IAAI,GAAG,MAAM,CAAC,GAAG,CAAC,MAAM,CAAC,eAAe,CAAC,IAAI,EAAE,CAAC;QACtD,IAAI,CAAC,IAAI,CAAC;YACT,IAAI,EAAE,MAAM,CAAC,IAAI;YACjB,MAAM,EAAE,OAAO,CAAC,SAAS,EAAE,GAAG,CAAC,MAAM,CAAC,IAAI,CAAC,CAAC,CAAC,CAAC,KAAG,CAAC,CAAC,CAAC,SAAS;YAC7D,KAAK,EAAE,CAAC,MAAM,CAAC,eAAe,CAAC,IAAI,CAAC,GAAG,CAAC,EAAE,MAAM,CAAC,UAAU,CAAC;YAC5D,MAAM,EAAE,MAAM,CAAC,WAAW,IAAI,kBAAkB,CAAC,MAAM,CAAC,MAAM,CAAC;SAC/D,CAAC,CAAC;QACH,MAAM,CAAC,GAAG,CAAC,MAAM,CAAC,eAAe,EAAE,IAAI,CAAC,CAAC;IAC1C,CAAC;IACD,OAAO,KAAK,CAAC,IAAI,CAAC,MAAM,EAAE,CAAC,CAAC,KAAK,EAAE,IAAI,CAAC,EAAE,EAAE,CAAC,CAAC,EAAE,KAAK,EAAE,IAAI,EAAE,CAAC,CAAC,CAAC;AAAA,CAChE;AAED,8EAA8E;AAC9E,MAAM,UAAU,mBAAmB,CAAC,OAAoC,EAAa;IACpF,OAAO,OAAO,CAAC,GAAG,CAAC,CAAC,MAAM,EAAE,EAAE,CAAC;QAC9B,MAAM,YAAY,GAAG,kBAAkB,CAAC,MAAM,CAAC,CAAC;QAChD,OAAO;YACN,IAAI,EAAE,GAAG,MAAM,CAAC,EAAE,GAAG,MAAM,CAAC,OAAO,CAAC,CAAC,CAAC,IAAI,MAAM,CAAC,OAAO,EAAE,CAAC,CAAC,CAAC,EAAE,EAAE;YACjE,sEAAsE;YACtE,uEAAsE;YACtE,KAAK,EAAE,CAAC,MAAM,CAAC,eAAe,CAAC,IAAI,CAAC,GAAG,CAAC,EAAE,IAAI,MAAM,CAAC,MAAM,GAAG,EAAE,YAAY,CAAC,IAAI,CAAC,IAAI,CAAC,IAAI,iBAAiB,CAAC;YAC7G,MAAM,EAAE,MAAM,CAAC,WAAW;SAC1B,CAAC;IAAA,CACF,CAAC,CAAC;AAAA,CACH","sourcesContent":["/**\n * Row shapes for the plugin listings, shared by every surface that prints one.\n *\n * `/plugin list`, `SearchPlugins` and `ListPlugins` describe the same objects,\n * and each used to build its own `name [a, b] — description` string, so the same\n * plugin printed three ways and the model's view never quite matched the user's.\n * They all go through here now; only the styling and the width differ.\n */\n\nimport type { ListGroup, ListRow } from \"../../format-list.js\";\nimport type { AvailablePlugin } from \"./install.js\";\nimport type { NormalizedPlugin } from \"./manifest.js\";\n\n/** Human-readable source for an available plugin (a URL, a path, an npm spec). */\nexport function formatPluginSource(source: AvailablePlugin[\"source\"]): string {\n\tif (typeof source === \"string\") return source;\n\tif (source.source === \"url\") return source.url;\n\treturn `${source.url}/${source.path}`;\n}\n\n/**\n * Capability classes a plugin actually ships.\n *\n * Covers every capability `NormalizedPlugin` can carry — themes and providers\n * included, which the old `ListPlugins` inline list omitted, so a plugin that\n * shipped only a theme or only a provider reported no capabilities at all.\n */\nexport function pluginCapabilities(plugin: NormalizedPlugin): string[] {\n\treturn [\n\t\tplugin.skillsDir && \"skills\",\n\t\tplugin.commandsDir && \"commands\",\n\t\tplugin.agentsDir && \"agents\",\n\t\tplugin.themesDir && \"themes\",\n\t\tplugin.hooks && \"hooks\",\n\t\tplugin.mcpServers && \"mcp\",\n\t\tplugin.providers?.length && \"providers\",\n\t].filter((value): value is string => typeof value === \"string\");\n}\n\n/**\n * Available plugins, grouped by the marketplace offering them.\n *\n * Grouping is what makes provenance legible: a flat list cannot answer \"where\n * would this come from if I installed it\", which is the one question that\n * matters at a trust boundary. Marketplace order is preserved from the caller.\n */\nexport function availablePluginGroups(\n\tplugins: readonly AvailablePlugin[],\n\toptions: { installed?: ReadonlySet<string> } = {},\n): ListGroup[] {\n\tconst groups = new Map<string, ListRow[]>();\n\tfor (const plugin of plugins) {\n\t\tconst rows = groups.get(plugin.marketplaceName) ?? [];\n\t\trows.push({\n\t\t\tname: plugin.name,\n\t\t\tmarker: options.installed?.has(plugin.name) ? \"✓\" : undefined,\n\t\t\tfacts: [plugin.supportPlatform.join(\"/\"), plugin.sourceKind],\n\t\t\tdetail: plugin.description ?? formatPluginSource(plugin.source),\n\t\t});\n\t\tgroups.set(plugin.marketplaceName, rows);\n\t}\n\treturn Array.from(groups, ([title, rows]) => ({ title, rows }));\n}\n\n/** Installed plugins as rows: id@version, platforms, format, capabilities. */\nexport function installedPluginRows(plugins: readonly NormalizedPlugin[]): ListRow[] {\n\treturn plugins.map((plugin) => {\n\t\tconst capabilities = pluginCapabilities(plugin);\n\t\treturn {\n\t\t\tname: `${plugin.id}${plugin.version ? `@${plugin.version}` : \"\"}`,\n\t\t\t// The manifest format is parenthesised because it is usually the same\n\t\t\t// word as the platform (\"claude/github · claude\" reads as a stutter).\n\t\t\tfacts: [plugin.supportPlatform.join(\"/\"), `(${plugin.format})`, capabilities.join(\", \") || \"no capabilities\"],\n\t\t\tdetail: plugin.description,\n\t\t};\n\t});\n}\n"]}

package/dist/core/extensions/types.d.ts

@@ -99,6 +99,15 @@ export interface ExtensionUIContext {
     askOptions(questions: AskQuestion[], opts?: ExtensionUIDialogOptions): Promise<string[] | undefined>;
     /** Show a notification to the user. */
     notify(message: string, type?: "info" | "warning" | "error"): void;
+    /**
+     * Terminal width in columns, when the surface has one.
+     *
+     * Undefined outside a terminal (RPC, print, headless), which is the signal to
+     * emit unwrapped text and let the consumer lay it out — a listing pre-wrapped
+     * to someone else's terminal is worse than no wrapping at all. Optional so
+     * third-party implementations of this interface keep compiling.
+     */
+    readonly columns?: number;
     /** Listen to raw terminal input (interactive mode only). Returns an unsubscribe function. */
     onTerminalInput(handler: TerminalInputHandler): () => void;
     /** Set status text in the footer/status bar. Pass undefined to clear. */