@clubnet/seedclub 0.2.22 → 0.2.23

package/assets/extensions/seedclub/branding.ts

@@ -3,8 +3,8 @@ import type { ExtensionAPI } from "@mariozechner/pi-coding-agent";
 const BRANDING_INSTRUCTIONS = `
 IMPORTANT BRANDING RULES:
 - Always refer to the product as Seed Club.
-- Never mention the name \"pi\" in any response.
-- If the user mentions \"pi\", interpret it as Seed Club and respond using \"Seed Club\".
+- Never mention the name "pi" in any response.
+- If the user mentions "pi", interpret it as Seed Club and respond using "Seed Club".
 - When summarizing intent or describing the system, use Seed Club wording only.
 
 IMPORTANT SEED CLUB API ROUTING:
@@ -15,7 +15,7 @@ IMPORTANT SEED CLUB API ROUTING:
 - If the user asks for "all transcripts" and the tool returns a limited page, summarize the returned transcript rows and say you can fetch full text for selected rows. Do not claim exhaustive coverage unless the API result proves it.
 - Use includeFullText only after narrowing to rows the user wants to inspect.
 - Use seedclub_list_program_media_assets(assetKind=full_conversation) only when the user asks for full conversations or media assets. Do not use it as the default source for transcript inventory.
-- For transcript retrieval asks (e.g., "I need transcripts...", "get transcripts...", guest/date transcript pulls), first use chat and metadata tools to establish exact constraints when needed, then call seedclub_export_transcripts with the user's original request. This preserves the user prompt in context, confirms destination, then writes VTT files.
+- For transcript retrieval asks (e.g., "I need transcripts...", "get transcripts...", guest/date transcript pulls), first use chat and metadata tools to establish exact constraints when needed, then call seedclub_export_transcripts with the user's original request. Prefer this single export tool path over chaining high-payload media tools.
 - Treat short transcript artifact prompts like "today's transcripts", "2pm transcripts", "Tuesday VTTs", or "recent captions" as local transcript export tool requests, not inline transcript display requests.
 - Do not paste full transcript JSON or raw session context into the reply unless the user explicitly asks for raw data.
 - Use seedclub_list_show_recordings for show recording URLs, then follow transcript event_date only when needed.
@@ -23,30 +23,30 @@ IMPORTANT SEED CLUB API ROUTING:
 
 const BRAND_REGEX = /\bpi\b/gi;
 
+const EXTERNAL_RESEARCH_INSTRUCTIONS = `
+EXTERNAL RESEARCH ROUTING:
+- Seed Club runs in a general-purpose coding harness with shell tools.
+- If the user asks an open-ended research question that is not explicitly scoped to Seed Club records, do a fast external research pass before answering.
+- Use shell tools (e.g., curl via bash) to gather at least 2 reputable sources, then answer with a concise synthesis.
+- Include source URLs inline so the user can verify.
+- If the user explicitly scopes to Seed Club records (transcripts, meetings, CRM, media), prioritize Seed Club tools first.
+`;
+
 function replaceBranding(text: string): string {
 	return text.replace(BRAND_REGEX, "Seed Club");
 }
 
-export default function registerBrandingGuard(pi: ExtensionAPI) {
-	pi.on("before_agent_start", async (event) => {
+export default function registerBrandingGuard(seedClub: ExtensionAPI) {
+	seedClub.on("before_agent_start", async (event) => {
 		return {
-			systemPrompt: `${event.systemPrompt}\n${BRANDING_INSTRUCTIONS}`,
+			systemPrompt: `${event.systemPrompt}\n${BRANDING_INSTRUCTIONS}\n${EXTERNAL_RESEARCH_INSTRUCTIONS}`,
 		};
 	});
 
-	pi.on("input", async (event) => {
+	seedClub.on("input", async (event) => {
 		if (event.source === "extension") return { action: "continue" };
 		const nextText = replaceBranding(event.text);
 		if (nextText !== event.text) return { action: "transform", text: nextText };
 		return { action: "continue" };
 	});
-
-	pi.on("tool_result", async (event) => {
-		const nextContent = event.content.map((item) => {
-			if (item.type !== "text") return item;
-			const nextText = replaceBranding(item.text);
-			return nextText === item.text ? item : { ...item, text: nextText };
-		});
-		return { content: nextContent };
-	});
 }