@llamaventures/cli 1.7.0 → 1.8.0

package/AGENT_BRIEFING.md

@@ -29,6 +29,19 @@ Don't:
 
 Conversation produces value → that value flows somewhere. This is not optional.
 
+### When someone gives you info about a deal (the most common case)
+
+A teammate says "I just met them and heard…" or pastes a chunk of notes. Your job: get it into the right deal, in the right layer, and confirm it's right. Three steps:
+
+1. **Find the deal** — `llama deal search "<name>"` (Pipeline First). New name → offer to create it.
+2. **Split what they gave you into two kinds** — this is the whole data model:
+   - **Verifiable claims → facts.** `llama deal fact add <dealId> --category <cat> --claim "…" --source "<where it came from>"`. A claim someone *relayed* ("their ARR is $3M", "raised from a16z") is a fact at **unverified** trust — it's hearsay until checked. Pass `--attested` ONLY if you actually verified it against a source yourself.
+   - **Their judgment / impression → a note.** `llama post <dealId> "…"`. "Founder seemed evasive", "I'd lean pass", "worth a second meeting" — opinion, not fact. Attributed, never "verified".
+   - A pasted blob → pull the verifiable claims out as facts, capture their take as a note.
+3. **Confirm accuracy.** After filing, tell them in plain language what you recorded and where, and ask if it's right. Facts you add stay **unverified** until a human confirms them (then they rise to human-vouched) — the confirmation IS the trust step. Never silently mark something verified.
+
+Why split it: facts and opinions live in different layers so the deal keeps one clean **source of truth** (facts, sourced + trust-rated) separate from people's **takes** (notes). The four layers — facts / notes / brief (AI's synthesis) / timeline — are documented in Llama Command's `docs/SCHEMA.md`.
+
 ### Where does this HTML / thesis / artifact go? (decision tree)
 
 When the user hands you an HTML page, thesis write-up, market map, dashboard, IC memo, sector landscape — anything that isn't a one-off note — pick the destination in this order. **Llama Command native (the workbench) outranks Netlify for everything internal.** Only escape to Netlify when the page is truly going to a public / founder-facing URL.

package/bin/llama-mcp.mjs

@@ -303,6 +303,22 @@ server.registerTool(
     callApi("GET", `/api/deals/${encodeURIComponent(dealId)}/blocks`)
 );
 
+server.registerTool(
+  "deal_feed",
+  {
+    description:
+      "The unified, time-sorted stream of everything a HUMAN has added to a deal — " +
+      "facts + notes/discussion + legacy posts, merged at query time, newest first. " +
+      "Excludes AI-generated content. Each item: kind (fact|note), ts, who, text, " +
+      "and for facts: source + trust rung + category.",
+    inputSchema: {
+      dealId: z.string(),
+    },
+  },
+  async ({ dealId }) =>
+    callApi("GET", `/api/deals/${encodeURIComponent(dealId)}/feed`)
+);
+
 server.registerTool(
   "brief_add_text",
   {

package/bin/llama.mjs

@@ -198,8 +198,7 @@ async function searchDeals(q, flags) {
   return result;
 }
 
-function usage() {
-  console.log(`Llama Command CLI
+const HELP_FULL = `Llama Command CLI
 
 Agent onboarding (run once on first install):
   llama agent-onboard                  # print AGENT_BRIEFING.md — the workflow contract for AI agents
@@ -225,6 +224,7 @@ Manually-set \`llc_\` tokens are used as a fallback.
 Deals:
   llama deal create "Company" --source <name> --description "..." --website https://...
   llama deal show <dealId>
+  llama deal feed <dealId>                                     # everything humans added (facts + notes), newest first
   llama deal update <dealId> <field> <value>
       Writable fields: status, theirStage, stage, notes, dealOwner, source,
       description, website, location, founders, proposedAmount, roundSize,
@@ -410,7 +410,86 @@ Token discovery (in order):
 Env:
   LLAMA_TOKEN    token override
   LLAMA_API_URL  API base URL override
-`);
+`;
+
+// ── Progressive help (Constitution §1) ──
+// Default `llama` / `llama --help` prints a SHORT root: the command groups +
+// a few starters. Drill into one group with `llama help <area>` (or
+// `llama <area> --help`); `llama help all` prints the full reference above.
+const HELP_ROOT = `Llama Command CLI — the \`llama\` command for the Llama Ventures workbench.
+
+Common:
+  llama deal search "<name>"        find a deal in the pipeline
+  llama deal show <dealId>          full deal record
+  llama deal feed <dealId>          everything humans added, newest first
+  llama post <dealId> "..."         add a note to a deal
+  llama agent-onboard               print the AI-agent workflow contract
+
+Command groups — run \`llama help <group>\` for that group's commands:
+  deal        create · show · feed · update · search · collaborators · links · delete
+  brief       brief blocks: list · add · edit · history · refresh
+  facts       deal facts + skill corrections (the sourced, trust-rated layer)
+  timeline    timeline · posts · mentions
+  wiki        cross-deal knowledge entries (markdown or HTML)
+  memo        long-form HTML investment memo
+  html        deal-specific HTML artifacts (/deals/<id>/browse/<slug>)
+  pitch       external founder intake (no token needed)
+  ownership   claim · nominate · approvals
+  admin       audit events (system admin only)
+  auth        setup · tokens · auth status
+
+  llama help all     the full command reference (everything at once)
+
+Auth: if you've run \`gcloud auth login\` with your @llamaventures.vc account,
+the CLI auto-detects it — no token needed (\`llc_\` tokens are a fallback).`;
+
+// Area → which top-level sections of HELP_FULL belong to it.
+const HELP_AREA_MATCH = {
+  deal: [/^Deals/, /^Collaborators/, /^Soft-delete/, /^Deal links/, /^Deal soft-delete/],
+  brief: [/^Brief blocks/, /^Brief \/ persona/],
+  facts: [/^Deal facts/, /^Skill corrections/],
+  timeline: [/^Timeline/, /^Mentions/],
+  wiki: [/^Wiki/, /^Where does this HTML/],
+  memo: [/^Memo/],
+  html: [/^Deal page HTML/],
+  pitch: [/^External pitch/],
+  ownership: [/^Ownership/, /^Approvals/],
+  admin: [/^Admin/],
+  auth: [/^Setup/, /^Zero-config/, /^Token discovery/, /^Env/],
+};
+
+// Slice HELP_FULL into sections: a top-level (non-indented) header line plus
+// the indented/blank lines that follow it, until the next header.
+function helpSections() {
+  const out = [];
+  let cur = null;
+  for (const line of HELP_FULL.split("\n")) {
+    if (/^[A-Za-z]/.test(line)) {
+      cur = { head: line, lines: [line] };
+      out.push(cur);
+    } else if (cur) {
+      cur.lines.push(line);
+    }
+  }
+  return out;
+}
+
+function usage(area) {
+  if (area === "all") {
+    console.log(HELP_FULL);
+    return;
+  }
+  const matchers = area && HELP_AREA_MATCH[area];
+  if (matchers) {
+    const blocks = helpSections()
+      .filter((s) => matchers.some((re) => re.test(s.head)))
+      .map((s) => s.lines.join("\n").replace(/\s+$/, ""));
+    if (blocks.length) {
+      console.log(blocks.join("\n\n"));
+      return;
+    }
+  }
+  console.log(HELP_ROOT);
 }
 
 // ============================================================
@@ -688,7 +767,12 @@ async function main() {
     return;
   }
   if (!area || area === "help" || area === "--help" || area === "-h") {
-    usage();
+    usage(area === "help" ? action : undefined);
+    return;
+  }
+  // `llama <area> --help` / `-h` → just that group's commands
+  if (action === "--help" || action === "-h") {
+    usage(area);
     return;
   }
 
@@ -978,6 +1062,13 @@ https://command.llamaventures.vc/settings/tokens, run
     return;
   }
 
+  if (area === "deal" && action === "feed") {
+    const dealId = rest[0];
+    if (!dealId) throw new Error("Usage: llama deal feed <dealId>");
+    print(await request("GET", `/api/deals/${encodeURIComponent(dealId)}/feed`));
+    return;
+  }
+
   if (area === "deal" && action === "update") {
     const [dealId, field, ...valueParts] = rest;
     const value = valueParts.join(" ");

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@llamaventures/cli",
-  "version": "1.7.0",
+  "version": "1.8.0",
   "description": "CLI + MCP server for the Llama Ventures investment workbench (command.llamaventures.vc).",
   "type": "module",
   "bin": {