pi-soly 1.12.1 → 1.13.0

package/ask/index.ts

@@ -71,7 +71,7 @@ export default function piAskExtension(pi: ExtensionAPI) {
 		name: "ask_pro",
 		label: "soly · ask_pro",
 		description:
-			"Ask the user one or more questions at once via a tabbed picker (≤6 questions); returns all answers in one call. USE WHEN: (a) you have 2+ related questions to gather in one batch, OR (b) you have ONE simple choice among 2-4 options where each option is a short label + 1-2 sentence description (no per-option code, no pros/cons). For ONE architectural/design comparison where each option needs its own code + pros/cons card on a full screen, use `decision_deck` instead. Per question: single-select (default), `multiSelect` (+ `minSelect`/`maxSelect`), `allowOther` (free-text 'Other…'), or `freeText` (typed answer, no options). Per option: `recommended` (⭐) and `preview` (side panel, fenced code highlighted). User can skip (`s`) or note (`n`). Prefer this over one-by-one questions.",
+			"Ask the user one or more questions at once via a tabbed picker (≤6 questions); returns all answers in one call. USE WHEN: (a) you have 2+ related questions to gather in one batch, OR (b) the choice is local — a sub-question inside an already-decided theme, or a simple label-vs-label «или/или» that doesn't justify a full-screen deck. Each option is a short label + 1-2 sentence description (no per-option code, no pros/cons). For a global architectural fork with real counterweight between options, use `decision_deck` instead. Per question: single-select (default), `multiSelect` (+ `minSelect`/`maxSelect`), `allowOther` (free-text 'Other…'), or `freeText` (typed answer, no options). Per option: `recommended` (⭐) and `preview` (side panel, fenced code highlighted). User can skip (`s`) or note (`n`). Prefer this over one-by-one questions.",
 		parameters: Type.Object({
 			questions: Type.Array(
 				Type.Object({

package/config.ts

@@ -45,6 +45,13 @@ export interface SolyConfig {
 		 *  user (ask "ready to implement, or discuss first?") before writing code.
 		 *  Default on. */
 		confirmBeforeCode: boolean;
+		/** Inject a compact list of rules applicable to the file being
+		 *  edited/written, appended to the tool's result. Forces the LLM to
+		 *  confirm in the next message which rules were applied — closes the
+		 *  "rules read at start of turn, forgotten by edit time" gap.
+		 *  Default on. Disable for verbose rule sets that would otherwise
+		 *  flood the per-edit context. */
+		preActionRuleReminder: boolean;
 	};
 	display: {
 		/** Always show the recommended (⭐) option as the first row. */
@@ -125,6 +132,7 @@ export const DEFAULT_CONFIG: SolyConfig = {
 		nudgeNotify: false,
 		toolHints: true,
 		confirmBeforeCode: true,
+		preActionRuleReminder: true,
 	},
 	display: {
 		defaultRecommendedFirst: true,
@@ -216,6 +224,8 @@ function deepMerge(base: SolyConfig, over: RawConfig): SolyConfig {
 			merged.agent.toolHints = over.agent.toolHints;
 		if (typeof over.agent.confirmBeforeCode === "boolean")
 			merged.agent.confirmBeforeCode = over.agent.confirmBeforeCode;
+		if (typeof over.agent.preActionRuleReminder === "boolean")
+			merged.agent.preActionRuleReminder = over.agent.preActionRuleReminder;
 	}
 	if (over.display) {
 		if (typeof over.display.defaultRecommendedFirst === "boolean")

package/core.ts

@@ -571,6 +571,68 @@ ${blocks.join("\n\n---\n\n")}${skippedNote}
   return { section, loaded: applicable.map(ruleKey), interactive };
 }
 
+// ============================================================================
+// Per-file rule lookup (used by pre-action reminder in tool_result hook)
+// ============================================================================
+//
+// Returns the subset of `rules` that apply to a single file path. Mirrors the
+// glob logic in `buildRulesSection` (always/no-globs = universal; otherwise
+// match `filePath` against `meta.globs`). Excludes disabled rules. Use this
+// to feed the pre-action reminder — LLM should see applicable rules AT THE
+// MOMENT of edit, not just at the start of the turn (where they decay).
+export function getApplicableRulesForFile(
+  filePath: string,
+  rules: RuleFile[],
+): RuleFile[] {
+  return rules.filter((r) => {
+    if (!r.enabled) return false;
+    if (r.meta.always === true) return true;
+    const globs = r.meta.globs;
+    if (!globs || globs.length === 0) return true;
+    return globs.some((g) => matchesGlob(filePath, g));
+  });
+}
+
+// Formats a compact reminder block for the LLM to see right after editing
+// `filePath`. Sorted by priority (high → medium → low → undefined), capped
+// at `cap` rules (default 3) so the LLM isn't flooded. Returns "" when no
+// rules apply — caller should treat that as "don't inject anything".
+export function formatRuleReminder(
+  rules: RuleFile[],
+  filePath: string,
+  cap = 3,
+): string {
+  if (rules.length === 0) return "";
+
+  const priorityOrder: Record<string, number> = { high: 0, medium: 1, low: 2 };
+  const sorted = [...rules].sort((a, b) => {
+    const pa = priorityOrder[a.meta.priority ?? ""] ?? 1;
+    const pb = priorityOrder[b.meta.priority ?? ""] ?? 1;
+    if (pa !== pb) return pa - pb;
+    return a.relPath.localeCompare(b.relPath);
+  });
+
+  const shown = sorted.slice(0, cap);
+  const remaining = rules.length - shown.length;
+
+  const lines: string[] = [];
+  lines.push(`\n\n---\n\n📋 **Applicable rules for \`${filePath}\`:**\n`);
+  shown.forEach((r, i) => {
+    const desc = r.meta.description ? ` — ${r.meta.description}` : "";
+    lines.push(`${i + 1}. [\`${r.relPath}\`]${desc}`);
+  });
+  if (remaining > 0) {
+    lines.push(
+      `\n_…and ${remaining} more — use \`/why ${filePath}\` to see all._`,
+    );
+  }
+  lines.push(
+    `\nIn your next message, briefly confirm which were applied (or note why not).`,
+  );
+
+  return lines.join("\n");
+}
+
 // ============================================================================
 // Phase-scoped rules loader
 // ============================================================================

package/deck/index.ts

@@ -24,7 +24,7 @@ export default function piDeckExtension(pi: ExtensionAPI) {
 		name: "decision_deck",
 		label: "soly · decision_deck",
 		description:
-			"Present ONE design/architecture decision as a full-screen deck of cards (one per option) the user flips through (←/→ or 1-N) and picks with Enter. Use when 2-6 options each need their own card with code + pros/cons to be properly compared (e.g. architectural forks, API shapes, data-model choices). STRICTLY ONE question per call — for 2+ related questions in one batch, use `ask_pro` instead. Each option SHOULD carry either a non-trivial code snippet or explicit pros/cons; for plain label-vs-label choices, `ask_pro` is lighter. The user can attach a free-text note (rationale, caveats) via `n`; it's returned in the result. Native TUI. Returns the chosen option.",
+			"Present ONE design/architecture decision as a full-screen deck of cards (one per option) the user flips through (←/→ or 1-N) and picks with Enter. Use when comparing global architectural forks (architecture, API shape, data model) where each option needs its own card with code + pros/cons to be properly weighed against its counterweight — trade-offs that genuinely pull in different directions (e.g. consistency vs availability, sync vs async). STRICTLY ONE question per call — for 2+ related questions in one batch, use `ask_pro` instead. For local sub-questions inside an already-decided theme, or simple label-vs-label «или/или», `ask_pro` is lighter. Default to `ask_pro` unless the stakes are global. The user can attach a free-text note (rationale, caveats) via `n`; it's returned in the result. Native TUI. Returns the chosen option.",
 		parameters: Type.Object({
 			title: Type.Optional(Type.String({ description: "Decision title." })),
 			prompt: Type.Optional(Type.String({ description: "Question shown above the cards." })),

package/index.ts

@@ -32,7 +32,9 @@ import {
 	CONTEXT_WINDOW_TOKENS,
 	DEFAULT_PROGRESS,
 	extractFilePathsFromPrompt,
+	formatRuleReminder,
 	formatTok,
+	getApplicableRulesForFile,
 	loadAllRules,
 	loadPhaseRules,
 	loadProjectState,
@@ -834,6 +836,29 @@ export default function solyExtension(pi: ExtensionAPI) {
 		}
 	});
 
+	// ============================================================================
+	// tool_result: inject a compact reminder of rules applicable to the file
+	// just edited/written, so the LLM sees them AT THE MOMENT of action (not
+	// 30 turns later when they've decayed in attention). The LLM is asked to
+	// confirm in its next message which rules were applied — closing the gap
+	// where rules loaded at the start of a turn are forgotten by the time the
+	// agent actually edits something.
+	// ============================================================================
+	pi.on("tool_result", async (event, _ctx) => {
+		if (!getActiveConfig().agent.preActionRuleReminder) return;
+		if (event.toolName !== "edit" && event.toolName !== "write") return;
+		if (event.isError) return; // tool failed — don't pile on
+		const input = event.input as { path?: string };
+		const filePath = input?.path;
+		if (!filePath) return;
+		const applicable = getApplicableRulesForFile(filePath, combinedRules());
+		const reminder = formatRuleReminder(applicable, filePath);
+		if (!reminder) return;
+		return {
+			content: [...event.content, { type: "text" as const, text: reminder }],
+		};
+	});
+
 	// ============================================================================
 	// Chrome: working-indicator telemetry lifecycle + reactive data refresh
 	// ============================================================================

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "pi-soly",
-  "version": "1.12.1",
+  "version": "1.13.0",
   "description": "Project management + workflow framework for pi-coding-agent. Plans, state, MANDATORY rules, self-review, multi-question picker, native footer + welcome chrome — one npm install, zero config. The LLM drives execution and delegates to a worker subagent when available.",
   "type": "module",
   "main": "index.ts",

package/tool-hints.ts

@@ -52,7 +52,7 @@ export function buildToolHintSection(h: ToolHint): string | null {
 	if (h.artifact)
 		bits.push("- Examples / a table / a visual result: **ask the user first** — render it in the browser as an artifact (`html_artifact`), or just as text here? Then proceed accordingly.");
 	if (h.deck)
-		bits.push("- Comparing 2-6 options: if it's ONE question and each option needs code + pros/cons on its own card → use `decision_deck`. If it's 2+ related questions in one batch → use `ask_pro`. **Default to `ask_pro` unless you have explicit code or trade-offs per option.** Never use `decision_deck` for 2+ questions.");
+		bits.push("- Comparing 2-6 options: if it's a global architectural fork with real counterweight (trade-offs pulling in different directions) and each option needs code + pros/cons on its own card → use `decision_deck`. If it's 2+ related questions OR a local sub-question → use `ask_pro`. **Default to `ask_pro` unless the stakes are global.** Never use `decision_deck` for 2+ questions.");
 	if (h.ask)
 		bits.push("- Several things to clarify → use `ask_pro` (one batched picker). `decision_deck` does NOT support multi-question — never reach for it here.");
 	if (bits.length === 0) return null;