sproutkit-code 1.5.0 → 1.5.2

package/dist/commands/sproutkit-leads.md

@@ -3,14 +3,14 @@ description: Show current leads and their stage
 argument-hint: "[filter] e.g. site_built, or Leeds"
 allowed-tools: Bash(sproutkit *)
 ---
-Leads:
-
-!`sproutkit list --compact 2>/dev/null`
+!`sproutkit list --limit 100 2>/dev/null`
 
 The operator asked to see: $ARGUMENTS
 
-Every lead is listed above (one JSON object per line, nothing truncated).
+The table above is the CLI's own formatted output — aligned columns, live links,
+a delivered marker and a stage tally.
 
-Show the matching leads as a compact table — id, name, town, stage, and whether
-they have a site / booking page. If they didn't narrow it down, group by stage.
-Read-only: don't build, contact, or change anything.
+Print it back VERBATIM inside a code block. Do NOT rebuild it as a markdown
+table, do not reformat or re-order it, do not truncate it, do not add commentary.
+If they asked for a subset (a stage or a town), show only those rows but keep the
+formatting exactly as-is, including the header.

package/dist/index.js

@@ -94446,7 +94446,10 @@ Interested?`;
           const status = input.status;
           const city = input.city;
           const limit = Math.min(Number(input.limit ?? 25), 100);
-          let sql = "SELECT id, name, status, type, city, phone, site_url, website, lead_kind, booking_status, booking_platform, booking_url FROM leads";
+          let sql = `SELECT id, name, status, type, city, phone, email, site_url, website, lead_kind,
+                booking_status, booking_platform, booking_url, admin_url, custom_domain,
+                handed_over_at
+         FROM leads`;
           const conds = [];
           const params = [];
           if (status) {
@@ -95833,7 +95836,7 @@ var require_package2 = __commonJS({
   "package.json"(exports2, module2) {
     module2.exports = {
       name: "sproutkit-code",
-      version: "1.5.0",
+      version: "1.5.2",
       description: "Sproutkit in your terminal \u2014 find leads, build sites, run outreach, all via chat.",
       bin: {
         sproutkit: "./dist/index.js"
@@ -96963,10 +96966,64 @@ async function cmdList(argv) {
     say(c.dim('  No leads yet. Try: sproutkit find "barbers in <area>"'));
     return;
   }
+  renderLeadTable(rows);
+}
+var STAGE_LABEL = {
+  discovered: "New",
+  site_built: "Built",
+  contacted: "Contacted",
+  replied: "Replied",
+  won: "Won",
+  dead: "Dead"
+};
+function cell(text, width) {
+  const t = text ?? "";
+  if (t.length === width) return t;
+  if (t.length < width) return t + " ".repeat(width - t.length);
+  return width <= 1 ? t.slice(0, width) : t.slice(0, width - 1) + "\u2026";
+}
+function renderLeadTable(rows) {
+  const term = process.stdout.columns && process.stdout.columns > 40 ? process.stdout.columns : 100;
+  const idW = Math.max(3, ...rows.map((r) => String(r.id).length + 1));
+  const stageW = Math.max(5, ...rows.map((r) => (STAGE_LABEL[r.status] ?? r.status).length));
+  const placeW = Math.min(14, Math.max(5, ...rows.map((r) => (r.city || "").length)));
+  const fixed = 2 + idW + 2 + stageW + 2 + placeW + 2;
+  const nameW = Math.max(16, Math.min(34, term - fixed - 24));
   say();
+  say(
+    "  " + c.dim(
+      cell("ID", idW) + "  " + cell("BUSINESS", nameW) + "  " + cell("STAGE", stageW) + "  " + cell("AREA", placeW) + "  WHAT THEY HAVE"
+    )
+  );
+  say("  " + c.dim("\u2500".repeat(Math.min(term - 4, idW + nameW + stageW + placeW + 23))));
   for (const r of rows) {
-    const site = r.site_url ? c.dim(`  ${r.site_url}`) : "";
-    say(`  ${c.greenBold("#" + r.id)} ${c.bold(r.name)} ${c.dim(`\xB7 ${r.status} \xB7 ${r.type}, ${r.city}`)}${site}`);
+    const stage = STAGE_LABEL[r.status] ?? r.status;
+    const stageColoured = r.status === "won" ? c.greenBold(cell(stage, stageW)) : r.status === "site_built" || r.status === "replied" ? c.green(cell(stage, stageW)) : r.status === "dead" ? c.dim(cell(stage, stageW)) : c.dim(cell(stage, stageW));
+    const short = (u) => u.replace(/^https?:\/\//, "").replace(/\/$/, "");
+    const assets = [];
+    if (r.custom_domain) assets.push(c.cyan(r.custom_domain));
+    else if (r.site_url) assets.push(short(r.site_url));
+    if (r.booking_url) assets.push(r.site_url ? c.dim("+ booking") : short(r.booking_url));
+    if (r.admin_url) assets.push(c.dim("+ admin"));
+    if (!r.site_url && !r.booking_url && r.website) {
+      assets.push(c.dim("own site: " + short(r.website)));
+    }
+    if (assets.length === 0) assets.push(c.dim("\u2014"));
+    if (r.handed_over_at) assets.push(c.greenBold("\u2713 delivered"));
+    say(
+      "  " + c.dim(cell("#" + r.id, idW)) + "  " + c.bold(cell(r.name, nameW)) + "  " + stageColoured + "  " + c.dim(cell(r.city || "\u2014", placeW)) + "  " + assets.join(c.dim(" \xB7 "))
+    );
+  }
+  const counts = rows.reduce((acc, r) => {
+    acc[r.status] = (acc[r.status] ?? 0) + 1;
+    return acc;
+  }, {});
+  const order = ["discovered", "site_built", "contacted", "replied", "won", "dead"];
+  const summary = order.filter((k) => counts[k]).map((k) => `${counts[k]} ${(STAGE_LABEL[k] ?? k).toLowerCase()}`).join(c.dim(" \xB7 "));
+  say();
+  say("  " + c.dim(`${rows.length} lead${rows.length === 1 ? "" : "s"} shown \u2014 `) + summary);
+  if (rows.length >= 25) {
+    say(c.dim("  More may exist \u2014 use --limit 100, or --status/--city to narrow."));
   }
   say();
 }
@@ -97506,18 +97563,26 @@ var TASK_SYSTEM_PROMPT = `You operate the "sproutkit" CLI on the user's behalf.
 HOW TO ACT \u2014 this is strict:
 - Fulfil each request by running the matching sproutkit command(s) via Bash. Nothing else.
 - Do NOT read, list, or explore the repo. Do NOT narrate a plan, think out loud, or look for a skill. No preamble, no "let me\u2026". Either ask a crisp question (below) or run the command.
-- Always pass --json and parse it. Get lead ids from \`sproutkit list --json\` \u2014 never guess an id.
+- Pass --json for commands you need to READ data from (to get ids, urls, credentials).
+- EXCEPTION \u2014 \`sproutkit list\`: run it WITHOUT --json and print its output verbatim. It
+  already prints a formatted table with links and a stage tally. Never re-render it yourself,
+  never reformat it, never summarise it, never truncate it. Use --json for list ONLY when you
+  need a field to feed into another command, and in that case don't display the JSON.
 
 OUTPUT FORMAT \u2014 terse, scannable, NO editorialising:
 - Never write rambling sentences or commentary about the results ("well short of 20, so the source is returning few matches" \u2014 DON'T). Just present the data.
 - For find: one line "Found N (M new)", then one line per NEW lead: "#<id> <name> \xB7 <type>".
-- For list: one line per lead "#<id> <name> \xB7 <type> \xB7 <city> \xB7 <status>" (cap at ~15, then "\u2026and K more").
+- For list: print the command's own table output EXACTLY as it comes back. It is already
+  formatted and aligned. Do not rebuild it as your own list, and do not cut it short.
 - For build/book: one line "\u2713 <name> \u2014 <url>".
-- Use a plain "#<id> <name>" style. No tables, no fluff, no "Here's what I found". If a result count is low, state the number plainly \u2014 do NOT speculate about why unless asked.
+- For your OWN summaries use a plain "#<id> <name>" style \u2014 no fluff, no "Here's what I found".
+  (This does not apply to \`sproutkit list\`, whose own table you pass straight through.)
+  If a result count is low, state the number plainly \u2014 do NOT speculate about why unless asked.
 
 GATHER REQUIRED CHOICES FIRST \u2014 ask, don't guess, don't chatter:
 When a request is missing information the command needs, ask a SHORT, STRUCTURED question that lists the options \u2014 then wait. Present choices as a tight numbered/bulleted list, no rambling. Specifically:
-- Which business/lead is not clear \u2192 run \`sproutkit list --json\`, then ask: "Which business?" and list a few (id + name).
+- Which business/lead is not clear \u2192 run \`sproutkit list --json\` to read ids (don't print the
+  JSON), then ask: "Which business?" and name a few (id + name).
 - "make/build a booking site" \u2192 you MUST establish the booking TYPE before running. Ask: "What type of booking site?" and present exactly:
     1. Slot-based \u2014 timed appointments (barbers, salons, clinics)
     2. Reservation \u2014 table / party booking (restaurants, cafes)
@@ -97528,7 +97593,8 @@ When a request is missing information the command needs, ask a SHORT, STRUCTURED
 COMMANDS:
 - sproutkit find "<area>" --categories "<type>,<type>" --json   \u2014 find website-less leads
 - sproutkit find "<area>" --categories "\u2026" --booking --json     \u2014 find businesses that HAVE a site but take bookings via WhatsApp/phone only (booking-page prospects)
-- sproutkit list --json [--status <s>] [--city <c>]             \u2014 list leads (get ids)
+- sproutkit list [--status <s>] [--city <c>] [--limit 100]      \u2014 formatted table; SHOW IT VERBATIM
+- sproutkit list --json                                         \u2014 same data as JSON, for reading ids only
 - sproutkit build <id> --json [--instructions "..."] [--cms] [--multipage]  \u2014 build a demo site (--multipage = real Home/Services/About/Contact pages, not one scroll)
 - sproutkit build-all --json [--ids 3,5] [--concurrency 3]      \u2014 build many at once
 - sproutkit regenerate <id> --instructions "..." --json         \u2014 rebuild an existing site with changes

package/dist/skill/SKILL.md

@@ -17,7 +17,7 @@ do not need any API key yourself — just run the commands.
 
 ## Commands
 
-All commands accept `--json` for structured output. **Always pass `--json`** so
+All commands accept `--json` for structured output. **Pass `--json`** so
 you can parse results reliably, then summarise them for the user in prose.
 
 - **Find leads** — `sproutkit find "<area>" --categories "<type>,<type>" --json`
@@ -27,7 +27,12 @@ you can parse results reliably, then summarise them for the user in prose.
   - Example: `sproutkit find "Shoreditch, London" --categories "barber shop,cafe" --json`
   - Optional: `--max 25`, `--radius 3000`.
 
-- **List leads** — `sproutkit list --json` (optional `--status site_built`, `--city London`, `--limit 25`)
+- **List leads** — `sproutkit list` (optional `--status site_built`, `--city London`, `--limit 100`)
+  - Run it WITHOUT `--json` and show the output VERBATIM. It already prints an aligned
+    table with the live site/booking links, a delivered marker and a stage tally.
+    Do not re-render, reformat, summarise or truncate it — that throws the formatting away.
+  - Use `sproutkit list --json` only when you need a field to feed another command; in that
+    case read it and don't print it.
   - Returns id, name, status, type, city, phone, site_url. Use this to get lead
     **ids** before building or to report the pipeline.
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "sproutkit-code",
-  "version": "1.5.0",
+  "version": "1.5.2",
   "description": "Sproutkit in your terminal — find leads, build sites, run outreach, all via chat.",
   "bin": {
     "sproutkit": "./dist/index.js"