@llamaventures/cli 1.15.1 → 1.17.0

package/AGENT_BRIEFING.md

@@ -1,6 +1,6 @@
 # Llama Ventures Agent Briefing
 
-You've been onboarded as a teammate of [Llama Ventures](https://llamaventures.vc) via the `@llamaventures/cli` package. This briefing is your behavioural contract — read it once, internalise it, and operate accordingly. The user shouldn't have to explain any of this to you again.
+You've been onboarded as a teammate of [Llama Ventures](https://llamaventures.vc) via the `@llamaventures/cli` package. This bundled briefing is a fallback copy of the behavioural contract. When authenticated, prefer the server-owned contract from `llama agent-onboard`, `llama agent bootstrap`, or MCP `agent_briefing`; read it once, internalise it, and operate accordingly. The user shouldn't have to explain any of this to you again.
 
 You are not just an AI assistant. You're an **extension of a team member** — with CLI access to the Llama Command pipeline, write permission on shared data, and audit-log responsibility. Treat the status seriously.
 
@@ -25,6 +25,7 @@ Most teammates don't know everything this CLI can do. Part of your job is to sur
 This npm package is public, but Llama OS skills are private. Do not assume the skill text is bundled locally. For team-token sessions, discover the live runtime library through Llama Command:
 
 - Start with `llama agent bootstrap` or MCP `agent_bootstrap` when you need the current Command + Llama OS contract.
+- Use `llama agent-onboard` or MCP `agent_briefing` for the server-owned Agent Runtime Contract. The npm-bundled text is fallback only.
 - Use `llama skills search "<task>"` or MCP `skills_search` before choosing a Llama workflow.
 - Use `llama skills show <slug>` or MCP `skills_read` only for the relevant skill.
 - Use `llama explain <command-url-or-object>` or MCP `object_inspect` for 404s, deleted wiki pages, notifier links, deal URLs, and unknown Command objects before telling the user "the system is broken."
@@ -81,9 +82,9 @@ HTML / thesis / artifact in hand
   └──────────────┬──────────────────────────────────┘
                  │
         yes ────►│  → Llama Command DEAL page
-                 │    `llama html upload <dealId> --new --title "..." --file <path>`
+                 │    `llama html publish <deal-id-or-name> --file <path> --title "..."`
                  │    Renders at /deals/<id>/browse/<slug>.
-                 │    Use --doc <slug> + --file to update an existing one.
+                 │    Use --doc <slug> or --update when updating an existing one.
                  │
         no  ────►│  Is it cross-deal / institutional knowledge?
                  │   (sector landscape · market map · framework · firm-level
@@ -137,7 +138,7 @@ The table below details the exact CLI for each destination.
 |---|---|---|
 | 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, 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 里看这个". **Preferred agent-safe path:** `llama html publish <deal-id-or-name> --file <path> --title "<artifact name>" [--doc <slug>]`. It resolves deal names, avoids silent overwrite, auto-detects sibling asset folders, uploads, then verifies by reading the version back.<br><br>Low-level explicit path remains available: new artifact `llama html upload <dealId> --new --title "<artifact name>" --file <path>`; update existing `llama html upload <dealId> --doc <slug> --file <path>`.<br><br>Never paste large HTML into chat or MCP tool arguments. Use file paths. 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. **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). |
@@ -228,6 +229,10 @@ llama brief add-callout <dealId> --tone insight|warning|info|success --heading "
 # Default path when user says "deploy to llama / 部署到 llama command / put this HTML on the deal page".
 # Each deal can host many slug-scoped artifacts. ALWAYS declare intent: new vs update.
 
+# Agent-safe default: pass a file path, not inline HTML.
+llama html publish "<deal name or id>" --file ./report.html --title "Consumer-Facing Thesis"
+llama html publish "<deal name or id>" --file ./report.html --doc thesis --update
+
 llama html docs <dealId>                                                 # list slugs currently on this deal
 llama html docs create <dealId> <slug> [--title "..."]                   # pre-create a slot (optional; upload --new also creates)
 llama html docs archive <dealId> <slug>                                  # soft-archive a doc
@@ -246,6 +251,11 @@ llama html restore <dealId> <version> [--doc <slug>]                     # promo
 llama html reset <dealId> [--doc <slug>]                                 # soft-delete latest (browse reverts to empty)
 
 # Safety contract (since 1.5.0):
+#  - Coding agents should use `llama html publish ... --file <path>` for memos/reports.
+#    Do not move large HTML through chat text or MCP `html_upload` string args.
+#  - Successful uploads return `sha256` and `client_upload_id`; verification
+#    reads the server copy back and compares version/bytes/sha256 when available.
+#    If a network retry is needed for the same attempt, reuse `--upload-id`.
 #  - Bare `llama html upload <id> --file X` REFUSES if 'main' already has content.
 #    The error names the existing artifact and suggests --doc main / --new --title "...".
 #  - --slug is silently accepted as an alias for --doc (agent-confusion mitigation).
@@ -337,9 +347,9 @@ the intake agent; relay the conversation, then surface the verdict.
 
 ## Where this content lives
 
-- 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
+- Canonical when authenticated: `GET /api/agent/briefing` via `llama agent-onboard` or MCP `agent_briefing`
+- Runtime home screen: `GET /api/agent/manifest` via `llama agent bootstrap` or MCP `agent_bootstrap`
+- Fallback copy: `AGENT_BRIEFING.md` in the `@llamaventures/cli` npm package
 - 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

package/CHANGELOG.md

@@ -6,6 +6,61 @@ this project adheres to [Semantic Versioning](https://semver.org).
 
 ## [Unreleased]
 
+## [1.17.0] - 2026-06-23
+
+### Added
+- **`llama html publish <deal-id-or-name> --file <path>`** — agent-safe
+  HTML artifact publishing for deal pages. It resolves deal names, preflights
+  file size/HTML shape, chooses a non-overwriting slug by default, auto-detects
+  sibling `*_files` asset folders, uploads, and performs read-after-write
+  verification before returning the viewer URL.
+- **`html_upload_file` MCP tool** — file-path based HTML upload for MCP-native
+  agents, including preflight checks, optional asset-folder upload, and
+  read-after-write verification.
+
+### Changed
+- HTML publishing now sends a per-attempt `client_upload_id` and verifies the
+  server copy by `sha256` when Command returns it. Retrying the same failed
+  attempt with `--upload-id` avoids duplicate versions. JSON and multipart
+  uploads also send the same id as `X-Llama-Upload-Id` so server logs and
+  retry/debug paths can correlate the attempt.
+- MCP `html_upload` now refuses inline HTML bodies over 50KB and instructs
+  agents to use `html_upload_file` or `llama html publish --file`. This avoids
+  moving large memos through model/tool-call context, the main reliability
+  failure mode for long IC memos.
+- MCP `html_upload_bundle` is now treated as a small inline fallback and refuses
+  tool-call payloads over 50KB. Agents should use `html_upload_file` with
+  `assetsDir` or `llama html publish --file --assets` for saved-page exports.
+- `AGENT_BRIEFING.md` now teaches coding agents to use file-path based HTML
+  publishing as the default Llama Command route.
+- Top-level CLI help now routes deal-specific HTML artifacts to `llama html
+  publish --file` instead of the lower-level upload command.
+- Local-agent telemetry now redacts content payload fields such as `html`,
+  `body`, `content`, `markdown`, `message`, and `text`, keeping only
+  chars/bytes/sha256. Incident-sized memo uploads remain observable without
+  storing memo text in the telemetry stream.
+
+## [1.16.0] - 2026-06-22
+
+### Added
+- CLI and MCP requests now send bounded local-agent telemetry metadata to
+  Llama Command: client kind/version, detected agent client, session id,
+  normalized command, latency, status, sanitized args, result ids, and bounded
+  result summaries.
+- `llama eval good|bad --last` and `llama eval add "<query>" --expect ...`
+  let agents and humans turn real search usage into Golden Query Eval
+  feedback.
+- MCP tool `record_eval_feedback` mirrors the CLI eval feedback path for
+  MCP-native agents.
+
+### Changed
+- `llama agent-onboard` and MCP `agent_briefing` now prefer the authenticated
+  Llama Command `/api/agent/briefing` runtime contract, with bundled
+  `AGENT_BRIEFING.md` retained as fallback only.
+- `llama agent bootstrap` and MCP `agent_bootstrap` now pass the local CLI
+  version to Command so the server can return stale/ok CLI guidance as part of
+  the agent contract.
+
 ## [1.15.1] — 2026-06-16
 
 ### Changed
@@ -402,7 +457,21 @@ assistant-drafted (🤖) and enforces the AI trust ceiling.
 
 ---
 
-[Unreleased]: https://github.com/Llama-Ventures/llama-cli/compare/v1.3.1...HEAD
+[Unreleased]: https://github.com/Llama-Ventures/llama-cli/compare/v1.17.0...HEAD
+[1.17.0]: https://github.com/Llama-Ventures/llama-cli/compare/v1.16.0...v1.17.0
+[1.16.0]: https://github.com/Llama-Ventures/llama-cli/compare/v1.15.1...v1.16.0
+[1.15.1]: https://github.com/Llama-Ventures/llama-cli/compare/v1.15.0...v1.15.1
+[1.15.0]: https://github.com/Llama-Ventures/llama-cli/compare/v1.14.1...v1.15.0
+[1.14.1]: https://github.com/Llama-Ventures/llama-cli/compare/v1.14.0...v1.14.1
+[1.14.0]: https://github.com/Llama-Ventures/llama-cli/compare/v1.13.0...v1.14.0
+[1.13.0]: https://github.com/Llama-Ventures/llama-cli/compare/v1.12.0...v1.13.0
+[1.12.0]: https://github.com/Llama-Ventures/llama-cli/compare/v1.11.0...v1.12.0
+[1.11.0]: https://github.com/Llama-Ventures/llama-cli/compare/v1.10.0...v1.11.0
+[1.10.0]: https://github.com/Llama-Ventures/llama-cli/compare/v1.7.0...v1.10.0
+[1.7.0]: https://github.com/Llama-Ventures/llama-cli/compare/v1.5.0...v1.7.0
+[1.5.0]: https://github.com/Llama-Ventures/llama-cli/compare/v1.4.4...v1.5.0
+[1.4.4]: https://github.com/Llama-Ventures/llama-cli/compare/v1.4.0...v1.4.4
+[1.4.0]: https://github.com/Llama-Ventures/llama-cli/compare/v1.3.1...v1.4.0
 [1.3.1]: https://github.com/Llama-Ventures/llama-cli/compare/v1.3.0...v1.3.1
 [1.3.0]: https://github.com/Llama-Ventures/llama-cli/compare/v1.2.4...v1.3.0
 [1.2.4]: https://github.com/Llama-Ventures/llama-cli/compare/v1.2.3...v1.2.4

package/README.md

@@ -226,6 +226,8 @@ llama agent bootstrap
 llama skills search "wiki delete tombstone"
 llama skills show llama-command
 llama explain https://command.llamaventures.vc/wiki/some-page
+llama eval bad --last --reason "missed the llamaos weekly note"
+llama eval add "last week llama dev weekly" --expect wiki:llamaos-weekly-2026-06-17
 
 # Wiki
 llama wiki search "<query>"
@@ -262,10 +264,31 @@ agents can pattern-match without parsing prose.
 
 ---
 
+### Golden Query Eval feedback
+
+The CLI and MCP server send lightweight client telemetry to Command for each
+authenticated request: client kind/version, detected agent client, local session
+id, normalized command, sanitized args, canonical result ids, status, latency,
+and bounded summaries. It records what Llama Command was asked to do, not the
+user's private Claude Code/Codex/Cursor conversation or local files.
+
+Search commands automatically become eval candidates. Agents can mark the latest
+result explicitly:
+
+```bash
+llama eval good --last
+llama eval bad --last --reason "wrong top wiki"
+llama eval add "AI陪伴" --surface deal --expect deal:<uuid>
+```
+
+MCP-native agents use `record_eval_feedback` for the same flow.
+
+---
+
 ## MCP server
 
 The bundled `llama-mcp` is a **stdio Model Context Protocol** server exposing
-**56 typed tools** that mirror the most-used CLI surface. Every tool is named
+typed tools that mirror the most-used CLI surface. Every tool is named
 and scoped — there is no generic API passthrough, by design (a public-package
 escape hatch reachable from a prompt-injectable agent context is exactly the
 shape we want to avoid).
@@ -290,9 +313,11 @@ printf '%s\n' \
 ```
 
 Auth is identical to the CLI's chain (gcloud → `$LLAMA_TOKEN` → `~/.llama/token`).
-The `agent_briefing` MCP **prompt** also returns
-[`AGENT_BRIEFING.md`](AGENT_BRIEFING.md) verbatim, so any new agent loading the
-server can self-onboard without leaving the protocol.
+The `agent_briefing` MCP **prompt** returns the server-owned Agent Runtime
+Contract when authenticated, so any new agent loading the server can
+self-onboard without leaving the protocol. The bundled
+[`AGENT_BRIEFING.md`](AGENT_BRIEFING.md) is only a fallback if the server
+briefing route is temporarily unavailable.
 
 For current Llama OS skills, use the runtime tools instead of looking for a
 local private repo: `agent_bootstrap`, `skills_search`, `skills_read`, and
@@ -352,8 +377,8 @@ extensions, no transport flags.
 
 > If you're new and want the agent to onboard itself, run
 > `llama agent-onboard` from the CLI or fetch the `agent_briefing` prompt from
-> the MCP server. It's the workflow contract — autonomy levels, attribution
-> grammar, error recovery, anti-pollution rules.
+> the MCP server. It pulls the Command-owned workflow contract — current CLI
+> guidance, attribution grammar, error recovery, and anti-pollution rules.
 
 ---
 

package/README.zh-CN.md

@@ -299,9 +299,10 @@ printf '%s\n' \
 ```
 
 认证链跟 CLI 完全一样（gcloud → `$LLAMA_TOKEN` → `~/.llama/token`）。
-`agent_briefing` 这个 MCP **prompt** 还会原样吐出
-[`AGENT_BRIEFING.md`](AGENT_BRIEFING.md)——刚装上 server 的 agent
-不用离开协议就能给自己 onboard。
+`agent_briefing` 这个 MCP **prompt** 会在认证后拉取 Command 服务端的
+Agent Runtime Contract——刚装上 server 的 agent 不用离开协议就能给自己
+onboard。包内 [`AGENT_BRIEFING.md`](AGENT_BRIEFING.md) 只是服务端 briefing
+临时不可用时的 fallback。
 
 要读当前 Llama OS skills，用 runtime tools：`agent_bootstrap`、
 `skills_search`、`skills_read`、`object_inspect`。公开 npm 包不打包私有
@@ -358,7 +359,7 @@ claude mcp add llama -- llama-mcp
 </details>
 
 > 想让 agent 自己 onboard？跑 `llama agent-onboard`，或者从 MCP server
-> 拉 `agent_briefing` prompt——那是 AI agent 的工作合约（autonomy 等级、
+> 拉 `agent_briefing` prompt——它会拿 Command 服务端的工作合约（CLI 状态、
 > attribution 语法、错误恢复、anti-pollution 规则）。
 
 ---