tenjin-cli 0.1.0-alpha.1 → 0.1.0-alpha.3

package/NOTICE.md

@@ -41,6 +41,39 @@ BlockRun MCP is licensed under the MIT License:
 > OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
 > SOFTWARE.
 
+## gitleaks
+
+The provider secret-token shape patterns in the publish redaction scan
+(`src/lib/scan.ts`: AWS access keys, GitHub/Slack/Stripe tokens, JWTs, and the
+PEM private-key marker) are adapted from the
+[gitleaks](https://github.com/gitleaks/gitleaks) ruleset (MIT), by Zachary Rice.
+The regexes are vendored and adapted inline; gitleaks is not a runtime
+dependency (the scan is pure and offline by design).
+
+gitleaks is licensed under the MIT License:
+
+> MIT License
+>
+> Copyright (c) 2019 Zachary Rice
+>
+> Permission is hereby granted, free of charge, to any person obtaining a copy
+> of this software and associated documentation files (the "Software"), to deal
+> in the Software without restriction, including without limitation the rights
+> to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+> copies of the Software, and to permit persons to whom the Software is
+> furnished to do so, subject to the following conditions:
+>
+> The above copyright notice and this permission notice shall be included in all
+> copies or substantial portions of the Software.
+>
+> THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+> IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+> FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+> AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+> LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+> OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+> SOFTWARE.
+
 ## tenjin-mcp
 
 This repository absorbs, with credit, patterns from the archived

package/README.md

@@ -17,9 +17,13 @@ already been produced, read free essays, buy valuable answers with USDC, and
 publish their own reusable research. This repo is the home of the `tenjin-cli`
 npm package and, soon, the Claude Code plugin and agent skills that wrap it.
 
-> **Status: early preview.** The CLI ships `doctor`, `config`, and `wallet`
-> today; `lookup`, `inspect`, `buy`, `outcome`, and `publish` are landing next.
-> Everything under "zero install" below is complete and live now; start there.
+> **Status: early preview.** The CLI ships `install`, `doctor`, `config`, and
+> `wallet` today. `lookup`, `inspect`, `buy`, and `outcome` are implemented but require the
+> marketplace lookup API (Track A2) to be deployed to the base URL you point at;
+> against a deploy without it, `doctor` shows a `lookup-contract` warning and those
+> commands will not work yet. `publish` writes a piece with an optional answer
+> card, gated by a local secrets scan and your `publish.mode` consent. Everything
+> under "zero install" below is complete and live now; start there.
 
 ## Use Tenjin today, zero install
 
@@ -39,17 +43,53 @@ your machine; Tenjin never receives a private key. It is listed in the
 [official MCP registry](https://registry.modelcontextprotocol.io) as
 `blog.tenjin/tenjin`.
 
-### Install the skill
+### Install the skills: `npx tenjin-cli install`
 
 ```bash
-npx skills add BackTrackCo/tenjin-agent
+npx tenjin-cli install
 ```
 
-Installs the `tenjin` skill into Claude Code, Codex, or any
-Agent-Skills-compatible harness. It is the same zero-install curriculum served
-at [tenjin.blog/skills.md](https://tenjin.blog/skills.md) (canonical), and works
-today with no CLI and no account; a funded wallet is only needed for paid reads
-and publishing.
+One command auto-detects your harness (Claude Code, Codex, or any
+Agent-Skills-compatible setup), copies the three Tenjin skills into place, and
+then runs the `doctor` checks as its last step. It is idempotent: re-run any
+time, `--dry-run` previews the changes without writing, and
+`--harness claude|codex|shared` (repeatable) targets a specific one.
+
+Where the skills land:
+
+- **Claude Code** (`~/.claude` present or `claude` on PATH):
+  `~/.claude/skills/`. The Claude Code plugin marketplace (a later release)
+  will supersede this path for Claude users.
+- **Codex** (`~/.codex` present or `codex` on PATH): `~/.agents/skills/`, the
+  harness-shared Agent Skills location. The installer also appends a one-line
+  pointer to your AGENTS.md and prints the `config.toml` rule Codex needs,
+  because its default `workspace-write` sandbox blocks network and would
+  otherwise break every paid call:
+
+  ```toml
+  [sandbox_workspace_write]
+  network_access = true
+  ```
+
+- **Nothing detected**: the installer falls back to `~/.agents/skills/`, so a
+  harness installed later still finds the skills.
+
+The repo ships three skills:
+
+- **`tenjin`**: the zero-install curriculum, a synced copy of the canonical
+  [tenjin.blog/skills.md](https://tenjin.blog/skills.md). Teaches the raw
+  HTTP/MCP surface; works with no CLI and no account. Use this when the CLI is
+  not installed.
+- **`tenjin-search`**: thin adapter over `tenjin lookup/inspect/buy/outcome`
+  with a deliberately narrow trigger (public, durable, costly-to-reproduce
+  questions). Requires the CLI below.
+- **`tenjin-publish`**: explicit-invocation-only publishing rubric and
+  `tenjin publish` adapter. Never triggers on its own.
+
+A funded wallet is only needed for paid reads and publishing.
+
+> Prefer no CLI? `npx skills add BackTrackCo/tenjin-agent` installs the same
+> skills into any Agent-Skills-compatible harness without the `tenjin` binary.
 
 ### Add the remote MCP server
 
@@ -92,25 +132,86 @@ npm install -g tenjin-cli@next   # pre-release channel
 tenjin doctor                    # verify Node floor, API reachability, contract, wallet
 ```
 
-Shipping today:
+Shipping today (no backend dependency):
 
 | Command                                 | Purpose                                                              |
 | --------------------------------------- | -------------------------------------------------------------------- |
+| `tenjin install`                        | Auto-detect harnesses, wire the skills, then run the doctor checks   |
 | `tenjin doctor`                         | Environment, API reachability, contract, and wallet checks           |
 | `tenjin config [get\|set]`              | Spend policy: `maxAutoSpend`, `sessionBudget`, `confirm`, allowlists |
 | `tenjin wallet [create\|show\|balance]` | Local Base wallet; the key never leaves the machine                  |
 
-Next: `lookup` / `inspect` / `buy` / `outcome` against the marketplace lookup
-API, `publish --draft`, an `install` command that auto-wires Claude Code and
-Codex, a Claude Code plugin marketplace in this repo, and `tenjin mcp` (local
+Marketplace commands (need the Track A2 lookup API deployed to your `--base-url`):
+
+| Command                                              | Purpose                                                                                            |
+| ---------------------------------------------------- | -------------------------------------------------------------------------------------------------- |
+| `tenjin lookup "<question>"`                         | Ask for payable candidates or an honest MISS; prints the compact JSON verbatim                     |
+| `tenjin inspect <url-or-id>`                         | Show a candidate's pre-purchase card from the 402 body; never pays                                 |
+| `tenjin buy <url-or-id> [--max-price <usd>] [--yes]` | Entitlement re-check (free re-read if owned), then x402 exact payment                              |
+| `tenjin outcome --lookup-id <id> --status <s>`       | Report `used` / `partially_used` / `rejected` / `regenerated` / `purchase_declined`                |
+| `tenjin publish <file.md> [--price <usd>] [--yes]`   | Publish a Markdown piece with an optional answer card, gated by a local scan and your consent mode |
+| `tenjin publish --candidate <id>`                    | Publish a parked candidate (its draft.md); clears it on success                                    |
+
+`buy` re-reads an entitled resource for free before ever paying, re-delivers
+already-bought content from the local library without paying again, and refuses to
+sign if the price rose since it first saw the 402. Spend policy is enforced in the
+wallet provider layer before any payment. The default output carries a heading
+outline, never the body: `--print-body` includes it, and `--sections <tokens>`
+includes the leading sections within a token budget (a deterministic heading
+split, no model calls).
+
+The lookup question must be **generalized public text**: derive the smallest
+public phrasing of your task and never include secrets or private context. By
+default the server stores no query text at all; `tenjin config set evalCohort
+true` opts into 90-day retention of the question for retrieval evaluation.
+
+> **Money units.** `--max-price` (and the spend-policy config values) are entered
+> in **decimal USD** at the CLI edge (e.g. `--max-price 0.10`), and emitted in
+> machine output as both atomic and USD. This is a deliberate deviation from the
+> atomic-unit flags in CLI spec 10, per plan 12 decision O1 (humans think in
+> dollars; agents read the atomic value in the JSON).
+
+### Consent modes and pricing
+
+`publish.mode` governs ALL publishing uniformly. A piece you asked for and a
+reusable answer your agent derived after a lookup both go through it, after a
+deterministic local scan (secrets, keys, PII, wallet addresses) that runs in
+every mode:
+
+- **`review`** (the default) asks a one-click yes/no for every publish, even a
+  clean scan. This is the safe default: nothing leaves your machine unseen.
+- **`auto`** publishes a clean scan immediately, including answers your agent
+  derives; any warning finding stops and asks; a hard block (a live secret or
+  private key) always refuses.
+- **`full-auto`** does not stop for warnings, only for hard blocks. It is honored
+  from your global config, an env var, a flag, or a gitignored `.tenjin.json`. Only
+  a committed `.tenjin.json` asking for `full-auto` is downgraded to `auto`, so
+  cloning a repo can never enable silent auto-publishing.
+
+`--yes` clears the warning findings and the review confirm; it never clears a hard
+block. Set the mode with `tenjin config set publish.mode <mode>`, or per run with
+`--mode`. `tenjin install` asks once on an interactive setup and otherwise leaves
+the default (review); change it any time with `tenjin config set publish.mode`.
+
+Pricing: `--price` (or a frontmatter `price:`) wins, otherwise `publish.defaultPrice`
+(default $0.10). A card never auto-prices; the `tenjin-publish` skill's rubric is
+what actually chooses a price before it calls the command.
+
+Instead of a file, `publish --candidate <id>` publishes a parked candidate (see
+`tenjin candidate`) from its stored `draft.md`, prefilling the card's question from
+the candidate. It runs the same scan and consent flow and clears the candidate only
+on a successful publish; a file and `--candidate` are mutually exclusive.
+
+Next: a Claude Code plugin marketplace in this repo, and `tenjin mcp` (local
 stdio server over the same core).
 
 ### Output contract
 
 Every invocation prints exactly one JSON envelope to stdout
 (`{schemaVersion, command, ok, data | error}`); human rendering goes to stderr
-only. Exit codes: `0` success, `1` runtime/network, `2` usage, `3` policy
-refusal, `4` payment failure (reserved).
+only. Exit codes: `0` success (including an honest MISS), `1` runtime/network,
+`2` usage, `3` policy refusal (spend cap, allowlist, missing approval), `4`
+payment failure after approval.
 
 ### Safety model
 
@@ -150,6 +251,56 @@ pnpm lint && pnpm typecheck && pnpm format:check
 pnpm pack-smoke   # exercises the packed npm artifact
 ```
 
+## Release
+
+Publishing to npm uses **Changesets** + **npm Trusted Publishing (OIDC)**,
+driven by the two-job `workflow_dispatch`-only `.github/workflows/release.yml`.
+This mirrors the house template in `BackTrackCo/x402r-sdk`. Nothing auto-fires
+from a push or a tag: a maintainer clicks Run workflow at each step.
+
+Day to day, add a changeset in the same PR as any shippable change:
+
+```sh
+pnpm changeset   # pick the bump type, write a summary; commit the .md
+```
+
+To cut a release (two clicks):
+
+1. **Dispatch (click 1)**: Actions -> Release -> Run workflow -> `main`. The
+   `version` job runs `changeset version` (consumes `.changeset/*.md`, bumps
+   `package.json`, regenerates `CHANGELOG.md`) and opens the
+   **"chore(release): version packages"** PR. Nothing is published yet.
+2. **Review and merge** that PR (its final state is what ships; edit the
+   version or changelog directly if needed).
+3. **Dispatch (click 2)**: same path. With no pending changesets, the `publish`
+   job builds, runs the check suite + `pnpm audit` + the packed-artifact smoke
+   as a pre-publish gate, then `changeset publish` ships `tenjin-cli` with
+   provenance and creates the GitHub release. Prereleases use Changesets' pre
+   mode (`pnpm changeset pre enter alpha`) and publish to that dist-tag; stable
+   goes to `latest`.
+
+Auth is npm Trusted Publishing (OIDC): each publish mints a short-lived,
+per-run token, so there is **no `NPM_TOKEN`** to store or rotate.
+
+### One-time owner setup
+
+`tenjin-cli` already exists on npm (published `0.1.0-alpha.1`), so no manual
+first publish is needed. The owner must, one time:
+
+1. **Install the release-bot GitHub App on `BackTrackCo/tenjin-agent`** (the
+   same `x402r-release-bot` App used by `x402r-sdk`, or an equivalent), then
+   set repo **variable** `RELEASE_APP_CLIENT_ID` and repo **secret**
+   `RELEASE_APP_PRIVATE_KEY`. Required because Changesets' version PR must be
+   opened by an App identity to trigger CI (the default `GITHUB_TOKEN` cannot,
+   by GitHub's anti-recursion rule). Neither the variable nor the secret is
+   set on this repo yet, so `release.yml` will fail at the token step until
+   they exist.
+2. **Add a Trusted Publisher** to `tenjin-cli` on npmjs.com: provider GitHub
+   Actions, organization `BackTrackCo`, repository `tenjin-agent`, workflow
+   filename `release.yml`, environment `npm-publish`.
+3. **Create a GitHub Environment named `npm-publish`** (Settings ->
+   Environments), optionally with required reviewers to gate each publish.
+
 ## License
 
 MIT. See [NOTICE.md](./NOTICE.md) for third-party attributions (wallet-safety

package/dist/{_esm-ZH2J4QEH.js → _esm-C5CRWCYU.js}

@@ -4,7 +4,7 @@ import {
   __export,
   __require,
   __toESM
-} from "./chunk-3IMLRUZE.js";
+} from "./chunk-ZXTAQYNA.js";
 
 // node_modules/.pnpm/ws@8.21.0/node_modules/ws/lib/constants.js
 var require_constants = __commonJS({
@@ -3734,4 +3734,4 @@ var WebSocket3 = (() => {
 export {
   WebSocket3 as WebSocket
 };
-//# sourceMappingURL=_esm-ZH2J4QEH.js.map
+//# sourceMappingURL=_esm-C5CRWCYU.js.map