appostle-installer 0.0.19 → 0.0.20

package/dist/appostle.js

@@ -1922,6 +1922,10 @@ function toAgentPayload(agent, options) {
     title: options?.title ?? null,
     labels: agent.labels,
     internal: agent.internal,
+    // Forward archivedAt on the live broadcast so paired clients (e.g. mobile)
+    // see the archive land — without this, only the device that ran the
+    // archive mutation knows about it.
+    archivedAt: agent.archivedAt ?? null,
     // Surface ownership so the client can render an owner badge / detect
     // "shared with me" agents. `sharedWithUserIds` deliberately stays off
     // the snapshot — only owners read the full ACL, via the dedicated
@@ -19464,11 +19468,53 @@ var ClaudeAgentSession = class {
       // sub-agents stop announcing them as suspected prompt injections. See
       // getSystemReminderGuidance for the full rationale.
       getSystemReminderGuidance(),
-      "Default response shape: open with a short, scannable plain-English read. 2\u20134 short sentences, one idea each, no comma-chained clauses or em-dash pile-ups. When the read covers 3+ discrete points, use bullets instead of prose. Then the technical detail in dense form (paths, line refs, code) without narration. Don't explain what well-named code already explains. Skip the shape for trivial questions.",
-      "For multi-step work with independent chunks, spawn Task subagents instead of doing every tool call yourself. Run them in parallel when chunks don't depend on each other. Keeps your main context lean.",
+      //
+      //
+      //
+      //
+      // ╔══════════════════════════════════════════════════════════════════╗
+      // ║  CUSTOM INSTRUCTIONS — add new system prompt lines below here  ║
+      // ║  Each line is a quoted string: "your instruction here",        ║
+      // ╚══════════════════════════════════════════════════════════════════╝
+      //
+      //
+      //
+      //
+      "Default response shape: open with a short, scannable plain-English read. 2\u20134 short sentences, one idea each, no comma-chained clauses or em-dash pile-ups. When the read covers 3+ discrete points, use bullets instead of prose. Then the technical detail in dense form (paths, line refs, code) without narration. Don\u2019t explain what well-named code already explains. Skip the shape for trivial questions.",
+      //
       "When the user sends `>learn`, re-explain your previous message in plain English only \u2014 1 short paragraph that helps them build the mental model. No code, no file references, no technical repeat.",
+      //
+      //
+      //
+      //
+      // ╔══════════════════════════════════════════════════════════════════╗
+      // ║  END CUSTOM INSTRUCTIONS — don't edit below this line          ║
+      // ╚══════════════════════════════════════════════════════════════════╝
+      //
+      //
+      //
+      //
       this.config.systemPrompt?.trim()
     ].filter((entry) => typeof entry === "string" && entry.length > 0).join("\n\n");
+    const appostleAgents = {
+      researcher: {
+        description: "Use this agent when you need to explore unfamiliar code, trace data flow across modules, search broadly across the codebase, or read more than 2 files you haven't seen yet. Delegate investigation work here to keep the main conversation context lean.",
+        prompt: "You are a codebase researcher. Your job is to investigate, trace, and report findings \u2014 never edit files. Read code, grep for patterns, follow imports, and build a clear picture. Report back a concise summary of what you found: key files, relevant code paths, and your conclusion. Keep your report under 300 words unless the investigation is complex.",
+        model: "sonnet"
+      },
+      refactorer: {
+        description: "Use this agent for refactors that touch more than 2 files \u2014 renames, migrations, pattern replacements, moving code between modules. Delegate multi-file changes here to isolate the blast radius.",
+        prompt: "You are a refactoring specialist. Make the requested changes across all affected files. Be thorough \u2014 update imports, references, types, and tests. Run typecheck after changes if available. Report what you changed and any issues found."
+      },
+      reviewer: {
+        description: "Use this agent to review code for bugs, security issues, performance problems, or style violations. Use it before committing large changes or when the user asks for a review.",
+        prompt: "You are a code reviewer. Analyze the code for correctness, security vulnerabilities (OWASP top 10), performance issues, and adherence to the project's coding standards. Be specific \u2014 cite file paths and line numbers. Flag severity: critical, warning, or nitpick. Keep the review focused and actionable."
+      },
+      debugger: {
+        description: "Use this agent to investigate bugs \u2014 read logs, trace error paths, check database state, reproduce issues. Delegate debugging here when the root cause isn't obvious from a quick look.",
+        prompt: "You are a debugger. Your job is to find the root cause, not patch symptoms. Check real data first \u2014 logs, network requests, database state. Trace the full lifecycle of the bug. Present your findings: root cause, evidence, and a proposed minimal fix. Do not edit files unless explicitly asked."
+      }
+    };
     const claudeBinary = await findExecutable("claude");
     this.logger.debug(
       {
@@ -19486,7 +19532,7 @@ var ClaudeAgentSession = class {
       // bypass launch capability available so later setPermissionMode("bypassPermissions")
       // calls do not fail after a model/thinking/rewind-driven restart.
       allowDangerouslySkipPermissions: true,
-      agents: this.defaults?.agents,
+      agents: { ...appostleAgents, ...this.defaults?.agents },
       canUseTool: this.handlePermissionRequest,
       ...claudeBinary ? { pathToClaudeCodeExecutable: claudeBinary } : {},
       // Use Claude Code preset system prompt and load CLAUDE.md files
@@ -35482,71 +35528,28 @@ function buildStructuralContext(allBrands) {
   return lines.length > 0 ? lines.join("\n") : "(No structural context established yet.)";
 }
 var TARGET_QUESTIONS = 7;
-var EMBEDDED_QA_FALLBACK = `## Compositional Philosophy
-- What's the single-sentence design philosophy that should govern every layout decision?
-- What's the ratio of whitespace to content density you're after?
-
-## Hero Behavior
-- How should the hero section behave? Full viewport takeover, contained module, asymmetric split?
-- Should the hero have scroll-triggered behavior or stay static?
-
-## Section Variation & Flow
-- How many distinct section types should the page cycle through?
-- Should any sections break out of the main container (full-bleed moments)?
-
-## Density & Spacing
-- How tight should content be packed within sections?
-- How much vertical breathing room between major sections?
-
-## Grid System
-- What grid philosophy \u2014 strict 12-column, asymmetric, modular, or freeform?
-
-## Containers & Cards
-- What's your card philosophy \u2014 flat, elevated, outlined, or glassmorphic?
-
-## Image Treatment
-- What role do images play \u2014 hero-level, supporting, or minimal?
-
-## CTA Strategy
-- How many CTAs per page and what's the hierarchy?
-
-## Mobile Behavior
-- How should the desktop layout transform on mobile?
-
-## Prohibitions & Bans
-- What design patterns are absolutely forbidden?
-- Any CSS properties or techniques that are banned?`;
-async function loadQaQuestions(logger) {
-  const filePath = await findFileUpward(QA_FILENAME);
-  if (filePath) {
-    try {
-      const content = await fs12.readFile(filePath, "utf8");
-      logger.debug({ filePath }, "layout-generator: loaded Q&A questions from disk");
-      return content;
-    } catch (err) {
-      logger.warn(
-        { err, filePath },
-        "layout-generator: failed to read Q&A file; using embedded fallback"
-      );
-    }
+async function loadSpecFile(filename, logger) {
+  const filePath = await findFileUpward(filename);
+  if (!filePath) {
+    throw new Error(
+      `layout-generator: ${filename} not found by walking up from ${fileURLToPath2(import.meta.url)}. This file is the canonical spec and must exist at the appostle repo root.`
+    );
+  }
+  try {
+    const content = await fs12.readFile(filePath, "utf8");
+    logger.debug({ filePath }, `layout-generator: loaded ${filename} from disk`);
+    return content;
+  } catch (err) {
+    throw new Error(
+      `layout-generator: failed to read ${filename} at ${filePath}: ${err.message}`
+    );
   }
-  return EMBEDDED_QA_FALLBACK;
+}
+async function loadQaQuestions(logger) {
+  return loadSpecFile(QA_FILENAME, logger);
 }
 async function loadLayoutPrompt(logger) {
-  const filePath = await findFileUpward(PROMPT_FILENAME);
-  if (filePath) {
-    try {
-      const content = await fs12.readFile(filePath, "utf8");
-      logger.debug({ filePath }, "layout-generator: loaded layout prompt from disk");
-      return content;
-    } catch (err) {
-      logger.warn(
-        { err, filePath },
-        "layout-generator: failed to read layout-prompt file; using embedded fallback"
-      );
-    }
-  }
-  return EMBEDDED_LAYOUT_PROMPT_FALLBACK;
+  return loadSpecFile(PROMPT_FILENAME, logger);
 }
 function interpolateTemplate(template, vars) {
   let out = template;
@@ -35555,66 +35558,6 @@ function interpolateTemplate(template, vars) {
   }
   return out;
 }
-var EMBEDDED_LAYOUT_PROMPT_FALLBACK = `You are an elite art director refining the layout and composition rules for a brand. This is ONLY about layout \u2014 structure, zones, grid, density, rhythm, containers, image placement, CTAs. Typography, colors, motion, animations, shadows are handled by separate brand files \u2014 do not duplicate them here.
-
-These rules must work across media \u2014 web pages, print, PDF, presentations. Use proportional language (fractions, ratios, percentages) as the primary system. CSS values are welcome as concrete examples but should not be the only expression of a rule.
-
-Your job: update the design role document based on the user's refinement prompt. This document will be injected wholesale into an AI builder's context. If your rules are vague, the output will be generic. If your rules are specific and opinionated, the output will be distinctive.
-
-The document must be a complete markdown document covering:
-- Enemy (a specific design this must NOT resemble, with 2-3 specific layout patterns that make it wrong \u2014 and for each, the exact counter-pattern this brand uses instead)
-- Signature Anomaly (the one structural layout choice that makes this unmistakably distinctive)
-- Compositional Philosophy (one structural law + the structural spine mechanism that enforces it across every zone)
-- Intensity Dials (Density 1-10, Grid Variance 1-10 \u2014 with concrete implications for THIS brand)
-- Opening Zone / Hero Behavior (surface coverage, bleed, content placement, containment)
-- Zone Inventory (ordered list of all major zones: name, layout job, dense/airy, full-bleed/contained \u2014 this is the master reference for the rhythm)
-- Zone Variation & Flow (how zones differ, transition strategy, full-bleed vs contained \u2014 references the Zone Inventory)
-- Density Philosophy (spacing values; the oscillation rhythm derived from the Zone Inventory \u2014 name which zones are dense, which are airy, in sequence)
-- Vertical Rhythm (three values: zone padding, element gap within zones, and the one zone that breaks the rhythm and why)
-- Grid System (exact column structure, asymmetry, proportions)
-- Content Width Strategy (max-width of the primary content area, which zones break it and why)
-- Container & Card Rules (borders, corners, nesting, exact border-radius)
-- Dividers & Graphic Structure (structural vs decorative, background strategy)
-- Image Treatment \u2014 Layout Only (placement, grid relationship, overlap behavior)
-- CTA Strategy (position in layout referencing Zone Inventory, container strategy, frequency)
-- Responsive Behavior (how the layout adapts across sizes \u2014 web: breakpoints and stacking; print: scale and margin strategy)
-- Bans (at least 20 specific layout prohibitions)
-
-## Critical rules
-
-1. This is a REFINEMENT. The user already has a role document (shown below). Their prompt refines, evolves, or redirects \u2014 it does NOT start from scratch unless they explicitly say so.
-
-2. SPECIFICITY IS MANDATORY. Every rule must be actionable at the structural level. Generic adjectives ("clean", "minimal", "modern", "elegant") are BANNED from the output.
-
-3. THE DOCUMENT MUST BE OPINIONATED, NOT HEDGED. Every sentence must prescribe or ban \u2014 never suggest. Use "Always", "Never", "Must", "Banned", "Required".
-
-4. STAY IN YOUR LANE. Do NOT include rules about typography, colors, motion/animation, or shadows \u2014 those belong in their own brand files.
-
-5. THE BANS ARE THE MOST IMPORTANT SECTION. At least 20 bans. The 7 universal AI-layout cliches MUST each appear as an explicit named ban: centered headline over full-width image; three equal-width feature cards in a row; alternating left-right image/text rows with identical padding; uniform zone height and padding; every block wrapped in a card with shadow + radius; CTA with gradient fill; full-width "Why Choose Us" icon grid. Plus 3-5 brand-specific AI tells.
-
-6. THE ENEMY IS MANDATORY. Name a specific real design and 2-3 exact layout patterns from it. Vague enemies fail.
-
-7. THE SIGNATURE ANOMALY IS MANDATORY. One specific structural choice. Apply the removal test: if removing this single decision would make the layout indistinguishable from a generic design \u2014 it qualifies. Must appear as a constraint in at least 2 other sections.
-
-8. USE THE STRUCTURAL CONTEXT. The {{structuralContext}} contains sibling brand files. Do not duplicate their rules \u2014 derive layout implications from them.
-
-## Current role document
-
-{{currentValues}}
-
-## Structural context (sibling brand files)
-
-{{structuralContext}}
-
-## User's refinement prompt
-
-{{userPrompt}}
-
-## Response format
-
-Return ONLY a JSON object: { "roleDocument": "# Brand Layout Role\\n\\n## Enemy\\n..." }
-
-Output ONLY the JSON object. No markdown fences. No explanation.`;
 function buildQaSystemPrompt(questions, layoutPromptSpec) {
   return `You are a chill creative director doing a quick vibe check on someone's layout taste.