@mjasnikovs/pi-task 0.17.2 → 0.17.4

package/dist/config/config.js

@@ -7,8 +7,8 @@ const DEFAULTS = {
     compressReasoning: true,
     autoCommit: true,
     orientation: true,
-    enforceGuidelines: false,
-    verifyWork: false
+    enforceGuidelines: true,
+    verifyWork: true
 };
 const CONFIG_PATH = path.join(os.homedir(), '.config', 'pi-task', 'config.json');
 const _g = globalThis;

package/dist/config/register.js

@@ -1,6 +1,51 @@
-import { SettingsList } from '@earendil-works/pi-tui';
+import { SettingsList, visibleWidth } from '@earendil-works/pi-tui';
 import { registerBridgeCommand } from '../remote/bridge.js';
 import { getConfig, saveConfig } from './config.js';
+const CONFIG_TITLE = 'pi-task settings';
+/**
+ * Frames a child component (the settings list) in a rounded border with a title
+ * woven into the top edge. Without this the overlay's content sits flush against
+ * the chat scrollback and reads as just more console text; the border gives it a
+ * distinct panel. Layout mirrors {@link renderQuestionBox}'s box chrome: render
+ * the child at the inner width, pad each line so the right edge lines up, then
+ * frame. Input and invalidation are forwarded straight through to the child.
+ */
+class BorderedBox {
+    child;
+    title;
+    border;
+    titleColor;
+    constructor(child, title, border, titleColor) {
+        this.child = child;
+        this.title = title;
+        this.border = border;
+        this.titleColor = titleColor;
+    }
+    render(width) {
+        const innerWidth = Math.max(1, width - 4); // "│ " + content + " │"
+        const dash = (n) => '─'.repeat(Math.max(0, n));
+        // Top border with the title woven in: "╭─ pi-task settings ─…─╮".
+        const tag = ` ${this.title} `;
+        const lead = 1; // one dash before the title
+        const rest = width - 2 - lead - visibleWidth(tag);
+        const top = rest >= 0 ?
+            this.border(`╭${dash(lead)}`) + this.titleColor(tag) + this.border(`${dash(rest)}╮`)
+            : this.border(`╭${dash(width - 2)}╮`);
+        const body = this.child.render(innerWidth).map(line => {
+            const pad = innerWidth - visibleWidth(line);
+            const padded = pad > 0 ? line + ' '.repeat(pad) : line;
+            return this.border('│ ') + padded + this.border(' │');
+        });
+        const bottom = this.border(`╰${dash(width - 2)}╯`);
+        return [top, ...body, bottom];
+    }
+    invalidate() {
+        this.child.invalidate();
+    }
+    handleInput(data) {
+        this.child.handleInput(data);
+    }
+}
 const ITEMS = [
     { id: 'remote', label: 'remote', description: 'Remote UI server (QR code, phone access)' },
     {
@@ -58,8 +103,8 @@ async function handleTaskConfig(_args, ctx) {
             cfg[id] = newValue === 'on';
             saveConfig(cfg).catch(() => { });
         }, () => done(undefined));
-        return list;
-    }, { overlay: true, overlayOptions: { width: 54 } });
+        return new BorderedBox(list, CONFIG_TITLE, s => theme.fg('borderMuted', s), s => theme.fg('accent', theme.bold(s)));
+    }, { overlay: true, overlayOptions: { width: 58 } });
 }
 export function registerConfig(pi) {
     registerBridgeCommand(pi, 'task-config', {

package/dist/task/prompts.js

@@ -222,6 +222,14 @@ LIVE-DATA RULE:
 - "### freshness-check skipped" → tag UNKNOWN and say current state needs verification.
 - No npm block + question is about latest/current version → tag UNKNOWN (training data goes stale).
 
+TRIAGE — run these checks IN ORDER first. The REVERSIBILITY TEST below applies ONLY to a question that survives all checks as a genuine preference.
+
+1. ALREADY-DECIDED CHECK — scan the refined task and research for a value, shape, response body, schema, route, or requirement that ALREADY determines the answer. If one does, this is a fact, not a preference. Emit "ANSWER: <value taken from that source>". If your instinct or a "nicer" alternative contradicts that source, the SOURCE WINS — never override a stated contract with a preferred default. (E.g. a stated response shape { items, total, page, pageSize } already answers a pagination question — page/offset — you may NOT answer "cursor".)
+
+2. FUNCTIONAL-REQUIREMENT CHECK — if the question is whether to include or defer a package, config file, or setup that something THIS task configures needs in order to FUNCTION (a build plugin's engine or required peer dependency, an entry file the build reads, a runtime module an import resolves to), then a "minimize / keep it minimal / defer to the step that uses it" preference does NOT override that functional requirement. A tool you wire up this step must have its required pieces present this step or the build/step is broken. Emit "ANSWER: <include it now, because configuring X requires it>". Do not defer something the step's own configuration depends on.
+
+3. PREFERENCE — only if neither check fires (a genuine choice the sources do not determine), apply the REVERSIBILITY TEST.
+
 REVERSIBILITY TEST:
   ANSWER: cheap to undo (output style, policy, report format, obvious scope, standard convention).
   UNKNOWN: costly to reverse (file mutations, tool/dependency choice, approach/algorithm, format that shapes downstream artifacts).

package/package.json

@@ -1,6 +1,6 @@
 {
     "name": "@mjasnikovs/pi-task",
-    "version": "0.17.2",
+    "version": "0.17.4",
     "description": "Deterministic spec-orchestration for local models, with a bundled real-time remote web view and web/docs/fetch/worker subagent tools.",
     "type": "module",
     "main": "./dist/index.js",