@lbruton/specflow 3.1.0 → 3.2.1

package/dist/prompts/prime.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"prime.d.ts","sourceRoot":"","sources":["../../src/prompts/prime.ts"],"names":[],"mappings":"AACA,OAAO,EAAE,gBAAgB,EAAE,MAAM,YAAY,CAAC;AAsS9C,eAAO,MAAM,WAAW,EAAE,gBAGzB,CAAC"}

package/dist/prompts/prime.js

@@ -1,290 +0,0 @@
-const prompt = {
-    name: 'prime',
-    title: 'Session Quick-Start',
-    description: 'Fast session boot (~15 seconds). Gathers git status, open issues/PRs, active specs, today\'s digest, and a targeted mem0 search — all in main context, no agents dispatched. Use "prime full" for a deep scan including code health, security, and indexing.',
-    arguments: [
-        {
-            name: 'mode',
-            description: 'Execution mode: "quick" (default, 15 seconds) or "full" (deep scan with agents, 60-90 seconds)',
-            required: false
-        }
-    ]
-};
-async function handler(args, context) {
-    const mode = args.mode || 'quick';
-    if (mode === 'full') {
-        return buildFullPrimeMessages(context);
-    }
-    return buildQuickPrimeMessages(context);
-}
-function buildQuickPrimeMessages(context) {
-    return [
-        {
-            role: 'user',
-            content: {
-                type: 'text',
-                text: `Quick session start. Gather project status fast — no agents, no indexing. Target: 15 seconds.
-
-**Context:**
-- Project: ${context.projectPath}
-${context.dashboardUrl ? `- Dashboard: ${context.dashboardUrl}` : ''}
-
----
-
-## Phase 0: Project Identity (instant)
-
-\`\`\`bash
-cat .claude/project.json 2>/dev/null
-\`\`\`
-
-Extract: \`name\`, \`tag\`, \`issuePrefix\`. If no project.json, infer from:
-\`\`\`bash
-basename "$(git remote get-url origin 2>/dev/null)" .git
-\`\`\`
-
----
-
-## Phase 1: Ground Truth (parallel, main context — no agents)
-
-Run ALL of these in parallel using Bash:
-
-\`\`\`bash
-# Branch and working tree state
-git branch --show-current && git status --short
-
-# Recent commits (last 15)
-git log --oneline -15 --no-merges
-
-# Open worktrees
-git worktree list
-
-# Version lock (if exists)
-cat devops/version.lock 2>/dev/null || echo "no-version-lock"
-\`\`\`
-
-\`\`\`bash
-# Open PRs
-gh pr list --state open --json number,title,headRefName,isDraft --jq '.[] | "PR #\\(.number): \\(.title) [\\(.headRefName)]\\(if .isDraft then " (draft)" else "" end)"' 2>/dev/null || echo "gh-unavailable"
-\`\`\`
-
-Also gather these (parallel with above):
-
-**Vault Issues** — if \`issuePrefix\` exists, scan the vault issues folder:
-\`\`\`bash
-# List open issues (scan frontmatter for status != done)
-grep -rl "status: backlog\\|status: todo\\|status: in-progress" /Volumes/DATA/GitHub/DocVault/Projects/<name>/Issues/*.md 2>/dev/null | head -20
-\`\`\`
-For each file found, extract just the title and status from frontmatter (read first 10 lines).
-
-**Active Specs** — if \`.spec-workflow/specs/\` exists:
-- Use the **spec-status** tool (no specName — returns all specs) or:
-\`\`\`bash
-ls .spec-workflow/specs/ 2>/dev/null
-\`\`\`
-For each spec, check if tasks.md has any \`[-]\` (in-progress) or \`[ ]\` (pending) markers.
-
-**Today's Digest** — check if a session digest was written today or yesterday:
-\`\`\`bash
-# Find most recent digest for this project
-ls -t "/Volumes/DATA/GitHub/DocVault/Daily Digests/<ProjectFolder>/"*.md 2>/dev/null | head -1
-\`\`\`
-If found and from today/yesterday, read it for context on where we left off.
-
----
-
-## Phase 2: Context (1-2 mem0 searches)
-
-Extract **keywords** from Phase 1 results:
-- Significant nouns from commit messages (skip generic: fix, update, add, remove, chore)
-- PR titles
-- Issue titles
-- Spec names
-
-Build 1-2 targeted mem0 searches:
-
-\`\`\`
-mcp__mem0__search_memories(
-  query: "<top 5-8 distinctive keywords from Phase 1>",
-  filters: {"AND": [{"agent_id": "<project-tag>"}]},
-  limit: 5
-)
-\`\`\`
-
-If the project tag yields <2 results, also try without the agent_id filter for cross-project context.
-
-From the results, extract only what adds context BEYOND what git/issues show:
-- Verbal decisions and rationale
-- Planned next steps from last session
-- Known blockers or dependencies
-- Gotchas or warnings for areas being worked on
-
----
-
-## Phase 3: Present
-
-Display a concise terminal summary. **Must stay under 25 lines.**
-
-\`\`\`
-# <ProjectName> — <date>
-Branch: \`<branch>\` | Version: \`<version>\` | Status: <clean/dirty>
-
-## Where We Left Off
-<2-3 sentences from today's digest + mem0 context. If no digest: use mem0 alone. If neither: "No recent session history.">
-
-## Open Work
-<Compact list: open PRs, active specs with task counts, in-progress issues — one line each, max 8 items>
-<If nothing open: "No open work items.">
-
-## Suggested Next Steps
-1. <highest priority — based on in-progress items, open PRs, or recent commits>
-2. <next priority>
-3. <next priority>
-\`\`\`
-
----
-
-## Rules
-
-- **No agents dispatched.** Everything runs in main context.
-- **No indexing.** CGC and claude-context are not touched (that's /audit's job).
-- **No Codacy queries.** Security scanning is /audit's job.
-- **No DocVault archive.** Quick primes don't write reports to disk.
-- **No session-digest processing.** That's /wrap's job at end of session.
-- **Target 15 seconds.** If it's taking longer, you're doing too much.
-- **Present, don't prescribe.** Show what's there, suggest next steps, then stop. The user decides what to work on.
-- **After presenting the summary, the session is ready for work.** Do not prompt to run prime again.`
-            }
-        }
-    ];
-}
-function buildFullPrimeMessages(context) {
-    return [
-        {
-            role: 'user',
-            content: {
-                type: 'text',
-                text: `Full session start with deep scanning. This includes everything from quick prime PLUS code health, security, and indexing.
-
-**Context:**
-- Project: ${context.projectPath}
-${context.dashboardUrl ? `- Dashboard: ${context.dashboardUrl}` : ''}
-
----
-
-## Step 1: Run Quick Prime First
-
-Execute the full quick prime sequence (Phase 0-3 from the quick mode) to get the baseline status fast. Present the quick summary to the user immediately — don't wait for the deep scans.
-
----
-
-## Step 2: Deep Scans (parallel agents, background)
-
-After presenting the quick summary, dispatch these in parallel:
-
-### 2.1: Code Health (Agent: code-oracle, background)
-Dispatch a \`code-oracle\` agent:
-\`\`\`
-Run a code health check:
-- query: "dead code, complexity hotspots, convention violations"
-- workingDir: ${context.projectPath}
-- Focus on: dead code (CGC), top 5 complex functions (CGC), convention issues in files changed last 7 days
-- Keep report compact — tables only, max 15 findings
-\`\`\`
-
-### 2.2: Security Scan (main context, parallel with 2.1)
-Query Codacy for open findings:
-\`\`\`
-mcp__codacy__codacy_search_repository_srm_items(
-  provider="gh", organization="<owner>", repository="<repo>",
-  options={"statuses": ["OnTrack", "DueSoon", "Overdue"], "priorities": ["Critical", "High"]},
-  limit=25
-)
-\`\`\`
-
-Also query critical code quality issues:
-\`\`\`
-mcp__codacy__codacy_list_repository_issues(
-  provider="gh", organization="<owner>", repository="<repo>",
-  options={"levels": ["Error"], "categories": ["security", "errorprone"]},
-  limit=25
-)
-\`\`\`
-
-### 2.3: Index Health (main context, parallel)
-\`\`\`
-mcp__claude-context__get_indexing_status(path="${context.projectPath}")
-\`\`\`
-
-If stale (>24h), trigger a re-index:
-\`\`\`
-mcp__claude-context__index_codebase(path="${context.projectPath}")
-\`\`\`
-
-Check CGC if available:
-\`\`\`
-mcp__code-graph-context__get_repository_stats(repo_path="/workspace/<name>")
-\`\`\`
-
----
-
-## Step 3: Deep Report
-
-When agents return, present an extended report BELOW the quick summary:
-
-\`\`\`
-## Deep Scan Results
-
-### Code Health
-<Dead code count, top complexity hotspots, convention issues — from code-oracle agent>
-
-### Security
-**Codacy SRM:** N Critical, N High | N Overdue
-<List any Critical or Overdue items>
-**Code Quality:** N Error-level issues
-<If clean: "No open security or critical findings.">
-
-### Index Health
-| Tool | Status | Details |
-|------|--------|---------|
-| claude-context | Fresh/Stale/Indexing | N files |
-| CGC | Running/Down | N functions, N relationships |
-\`\`\`
-
----
-
-## Step 4: Archive to DocVault
-
-Write the full report (quick summary + deep results) to:
-\`\`\`
-/Volumes/DATA/GitHub/DocVault/Projects/<name>/prime/<YYYY-MM-DD>-<HHMMSS>.md
-\`\`\`
-
-Create the directory if needed (\`mkdir -p\`). Include YAML frontmatter:
-\`\`\`yaml
----
-tags: [prime-report, <tag>]
-project: <name>
-date: <YYYY-MM-DD>
-branch: <branch>
----
-\`\`\`
-
-Commit to DocVault (direct to main).
-
----
-
-## Rules
-
-- **Quick summary first.** Don't make the user wait for agents — show quick results immediately.
-- **Agents run in background.** Present deep results as they arrive.
-- **Graceful degradation.** If CGC is down, Codacy fails, or agents timeout — note it and continue.
-- **Full mode is opt-in.** Users run this when they want a thorough check, not every session.`
-            }
-        }
-    ];
-}
-export const primePrompt = {
-    prompt,
-    handler
-};
-//# sourceMappingURL=prime.js.map

package/dist/prompts/prime.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"prime.js","sourceRoot":"","sources":["../../src/prompts/prime.ts"],"names":[],"mappings":"AAIA,MAAM,MAAM,GAAW;IACrB,IAAI,EAAE,OAAO;IACb,KAAK,EAAE,qBAAqB;IAC5B,WAAW,EAAE,8PAA8P;IAC3Q,SAAS,EAAE;QACT;YACE,IAAI,EAAE,MAAM;YACZ,WAAW,EAAE,gGAAgG;YAC7G,QAAQ,EAAE,KAAK;SAChB;KACF;CACF,CAAC;AAEF,KAAK,UAAU,OAAO,CAAC,IAAyB,EAAE,OAAoB;IACpE,MAAM,IAAI,GAAG,IAAI,CAAC,IAAI,IAAI,OAAO,CAAC;IAElC,IAAI,IAAI,KAAK,MAAM,EAAE,CAAC;QACpB,OAAO,sBAAsB,CAAC,OAAO,CAAC,CAAC;IACzC,CAAC;IAED,OAAO,uBAAuB,CAAC,OAAO,CAAC,CAAC;AAC1C,CAAC;AAED,SAAS,uBAAuB,CAAC,OAAoB;IACnD,OAAO;QACL;YACE,IAAI,EAAE,MAAM;YACZ,OAAO,EAAE;gBACP,IAAI,EAAE,MAAM;gBACZ,IAAI,EAAE;;;aAGD,OAAO,CAAC,WAAW;EAC9B,OAAO,CAAC,YAAY,CAAC,CAAC,CAAC,gBAAgB,OAAO,CAAC,YAAY,EAAE,CAAC,CAAC,CAAC,EAAE;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;qGA6HiC;aAC9F;SACF;KACF,CAAC;AACJ,CAAC;AAED,SAAS,sBAAsB,CAAC,OAAoB;IAClD,OAAO;QACL;YACE,IAAI,EAAE,MAAM;YACZ,OAAO,EAAE;gBACP,IAAI,EAAE,MAAM;gBACZ,IAAI,EAAE;;;aAGD,OAAO,CAAC,WAAW;EAC9B,OAAO,CAAC,YAAY,CAAC,CAAC,CAAC,gBAAgB,OAAO,CAAC,YAAY,EAAE,CAAC,CAAC,CAAC,EAAE;;;;;;;;;;;;;;;;;;;gBAmBpD,OAAO,CAAC,WAAW;;;;;;;;;;;;;;;;;;;;;;;;;;iDA0Bc,OAAO,CAAC,WAAW;;;;;4CAKxB,OAAO,CAAC,WAAW;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;8FA6D+B;aACvF;SACF;KACF,CAAC;AACJ,CAAC;AAED,MAAM,CAAC,MAAM,WAAW,GAAqB;IAC3C,MAAM;IACN,OAAO;CACR,CAAC"}

package/dist/prompts/wrap.d.ts

@@ -1,3 +0,0 @@
-import { PromptDefinition } from './types.js';
-export declare const wrapPrompt: PromptDefinition;
-//# sourceMappingURL=wrap.d.ts.map

package/dist/prompts/wrap.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"wrap.d.ts","sourceRoot":"","sources":["../../src/prompts/wrap.ts"],"names":[],"mappings":"AACA,OAAO,EAAE,gBAAgB,EAAE,MAAM,YAAY,CAAC;AA+R9C,eAAO,MAAM,UAAU,EAAE,gBAGxB,CAAC"}

package/dist/prompts/wrap.js

@@ -1,285 +0,0 @@
-const prompt = {
-    name: 'wrap',
-    title: 'Wrap Session',
-    description: 'End-of-session orchestrator. Verifies work is complete, cleans up worktrees, updates documentation, captures retrospective lessons to mem0, writes a session digest to DocVault, and closes out the session cleanly. Replaces /goodnight and /digest-session with a single, higher-fidelity workflow.',
-    arguments: [
-        {
-            name: 'skipCleanup',
-            description: 'Skip worktree cleanup and PR verification (use when wrapping a session that had no code changes)',
-            required: false
-        }
-    ]
-};
-async function handler(args, context) {
-    const { skipCleanup } = args;
-    const messages = [
-        {
-            role: 'user',
-            content: {
-                type: 'text',
-                text: `Wrap up this session. Follow each phase in order — do not skip phases unless explicitly noted.
-
-**Context:**
-- Project: ${context.projectPath}
-${context.dashboardUrl ? `- Dashboard: ${context.dashboardUrl}` : ''}
-- Skip cleanup: ${skipCleanup ? 'yes' : 'no'}
-
----
-
-## Phase 1: Status Check
-
-Gather the current state before making any changes. Run ALL of these in parallel:
-
-\`\`\`bash
-# Git state
-git status --short
-git branch --show-current
-git stash list
-
-# Open worktrees
-git worktree list
-
-# Check for open PRs from this repo
-gh pr list --state open --json number,title,headRefName,state,mergeStateStatus
-\`\`\`
-
-Also check spec-workflow state if the project uses it:
-- If \`.spec-workflow/specs/\` exists, use the **spec-status** tool to check for in-progress tasks
-- Look for any tasks marked \`[-]\` (in-progress) that need to be completed or reverted
-
-**Report the status** before proceeding. If there are blockers (uncommitted files, unmerged PRs, in-progress tasks), present them and ask what to do.
-
----
-
-## Phase 2: Cleanup Gate${skipCleanup ? ' (SKIPPED — skipCleanup=true)' : ''}
-
-${skipCleanup ? 'Skipping cleanup — no code changes this session. Proceed to Phase 3.' : `Work through each item. **Do not proceed to Phase 3 until all gates pass.**
-
-### 2.1: Uncommitted Changes
-If \`git status\` shows dirty files:
-- Present the list and ask: **commit, stash, or discard?**
-- If commit: stage relevant files and commit with a descriptive message
-- If stash: \`git stash push -m "wrap: uncommitted work from session"\`
-- If discard: confirm with user before running \`git checkout -- .\`
-
-### 2.2: Implementation Logging
-If spec-workflow is active and tasks were completed this session:
-- Check that **log-implementation** was called for every task marked \`[x]\` during this session
-- If any task was marked complete WITHOUT a log entry, run log-implementation NOW
-- This is a **hard gate** — the most commonly skipped step in the workflow
-
-### 2.3: PR Status
-For each open PR from this session:
-- If **merged**: note it, proceed to worktree cleanup
-- If **open, checks passing**: ask user — merge now or leave for review?
-- If **open, checks failing**: flag it, ask user how to proceed
-- If **draft**: leave it, note it in the session summary
-
-### 2.4: Version Bump
-If the project has \`devops/version.lock\`:
-- Check if runtime code was changed this session (check git log for non-chore commits)
-- If runtime changes exist and no version bump commit is present, flag it:
-  "Runtime code changed but no version bump detected. Run /release patch before merging."
-
-### 2.5: Worktree Cleanup
-For each worktree listed in \`git worktree list\`:
-- If the branch was **merged**: remove the worktree (\`git worktree remove <path>\`) and delete the branch (\`git branch -d <branch>\`)
-- If the branch is **unmerged with no uncommitted changes**: ask user — delete or keep?
-- If the branch has **uncommitted changes**: flag it, do not auto-delete
-
-After cleanup, verify main/dev branch is clean:
-\`\`\`bash
-git checkout <main-branch>
-git pull origin <main-branch>
-git status --short
-\`\`\``}
-
----
-
-## Phase 3: Documentation
-
-### 3.1: DocVault Updates
-If code was changed this session, update relevant DocVault documentation:
-- Identify which DocVault pages are affected by the changes (architecture, API, features, etc.)
-- Read each affected page to check if it needs updates
-- Update pages with current information
-- Commit DocVault changes directly to main (DocVault uses direct commits, no PR needed)
-
-The DocVault lives at \`/Volumes/DATA/GitHub/DocVault/\`. Use the project name to find the right subdirectory under \`Projects/\`.
-
-### 3.2: Issue Updates
-If the session was driven by an issue (DocVault or GitHub):
-- If work is **complete**: update the issue status to \`done\` and add a completion note with PR/commit references
-- If work is **partially complete**: update the issue with progress notes and remaining work
-- If work is **blocked**: update the issue with blocker details
-
-### 3.3: Spec Status
-If spec-workflow specs were involved:
-- Update spec phase status if all tasks are complete
-- Check for pending approvals that should be resolved
-
----
-
-## Phase 4: Knowledge Capture
-
-This is the most important phase — it's what makes the next session productive. Run steps 4.1 and 4.2 sequentially (retro first, then digest), but 4.3 can run in parallel with 4.2.
-
-### 4.1: Retrospective (prescriptive lessons)
-
-Scan the current conversation for high-signal lessons. Look for:
-- **Mistakes** that cost time or caused rework
-- **Wrong assumptions** that led you astray
-- **Successful approaches** worth repeating
-- **User preferences** expressed during the session
-- **Codebase gotchas** discovered (tricky code, hidden dependencies, surprising behavior)
-- **Process improvements** — things that should be done differently next time
-
-For each lesson (target 3-8), save to mem0:
-
-\`\`\`
-mcp__mem0__add_memory(
-  text: "<single prescriptive sentence — action verb or 'When X, do Y' format>",
-  user_id: "lbruton",
-  agent_id: "<project-tag from project.json>",
-  metadata: {
-    "type": "retro-learning",
-    "category": "<error|pattern|preference|improvement|warning|win>",
-    "source": "retro",
-    "project": "<project-name>"
-  }
-)
-\`\`\`
-
-**Categories:**
-- **error**: Mistake that cost time — "Always check X before Y"
-- **pattern**: Reusable approach — "When doing X, use Y"
-- **preference**: User preference — "lbruton prefers X over Y"
-- **improvement**: Process improvement — "Next time, do X first"
-- **warning**: Gotcha or risk — "Watch out for X when touching Y"
-- **win**: Successful approach — "X worked well for Y"
-
-**Actor attribution rules (strict):**
-- Things lbruton did → "lbruton prefers/uses/instructs..."
-- Things Claude did → "Claude should..."
-- Codebase facts → passive voice or component name
-
-**Critical:** Always set BOTH \`user_id\` AND \`agent_id\`. Without \`agent_id\`, mem0 creates placeholder entity names.
-
-### 4.2: Session Digest (human-readable report for DocVault)
-
-Write a session digest entry to the DocVault daily digest file. This is the human-readable record of what happened.
-
-**Path:** \`/Volumes/DATA/GitHub/DocVault/Daily Digests/<ProjectFolder>/<YYYY-MM-DD>.md\`
-
-Where \`<ProjectFolder>\` maps to the project name (e.g., StakTrakr, HexTrackr, Infrastructure, SpecFlow).
-
-**If the file doesn't exist**, create it with this format:
-\`\`\`markdown
----
-date: <YYYY-MM-DD>
-project: <ProjectName>
-tags: [daily-digest, <project-tag>]
----
-
-# Daily Digest — <ProjectName> (<YYYY-MM-DD>)
-
-## <HH:MM AM/PM>
-
-<session summary>
-\`\`\`
-
-**If the file exists**, append a new \`## <HH:MM AM/PM>\` section.
-
-**Session summary content** (200-300 words, flowing prose):
-- What was the goal of this session?
-- What was accomplished? (specific: commits, PRs, issues closed, features shipped)
-- What problems were encountered and how were they resolved?
-- What decisions were made and why?
-- What's the current state? (branch, version, open work)
-- What should happen next?
-
-Include **concrete anchors**: commit hashes, issue IDs, version numbers, file paths. These make the digest searchable and verifiable.
-
-Commit the digest to DocVault:
-\`\`\`bash
-cd /Volumes/DATA/GitHub/DocVault && git add "Daily Digests/" && git commit -m "digest: <project> session <date>" && git push origin main
-\`\`\`
-
-### 4.3: Curated Session Summary (mem0 — machine-readable)
-
-Write ONE concise mem0 entry summarizing this session. This is what the startup hook and /prime will retrieve next session.
-
-\`\`\`
-mcp__mem0__add_memory(
-  text: "[<ProjectName> | <branch> | <date>] <2-3 sentence summary of what was accomplished, key decisions, and current state. Include commit hashes, issue IDs, and version numbers as anchors.>",
-  user_id: "lbruton",
-  agent_id: "<project-tag>",
-  metadata: {
-    "category": "session-summary",
-    "type": "session-digest",
-    "source": "wrap",
-    "date": "<YYYY-MM-DD>",
-    "project": "<ProjectName>"
-  }
-)
-\`\`\`
-
-**Quality bar for this entry:**
-- Would this be useful if it showed up in 5 search results next session? If not, make it more specific.
-- Does it contain at least one concrete anchor (commit, issue ID, version)?
-- Does it say what CHANGED, not just what was "worked on"?
-- Is it different enough from the retro lessons to avoid redundancy?
-
----
-
-## Phase 5: Final Verification
-
-Run these checks and present the results:
-
-\`\`\`bash
-# Confirm repo is clean
-git status --short
-git worktree list
-
-# Confirm we're on the right branch
-git branch --show-current
-\`\`\`
-
-### Session Recap
-
-Present a compact summary:
-
-\`\`\`
-## Session Complete
-
-**Shipped:** <list PRs merged, issues closed, versions bumped>
-**Pending:** <list open PRs, unfinished work, blockers>
-**Lessons:** <count> retro entries saved to mem0
-**Digest:** Written to DocVault/Daily Digests/<path>
-**Cleanup:** <worktrees removed, branches deleted>
-
-Next session: <1-2 sentence suggestion for what to work on>
-\`\`\`
-
----
-
-## Rules
-
-- **Sequential phases**: Do not skip ahead. Phase 2 must complete before Phase 3.
-- **Ask, don't assume**: At every decision point (commit/stash/discard, merge/wait), ask the user.
-- **No Haiku agents**: All summaries and digests are written by YOU (the current in-context model). Never dispatch a subagent for summarization — that's the old pipeline we're replacing.
-- **Idempotent**: Running /wrap twice should be safe. Check if retro/digest already ran before duplicating.
-- **mem0 writes require both user_id and agent_id**: Missing agent_id causes entity tracking issues.
-- **DocVault commits go direct to main**: No PR needed for documentation updates.
-- **Never auto-delete uncommitted work**: Always ask first.
-- **The session isn't over until Phase 5 prints the recap.**`
-            }
-        }
-    ];
-    return messages;
-}
-export const wrapPrompt = {
-    prompt,
-    handler
-};
-//# sourceMappingURL=wrap.js.map

package/dist/prompts/wrap.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"wrap.js","sourceRoot":"","sources":["../../src/prompts/wrap.ts"],"names":[],"mappings":"AAIA,MAAM,MAAM,GAAW;IACrB,IAAI,EAAE,MAAM;IACZ,KAAK,EAAE,cAAc;IACrB,WAAW,EAAE,uSAAuS;IACpT,SAAS,EAAE;QACT;YACE,IAAI,EAAE,aAAa;YACnB,WAAW,EAAE,kGAAkG;YAC/G,QAAQ,EAAE,KAAK;SAChB;KACF;CACF,CAAC;AAEF,KAAK,UAAU,OAAO,CAAC,IAAyB,EAAE,OAAoB;IACpE,MAAM,EAAE,WAAW,EAAE,GAAG,IAAI,CAAC;IAE7B,MAAM,QAAQ,GAAoB;QAChC;YACE,IAAI,EAAE,MAAM;YACZ,OAAO,EAAE;gBACP,IAAI,EAAE,MAAM;gBACZ,IAAI,EAAE;;;aAGD,OAAO,CAAC,WAAW;EAC9B,OAAO,CAAC,YAAY,CAAC,CAAC,CAAC,gBAAgB,OAAO,CAAC,YAAY,EAAE,CAAC,CAAC,CAAC,EAAE;kBAClD,WAAW,CAAC,CAAC,CAAC,KAAK,CAAC,CAAC,CAAC,IAAI;;;;;;;;;;;;;;;;;;;;;;;;;;;;;0BA6BlB,WAAW,CAAC,CAAC,CAAC,+BAA+B,CAAC,CAAC,CAAC,EAAE;;EAE1E,WAAW,CAAC,CAAC,CAAC,sEAAsE,CAAC,CAAC,CAAC;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;OAuClF;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;6DAoLsD;aACtD;SACF;KACF,CAAC;IAEF,OAAO,QAAQ,CAAC;AAClB,CAAC;AAED,MAAM,CAAC,MAAM,UAAU,GAAqB;IAC1C,MAAM;IACN,OAAO;CACR,CAAC"}