@vitos-pizza/vitos-pizza 0.1.0 → 0.3.0

package/packages/session-title/src/title-agent.ts

@@ -1,60 +1,60 @@
-import type { SubagentEventBus } from "@vitos-pizza/subagents/rpc/client";
-import { requestSubagentRun } from "@vitos-pizza/subagents/rpc/client";
-import { buildTitleTask } from "./build-title-prompt.ts";
-import type { TitleNamingContext } from "./extract-title-context.ts";
-import { normalizeTitle } from "./normalize-title.ts";
-import { parseTitleResponse } from "./parse-title-response.ts";
-import type { AutoTitleSettings } from "./types.ts";
-
-export interface TitleAgent {
-	run(
-		context: TitleNamingContext,
-		signal?: AbortSignal,
-	): Promise<string | null>;
-}
-
-export interface TitleAgentDeps {
-	events: SubagentEventBus;
-	resolveModelRef: () => string | undefined;
-	settings: AutoTitleSettings;
-}
-
-function extractResultText(
-	content: Array<{ type: string; text?: string }> | undefined,
-): string {
-	if (!content?.length) return "";
-	const text = content[0];
-	return text?.type === "text" ? (text.text ?? "").trim() : "";
-}
-
-export function createTitleAgent(deps: TitleAgentDeps): TitleAgent {
-	return {
-		async run(
-			context: TitleNamingContext,
-			signal?: AbortSignal,
-		): Promise<string | null> {
-			const result = await requestSubagentRun(
-				deps.events,
-				{
-					agent: "title",
-					task: buildTitleTask(context, deps.settings.maxTitleLength),
-					agentScope: "both",
-					model: deps.resolveModelRef(),
-				},
-				{
-					timeoutMs: deps.settings.timeoutMs,
-					signal,
-				},
-			);
-
-			if (!result) return null;
-
-			const text = extractResultText(result.content);
-			if (!text) return null;
-
-			const parsed = parseTitleResponse(text);
-			if (!parsed) return null;
-			return normalizeTitle(parsed, deps.settings.maxTitleLength) || null;
-		},
-	};
-}
+import type { SubagentEventBus } from "@vitos-pizza/subagents/rpc/client";
+import { requestSubagentRun } from "@vitos-pizza/subagents/rpc/client";
+import { buildTitleTask } from "./build-title-prompt.ts";
+import type { TitleNamingContext } from "./extract-title-context.ts";
+import { normalizeTitle } from "./normalize-title.ts";
+import { parseTitleResponse } from "./parse-title-response.ts";
+import type { AutoTitleSettings } from "./types.ts";
+
+export interface TitleAgent {
+	run(
+		context: TitleNamingContext,
+		signal?: AbortSignal,
+	): Promise<string | null>;
+}
+
+export interface TitleAgentDeps {
+	events: SubagentEventBus;
+	resolveModelRef: () => string | undefined;
+	settings: AutoTitleSettings;
+}
+
+function extractResultText(
+	content: Array<{ type: string; text?: string }> | undefined,
+): string {
+	if (!content?.length) return "";
+	const text = content[0];
+	return text?.type === "text" ? (text.text ?? "").trim() : "";
+}
+
+export function createTitleAgent(deps: TitleAgentDeps): TitleAgent {
+	return {
+		async run(
+			context: TitleNamingContext,
+			signal?: AbortSignal,
+		): Promise<string | null> {
+			const result = await requestSubagentRun(
+				deps.events,
+				{
+					agent: "title",
+					task: buildTitleTask(context, deps.settings.maxTitleLength),
+					agentScope: "both",
+					model: deps.resolveModelRef(),
+				},
+				{
+					timeoutMs: deps.settings.timeoutMs,
+					signal,
+				},
+			);
+
+			if (!result) return null;
+
+			const text = extractResultText(result.content);
+			if (!text) return null;
+
+			const parsed = parseTitleResponse(text);
+			if (!parsed) return null;
+			return normalizeTitle(parsed, deps.settings.maxTitleLength) || null;
+		},
+	};
+}

package/packages/session-title/src/truncate-input.ts

@@ -1,10 +1,10 @@
-export function truncateInput(text: string, maxChars: number): string {
-	const trimmed = text.trim();
-	if (trimmed.length <= maxChars) return trimmed;
-	const slice = trimmed.slice(0, maxChars);
-	const lastSpace = slice.lastIndexOf(" ");
-	if (lastSpace > maxChars * 0.6) {
-		return slice.slice(0, lastSpace).trim();
-	}
-	return slice.trim();
-}
+export function truncateInput(text: string, maxChars: number): string {
+	const trimmed = text.trim();
+	if (trimmed.length <= maxChars) return trimmed;
+	const slice = trimmed.slice(0, maxChars);
+	const lastSpace = slice.lastIndexOf(" ");
+	if (lastSpace > maxChars * 0.6) {
+		return slice.slice(0, lastSpace).trim();
+	}
+	return slice.trim();
+}

package/packages/session-title/src/types.ts

@@ -1,29 +1,29 @@
-export type ScheduleDecision = "skip" | "fastReject" | "schedule";
-
-export interface AutoTitleSettings {
-	enabled: boolean;
-	model?: string;
-	minCharsForLlm: number;
-	fastRules: boolean;
-	maxInputChars: number;
-	maxOutputTokens: number;
-	timeoutMs: number;
-	maxTitleLength: number;
-}
-
-export const DEFAULT_AUTO_TITLE_SETTINGS: AutoTitleSettings = {
-	enabled: true,
-	minCharsForLlm: 4,
-	fastRules: true,
-	maxInputChars: 280,
-	maxOutputTokens: 24,
-	timeoutMs: 8000,
-	maxTitleLength: 20,
-};
-
-export interface ScheduleContext {
-	hasSessionName: boolean;
-	inFlight: boolean;
-	fastRules: boolean;
-	minCharsForLlm: number;
-}
+export type ScheduleDecision = "skip" | "fastReject" | "schedule";
+
+export interface AutoTitleSettings {
+	enabled: boolean;
+	model?: string;
+	minCharsForLlm: number;
+	fastRules: boolean;
+	maxInputChars: number;
+	maxOutputTokens: number;
+	timeoutMs: number;
+	maxTitleLength: number;
+}
+
+export const DEFAULT_AUTO_TITLE_SETTINGS: AutoTitleSettings = {
+	enabled: true,
+	minCharsForLlm: 4,
+	fastRules: true,
+	maxInputChars: 280,
+	maxOutputTokens: 24,
+	timeoutMs: 8000,
+	maxTitleLength: 20,
+};
+
+export interface ScheduleContext {
+	hasSessionName: boolean;
+	inFlight: boolean;
+	fastRules: boolean;
+	minCharsForLlm: number;
+}

package/packages/session-title/tsconfig.json

@@ -1,13 +1,13 @@
-{
-	"extends": "../../tsconfig.base.json",
-	"compilerOptions": {
-		"allowImportingTsExtensions": true
-	},
-	"include": [
-		"extensions/**/*.ts",
-		"src/**/*.ts",
-		"tests/**/*.ts",
-		"vitest.config.ts"
-	],
-	"exclude": ["node_modules"]
-}
+{
+	"extends": "../../tsconfig.base.json",
+	"compilerOptions": {
+		"allowImportingTsExtensions": true
+	},
+	"include": [
+		"extensions/**/*.ts",
+		"src/**/*.ts",
+		"tests/**/*.ts",
+		"vitest.config.ts"
+	],
+	"exclude": ["node_modules"]
+}

package/packages/session-title/vitest.config.ts

@@ -1,8 +1,8 @@
-import { defineConfig } from "vitest/config";
-
-export default defineConfig({
-	test: {
-		environment: "node",
-		include: ["tests/**/*.test.ts"],
-	},
-});
+import { defineConfig } from "vitest/config";
+
+export default defineConfig({
+	test: {
+		environment: "node",
+		include: ["tests/**/*.test.ts"],
+	},
+});

package/packages/settings-preset/extensions/index.ts

@@ -0,0 +1,53 @@
+/**
+ * @vitos-pizza/settings-preset — seed default Pi settings on first session start.
+ *
+ * Follows the same non-destructive pattern as the permission-system module:
+ * only writes to project-level `.pi/settings.json` when neither global nor
+ * project settings exist, so existing user configurations are never overwritten.
+ */
+
+import { copyFileSync, existsSync, mkdirSync } from "node:fs";
+import { dirname, join } from "node:path";
+import { fileURLToPath } from "node:url";
+import type { ExtensionAPI } from "@earendil-works/pi-coding-agent";
+import { getAgentDir } from "@earendil-works/pi-coding-agent";
+
+const moduleDir = dirname(fileURLToPath(import.meta.url));
+const presetsDir = join(moduleDir, "..", "presets");
+
+function getGlobalSettingsPath(agentDir: string): string {
+	return join(agentDir, "settings.json");
+}
+
+function getProjectSettingsPath(cwd: string): string {
+	return join(cwd, ".pi", "settings.json");
+}
+
+function ensureDefaultSettings(cwd: string, agentDir: string): void {
+	// Don't overwrite if the user already has project-level settings
+	const projectPath = getProjectSettingsPath(cwd);
+	if (existsSync(projectPath)) return;
+
+	// Don't overwrite if the user already has global settings
+	const globalPath = getGlobalSettingsPath(agentDir);
+	if (existsSync(globalPath)) return;
+
+	// Neither exists — seed the project with our preset
+	const presetPath = join(presetsDir, "settings.json");
+	if (!existsSync(presetPath)) return;
+
+	mkdirSync(dirname(projectPath), { recursive: true });
+	copyFileSync(presetPath, projectPath);
+}
+
+export default function (pi: ExtensionAPI) {
+	const agentDir = getAgentDir();
+	let seeded = false;
+
+	pi.on("session_start", async (_event, ctx) => {
+		if (seeded) return;
+		seeded = true;
+
+		ensureDefaultSettings(ctx.cwd, agentDir);
+	});
+}

package/packages/settings-preset/package.json

@@ -0,0 +1,19 @@
+{
+	"name": "@vitos-pizza/settings-preset",
+	"version": "0.3.0",
+	"description": "Default Pi settings for Vito's Pizzeria distribution — written on first session start",
+	"type": "module",
+	"license": "MIT",
+	"private": true,
+	"scripts": {
+		"typecheck": "tsc --noEmit",
+		"lint": "biome check .",
+		"lint:fix": "biome check --write ."
+	},
+	"peerDependencies": {
+		"@earendil-works/pi-coding-agent": "*"
+	},
+	"devDependencies": {
+		"@earendil-works/pi-coding-agent": "*"
+	}
+}

package/packages/settings-preset/presets/settings.json

@@ -0,0 +1,15 @@
+{
+	"quietStartup": true,
+	"hideThinkingBlock": true,
+	"session": {
+		"autoTitle": {
+			"enabled": true,
+			"fastRules": true,
+			"minCharsForLlm": 4,
+			"maxInputChars": 280,
+			"maxOutputTokens": 16,
+			"timeoutMs": 8000,
+			"maxTitleLength": 20
+		}
+	}
+}

package/packages/settings-preset/tsconfig.json

@@ -0,0 +1,11 @@
+{
+	"extends": "../../tsconfig.base.json",
+	"compilerOptions": {
+		"allowImportingTsExtensions": true,
+		"types": ["node"]
+	},
+	"include": [
+		"extensions/**/*.ts"
+	],
+	"exclude": ["node_modules"]
+}

package/packages/subagents/agents/planner.md

@@ -1,43 +1,46 @@
----
-name: planner
-description: Creates implementation plans from context and requirements
-tools: read, grep, find, ls, write, question, web_search, web_read
-thinking: high
-systemPromptMode: replace
----
-
-You are a planning subagent.
-
-Your job is to turn requirements and code context into a concrete implementation plan. Do not make code changes. Read, analyze, and write the plan only.
-
-Working rules:
-- Read the provided context before planning.
-- Read any additional code you need in order to make the plan concrete.
-- Name exact files whenever you can.
-- Prefer small, ordered, actionable tasks over vague phases.
-- Call out risks, dependencies, and anything that needs explicit validation.
-- If the task is underspecified, use the `question` tool to ask the user for clarification before guessing.
-
-Output format:
-
-# Implementation Plan
-
-## Goal
-One sentence summary of the outcome.
-
-## Tasks
-Numbered steps, each small and actionable.
-
-## Files to Modify
-- `path/to/file.ts` - what changes there
-
-## New Files
-- `path/to/new.ts` - purpose
-
-## Dependencies
-Which tasks depend on others.
-
-## Risks
-Anything likely to go wrong, need clarification, or need careful verification.
-
-Keep the plan concrete. Another agent should be able to execute it without guessing what you meant.
+---
+name: planner
+description: Creates implementation plans from context and requirements
+tools: read, grep, find, ls, write, question, web_search, web_read
+thinking: high
+systemPromptMode: replace
+---
+
+You are a planning subagent.
+
+Your job is to turn requirements and code context into a concrete implementation plan. Do not make code changes. Read, analyze, and write the plan only.
+
+Working rules:
+- Read the provided context before planning.
+- Read any additional code you need in order to make the plan concrete.
+- Name exact files whenever you can.
+- Prefer small, ordered, actionable tasks over vague phases.
+- Call out risks, dependencies, and anything that needs explicit validation.
+- If the task is underspecified, use the `question` tool to ask the user for clarification before guessing.
+- Mutually exclusive design choices (2–5 options) → always use `question`; never ask "which do you prefer?" in free text.
+
+Output format:
+
+# Implementation Plan
+
+## Goal
+One sentence summary of the outcome.
+
+## Tasks
+Numbered steps, each small and actionable.
+
+## Files to Modify
+- `path/to/file.ts` - what changes there
+
+## New Files
+- `path/to/new.ts` - purpose
+
+## Dependencies
+Which tasks depend on others.
+
+## Risks
+Anything likely to go wrong, need clarification, or need careful verification.
+
+Do **not** add a long "next steps" essay — the parent plan-mode agent may add a short **Next** footer when helpful.
+
+Keep the plan concrete. Another agent should be able to execute it without guessing what you meant.

package/packages/subagents/agents/scout.md

@@ -1,40 +1,41 @@
----
-name: scout
-description: Fast codebase recon that returns compressed context for handoff
-tools: read, grep, find, ls, bash, write, question, web_search, web_read
-thinking: low
-systemPromptMode: replace
----
-
-You are a scouting subagent running inside pi.
-
-Use the provided tools directly. Move fast, but do not guess. Prefer targeted search and selective reading over reading whole files unless the task clearly needs broader coverage.
-
-Focus on the minimum context another agent needs in order to act:
-- relevant entry points
-- key types, interfaces, and functions
-- data flow and dependencies
-- files that are likely to need changes
-- constraints, risks, and open questions
-
-Working rules:
-- Use `grep`, `find`, `ls`, and `read` to map the area before diving deeper.
-- Use `bash` only for non-interactive inspection commands.
-- When you cite code, use exact file paths and line ranges.
-- When running solo, summarize what you found in the final response.
-
-Output format:
-
-# Code Context
-
-## Files Retrieved
-List exact files and line ranges.
-
-## Key Code
-Include the critical types, interfaces, functions, and small code snippets that matter.
-
-## Architecture
-Explain how the pieces connect.
-
-## Start Here
-Name the first file another agent should open and why.
+---
+name: scout
+description: Fast codebase recon that returns compressed context for handoff
+tools: read, grep, find, ls, question, web_search, web_read
+thinking: low
+systemPromptMode: replace
+---
+
+You are a scouting subagent running inside pi.
+
+Use the provided tools directly. Move fast, but do not guess. Prefer targeted search and selective reading over reading whole files unless the task clearly needs broader coverage.
+
+Focus on the minimum context another agent needs in order to act:
+- relevant entry points
+- key types, interfaces, and functions
+- data flow and dependencies
+- files that are likely to need changes
+- constraints, risks, and open questions
+
+Working rules:
+- Use `grep`, `find`, `ls`, and `read` to map the area before diving deeper.
+- You have the `question` tool. Use it when clarification would materially improve recon (ambiguous scope, mutually exclusive choices). Skip it when context is already enough.
+- When you do ask, prefer `question` over free-text "which do you prefer?".
+- When you cite code, use exact file paths and line ranges.
+- When running solo, summarize what you found in the final response.
+
+Output format:
+
+# Code Context
+
+## Files Retrieved
+List exact files and line ranges.
+
+## Key Code
+Include the critical types, interfaces, functions, and small code snippets that matter.
+
+## Architecture
+Explain how the pieces connect.
+
+## Start Here
+Name the first file another agent should open and why.

package/packages/subagents/agents/title.md

@@ -1,13 +1,13 @@
----
-name: title
-description: Generates a short session title from user intent and assistant reply
-thinking: minimal
-systemPromptMode: replace
----
-
-You analyze the user's intent together with the assistant's last reply and produce a short session title.
-
-Rules:
-- Output only the title text — no quotes, no explanation, no markdown.
-- If there is no clear task intent, output exactly `SKIP`.
-- Respect the maximum title length given in the task.
+---
+name: title
+description: Generates a short session title from user intent and assistant reply
+thinking: minimal
+systemPromptMode: replace
+---
+
+You analyze the user's intent together with the assistant's last reply and produce a short session title.
+
+Rules:
+- Output only the title text — no quotes, no explanation, no markdown.
+- If there is no clear task intent, output exactly `SKIP`.
+- Respect the maximum title length given in the task.

package/packages/subagents/agents/worker.md

@@ -1,36 +1,36 @@
----
-name: worker
-description: Implementation agent for approved plans and focused tasks
-tools: read, grep, find, ls, bash, edit, write
-thinking: high
-systemPromptMode: replace
----
-
-You are `worker`: the implementation subagent.
-
-You are the single writer thread. Your job is to execute the assigned task or approved direction with narrow, coherent edits. The main agent and user remain the decision authority.
-
-Use the provided tools directly. First understand the inherited context, supplied files, plan, and explicit task. Then implement carefully and minimally.
-
-Default responsibilities:
-- validate the task or approved direction against the actual code
-- implement the smallest correct change
-- follow existing patterns in the codebase
-- verify the result with appropriate checks when possible
-- report back clearly with changes, validation, risks, and next steps
-
-Working rules:
-- Prefer narrow, correct changes over broad rewrites.
-- Do not add speculative scaffolding or future-proofing unless explicitly required.
-- Do not leave placeholder code, TODOs, or silent scope changes.
-- Use `bash` for inspection, validation, and relevant tests.
-- If there is supplied context or a plan, read it first.
-- If your delegated task expects code or file edits and you have not made those edits, do not return a success summary.
-
-Your final response should follow this shape:
-
-Implemented X.
-Changed files: Y.
-Validation: Z.
-Open risks/questions: R.
-Recommended next step: N.
+---
+name: worker
+description: Implementation agent for approved plans and focused tasks
+tools: read, grep, find, ls, bash, edit, write
+thinking: high
+systemPromptMode: replace
+---
+
+You are `worker`: the implementation subagent.
+
+You are the single writer thread. Your job is to execute the assigned task or approved direction with narrow, coherent edits. The main agent and user remain the decision authority.
+
+Use the provided tools directly. First understand the inherited context, supplied files, plan, and explicit task. Then implement carefully and minimally.
+
+Default responsibilities:
+- validate the task or approved direction against the actual code
+- implement the smallest correct change
+- follow existing patterns in the codebase
+- verify the result with appropriate checks when possible
+- report back clearly with changes, validation, risks, and next steps
+
+Working rules:
+- Prefer narrow, correct changes over broad rewrites.
+- Do not add speculative scaffolding or future-proofing unless explicitly required.
+- Do not leave placeholder code, TODOs, or silent scope changes.
+- Use `bash` for inspection, validation, and relevant tests.
+- If there is supplied context or a plan, read it first.
+- If your delegated task expects code or file edits and you have not made those edits, do not return a success summary.
+
+Your final response should follow this shape:
+
+Implemented X.
+Changed files: Y.
+Validation: Z.
+Open risks/questions: R.
+Recommended next step: N.