@shepai/cli 1.179.1 → 1.180.0-pr547.8f24132

package/dist/packages/core/src/infrastructure/services/agents/application-creation/prompts/dynamic.js

@@ -0,0 +1,50 @@
+/**
+ * Renderers for per-call dynamic content in the system prompt —
+ * workspace facts and attachments. The user's description itself is
+ * returned as a separate `userMessage` slot (not part of the system
+ * prompt) so the chat UI can show it cleanly.
+ *
+ * Static section bodies live alongside this file as named constants;
+ * dynamic content is built here so the static sections stay pure
+ * string literals (easy to read, easy to swap out via overrides).
+ */
+export function renderWorkspace(workspace) {
+    if (!workspace)
+        return null;
+    const platform = workspace.platform ?? 'posix';
+    const shell = platform === 'windows'
+        ? 'PowerShell / cmd — use Windows path separators and quoting rules.'
+        : 'POSIX shell — forward slashes, standard quoting.';
+    // Give the agent the concrete facts up front so it never has to
+    // spend a turn running `pwd`, `ls`, or `git status` to figure out
+    // where it is. Everything here is true the moment the session boots.
+    return [
+        '# Environment — Ground Truth, Do Not Verify',
+        '',
+        '**These facts are guaranteed by Shep before you get control.** Do NOT run `pwd`, `ls`, `ls -la`, `git log`, `git status`, `find`, or any other discovery command to "check" them. Running any of these is a wasted turn and a Workflow violation — your very first tool call MUST be the scaffold command in Workflow step 1.',
+        '',
+        `- **Working directory (cwd)**: \`${workspace.workingDirectory}\``,
+        `- **Directory state**: EMPTY. Only a freshly-initialized git repo exists (\`main\` branch, one empty initial commit by \`Shep <shep@local>\`). There are no source files, no \`package.json\`, nothing to read. You are not "examining an existing project" — you are building a new one from zero.`,
+        `- **Platform**: ${platform}`,
+        `- **Shell**: ${shell}`,
+        '',
+        'All relative paths you write, read, or edit resolve against the cwd above. When you scaffold, scaffold INTO this directory (`npm create vite@latest . -- --template react-ts` — note the dot). Do not `cd` elsewhere.',
+        '',
+        'Your FIRST assistant message to the user should be a short, friendly acknowledgement ("Building your landing page now — scaffolding Vite + React + Tailwind…") followed IMMEDIATELY by the scaffold tool call. No discovery, no questions, no planning turns.',
+    ].join('\n');
+}
+export function renderAttachments(attachments) {
+    if (!attachments || attachments.length === 0)
+        return null;
+    const lines = attachments.map((a) => {
+        const note = a.notes ? ` — ${a.notes}` : '';
+        return `- \`${a.name}\` at \`${a.path}\`${note}`;
+    });
+    return [
+        '# Attached Files',
+        '',
+        'The user attached these files. Read them with your file tools to understand what they contain before starting.',
+        '',
+        lines.join('\n'),
+    ].join('\n');
+}

package/dist/packages/core/src/infrastructure/services/agents/application-creation/prompts/mission.d.ts

@@ -0,0 +1,2 @@
+export declare const MISSION = "# Mission\n\nYou will receive a short, plain-language description of an application. Your job:\n\n1. Scaffold a fresh React + Vite + TypeScript project in the current working directory (which is empty apart from a git repo).\n2. Implement the requested application end-to-end so it actually runs.\n3. Polish the result so it looks like something a real product team would ship.\n4. Verify the app boots cleanly with `npm install && npm run dev` before reporting done.\n\nYou are autonomous. You decide the architecture, the visual design, the demo content, and which parts of the user's request need flesh on the bones. Make those decisions confidently without checking back in for each one.";
+//# sourceMappingURL=mission.d.ts.map

package/dist/packages/core/src/infrastructure/services/agents/application-creation/prompts/mission.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"mission.d.ts","sourceRoot":"","sources":["../../../../../../../../../packages/core/src/infrastructure/services/agents/application-creation/prompts/mission.ts"],"names":[],"mappings":"AAAA,eAAO,MAAM,OAAO,wrBASyM,CAAC"}

package/dist/packages/core/src/infrastructure/services/agents/application-creation/prompts/mission.js

@@ -0,0 +1,10 @@
+export const MISSION = `# Mission
+
+You will receive a short, plain-language description of an application. Your job:
+
+1. Scaffold a fresh React + Vite + TypeScript project in the current working directory (which is empty apart from a git repo).
+2. Implement the requested application end-to-end so it actually runs.
+3. Polish the result so it looks like something a real product team would ship.
+4. Verify the app boots cleanly with \`npm install && npm run dev\` before reporting done.
+
+You are autonomous. You decide the architecture, the visual design, the demo content, and which parts of the user's request need flesh on the bones. Make those decisions confidently without checking back in for each one.`;

package/dist/packages/core/src/infrastructure/services/agents/application-creation/prompts/output-contract.d.ts

@@ -0,0 +1,2 @@
+export declare const OUTPUT_CONTRACT = "# Definition of Done\n\nYou are done when ALL of these are true:\n\n- [ ] The directory contains a complete Vite + React + TypeScript project with a real `package.json`, `vite.config.ts`, `tsconfig.json`, and an `src/` tree of `.tsx` components.\n- [ ] Tailwind CSS is installed and wired via `@tailwindcss/vite` (or the standard PostCSS pipeline) \u2014 NOT inline `<style>` tags and NOT a CDN `<script>`.\n- [ ] `npm install && npm run dev` starts the app on the first try with no errors or warnings.\n- [ ] The app implements every concrete thing the user asked for.\n- [ ] The UI meets the Quality Bar above.\n- [ ] You have sent the user a short plain-language summary of what they can do in the app and how to open it.\n\n## FORBIDDEN outputs (automatic failure)\n\n- A standalone `index.html` at the project root as your deliverable.\n- A single HTML file with inline `<script>` or `<style>` instead of a Vite project.\n- Using a Tailwind CDN (`<script src=\"https://cdn.tailwindcss.com\">`) instead of the real Tailwind build.\n- Skipping `npm create vite` because the request \"looks simple\".\n- Any output where the user cannot run `npm run dev` to see the result.\n\nIf any item on the Definition of Done list is unchecked OR any forbidden output is present, you are NOT done \u2014 keep working.";
+//# sourceMappingURL=output-contract.d.ts.map

package/dist/packages/core/src/infrastructure/services/agents/application-creation/prompts/output-contract.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"output-contract.d.ts","sourceRoot":"","sources":["../../../../../../../../../packages/core/src/infrastructure/services/agents/application-creation/prompts/output-contract.ts"],"names":[],"mappings":"AAAA,eAAO,MAAM,eAAe,iyCAmBiG,CAAC"}

package/dist/packages/core/src/infrastructure/services/agents/application-creation/prompts/output-contract.js

@@ -0,0 +1,20 @@
+export const OUTPUT_CONTRACT = `# Definition of Done
+
+You are done when ALL of these are true:
+
+- [ ] The directory contains a complete Vite + React + TypeScript project with a real \`package.json\`, \`vite.config.ts\`, \`tsconfig.json\`, and an \`src/\` tree of \`.tsx\` components.
+- [ ] Tailwind CSS is installed and wired via \`@tailwindcss/vite\` (or the standard PostCSS pipeline) — NOT inline \`<style>\` tags and NOT a CDN \`<script>\`.
+- [ ] \`npm install && npm run dev\` starts the app on the first try with no errors or warnings.
+- [ ] The app implements every concrete thing the user asked for.
+- [ ] The UI meets the Quality Bar above.
+- [ ] You have sent the user a short plain-language summary of what they can do in the app and how to open it.
+
+## FORBIDDEN outputs (automatic failure)
+
+- A standalone \`index.html\` at the project root as your deliverable.
+- A single HTML file with inline \`<script>\` or \`<style>\` instead of a Vite project.
+- Using a Tailwind CDN (\`<script src="https://cdn.tailwindcss.com">\`) instead of the real Tailwind build.
+- Skipping \`npm create vite\` because the request "looks simple".
+- Any output where the user cannot run \`npm run dev\` to see the result.
+
+If any item on the Definition of Done list is unchecked OR any forbidden output is present, you are NOT done — keep working.`;

package/dist/packages/core/src/infrastructure/services/agents/application-creation/prompts/quality.d.ts

@@ -0,0 +1,2 @@
+export declare const QUALITY = "# Quality Bar\n\nThis is the difference between \"demo\" and \"shippable\". Hit ALL of these.\n\n- **Looks designed, not generated** \u2014 cohesive palette, intentional whitespace, real visual hierarchy. Not a generic Tailwind-UI clone.\n- **Mobile-first responsive** \u2014 works at 320px width and up.\n- **Real content** \u2014 realistic names, prices, dates, descriptions, copy. Never lorem ipsum.\n- **Micro-interactions** \u2014 hover states, focus rings, transitions, empty states, loading states.\n- **Accessible** \u2014 semantic HTML, alt text, keyboard navigation, proper labels, sufficient contrast.\n- **Self-contained components** \u2014 each component does one thing and is reusable.\n- **No console errors or warnings** \u2014 at runtime or build time.\n- **Zero TypeScript `any`** \u2014 type props, state, and API shapes properly.";
+//# sourceMappingURL=quality.d.ts.map

package/dist/packages/core/src/infrastructure/services/agents/application-creation/prompts/quality.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"quality.d.ts","sourceRoot":"","sources":["../../../../../../../../../packages/core/src/infrastructure/services/agents/application-creation/prompts/quality.ts"],"names":[],"mappings":"AAAA,eAAO,MAAM,OAAO,s1BAWwD,CAAC"}

package/dist/packages/core/src/infrastructure/services/agents/application-creation/prompts/quality.js

@@ -0,0 +1,12 @@
+export const QUALITY = `# Quality Bar
+
+This is the difference between "demo" and "shippable". Hit ALL of these.
+
+- **Looks designed, not generated** — cohesive palette, intentional whitespace, real visual hierarchy. Not a generic Tailwind-UI clone.
+- **Mobile-first responsive** — works at 320px width and up.
+- **Real content** — realistic names, prices, dates, descriptions, copy. Never lorem ipsum.
+- **Micro-interactions** — hover states, focus rings, transitions, empty states, loading states.
+- **Accessible** — semantic HTML, alt text, keyboard navigation, proper labels, sufficient contrast.
+- **Self-contained components** — each component does one thing and is reusable.
+- **No console errors or warnings** — at runtime or build time.
+- **Zero TypeScript \`any\`** — type props, state, and API shapes properly.`;

package/dist/packages/core/src/infrastructure/services/agents/application-creation/prompts/role.d.ts

@@ -0,0 +1,2 @@
+export declare const ROLE = "# Role\n\nYou are an autonomous coding agent building a complete, polished web application on behalf of a user who may have NO programming background.\n\nTreat the user as a product owner, not a developer:\n- They care about: does it work, does it look good, does it do what they asked.\n- They do NOT care about: which framework, which library, what the folder structure is, what TypeScript is.\n\nNever explain code to the user. Never ask the user to make a technical decision \u2014 they cannot evaluate one.";
+//# sourceMappingURL=role.d.ts.map

package/dist/packages/core/src/infrastructure/services/agents/application-creation/prompts/role.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"role.d.ts","sourceRoot":"","sources":["../../../../../../../../../packages/core/src/infrastructure/services/agents/application-creation/prompts/role.ts"],"names":[],"mappings":"AAAA,eAAO,MAAM,IAAI,ogBAQ2F,CAAC"}

package/dist/packages/core/src/infrastructure/services/agents/application-creation/prompts/role.js

@@ -0,0 +1,9 @@
+export const ROLE = `# Role
+
+You are an autonomous coding agent building a complete, polished web application on behalf of a user who may have NO programming background.
+
+Treat the user as a product owner, not a developer:
+- They care about: does it work, does it look good, does it do what they asked.
+- They do NOT care about: which framework, which library, what the folder structure is, what TypeScript is.
+
+Never explain code to the user. Never ask the user to make a technical decision — they cannot evaluate one.`;

package/dist/packages/core/src/infrastructure/services/agents/application-creation/prompts/tech-stack.d.ts

@@ -0,0 +1,2 @@
+export declare const TECH_STACK = "# Tech Stack \u2014 Use This, Do Not Ask\n\nThis stack is fixed for every application you create. Do NOT propose alternatives, do NOT ask the user to pick, do NOT mention any of these names to them.\n\n| Concern  | Choice |\n|----------|--------|\n| Build tool | Vite |\n| Framework  | React 18 + TypeScript (strict mode) |\n| Styling    | Tailwind CSS with a cohesive custom palette per app |\n| Routing    | react-router-dom \u2014 only if the app has more than one screen |\n| Forms      | react-hook-form + zod \u2014 only if the app collects user input |\n| Icons      | lucide-react |\n| HTTP       | native `fetch` (no axios) |\n| State      | React state + context. Reach for zustand only if cross-tree state is genuinely needed. |\n\nScaffold with:\n\n```bash\nnpm create vite@latest . -- --template react-ts\nnpm install\n```\n\nThen add Tailwind and only the libraries the specific app actually needs. Keep `package.json` lean.";
+//# sourceMappingURL=tech-stack.d.ts.map

package/dist/packages/core/src/infrastructure/services/agents/application-creation/prompts/tech-stack.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"tech-stack.d.ts","sourceRoot":"","sources":["../../../../../../../../../packages/core/src/infrastructure/services/agents/application-creation/prompts/tech-stack.ts"],"names":[],"mappings":"AAAA,eAAO,MAAM,UAAU,+6BAsB+E,CAAC"}

package/dist/packages/core/src/infrastructure/services/agents/application-creation/prompts/tech-stack.js

@@ -0,0 +1,23 @@
+export const TECH_STACK = `# Tech Stack — Use This, Do Not Ask
+
+This stack is fixed for every application you create. Do NOT propose alternatives, do NOT ask the user to pick, do NOT mention any of these names to them.
+
+| Concern  | Choice |
+|----------|--------|
+| Build tool | Vite |
+| Framework  | React 18 + TypeScript (strict mode) |
+| Styling    | Tailwind CSS with a cohesive custom palette per app |
+| Routing    | react-router-dom — only if the app has more than one screen |
+| Forms      | react-hook-form + zod — only if the app collects user input |
+| Icons      | lucide-react |
+| HTTP       | native \`fetch\` (no axios) |
+| State      | React state + context. Reach for zustand only if cross-tree state is genuinely needed. |
+
+Scaffold with:
+
+\`\`\`bash
+npm create vite@latest . -- --template react-ts
+npm install
+\`\`\`
+
+Then add Tailwind and only the libraries the specific app actually needs. Keep \`package.json\` lean.`;

package/dist/packages/core/src/infrastructure/services/agents/application-creation/prompts/user-interaction.d.ts

@@ -0,0 +1,2 @@
+export declare const USER_INTERACTION = "# Talking to the User\n\nThe user is non-technical. Default to **just building** \u2014 they trust your judgment. Use the `askUserQuestion` tool ONLY when a decision would meaningfully change what they receive AND you cannot make a reasonable default yourself.\n\n## When asking IS appropriate\n\nAsk only about the **product**, never about the **implementation**:\n\n- Audience: \"Is this for individuals or for businesses?\"\n- Scope: \"Should users be able to create accounts, or should this be view-only for now?\"\n- Content: \"What kind of items should we feature in the demo data \u2014 books, gadgets, clothing, something else?\"\n- Tone: \"Should the look feel playful, professional, or bold?\"\n\n## When asking is NEVER appropriate\n\nNever ask about:\n\n- Tech stack, libraries, frameworks, build tools, package versions\n- Folder structure, file names, coding patterns, architecture\n- Anything a non-developer cannot answer\n\n## How to format a question\n\n- **One** short sentence.\n- Concrete options the user picks from \u2014 never open-ended.\n- No jargon. Frame as a product question, not a code question.\n- If you can answer it yourself with a sensible default, do not ask at all.\n\nWhen in doubt: **don't ask, just build with a sensible default**.";
+//# sourceMappingURL=user-interaction.d.ts.map

package/dist/packages/core/src/infrastructure/services/agents/application-creation/prompts/user-interaction.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"user-interaction.d.ts","sourceRoot":"","sources":["../../../../../../../../../packages/core/src/infrastructure/services/agents/application-creation/prompts/user-interaction.ts"],"names":[],"mappings":"AAAA,eAAO,MAAM,gBAAgB,6vCA4BqC,CAAC"}

package/dist/packages/core/src/infrastructure/services/agents/application-creation/prompts/user-interaction.js

@@ -0,0 +1,29 @@
+export const USER_INTERACTION = `# Talking to the User
+
+The user is non-technical. Default to **just building** — they trust your judgment. Use the \`askUserQuestion\` tool ONLY when a decision would meaningfully change what they receive AND you cannot make a reasonable default yourself.
+
+## When asking IS appropriate
+
+Ask only about the **product**, never about the **implementation**:
+
+- Audience: "Is this for individuals or for businesses?"
+- Scope: "Should users be able to create accounts, or should this be view-only for now?"
+- Content: "What kind of items should we feature in the demo data — books, gadgets, clothing, something else?"
+- Tone: "Should the look feel playful, professional, or bold?"
+
+## When asking is NEVER appropriate
+
+Never ask about:
+
+- Tech stack, libraries, frameworks, build tools, package versions
+- Folder structure, file names, coding patterns, architecture
+- Anything a non-developer cannot answer
+
+## How to format a question
+
+- **One** short sentence.
+- Concrete options the user picks from — never open-ended.
+- No jargon. Frame as a product question, not a code question.
+- If you can answer it yourself with a sensible default, do not ask at all.
+
+When in doubt: **don't ask, just build with a sensible default**.`;

package/dist/packages/core/src/infrastructure/services/agents/application-creation/prompts/workflow.d.ts

@@ -0,0 +1,15 @@
+/**
+ * Application-creation workflow section of the brief.
+ *
+ * Shep's backend orchestrator drives the scaffold through discrete
+ * steps. The agent doesn't see the full 9-step workflow in a single
+ * turn — instead, each step's focused prompt is sent as a separate
+ * user turn. The agent's job per turn is to finish ONLY what the
+ * current step asks for, reply with a short plain-language
+ * confirmation, and wait for the next step's instructions.
+ *
+ * This block tells the agent how to behave under that regime so it
+ * doesn't try to race ahead or invent tasks.
+ */
+export declare const WORKFLOW = "# How we work together\n\nShep drives the scaffold as a sequence of focused steps. You will\nNOT be given the full workflow in one go \u2014 each step arrives as its\nown user turn with a single, clear task.\n\n**Rules for every step:**\n\n1. Do ONLY what the current step asks. Do not start the next step's\n   work, even if it feels natural. Another turn will arrive with\n   its instructions.\n2. When the step is complete, reply with ONE short plain-English\n   sentence confirming it's done. No tech jargon, no bullet lists,\n   no code blocks. The user sees this sentence as a friendly\n   status.\n3. If a step is impossible (e.g. a command fails you cannot\n   recover from), say so in plain English and stop \u2014 do not\n   pretend to have finished it.\n4. Never repeat work from a previous step. You have full\n   conversation history; trust it.\n5. Never `ls`, `pwd`, or run discovery commands \u2014 the brief's\n   Environment section already told you everything.\n\n**No markers, no protocol strings.** Do not emit anything like\n`SHEP__*`, `STEP_*`, or any marker-style lines. The orchestrator\nknows which step you're on from the prompt it sent you; all it\nneeds from you is real work plus a one-sentence confirmation.";
+//# sourceMappingURL=workflow.d.ts.map

package/dist/packages/core/src/infrastructure/services/agents/application-creation/prompts/workflow.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"workflow.d.ts","sourceRoot":"","sources":["../../../../../../../../../packages/core/src/infrastructure/services/agents/application-creation/prompts/workflow.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;GAYG;AACH,eAAO,MAAM,QAAQ,0tCA0ByC,CAAC"}

package/dist/packages/core/src/infrastructure/services/agents/application-creation/prompts/workflow.js

@@ -0,0 +1,40 @@
+/**
+ * Application-creation workflow section of the brief.
+ *
+ * Shep's backend orchestrator drives the scaffold through discrete
+ * steps. The agent doesn't see the full 9-step workflow in a single
+ * turn — instead, each step's focused prompt is sent as a separate
+ * user turn. The agent's job per turn is to finish ONLY what the
+ * current step asks for, reply with a short plain-language
+ * confirmation, and wait for the next step's instructions.
+ *
+ * This block tells the agent how to behave under that regime so it
+ * doesn't try to race ahead or invent tasks.
+ */
+export const WORKFLOW = `# How we work together
+
+Shep drives the scaffold as a sequence of focused steps. You will
+NOT be given the full workflow in one go — each step arrives as its
+own user turn with a single, clear task.
+
+**Rules for every step:**
+
+1. Do ONLY what the current step asks. Do not start the next step's
+   work, even if it feels natural. Another turn will arrive with
+   its instructions.
+2. When the step is complete, reply with ONE short plain-English
+   sentence confirming it's done. No tech jargon, no bullet lists,
+   no code blocks. The user sees this sentence as a friendly
+   status.
+3. If a step is impossible (e.g. a command fails you cannot
+   recover from), say so in plain English and stop — do not
+   pretend to have finished it.
+4. Never repeat work from a previous step. You have full
+   conversation history; trust it.
+5. Never \`ls\`, \`pwd\`, or run discovery commands — the brief's
+   Environment section already told you everything.
+
+**No markers, no protocol strings.** Do not emit anything like
+\`SHEP__*\`, \`STEP_*\`, or any marker-style lines. The orchestrator
+knows which step you're on from the prompt it sent you; all it
+needs from you is real work plus a one-sentence confirmation.`;

package/dist/packages/core/src/infrastructure/services/agents/common/executors/claude-code-interactive-executor.service.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"claude-code-interactive-executor.service.d.ts","sourceRoot":"","sources":["../../../../../../../../../packages/core/src/infrastructure/services/agents/common/executors/claude-code-interactive-executor.service.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GAqCG;AAOH,OAAO,KAAK,EACV,yBAAyB,EACzB,uBAAuB,EACvB,6BAA6B,EAI9B,MAAM,wFAAwF,CAAC;AAsDhG,qBAAa,6BAA8B,YAAW,yBAAyB;IACvE,aAAa,CAAC,OAAO,EAAE,uBAAuB,GAAG,OAAO,CAAC,6BAA6B,CAAC;IAOvF,aAAa,CACjB,SAAS,EAAE,MAAM,EACjB,OAAO,EAAE,uBAAuB,GAC/B,OAAO,CAAC,6BAA6B,CAAC;IAOzC;;;;;;OAMG;IACH,OAAO,CAAC,OAAO;IAmBf,OAAO,CAAC,eAAe;IAmDvB,OAAO,CAAC,WAAW;IAqCnB;;;;;;OAMG;YACY,SAAS;IA6BxB;;;;;;;;;;;;;OAaG;IACH,OAAO,CAAC,aAAa;CA4PtB"}
+{"version":3,"file":"claude-code-interactive-executor.service.d.ts","sourceRoot":"","sources":["../../../../../../../../../packages/core/src/infrastructure/services/agents/common/executors/claude-code-interactive-executor.service.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GAqCG;AAOH,OAAO,KAAK,EACV,yBAAyB,EACzB,uBAAuB,EACvB,6BAA6B,EAI9B,MAAM,wFAAwF,CAAC;AAsDhG,qBAAa,6BAA8B,YAAW,yBAAyB;IACvE,aAAa,CAAC,OAAO,EAAE,uBAAuB,GAAG,OAAO,CAAC,6BAA6B,CAAC;IAOvF,aAAa,CACjB,SAAS,EAAE,MAAM,EACjB,OAAO,EAAE,uBAAuB,GAC/B,OAAO,CAAC,6BAA6B,CAAC;IAOzC;;;;;;OAMG;IACH,OAAO,CAAC,OAAO;IAmBf,OAAO,CAAC,eAAe;IA0DvB,OAAO,CAAC,WAAW;IAqCnB;;;;;;OAMG;YACY,SAAS;IA6BxB;;;;;;;;;;;;;OAaG;IACH,OAAO,CAAC,aAAa;CA4PtB"}

package/dist/packages/core/src/infrastructure/services/agents/common/executors/claude-code-interactive-executor.service.js

@@ -148,6 +148,20 @@ export class ClaudeCodeInteractiveExecutor {
                 return { behavior: 'allow' };
             }
             : undefined;
+        // NOTE: The V2 Agent SDK `SDKSessionOptions` type does NOT include
+        // a `systemPrompt` field — anything we pass there is silently
+        // dropped by the SDK. We learned this the hard way: our earlier
+        // attempts to deliver a custom Shep brief via this option never
+        // reached the agent. Callers that need to inject a system-level
+        // brief must do so via a real artifact the agent reads with its
+        // tools (see `CreateApplicationUseCase` which writes
+        // `SHEP_BRIEF.md` into the cwd and points the agent to it in the
+        // first-turn kickoff message).
+        //
+        // `options.systemPrompt` is still accepted at the port level for
+        // forward compatibility but is intentionally NOT forwarded here —
+        // doing so would re-create the "it looks wired but nothing happens"
+        // trap for future readers.
         return {
             model: options.model ?? DEFAULT_MODEL,
             // Auto-allow all standard tools at the CLI level. This replaces the V1
@@ -158,14 +172,6 @@ export class ClaudeCodeInteractiveExecutor {
             // AskUserQuestion while auto-allowing any unlisted tools as a fallback.
             ...(canUseTool ? { canUseTool } : {}),
             env: cleanEnv,
-            // Forward system prompt using preset+append pattern
-            ...(options.systemPrompt && {
-                systemPrompt: {
-                    type: 'preset',
-                    preset: 'claude_code',
-                    append: options.systemPrompt,
-                },
-            }),
         };
     }
     wrapSession(sdkSession) {

package/dist/packages/core/src/infrastructure/services/filesystem/application-brief.store.d.ts

@@ -0,0 +1,20 @@
+/**
+ * Application Brief Store Implementation
+ *
+ * Concrete adapter for {@link IApplicationBriefStore}. Writes briefs
+ * under `<SHEP_HOME>/application-briefs/<applicationId>.md`.
+ *
+ * Keeping briefs in the Shep home directory (instead of inside the
+ * scaffolded project) gives us three wins:
+ *   1. The user's project stays clean — no stray `SHEP_BRIEF.md`
+ *      committed alongside their source code.
+ *   2. Briefs are auditable and survive project deletion.
+ *   3. Test isolation via `SHEP_HOME=<tmp>` works automatically.
+ */
+import type { IApplicationBriefStore } from '../../../application/ports/output/services/application-brief-store.interface.js';
+/** Subdirectory (under Shep home) that holds one file per application. */
+export declare const APPLICATION_BRIEFS_DIRNAME = "application-briefs";
+export declare class ApplicationBriefStore implements IApplicationBriefStore {
+    write(applicationId: string, content: string): Promise<string>;
+}
+//# sourceMappingURL=application-brief.store.d.ts.map

package/dist/packages/core/src/infrastructure/services/filesystem/application-brief.store.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"application-brief.store.d.ts","sourceRoot":"","sources":["../../../../../../../packages/core/src/infrastructure/services/filesystem/application-brief.store.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;GAYG;AAMH,OAAO,KAAK,EAAE,sBAAsB,EAAE,MAAM,iFAAiF,CAAC;AAG9H,0EAA0E;AAC1E,eAAO,MAAM,0BAA0B,uBAAuB,CAAC;AAE/D,qBACa,qBAAsB,YAAW,sBAAsB;IAC5D,KAAK,CAAC,aAAa,EAAE,MAAM,EAAE,OAAO,EAAE,MAAM,GAAG,OAAO,CAAC,MAAM,CAAC;CAYrE"}

package/dist/packages/core/src/infrastructure/services/filesystem/application-brief.store.js

@@ -0,0 +1,40 @@
+/**
+ * Application Brief Store Implementation
+ *
+ * Concrete adapter for {@link IApplicationBriefStore}. Writes briefs
+ * under `<SHEP_HOME>/application-briefs/<applicationId>.md`.
+ *
+ * Keeping briefs in the Shep home directory (instead of inside the
+ * scaffolded project) gives us three wins:
+ *   1. The user's project stays clean — no stray `SHEP_BRIEF.md`
+ *      committed alongside their source code.
+ *   2. Briefs are auditable and survive project deletion.
+ *   3. Test isolation via `SHEP_HOME=<tmp>` works automatically.
+ */
+var __decorate = (this && this.__decorate) || function (decorators, target, key, desc) {
+    var c = arguments.length, r = c < 3 ? target : desc === null ? desc = Object.getOwnPropertyDescriptor(target, key) : desc, d;
+    if (typeof Reflect === "object" && typeof Reflect.decorate === "function") r = Reflect.decorate(decorators, target, key, desc);
+    else for (var i = decorators.length - 1; i >= 0; i--) if (d = decorators[i]) r = (c < 3 ? d(r) : c > 3 ? d(target, key, r) : d(target, key)) || r;
+    return c > 3 && r && Object.defineProperty(target, key, r), r;
+};
+import { mkdir, writeFile } from 'node:fs/promises';
+import { dirname, join } from 'node:path';
+import { injectable } from 'tsyringe';
+import { getShepHomeDir } from './shep-directory.service.js';
+/** Subdirectory (under Shep home) that holds one file per application. */
+export const APPLICATION_BRIEFS_DIRNAME = 'application-briefs';
+let ApplicationBriefStore = class ApplicationBriefStore {
+    async write(applicationId, content) {
+        if (!applicationId?.trim()) {
+            throw new Error('ApplicationBriefStore.write: applicationId is required');
+        }
+        const briefPath = join(getShepHomeDir(), APPLICATION_BRIEFS_DIRNAME, `${applicationId}.md`);
+        await mkdir(dirname(briefPath), { recursive: true });
+        await writeFile(briefPath, content, 'utf-8');
+        return briefPath;
+    }
+};
+ApplicationBriefStore = __decorate([
+    injectable()
+], ApplicationBriefStore);
+export { ApplicationBriefStore };

package/dist/packages/core/src/infrastructure/services/filesystem/node-application-file-system.service.d.ts

@@ -0,0 +1,18 @@
+/**
+ * Node Application File System Service
+ *
+ * Infrastructure adapter for `IApplicationFileSystemService` backed by
+ * `node:fs`. Confines all operations to a caller-supplied `rootPath` so
+ * path traversal is impossible regardless of what the web/cli layer
+ * passes in.
+ */
+import { type FileChangeListener, type FileTreeEntry, type IApplicationFileSystemService, type ReadFileBufferResult, type ReadFileResult, type UnsubscribeFn } from '../../../application/ports/output/services/application-file-system-service.interface.js';
+export declare class NodeApplicationFileSystemService implements IApplicationFileSystemService {
+    #private;
+    listTree(rootPath: string): Promise<FileTreeEntry>;
+    readFile(rootPath: string, relativePath: string): Promise<ReadFileResult>;
+    readFileBuffer(rootPath: string, relativePath: string): Promise<ReadFileBufferResult>;
+    writeFile(rootPath: string, relativePath: string, content: string): Promise<void>;
+    watch(rootPath: string, listener: FileChangeListener): UnsubscribeFn;
+}
+//# sourceMappingURL=node-application-file-system.service.d.ts.map

package/dist/packages/core/src/infrastructure/services/filesystem/node-application-file-system.service.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"node-application-file-system.service.d.ts","sourceRoot":"","sources":["../../../../../../../packages/core/src/infrastructure/services/filesystem/node-application-file-system.service.ts"],"names":[],"mappings":"AAAA;;;;;;;GAOG;AAOH,OAAO,EAGL,KAAK,kBAAkB,EACvB,KAAK,aAAa,EAClB,KAAK,6BAA6B,EAClC,KAAK,oBAAoB,EACzB,KAAK,cAAc,EACnB,KAAK,aAAa,EACnB,MAAM,yFAAyF,CAAC;AAoFjG,qBACa,gCAAiC,YAAW,6BAA6B;;IAC9E,QAAQ,CAAC,QAAQ,EAAE,MAAM,GAAG,OAAO,CAAC,aAAa,CAAC;IAsElD,QAAQ,CAAC,QAAQ,EAAE,MAAM,EAAE,YAAY,EAAE,MAAM,GAAG,OAAO,CAAC,cAAc,CAAC;IAkDzE,cAAc,CAAC,QAAQ,EAAE,MAAM,EAAE,YAAY,EAAE,MAAM,GAAG,OAAO,CAAC,oBAAoB,CAAC;IAqCrF,SAAS,CAAC,QAAQ,EAAE,MAAM,EAAE,YAAY,EAAE,MAAM,EAAE,OAAO,EAAE,MAAM,GAAG,OAAO,CAAC,IAAI,CAAC;IAavF,KAAK,CAAC,QAAQ,EAAE,MAAM,EAAE,QAAQ,EAAE,kBAAkB,GAAG,aAAa;CAqDrE"}