@mjasnikovs/pi-task 0.38.32 → 0.39.1

package/dist/config/register.d.ts

@@ -1,7 +1,8 @@
 import type { ExtensionAPI, ExtensionCommandContext } from '@earendil-works/pi-coding-agent';
 import { SettingsList } from '@earendil-works/pi-tui';
-import type { Component, SelectItem } from '@earendil-works/pi-tui';
+import type { Component } from '@earendil-works/pi-tui';
 import { type ReasoningModelFacts } from '../shared/reasoning-capability.js';
+import { type PairOptions } from './option-picker.js';
 import { type PiTaskConfig } from './config.js';
 import { type InstalledExtension } from './extension-list.js';
 import { type GuardableTool } from './tool-list.js';
@@ -55,7 +56,7 @@ declare class BorderedBox implements Component {
 export interface ConfigItem {
     /**
      * The row's id. A `keyof PiTaskConfig` for a fixed setting; a prefixed
-     * string (`reason:`, `tool:`, `ext:`) for a DISCOVERED one.
+     * string (`step:`, `tool:`, `ext:`) for a DISCOVERED one.
      *
      * It is `string`, not `keyof PiTaskConfig`, and that is what lets the three
      * dynamic families BE rows instead of bypassing them — so the round-trip
@@ -84,7 +85,7 @@ export interface ConfigItem {
      * `values` stays the STATIC complete vocabulary, because that is what the
      * round-trip property in config-items.test.ts quantifies over.
      */
-    submenu?: (cfg: PiTaskConfig) => SelectItem[];
+    picker?: (cfg: PiTaskConfig) => PairOptions;
     /** What the panel shows for the current value. */
     format: (cfg: PiTaskConfig) => string;
     /** Write the chosen label back. A value it does not recognise is ignored. */
@@ -104,7 +105,7 @@ export interface ConfigItem {
  * exemptions from it) end up separated by rows that have nothing to do with
  * them. The headers are inert rows: no `values`, so Enter does nothing on them.
  */
-export type Section = 'session' | 'checks' | 'research' | 'models' | 'reasoning' | 'timeouts' | 'unattended' | 'logging' | 'extensions';
+export type Section = 'session' | 'checks' | 'research' | 'profile' | 'reasoning' | 'timeouts' | 'unattended' | 'logging' | 'extensions';
 /** Section order, and the label each header renders. */
 export declare const SECTIONS: ReadonlyArray<{
     key: Section;
@@ -138,7 +139,7 @@ export declare function toolItems(tools: readonly GuardableTool[]): ConfigItem[]
 /** Apply a per-tool watchdog toggle to the exemption list (idempotent both ways). */
 export declare function applyToolToggle(exempt: readonly string[], toolName: string, watched: boolean): string[];
 /**
- * The label for one `think:` row.
+ * The label for one step row.
  *
  * A group whose name carries a colon is a CHILD of the group before the colon —
  * `research:files` is one of the four workers `research` fans out to. Rendered
@@ -147,14 +148,18 @@ export declare function applyToolToggle(exempt: readonly string[], toolName: str
  * parent is also a row.
  *
  * So a child is drawn as a tree branch under its parent and loses the repeated
- * `think: research:` prefix, the same text at the head of four consecutive
- * lines. `└─` on the last child, `├─` on the rest, decided from the group's
- * position in {@link CHILD_GROUPS} rather than a hand-kept list — adding a
- * fifth worker moves the corner on its own.
+ * `research:` prefix, the same text at the head of four consecutive lines. `└─`
+ * on the last child, `├─` on the rest, decided from the group's position in
+ * {@link CHILD_GROUPS} rather than a hand-kept list — adding a fifth worker
+ * moves the corner on its own.
+ *
+ * A parentless group is its own bare name. It carried a `think: ` prefix while
+ * there were two families to tell apart; with one row per step there is nothing
+ * to disambiguate, and the prefix was the widest thing in the column.
  *
  * Leading spaces survive: SettingsList pads the label right, never trims it.
  */
-export declare function reasoningRowLabel(group: ChildGroup): string;
+export declare function stepRowLabel(group: ChildGroup): string;
 /**
  * What this machine can offer a model row, and what each offer can DO.
  *
@@ -173,36 +178,56 @@ export interface ModelCatalog {
 }
 /** No registry reachable. Every row still renders; nothing narrows. */
 export declare const EMPTY_CATALOG: ModelCatalog;
-export declare function modelItems(catalog: ModelCatalog): ConfigItem[];
 /**
- * Write a group's model, and RE-CLAMP its thinking cell in the same write.
+ * `level · provider/id`, the one string a step row shows and accepts.
  *
- * Narrowing the picker does nothing about a level already stored from before the
- * model was chosen: on its own it would freeze a lie into a cell it has just
- * made unconfigurable. `syncRows` re-renders every row, so the user sees the
- * level move.
+ * THE LEVEL COMES FIRST, and that is a display decision with teeth.
+ * `SettingsList` truncates a value from the RIGHT, so whatever is last is what
+ * silently disappears — and a real local model id (`local/Qwen3.8-27B-UD-Q4_K_XL
+ * .gguf`) is wide enough to consume the whole column on its own. Level-first
+ * means the half that falls off is the one still identifiable from its head, and
+ * the levels line up as a column you can read down.
+ */
+export declare function formatStepValue(spec: string, level: GroupSetting): string;
+/**
+ * The two halves back out, or `undefined` for anything not of that shape.
  *
- * The clamp reads `resolveReasoning`, NOT `cfg.reasoningLevels[group]`. In mode
- * `on` or `off` the stored table is ignored entirely, so a user in `on` who
- * picks a non-reasoning model has a stored cell that says nothing and an
- * effective `medium` the model will erase — and comparing the stored cell would
- * see no clamp and stay silent about a real lie.
+ * Split on the FIRST separator, because the level leads and is a closed set,
+ * while a `provider/id` could conceivably contain one.
+ */
+export declare function parseStepValue(value: string): {
+    spec: string;
+    level: GroupSetting;
+} | undefined;
+/**
+ * One row per step, carrying BOTH dials.
+ *
+ * They were two parallel blocks of eleven, and the coupling between them was
+ * invisible: choosing a model re-clamps that step's thinking level, but the row
+ * that moved was eleven rows away from the row you touched. One row shows the
+ * pair, and the two-step picker shows the clamp happening.
  *
- * Guarded on the clamp actually MOVING something, because `applyReasoningLevel`
- * flips the whole table to `custom`, and picking a fully-capable model must not
- * do that as a side effect.
+ * `values` is the LEGAL cross product — every model against only the levels that
+ * model declares. Nothing renders it: the picker offers two short lists, and the
+ * round-trip property in config-items.test.ts is its only reader. Building it
+ * from `offeredLevels` rather than the full ladder is what makes the property
+ * true, because a pair the model cannot honour would be clamped by `apply` and
+ * would not round-trip.
  */
-export declare function applyGroupModel(cfg: PiTaskConfig, group: ChildGroup, chosen: string, catalog: ModelCatalog): void;
+export declare function stepItems(catalog?: ModelCatalog): ConfigItem[];
 /**
- * The levels a row may offer, given the model that row's group will run on.
+ * Write both halves of a step row, atomically.
+ *
+ * Atomically matters for the round-trip property, which starts from a FRESH
+ * config every iteration: a value that wrote only one half would leave the other
+ * at its default and render as something else.
  *
- * The INTERSECTION with `REASONING_SETTINGS`, not `supportedThinkingLevels`
- * directly: that returns the whole ladder including `xhigh` and `max`, which
- * this menu excludes on purpose (see reasoning.ts) because pi's own UI may not
- * offer them. A model declaring `xhigh` must not smuggle it in here.
+ * The level is re-clamped even though the picker only ever offers legal pairs.
+ * The picker is not the only door — `values` is built when the panel opens, and
+ * a registry that moved underneath it would otherwise let an unhonourable level
+ * through.
  */
-export declare function offeredLevels(facts: ReasoningModelFacts | undefined): GroupSetting[];
-export declare function reasoningItems(catalog?: ModelCatalog): ConfigItem[];
+export declare function applyStepValue(cfg: PiTaskConfig, group: ChildGroup, chosen: string, catalog: ModelCatalog): void;
 /**
  * Apply one group row's new value.
  *
@@ -247,13 +272,13 @@ export type PanelItem = {
      * {@link createSettingsPanel} is where a theme exists, so it is where these
      * options become a component.
      */
-    submenuOptions?: () => SelectItem[];
+    pickerOptions?: () => PairOptions;
     /**
      * What the headless one-line rendering calls this row, when `label` reads
      * only in the panel. A tree branch means nothing on a line of `|`-joined
-     * rows: `├─ files` there names no parent, where `think: research:files`
-     * does. Set by the reasoning rows; every other row leaves it off and its
-     * `label` is used.
+     * rows: `├─ files` there names no parent, where `step: research:files`
+     * does. Set by the step rows; every other row leaves it off and its `label`
+     * is used.
      */
     headlessLabel?: string;
 };
@@ -267,10 +292,10 @@ export declare function createSettingsPanel(items: PanelItem[], theme: Theme,
  * Called with the row's id, its new value, and the LIST ITSELF.
  *
  * The list is handed back because some rows change what OTHER rows display:
- * flipping `reasoning` to off means every `think:` row now runs at off, and
- * a row's `currentValue` is a snapshot taken when the panel was built.
- * Without a way to write the others back, the menu would show
- * `reasoning off` beside rows still claiming `inherit`.
+ * flipping `profile` to off means every `step:` row now runs at off, and a
+ * row's `currentValue` is a snapshot taken when the panel was built. Without
+ * a way to write the others back, the menu would show `profile off` beside
+ * rows still claiming `inherit`.
  */
 onChange: (id: string, newValue: string, list: SettingsList) => void, onCancel: () => void): BorderedBox;
 /**
@@ -294,7 +319,7 @@ export declare function panelItems(cfg: PiTaskConfig, installed: InstalledExtens
  *
  * A row's `currentValue` in the live list is a snapshot taken when the panel was
  * built, and rows describe each other: cycling `reasoning` to `off` changes what
- * every `think:` row runs at, and cycling one group row flips the mode, which
+ * every `step:` row runs at, and setting one step row flips the profile, which
  * changes all the others.
  *
  * This runs after ANY change, over EVERY row. Re-reading a `format` costs