memento-mori-jester 0.1.3 → 0.1.5

package/README.md

@@ -10,16 +10,16 @@ It roasts the reasoning, not the human.
 
 ## Try It
 
-Run directly from GitHub now:
+Run the published package:
 
 ```powershell
-npx -y github:Martin123132/Memento-Mori command "git reset --hard"
+npx -y memento-mori-jester@latest command "git reset --hard"
 ```
 
-After npm publish:
+Start a project with config, MCP JSON, and agent instructions:
 
 ```powershell
-npx -y memento-mori-jester@latest command "git reset --hard"
+npx -y memento-mori-jester@latest bootstrap --preset node
 ```
 
 Installed globally:
@@ -51,23 +51,16 @@ A dazzling command, if the desired outcome is court-sponsored regret.
 For a copy-pasteable MCP config and suggested agent instruction:
 
 ```powershell
-npx -y github:Martin123132/Memento-Mori init --package github:Martin123132/Memento-Mori
+npx -y memento-mori-jester@latest init
 ```
 
 For a starter kit that writes project files:
 
 ```powershell
-npx -y github:Martin123132/Memento-Mori bootstrap --preset node --package github:Martin123132/Memento-Mori
-```
-
-After npm publish:
-
-```powershell
-npx -y memento-mori-jester@latest init
 npx -y memento-mori-jester@latest bootstrap --preset node
 ```
 
-For this local checkout before npm publish:
+For this local checkout:
 
 ```powershell
 node .\dist\cli.js init --mode local
@@ -253,8 +246,15 @@ Before risky commands, final answers, commits, or large edits, call the Memento
 
 More setup examples:
 
+- [Getting Started](docs/GETTING_STARTED.md)
+- [CLI Setup](docs/CLI.md)
+- [Codex Setup](docs/CODEX.md)
+- [Claude Code Setup](docs/CLAUDE_CODE.md)
 - [Agent Setup](docs/AGENTS.md)
 - [GitHub Actions](docs/GITHUB_ACTIONS.md)
+- [Demo Script](docs/DEMO.md)
+- [Roadmap](ROADMAP.md)
+- [Trusted npm Publishing](docs/TRUSTED_PUBLISHING.md)
 
 ## Installer Scripts
 
@@ -297,8 +297,6 @@ Both scripts check Node 20+, run a smoke `doctor`, and print MCP config.
 
 ## Publishing
 
-The npm package name `memento-mori-jester` was available when checked on 2026-05-17.
-
 Release checklist:
 
 ```powershell

package/docs/AGENTS.md

@@ -8,7 +8,7 @@ Memento Mori Jester is an MCP stdio server plus a normal CLI. The safest pattern
 
 ## Quick MCP Config
 
-After npm publish, use the `npx` config:
+Use the published package with `npx`:
 
 ```json
 {
@@ -57,13 +57,7 @@ Before risky commands, final answers, commits, or large edits, call the Memento
 Use `bootstrap` inside a repo when you want the project files created for you:
 
 ```powershell
-jester bootstrap --preset node
-```
-
-Before npm publish, the GitHub `npx` path should keep using the GitHub package spec in generated MCP config:
-
-```powershell
-npx -y github:Martin123132/Memento-Mori bootstrap --preset node --package github:Martin123132/Memento-Mori
+npx -y memento-mori-jester@latest bootstrap --preset node
 ```
 
 It writes `jester.config.json`, `memento-mori.mcp.json`, and `MEMENTO_MORI.md`. Existing files are kept unless `--force` is passed.
@@ -80,10 +74,10 @@ jester bootstrap --preset security --hook pre-commit --hook pre-push
 Use:
 
 ```powershell
-jester init --agent codex
+npx -y memento-mori-jester@latest init --agent codex
 ```
 
-Then paste the generated `mcpServers` block wherever your Codex MCP configuration is kept. For local development before npm publish:
+Then paste the generated `mcpServers` block wherever your Codex MCP configuration is kept. For local development:
 
 ```powershell
 node .\dist\cli.js init --mode local --agent codex
@@ -94,7 +88,7 @@ node .\dist\cli.js init --mode local --agent codex
 Use:
 
 ```powershell
-jester init --agent claude
+npx -y memento-mori-jester@latest init --agent claude
 ```
 
 Then paste the generated `mcpServers` block into Claude Code's MCP configuration. If Claude Code asks for a command and args separately, keep the generated values exactly.
@@ -104,7 +98,7 @@ Then paste the generated `mcpServers` block into Claude Code's MCP configuration
 Use:
 
 ```powershell
-jester mcp-config --mode npx
+npx -y memento-mori-jester@latest mcp-config --mode npx
 ```
 
 If the client does not support `npx`, install globally:

package/docs/CLAUDE_CODE.md

@@ -0,0 +1,42 @@
+# Claude Code Setup
+
+## Generate The Config
+
+```powershell
+npx -y memento-mori-jester@latest init --agent claude
+```
+
+Copy the generated command and args into Claude Code's MCP configuration.
+
+The default server command is:
+
+```json
+{
+  "command": "npx",
+  "args": [
+    "-y",
+    "memento-mori-jester@latest",
+    "mcp-server"
+  ]
+}
+```
+
+## Project Starter Kit
+
+Inside a repo:
+
+```powershell
+npx -y memento-mori-jester@latest bootstrap --preset node
+```
+
+This creates:
+
+- `jester.config.json`
+- `memento-mori.mcp.json`
+- `MEMENTO_MORI.md`
+
+## Suggested Claude Instruction
+
+```text
+Before risky commands, final answers, commits, or large edits, call the Memento Mori Jester. Treat BLOCK as requiring a changed plan, and CAUTION as requiring at least one concrete verification step.
+```

package/docs/CLI.md

@@ -0,0 +1,48 @@
+# CLI Setup
+
+Use the CLI when you want quick checks without wiring an agent yet.
+
+## Run Without Installing
+
+```powershell
+npx -y memento-mori-jester@latest doctor
+npx -y memento-mori-jester@latest command "git reset --hard"
+npx -y memento-mori-jester@latest plan "I will just refactor auth and ship it"
+```
+
+## Install Globally
+
+```powershell
+npm install -g memento-mori-jester
+jester doctor
+```
+
+After that, use `jester` directly:
+
+```powershell
+jester command "Remove-Item .\dist -Recurse -Force"
+jester final --file .\final-answer.txt --tone professional
+git diff | jester diff --fail-on block
+```
+
+## Bootstrap A Repo
+
+```powershell
+jester bootstrap --preset node
+```
+
+Presets:
+
+- `node`: npm/package rules.
+- `python`: Python dependency and dynamic execution rules.
+- `security`: stricter TLS, CORS, secrets, and permission checks.
+
+## JSON Output
+
+Use `--json` when another tool needs to parse the result:
+
+```powershell
+jester command "git reset --hard" --json
+jester config validate --json
+jester bootstrap --preset node --json
+```

package/docs/CODEX.md

@@ -0,0 +1,33 @@
+# Codex Setup
+
+## Generate The Config
+
+```powershell
+npx -y memento-mori-jester@latest init --agent codex
+```
+
+Copy the generated `mcpServers` block into your Codex MCP configuration.
+
+## Project Starter Kit
+
+Inside a repo:
+
+```powershell
+npx -y memento-mori-jester@latest bootstrap --preset node
+```
+
+This creates `memento-mori.mcp.json` and `MEMENTO_MORI.md`. Use the generated agent instruction from `MEMENTO_MORI.md` in your Codex rules.
+
+## Suggested Codex Rule
+
+```text
+Before risky commands, final answers, commits, or large edits, call the Memento Mori Jester. Treat BLOCK as requiring a changed plan, and CAUTION as requiring at least one concrete verification step.
+```
+
+## Local Development From This Repo
+
+```powershell
+npm.cmd install
+npm.cmd run build
+node .\dist\cli.js init --mode local --agent codex
+```

package/docs/DEMO.md

@@ -0,0 +1,49 @@
+# Demo Script
+
+Use this when showing someone what the project does.
+
+## 1. Health Check
+
+```powershell
+npx -y memento-mori-jester@latest doctor
+```
+
+Expected result: `PASS` checks and a final line saying the tool is fit for use.
+
+## 2. Dangerous Command Review
+
+```powershell
+npx -y memento-mori-jester@latest command "git reset --hard"
+```
+
+Expected result: `BLOCK`.
+
+## 3. Overconfident Plan Review
+
+```powershell
+npx -y memento-mori-jester@latest plan "I will just refactor auth and ship it"
+```
+
+Expected result: usually `CAUTION`, because the plan touches a sensitive area and has no verification step.
+
+## 4. Bootstrap A Fresh Folder
+
+```powershell
+mkdir jester-demo
+cd jester-demo
+npx -y memento-mori-jester@latest bootstrap --preset node
+```
+
+Expected files:
+
+- `jester.config.json`
+- `memento-mori.mcp.json`
+- `MEMENTO_MORI.md`
+
+## 5. Validate The Config
+
+```powershell
+npx -y memento-mori-jester@latest config validate
+```
+
+Expected result: `Config valid`.

package/docs/GETTING_STARTED.md

@@ -0,0 +1,69 @@
+# Getting Started
+
+This is the shortest path for a normal project.
+
+## 1. Check It Runs
+
+```powershell
+npx -y memento-mori-jester@latest doctor
+```
+
+You should see four `PASS` lines.
+
+## 2. See The Point
+
+```powershell
+npx -y memento-mori-jester@latest command "git reset --hard"
+```
+
+That should return `BLOCK`. Nothing dangerous is run; the command is only reviewed as text.
+
+## 3. Add It To A Project
+
+Run this from the folder of the project you want protected:
+
+```powershell
+npx -y memento-mori-jester@latest bootstrap --preset node
+```
+
+That creates:
+
+- `jester.config.json`
+- `memento-mori.mcp.json`
+- `MEMENTO_MORI.md`
+
+Existing files are kept. Add `--force` only when you want to overwrite the starter files.
+
+## 4. Optional Git Hooks
+
+To make git call the Jester before commits:
+
+```powershell
+npx -y memento-mori-jester@latest bootstrap --preset node --hook pre-commit
+```
+
+To also check before pushing:
+
+```powershell
+npx -y memento-mori-jester@latest bootstrap --preset node --hook pre-commit --hook pre-push
+```
+
+## 5. Agent Instruction
+
+Put this in your agent rules or custom instructions:
+
+```text
+Before risky commands, final answers, commits, or large edits, call the Memento Mori Jester. Treat BLOCK as requiring a changed plan, and CAUTION as requiring at least one concrete verification step.
+```
+
+## What To Share With Someone Else
+
+For most people, this is enough:
+
+```powershell
+npx -y memento-mori-jester@latest bootstrap --preset node
+```
+
+Then tell them to open `MEMENTO_MORI.md`.
+
+For where this is going next, see [ROADMAP.md](../ROADMAP.md).

package/docs/RELEASE.md

@@ -1,34 +1,8 @@
 # Release Guide
 
-This project is ready to become a one-command package.
+This project is published as a one-command package on npm.
 
-## 1. Create The Repo
-
-Suggested repo name:
-
-```text
-Memento-Mori
-```
-
-After creating it:
-
-```powershell
-git remote add origin https://github.com/Martin123132/Memento-Mori.git
-git branch -M main
-git push -u origin main
-```
-
-## 2. Confirm Package Name
-
-The name was available on 2026-05-17:
-
-```powershell
-npm view memento-mori-jester version
-```
-
-An npm 404 means the name is still unclaimed.
-
-## 3. Publish To npm
+## 1. Publish To npm
 
 ```powershell
 npm login
@@ -37,13 +11,17 @@ npm run pack:dry
 npm publish
 ```
 
+If npm asks for browser authentication, approve it in the browser window that opens.
+
+For the less painful route, configure trusted publishing once using [TRUSTED_PUBLISHING.md](TRUSTED_PUBLISHING.md), then run the `npm Publish` workflow in GitHub Actions.
+
 The package publishes these bins:
 
 - `jester`: human CLI
 - `memento-mori-jester`: human CLI, useful for `npx`
 - `memento-mori-jester-mcp`: MCP stdio server
 
-## 4. Smoke Test Published Package
+## 2. Smoke Test Published Package
 
 ```powershell
 npx -y memento-mori-jester@latest doctor
@@ -64,7 +42,7 @@ npm whoami
 
 Then run the publish commands again.
 
-## 5. MCP Copy-Paste
+## 3. MCP Copy-Paste
 
 The lowest-friction config uses `npx`:
 
@@ -96,7 +74,7 @@ For users who install globally:
 }
 ```
 
-## 6. Repository Metadata
+## 4. Repository Metadata
 
 The package is configured for:
 
@@ -106,7 +84,7 @@ https://github.com/Martin123132/Memento-Mori
 
 If the repo moves, update `repository`, `homepage`, and `bugs` in `package.json`, plus the raw installer URLs in `README.md`.
 
-## 7. Post-Release Workflow Check
+## 5. Post-Release Workflow Check
 
 In a throwaway git repo:
 
@@ -117,3 +95,7 @@ npx -y memento-mori-jester@latest hook-status
 ```
 
 Then stage a risky diff and confirm the hook blocks or cautions according to `hookFailOn`.
+
+## 6. GitHub Release
+
+Pushing a `v*` tag now creates a GitHub Release automatically. If `docs/RELEASE_NOTES_<tag>.md` exists, those notes are used; otherwise GitHub-generated notes are used.

package/docs/RELEASE_NOTES_v0.1.4.md

@@ -0,0 +1,23 @@
+# v0.1.4 Release Notes
+
+This is the first polish release after the npm package went live.
+
+## Highlights
+
+- The README now starts with the published npm command instead of the old GitHub-only pre-publish path.
+- Added plain setup docs for getting started, CLI use, Codex, and Claude Code.
+- Added a short demo script for showing the tool quickly.
+- Cleaned agent setup docs now that `memento-mori-jester@latest` exists.
+
+## Useful Commands
+
+```powershell
+npx -y memento-mori-jester@latest doctor
+npx -y memento-mori-jester@latest command "git reset --hard"
+npx -y memento-mori-jester@latest bootstrap --preset node
+```
+
+## Links
+
+- npm: https://www.npmjs.com/package/memento-mori-jester
+- GitHub: https://github.com/Martin123132/Memento-Mori

package/docs/RELEASE_NOTES_v0.1.5.md

@@ -0,0 +1,19 @@
+# v0.1.5 Release Notes
+
+This release makes the public release process feel more real and less manual.
+
+## Added
+
+- GitHub Release workflow for future `v*` tags.
+- Manual npm trusted-publishing workflow, ready for npm's one-time trusted publisher setup.
+- `ROADMAP.md` with near-term direction and product ideas.
+- Trusted publishing setup guide.
+
+## Why
+
+The package is now live on npm, so the project needs a cleaner release path and a public roadmap. This release puts those pieces in the repo instead of leaving them as scattered instructions.
+
+## Useful Links
+
+- npm: https://www.npmjs.com/package/memento-mori-jester
+- GitHub: https://github.com/Martin123132/Memento-Mori

package/docs/TRUSTED_PUBLISHING.md

@@ -0,0 +1,39 @@
+# Trusted npm Publishing
+
+Trusted publishing lets GitHub Actions publish this package to npm without a long-lived npm token.
+
+## One-Time npm Setup
+
+Open the package settings on npm:
+
+```text
+https://www.npmjs.com/package/memento-mori-jester/access
+```
+
+Find the trusted publishing settings and add:
+
+- Provider: `GitHub Actions`
+- Organization or user: `Martin123132`
+- Repository: `Memento-Mori`
+- Workflow filename: `npm-publish.yml`
+
+The workflow file must exist in `.github/workflows/`, which this repo now has.
+
+## Manual Publish From GitHub
+
+After the npm trusted publisher is configured:
+
+1. Open the GitHub repo.
+2. Go to `Actions`.
+3. Open `npm Publish`.
+4. Click `Run workflow`.
+
+The workflow installs dependencies, runs tests, and publishes the current package version to npm.
+
+## Why It Exists
+
+Manual `npm publish` works, but npm asks for browser authentication. Trusted publishing moves that trust to the GitHub workflow and avoids storing a reusable npm token.
+
+## Important
+
+Only run the workflow after `package.json` has a version that npm does not already have. npm will reject publishing the same version twice.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "memento-mori-jester",
-  "version": "0.1.3",
+  "version": "0.1.5",
   "description": "A local court-jester sidecar for AI coding agents: review plans, commands, diffs, and final claims before they get too pleased with themselves.",
   "type": "module",
   "repository": {