@llamaventures/cli 1.5.0 → 1.6.0

package/AGENT_BRIEFING.md

@@ -29,13 +29,69 @@ Don't:
 
 Conversation produces value → that value flows somewhere. This is not optional.
 
+### 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.
+
+```
+HTML / thesis / artifact in hand
+        │
+        ▼
+  ┌─────────────────────────────────────────────────┐
+  │ Is it about ONE specific company or deal?       │
+  │  (deal IC memo · dashboard for X · X 的 thesis  │
+  │   · founder briefing for X · X 的 2×2 …)        │
+  └──────────────┬──────────────────────────────────┘
+                 │
+        yes ────►│  → Llama Command DEAL page
+                 │    `llama html upload <dealId> --new --title "..." --file <path>`
+                 │    Renders at /deals/<id>/browse/<slug>.
+                 │    Use --doc <slug> + --file to update an existing one.
+                 │
+        no  ────►│  Is it cross-deal / institutional knowledge?
+                 │   (sector landscape · market map · framework · firm-level
+                 │    thesis · methodology · "AI infra in 2026" …)
+                 │
+                 │       yes ──►  → Llama Command WIKI entry
+                 │                  Markdown body:
+                 │                    `llama wiki save <slug> --title "..." \`
+                 │                    `  --content "..." --sources "..."`
+                 │                  Standalone HTML page (full-viewport iframe):
+                 │                    `llama wiki save <slug> --title "..." \`
+                 │                    `  --file <path>.html --sources "..."`
+                 │                  Renders at /wiki/<slug>. Sources mandatory.
+                 │
+                 │       no  ──►  Likely doesn't need to live anywhere
+                 │                durable — confirm with the user before
+                 │                inventing a destination.
+                 ▼
+  ┌─────────────────────────────────────────────────┐
+  │ Does the user EXPLICITLY say "share with        │
+  │ founder" / "public share link" / "give it to    │
+  │ <external person>" / "publish publicly"?        │
+  └──────────────┬──────────────────────────────────┘
+                 │
+        no  ────►│  → STAY on Llama Command. Don't reach for Netlify.
+                 │
+        yes ────►│  → Netlify (only this case).
+                 │    Use the `netlify-access-guard` workflow:
+                 │    server-side password + edge 401 verification.
+                 │    Verify enforcement is at the Netlify edge, not a
+                 │    browser-side JS fake.
+```
+
+**Default bias:** when in doubt, route to Llama Command. It has auth, audit, search, backlinks, and lives next to the rest of the team's context. Netlify is the escape hatch for genuinely-external surfaces — not "where pretty HTML goes."
+
+The table below details the exact CLI for each destination.
+
 | Type | Destination | How |
 |---|---|---|
 | Deal metadata (status, stage, valuation, founders, notes, etc.) | Pipeline (Postgres) | `llama deal create` / `llama deal update` |
 | Brief blocks (text / link / embed / callout) | Pipeline | `llama brief add-text` / `add-link` / `add-callout` |
 | **HTML artifact, internal — IC report, dashboard, market map, 2×2, any hand-authored page** | **Llama Command native** (Postgres + sandboxed iframe at `/deals/<id>/browse/<slug>`) | Default path when the user says "deploy to llama", "deploy to llama command", "部署到 llama command", "put this HTML on the deal page", "在 deal 里看这个". **You MUST declare intent — "new artifact" vs "update existing":**<br><br>**New artifact:** `llama html upload <dealId> --new --title "<artifact name>" --file <path>` (CLI slugifies the title; pass `--doc <slug>` to override).<br>**Update existing:** `llama html upload <dealId> --doc <slug> --file <path>` (slug must already exist — run `llama html docs <dealId>` first to see what's there).<br><br>The bare form `llama html upload <id> --file <path>` REFUSES if `main` already has content. Do NOT default to Netlify for internal pages. |
 | HTML artifact, external — founder-facing share link | Netlify | Only when the user explicitly says "share link", "give it to the founder", "publish publicly". Use the `netlify-access-guard` workflow (server-side password + edge 401 verification). |
-| Insights, decisions, framework improvements | Wiki | `llama wiki save` (with attribution — see below) |
+| Insights, decisions, framework improvements | Wiki (markdown) | `llama wiki save <slug> --content "..."` (with attribution — see below) |
+| **HTML wiki entry — standalone HTML page hosted at `/wiki/<slug>`** (sector landscape, market map, dashboard, hand-styled thesis page) | **Wiki (HTML)** | `llama wiki save <slug> --title "..." --file <path.html> --sources "..."`. Auto-detects content_type=html from extension. Public page is full-viewport sandboxed iframe takeover (no wiki chrome). Sources/status/title still required; appears in `wiki search` + backlinks. Use when the user says "deploy this HTML to wiki", "wiki 词条", "make this page a wiki entry". HTML must be self-contained (inline CSS/JS, image data URIs or external URLs) — asset bundles aren't supported on wiki yet. |
 | Large files (deck / PDF / transcript) | Drive deal folder | the deal's `folder_url` (from `llama deal show`) → upload via your filesystem / Drive tool |
 | Cross-team mentions | Inbox + email | `llama post <dealId> "@<teammate> ..."` — server fires email + UI badge to the recipient |
 
@@ -138,7 +194,17 @@ llama html reset <dealId> [--doc <slug>]                                 # soft-
 
 # Wiki (knowledge base)
 llama wiki search "<query>"
-llama wiki save <slug> --title "..." --content "..."
+llama wiki read <slug> [--lang en|zh]
+
+# Markdown entry (default):
+llama wiki save <slug> --title "..." --content "..." --sources "url1;url2"
+
+# HTML entry — standalone page at /wiki/<slug>, full-viewport sandboxed iframe:
+llama wiki save <slug> --title "..." --file path.html --sources "..." [--content-type html]
+#   .html / .htm extension auto-implies content_type=html.
+#   --content-type html (or markdown) overrides the inference.
+#   Refuses to switch content_type on an existing slug; delete + re-create
+#   if you really mean to change format.
 
 # Timeline + posts
 llama timeline <dealId>
@@ -165,7 +231,7 @@ Tools available:
 - `auth_status` — verify creds + identity (call first if anything 401s)
 - `deal_search` / `deal_show` / `deal_create` / `deal_update`
 - `brief_blocks` / `brief_add_text` / `brief_add_link` / `brief_add_callout`
-- `wiki_search` / `wiki_save`
+- `wiki_search` / `wiki_save` (accepts `content_type: 'markdown' | 'html'` — HTML entries render as full-viewport sandboxed iframe at `/wiki/<slug>`)
 - `timeline` / `post`
 - `mentions_list`
 - `pitch_start` / `pitch_send_message` / `pitch_upload_file` / `pitch_status` / `pitch_finalize` — public intake (no Llama token needed; for founders / EAs / external agents)

package/bin/llama-mcp.mjs

@@ -328,24 +328,56 @@ server.registerTool(
   "wiki_save",
   {
     description:
-      "Create or update a wiki page. Content should be markdown with attribution " +
-      "blocks (**[Name · YYYY-MM-DD · source · fact|opinion]**) for traceability. " +
-      "`sources` is a separate citation list (URLs, doc names, or meeting references) " +
-      "— at least one is required; URLs embedded inside `content` do not count.",
+      "Create or update a wiki page — Llama's CROSS-DEAL / institutional " +
+      "knowledge surface (sector landscape · market map · thesis · framework · " +
+      "methodology · anything not tied to ONE specific deal). Renders at " +
+      "/wiki/<slug>. " +
+      "**Routing — decide BEFORE calling:** " +
+      "(a) Deal-specific HTML (IC memo for X, dashboard for X) → use " +
+      "`html_upload` instead, NOT this. " +
+      "(b) Cross-deal / institutional (this tool) → /wiki/<slug>. " +
+      "(c) Founder-facing public share → Netlify only when user explicitly " +
+      "says so; Llama Command outranks Netlify for everything internal. " +
+      "By default `content` is markdown with attribution blocks " +
+      "(**[Name · YYYY-MM-DD · source · fact|opinion]**) for traceability. " +
+      "Set `content_type: 'html'` to deploy a standalone HTML page as the " +
+      "wiki entry (full-viewport sandboxed iframe takeover on /wiki/<slug>; " +
+      "the HTML itself is the page — no wiki chrome). `sources` is a " +
+      "separate citation list (URLs, doc names, or meeting references) — " +
+      "at least one required; URLs inside `content` do not count. For HTML " +
+      "asset bundles use the `llama wiki save --file ... --assets ...` CLI " +
+      "path; MCP only supports single-file HTML.",
     inputSchema: {
       slug: z.string().describe("kebab-case slug"),
       title: z.string(),
-      content: z.string().describe("markdown content"),
+      content: z
+        .string()
+        .describe(
+          "body — markdown source by default, or raw HTML when content_type='html'"
+        ),
       sources: z
         .array(z.string())
         .min(1)
         .describe(
           "citation list — URLs, doc names, or meeting references. At least one required."
         ),
+      content_type: z
+        .enum(["markdown", "html"])
+        .optional()
+        .describe(
+          "'markdown' (default) renders via the wiki markdown pipeline. " +
+            "'html' stores the body as a standalone HTML page (sandboxed iframe)."
+        ),
     },
   },
-  async ({ slug, title, content, sources }) =>
-    callApi("POST", "/api/wiki/save", { slug, title, content, sources })
+  async ({ slug, title, content, sources, content_type }) =>
+    callApi("POST", "/api/wiki/save", {
+      slug,
+      title,
+      content,
+      sources,
+      ...(content_type ? { content_type } : {}),
+    })
 );
 
 // ============================================================
@@ -707,7 +739,16 @@ server.registerTool(
   "html_upload",
   {
     description:
-      "Upload (PUT) a new HTML version for a deal's /browse page. " +
+      "Upload (PUT) a new HTML version for a SPECIFIC DEAL's /browse page " +
+      "(deal-scoped artifact: IC memo for X · dashboard for X · 2×2 for X). " +
+      "Renders at /deals/<id>/browse/<slug>. " +
+      "**Routing — pick the right destination BEFORE calling this:** " +
+      "(a) Deal-specific HTML (this tool) → /deals/<id>/browse/<slug>. " +
+      "(b) Cross-deal / institutional / thesis / sector landscape → use " +
+      "`wiki_save` with content_type='html' instead (/wiki/<slug>). " +
+      "(c) Founder-facing public share link → escape to Netlify only when " +
+      "the user explicitly says 'share with founder' / 'publish publicly'; " +
+      "Llama Command outranks Netlify for everything internal. " +
       "Creates a NEW version row — the previous version is retained " +
       "and restorable. Triggers SSE push so any open viewer auto- " +
       "refreshes. Constraints: HTML body MUST start with " +

package/bin/llama.mjs

@@ -324,10 +324,25 @@ Mentions / Inbox:
   llama mentions resolve <mentionId>                   # mark thread resolved (idempotent)
   llama mentions unread                                # just the badge count
 
+Where does this HTML / thesis / artifact go?
+  About ONE specific deal? ........ llama html upload <dealId> --new --title "..." --file <path>
+                                      (renders at /deals/<id>/browse/<slug>; see "Deal page HTML" below)
+  Cross-deal / institutional? ..... llama wiki save <slug> --title "..." --file <path>.html --sources "..."
+                                      (renders at /wiki/<slug>; see "Wiki" below)
+  Founder-facing public share? .... Netlify (with netlify-access-guard skill), only when user explicitly
+                                      says "share publicly". Llama Command outranks Netlify for everything
+                                      internal — don't reach for Netlify by default.
+
 Wiki:
   llama wiki search <query>
   llama wiki read <slug>
-  llama wiki save <slug> --title "..." --content "..." --sources "url1;url2" [--type company] [--related "A;B"]
+  Markdown entry (default):
+    llama wiki save <slug> --title "..." --content "..." --sources "url1;url2" [--type company] [--related "A;B"]
+  HTML entry — standalone HTML page at /wiki/<slug> (full-viewport sandboxed iframe):
+    llama wiki save <slug> --title "..." --file path.html --sources "..." [--content-type html]
+      (.html / .htm extension auto-implies content_type=html)
+  ➜ Use Wiki when the artifact is NOT tied to one specific deal — sector landscape, market map,
+    thesis, framework, methodology. For deal-specific HTML use "llama html upload <dealId>" instead.
 
 Memo (long-form HTML investment memo — Memo tab in the UI):
   llama memo show <dealId> [--out <path>] [--json]          # default: html → stdout (pipeable to file / browser)
@@ -336,6 +351,9 @@ Memo (long-form HTML investment memo — Memo tab in the UI):
   llama memo reset <dealId> [--all]                          # default drops manual override; --all drops every version
 
 Deal page HTML (hand-authored sandboxed pages on /deals/<id>/browse/<slug>):
+  ➜ Use this for DEAL-SPECIFIC artifacts: IC memo for X, dashboard for X, 2×2 for X.
+    For cross-deal / institutional pages (sector landscape, market map, thesis) use
+    "llama wiki save <slug> --file ..." instead — see "Wiki" above.
   Each deal can host many HTML artifacts (IC report, dashboard, market map, …).
   Each one has a stable slug. UPLOAD must declare intent — update an existing
   artifact or add a new one — to avoid silent overwrites.
@@ -1337,27 +1355,75 @@ https://command.llamaventures.vc/settings/tokens, run
   }
 
   // ----- Wiki: save (create or update) -----
+  // Two body modes:
+  //   --content "..."  inline markdown OR raw HTML (string)
+  //   --file <path>    read body from a file; if .html/.htm,
+  //                    content_type auto-detects to 'html'
+  // --content-type <markdown|html> overrides auto-detect.
+  // Refuses content_type mismatch on existing entries (server-side check;
+  // CLI surfaces the server error verbatim).
   if (area === "wiki" && action === "save") {
     const { flags, positional } = parseFlags(rest);
     const slug = positional[0];
     const title = flags.title;
-    const content = flags.content;
+    const inlineContent = flags.content;
+    const filePath = flags.file;
     const sourcesRaw = flags.sources;
-    if (!slug || !title || !content || !sourcesRaw) {
+    if (!slug || !title || !sourcesRaw || (!inlineContent && !filePath)) {
       throw new Error(
-        `Usage: llama wiki save <slug> --title "..." --content "..." --sources "url1;url2" [--type company] [--related "A;B"] [--lang en|zh]`
+        `Usage:
+  llama wiki save <slug> --title "..." --content "..." --sources "url1;url2" [--type company] [--related "A;B"] [--lang en|zh] [--content-type markdown|html]
+or
+  llama wiki save <slug> --title "..." --file path/to/article.{md,html} --sources "url1;url2" [--type company] [--related "A;B"] [--lang en|zh] [--content-type markdown|html]
+
+Pass either --content (inline) or --file (read from disk). With --file, content_type auto-detects from extension (.html/.htm → html, else markdown). Use --content-type to override.
+
+Routing — is this the right command?
+  ✓ Cross-deal / institutional knowledge (sector landscape, market map, thesis, framework, methodology)
+      → YES, you're in the right place.
+  ✗ Deal-specific HTML (IC memo for X, dashboard for X, 2×2 for one company)
+      → use \`llama html upload <dealId> --new --title "..." --file <path>\` instead.
+  ✗ Founder-facing public share link
+      → escape to Netlify only when the user explicitly says "share publicly" / "give it to the founder";
+        Llama Command outranks Netlify for everything internal.`
       );
     }
+    if (inlineContent && filePath) {
+      throw new Error("Pass either --content OR --file, not both.");
+    }
+    // Read body — either inline or from file.
+    let body;
+    let inferredType = "markdown";
+    if (filePath) {
+      const { readFileSync } = await import("fs");
+      body = readFileSync(String(filePath), "utf-8");
+      const lower = String(filePath).toLowerCase();
+      if (lower.endsWith(".html") || lower.endsWith(".htm")) {
+        inferredType = "html";
+      }
+    } else {
+      body = String(inlineContent);
+    }
+    // Determine content_type: explicit flag wins over file-extension inference.
+    let contentType = inferredType;
+    if (flags["content-type"]) {
+      const v = String(flags["content-type"]).toLowerCase();
+      if (v !== "markdown" && v !== "html") {
+        throw new Error(`--content-type must be 'markdown' or 'html', got "${v}"`);
+      }
+      contentType = v;
+    }
     const splitCsv = (v) => String(v).split(/[;|]/).map((s) => s.trim()).filter(Boolean);
     const payload = {
       slug,
       title: String(title),
-      content: String(content),
+      content: body,
       sources: splitCsv(sourcesRaw),
       type: flags.type ? String(flags.type) : undefined,
       related: flags.related ? splitCsv(flags.related) : undefined,
       lang: flags.lang === "zh" ? "zh" : "en",
       status: flags.status ? String(flags.status) : undefined,
+      content_type: contentType,
     };
     print(await request("POST", "/api/wiki/save", payload));
     return;
@@ -2052,7 +2118,18 @@ https://command.llamaventures.vc/settings/tokens, run
             "\n" +
             "Default (no --doc, no --new) targets slug 'main' but REFUSES if 'main'\n" +
             "already has content — pass --doc main to update it explicitly, or\n" +
-            "--new --title \"...\" to add a NEW artifact alongside.",
+            "--new --title \"...\" to add a NEW artifact alongside.\n" +
+            "\n" +
+            "Routing — is this the right command?\n" +
+            "  ✓ DEAL-specific HTML (IC memo for X, dashboard for X, 2×2 for X)\n" +
+            "      → YES, you're in the right place. Pass <dealId> + --new / --doc.\n" +
+            "  ✗ Cross-deal / institutional knowledge (sector landscape, market map,\n" +
+            "    thesis, framework, methodology, anything not tied to one company)\n" +
+            "      → use `llama wiki save <slug> --title \"...\" --file <path>.html --sources \"...\"`\n" +
+            "        instead (renders at /wiki/<slug>).\n" +
+            "  ✗ Founder-facing public share link\n" +
+            "      → escape to Netlify only when the user explicitly says \"share publicly\";\n" +
+            "        Llama Command outranks Netlify for everything internal.",
         );
       }
       const knownFlags = [

package/package.json

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