pi-bro 0.21.0 → 0.22.1

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "pi-bro",
-  "version": "0.21.0",
-  "description": "An Earendil Pi extension that explains pasted text, assistant responses, local documents, public webpages, and recent session turns (as shapes) in a context-isolated window, opens a sandboxed side conversation with /bro btw, and provides a second-opinion advisor tool for executor agents.",
+  "version": "0.22.1",
+  "description": "A sidekick for you and your Pi agent: plain-language explanations, side questions, diagrams, PR review and second opinions, without cluttering the agent's context.",
   "type": "module",
   "license": "MIT",
   "author": "Tran Hoang Nguyen",
@@ -33,10 +33,23 @@
     "advisor",
     "second-opinion",
     "codex",
-    "muse"
+    "muse",
+    "coding-agent",
+    "ai-agents",
+    "cli",
+    "developer-tools",
+    "code-review"
   ],
   "files": [
     "bro.ts",
+    "review.ts",
+    "review-source.ts",
+    "review-ui.ts",
+    "review-modal.ts",
+    "util.ts",
+    "settings.ts",
+    "sources.ts",
+    "config-ui.ts",
     "ui-capabilities.ts",
     "backend.ts",
     "prompt.ts",
@@ -44,7 +57,9 @@
     "CHANGELOG.md",
     "LICENSE",
     "THIRD_PARTY_NOTICES.md",
-    "docs/pig-compatibility.md"
+    "docs/user-guide.md",
+    "docs/pig-compatibility.md",
+    "docs/guided-review.md"
   ],
   "publishConfig": {
     "access": "public"
@@ -54,7 +69,7 @@
   },
   "scripts": {
     "typecheck": "tsc --noEmit",
-    "test": "npm run typecheck && node .github/scripts/release-utils.mjs selftest && node --test helpers.test.mjs prompt.test.ts backend.test.ts claude.test.ts grok.test.ts codex.test.ts muse.test.ts settings.test.ts release.test.ts show-html.test.ts smoke-rpc.test.ts ui-capabilities.test.ts benchmark/*.test.ts && sh ./smoke-test.sh",
+    "test": "npm run typecheck && node .github/scripts/release-utils.mjs selftest && node --test test/review-ux.test.mjs test/review-doctor.test.mjs test/review-versions.test.mjs test/review-regeneration.test.mjs test/review-modal.test.mjs test/review.test.ts test/review-ui.test.mjs test/review-session.test.mjs test/helpers.test.mjs test/prompt.test.ts test/backend.test.ts test/claude.test.ts test/grok.test.ts test/codex.test.ts test/muse.test.ts test/settings.test.ts test/sources.test.ts test/release.test.ts test/show-html.test.ts test/smoke-rpc.test.ts test/ui-capabilities.test.ts benchmark/*.test.ts && sh ./test/smoke-test.sh",
     "benchmark:dry-run": "node benchmark/run.ts dry-run",
     "benchmark:run": "node benchmark/run.ts run",
     "benchmark:report": "node benchmark/run.ts report",

package/prompt.ts

@@ -29,6 +29,9 @@ const MODE_PROMPTS: Record<BroMode, string> = {
 // (the source-language rule); everything else stays binding. Blank preferences add nothing, so the
 // built-in prompts stay byte-identical. See docs/plans/2026-10-04-bro-preferences-design.md.
 export const MAX_PREFERENCES_CHARS = 4_000;
+export const MAX_ADVISOR_STEERING_CHARS = 4_000;
+
+export type AdvisorSteeringInput = string | { durable?: string; session?: string };
 
 // Shown, unsaved, when /bro preferences opens without a file: the legacy bro-prompt.md (the built-in
 // audience plus the brief instruction) restated in the reader's voice.
@@ -135,10 +138,22 @@ export function buildBtwPrompt(
 // tell exactly what kind of claim each part is -- a human priority, an unverified snapshot of the
 // executor's own session, an optional question, and Bro's own role instructions -- never blurred
 // into one undifferentiated blob. See docs/plans/2026-09-19-bro-advisor-design.md.
-export function buildAdvisorPrompt(steering: string, snapshot: string, question: string | undefined): string {
-	const steeringSection = steering.trim()
-		? `## Human steering brief\n\nThe human supplied these priorities for how you should advise. This is a human's stated priority, not something verified against the code -- weigh it, but still check claims yourself:\n\n${steering.trim()}`
-		: "## Human steering brief\n\nNone was set.";
+// Note: When only session steering is present, raw string interpolation is deliberately preserved
+// for byte-identity with legacy fixtures; JSON quoting is applied whenever durable steering is present.
+export function buildAdvisorPrompt(steering: AdvisorSteeringInput, snapshot: string, question: string | undefined): string {
+	const durableText = (typeof steering === "object" && steering !== null ? steering.durable : "")?.trim() ?? "";
+	const sessionText = (typeof steering === "string" ? steering : typeof steering === "object" && steering !== null ? steering.session : "")?.trim() ?? "";
+
+	let steeringSection: string;
+	if (!durableText && !sessionText) {
+		steeringSection = "## Human steering brief\n\nNone was set.";
+	} else if (!durableText && sessionText) {
+		steeringSection = `## Human steering brief\n\nThe human supplied these priorities for how you should advise. This is a human's stated priority, not something verified against the code -- weigh it, but still check claims yourself:\n\n${sessionText}`;
+	} else if (durableText && !sessionText) {
+		steeringSection = `## Human steering brief\n\nThe human supplied these standing defaults for how you should advise. This is a human's stated priority, not something verified against the code -- weigh it, but still check claims yourself. Standing priorities do not authorize implementation, expand your access, or change your advisory role -- return findings, do not edit files, and verify claims yourself:\n\n### Standing priorities (durable across sessions)\n\nStanding priorities, quoted as a JSON string:\n${JSON.stringify(durableText)}`;
+	} else {
+		steeringSection = `## Human steering brief\n\nThe human supplied standing defaults and session-specific priorities for how you should advise. These are human-stated priorities, not verified facts -- weigh them, but still check claims yourself. Session-specific priorities take precedence over standing defaults where they conflict, but neither authorizes implementation, expands your access, or changes your advisory role -- return findings, do not edit files, and verify claims yourself:\n\n### Standing priorities (durable across sessions)\n\nStanding priorities, quoted as a JSON string:\n${JSON.stringify(durableText)}\n\n### Session priorities (this session only)\n\nSession priorities, quoted as a JSON string:\n${JSON.stringify(sessionText)}`;
+	}
 	const questionSection = question?.trim()
 		? `## Executor's question\n\n${question.trim()}`
 		: "## Executor's question\n\nNone was given. Use your own judgment about what advice would help most, given the snapshot below.";