@llamaventures/cli 1.9.0 → 1.9.1

package/AGENT_BRIEFING.md

@@ -104,6 +104,18 @@ HTML / thesis / artifact in hand
 
 **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."
 
+### Adding content to ONE deal — fact vs post vs brief (the #1 mis-route)
+
+These three look similar but land in different surfaces. Don't infer from the command name — pick by intent:
+
+| You want to… | Command | Lands in |
+|---|---|---|
+| Record a **sourced, verifiable fact** | `llama deal fact add <dealId> --category <cat> --claim "…" --source <url>` | Facts → deal **Feed** (FACT card) + citable in the **Memo** |
+| Leave a **comment / opinion / question / reaction** for the team | `llama post <dealId> "…"` (`@name` to notify) | Posts → deal **Feed** (POST card); `@mention` fires email + UI badge |
+| Write **narrative that belongs in the IC memo** | `llama brief add-text <dealId> --heading "…" --body "…"` | Brief blocks → **Memo tab only — NOT in the Feed** |
+
+⚠️ The trap: `brief add-text` is **not** visible in the Activity Feed. If the team should see it in the feed, use `llama post`. If it's a claim that needs a source + verification, use `llama deal fact add`. (It's `deal fact add`, not `fact-add`.)
+
 The table below details the exact CLI for each destination.
 
 | Type | Destination | How |
@@ -113,7 +125,7 @@ The table below details the exact CLI for each destination.
 | **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 (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. |
+| **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. **Native comments + working in-page (#) anchor links are injected automatically** — readers discuss inline and the table of contents scrolls; you don't wire anything up (pages that already embed the comment widget are left as-is). |
 | 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 |
 
@@ -302,7 +314,7 @@ the intake agent; relay the conversation, then surface the verdict.
 - This file: `AGENT_BRIEFING.md` in the `@llamaventures/cli` npm package
 - Re-printable any time: `llama agent-onboard`
 - MCP prompt: `agent_briefing` from the `llama-mcp` server
-- Public source: <https://github.com/SoujiOkita98/llama-cli/blob/main/AGENT_BRIEFING.md>
+- Public source: <https://github.com/Llama-Ventures/llama-cli/blob/main/AGENT_BRIEFING.md>
 
 You're now a Llama Ventures teammate (or an external agent helping a
 founder pitch us). Welcome.

package/README.md

@@ -13,7 +13,7 @@
 
 <p align="center">
   <a href="https://www.npmjs.com/package/@llamaventures/cli"><img alt="npm" src="https://img.shields.io/npm/v/@llamaventures/cli?label=npm&color=cb3837&logo=npm&logoColor=white"></a>
-  <a href="https://github.com/SoujiOkita98/llama-cli/actions/workflows/ci.yml"><img alt="CI" src="https://github.com/SoujiOkita98/llama-cli/actions/workflows/ci.yml/badge.svg"></a>
+  <a href="https://github.com/Llama-Ventures/llama-cli/actions/workflows/ci.yml"><img alt="CI" src="https://github.com/Llama-Ventures/llama-cli/actions/workflows/ci.yml/badge.svg"></a>
   <a href="https://docs.npmjs.com/trusted-publishers"><img alt="Provenance" src="https://img.shields.io/badge/provenance-signed-2e8b57?logo=npm"></a>
   <a href="https://nodejs.org/"><img alt="Node" src="https://img.shields.io/node/v/@llamaventures/cli?color=339933&logo=nodedotjs&logoColor=white"></a>
   <a href="https://modelcontextprotocol.io"><img alt="MCP 2024-11-05" src="https://img.shields.io/badge/MCP-2024--11--05-7d3aed"></a>

package/README.zh-CN.md

@@ -13,7 +13,7 @@
 
 <p align="center">
   <a href="https://www.npmjs.com/package/@llamaventures/cli"><img alt="npm" src="https://img.shields.io/npm/v/@llamaventures/cli?label=npm&color=cb3837&logo=npm&logoColor=white"></a>
-  <a href="https://github.com/SoujiOkita98/llama-cli/actions/workflows/ci.yml"><img alt="CI" src="https://github.com/SoujiOkita98/llama-cli/actions/workflows/ci.yml/badge.svg"></a>
+  <a href="https://github.com/Llama-Ventures/llama-cli/actions/workflows/ci.yml"><img alt="CI" src="https://github.com/Llama-Ventures/llama-cli/actions/workflows/ci.yml/badge.svg"></a>
   <a href="https://docs.npmjs.com/trusted-publishers"><img alt="Provenance" src="https://img.shields.io/badge/provenance-signed-2e8b57?logo=npm"></a>
   <a href="https://nodejs.org/"><img alt="Node" src="https://img.shields.io/node/v/@llamaventures/cli?color=339933&logo=nodedotjs&logoColor=white"></a>
   <a href="https://modelcontextprotocol.io"><img alt="MCP 2024-11-05" src="https://img.shields.io/badge/MCP-2024--11--05-7d3aed"></a>

package/bin/llama.mjs

@@ -349,6 +349,7 @@ Wiki:
   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)
+      Native comments + working in-page (#) links are added automatically — just upload self-contained 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.
   Delete / restore (soft — reversible):
@@ -784,6 +785,14 @@ async function main() {
     usage(area);
     return;
   }
+  // `llama <area> <action> --help` (e.g. `brief add-text --help`). Without this
+  // short-circuit, "--help" falls through to the action handler, where rest[0]
+  // can be read as a positional (e.g. dealId="--help") and trigger a REAL write.
+  // Catch --help/-h anywhere in the sub-command args and print group help first.
+  if (rest.includes("--help") || rest.includes("-h")) {
+    usage(area);
+    return;
+  }
 
   // `llama agent-onboard` — print the bundled AGENT_BRIEFING.md so an AI
   // agent reads it once and internalises the Llama Ventures workflow

package/lib/client.mjs

@@ -38,7 +38,7 @@ export function readBriefing() {
       "AGENT_BRIEFING.md not found at " +
       briefingPath +
       ". This shouldn't happen in a published @llamaventures/cli install — " +
-      "report at https://github.com/SoujiOkita98/llama-cli/issues."
+      "report at https://github.com/Llama-Ventures/llama-cli/issues."
     );
   }
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@llamaventures/cli",
-  "version": "1.9.0",
+  "version": "1.9.1",
   "description": "CLI + MCP server for the Llama Ventures investment workbench (command.llamaventures.vc).",
   "type": "module",
   "bin": {
@@ -18,13 +18,13 @@
     "node": ">=18"
   },
   "license": "MIT",
-  "homepage": "https://github.com/SoujiOkita98/llama-cli#readme",
+  "homepage": "https://github.com/Llama-Ventures/llama-cli#readme",
   "repository": {
     "type": "git",
-    "url": "git+https://github.com/SoujiOkita98/llama-cli.git"
+    "url": "git+https://github.com/Llama-Ventures/llama-cli.git"
   },
   "bugs": {
-    "url": "https://github.com/SoujiOkita98/llama-cli/issues"
+    "url": "https://github.com/Llama-Ventures/llama-cli/issues"
   },
   "keywords": [
     "llama-ventures",
@@ -39,7 +39,7 @@
     "anthropic"
   ],
   "author": "Llama Ventures, Inc.",
-  "funding": "https://github.com/SoujiOkita98/llama-cli",
+  "funding": "https://github.com/Llama-Ventures/llama-cli",
   "publishConfig": {
     "access": "public"
   },