From dde344efd1d188c561140d064d257b6032edadd0 Mon Sep 17 00:00:00 2001 From: Robey Beswick <88316323+RobeyBeswick@users.noreply.github.com> Date: Thu, 29 Oct 2026 17:41:56 +0100 Subject: [PATCH 1/5] chore(release): prepare 0.1.0 public launch --- CHANGELOG.md | 26 +++++++++++ NOTICE | 3 +- README.md | 11 ++--- SECURITY.md | 9 ++++ docs/COMPATIBILITY.md | 28 +++++++----- docs/PUBLISHING.md | 85 +++++++++++++++++------------------ docs/SETUP.md | 25 +++++------ docs/compatibility.local.json | 10 ++--- package-lock.json | 4 +- package.json | 3 +- 10 files changed, 120 insertions(+), 84 deletions(-) create mode 100644 CHANGELOG.md create mode 100644 SECURITY.md diff --git a/CHANGELOG.md b/CHANGELOG.md new file mode 100644 index 0000000..01b6ae1 --- /dev/null +++ b/CHANGELOG.md @@ -0,0 +1,26 @@ +# Changelog + +## 0.1.0 — Prototype + +First public prototype release. + +- Inspect selected POSIX-shell file and Git operations before an integrated agent + runs them, including risky deletion/restoration of protected or locally changed + files and remote history rewrites. +- Integrations are available for Claude Code, Codex, and OpenCode. Live canary + results and tested client versions are recorded in + [compatibility](docs/COMPATIBILITY.md). Antigravity support remains experimental; + live enforcement has not been verified. +- Install with `npm install --global nomeatproxy` (Node.js 22+ and Git required), + then run `nomeatproxy install ` and restart the agent. Codex users must + review and trust the hook through `/hooks`. + +### Limitations + +NoMeatProxy is a local accident guard, not a sandbox or a security boundary against +a malicious agent. It does not execute checked commands, and it does not inspect +all ways to change files or affect remote systems. Coverage is limited to selected +POSIX shell operations; arbitrary scripts, unsupported wrappers, PowerShell, and +cmd.exe operations may pass without inspection. A passing check means only that no +implemented rule blocked that command. See the [design](docs/DESIGN.md) and +[compatibility notes](docs/COMPATIBILITY.md) for scope and evidence. diff --git a/NOTICE b/NOTICE index 0d88da7..95a6e6a 100644 --- a/NOTICE +++ b/NOTICE @@ -1,6 +1,7 @@ src/shell/tokenize.ts and src/shell/parse.ts are adapted from PlanSentry. Copyright (c) 2026 plansentry contributors. -Source: https://github.com/RobeyBeswick/plansentry +Source: https://github.com/RobeyBeswick/plansentry (private repository; source is +not publicly available). PlanSentry is distributed under the MIT License. The permission notice and disclaimer in this project's LICENSE also apply to these files. diff --git a/README.md b/README.md index ae60176..9177efb 100644 --- a/README.md +++ b/README.md @@ -52,14 +52,10 @@ review when it’s time to step in. Requires **Node.js 22+** and **Git**. No model subscription for the guard. No Go compiler for the standard installation. Your finger may now leave the approval button. -An npm registry release is planned. Build and install from a checkout: +Install from npm: ```sh -git clone https://github.com/RobeyBeswick/nomeatproxy.git -cd nomeatproxy -npm ci -npm pack -npm install --global ./nomeatproxy-0.0.1.tgz +npm install --global nomeatproxy nomeatproxy install claude nomeatproxy doctor claude ``` @@ -227,7 +223,8 @@ permissions scoped to the work. Yes. It builds on PlanSentry’s approach: inspect the consequences and show why an operation needs a human. PlanSentry integration is planned; infrastructure protection -is not included in NoMeatProxy yet. The shell parser is adapted from PlanSentry. +is not included in NoMeatProxy yet. Some shell parsing code is adapted from PlanSentry; +its source repository is private and is not required to use NoMeatProxy. See [NOTICE](NOTICE). diff --git a/SECURITY.md b/SECURITY.md new file mode 100644 index 0000000..455e2e3 --- /dev/null +++ b/SECURITY.md @@ -0,0 +1,9 @@ +# Security policy + +NoMeatProxy is a prototype accident guard, not a sandbox or a security boundary +against a malicious agent. Please keep permissions and credentials appropriately +scoped. + +To report a suspected vulnerability, use +[GitHub's private vulnerability reporting form](https://github.com/RobeyBeswick/nomeatproxy/security/advisories/new). +Please do not disclose security reports in public issues. diff --git a/docs/COMPATIBILITY.md b/docs/COMPATIBILITY.md index 68c7831..df34f38 100644 --- a/docs/COMPATIBILITY.md +++ b/docs/COMPATIBILITY.md @@ -1,13 +1,18 @@ # Agent compatibility -Measured 2026-10-09. Raw sanitized results: [compatibility.local.json](compatibility.local.json). +Claude Code and Codex were measured 2026-10-09; OpenCode was retested +2026-10-29. Sanitized canary summaries: +[compatibility.local.json](compatibility.local.json). -| Agent | Version | Tested mode | Result | -| --- | --- | --- | --- | -| Claude Code | 2.1.295 | `--dangerously-skip-permissions` | Live canary verified | -| Codex | 0.162.0 | `--dangerously-bypass-approvals-and-sandbox`, with invocation-scoped hook trust bypass | Live canary verified | -| OpenCode | 1.18.30 | `--auto` | Live canary verified | -| Antigravity | Live version not checked | Documented `run_command` protocol | Adapter/configuration tests only | +| Agent | Version | Test date | Tested mode | Result | +| --- | --- | --- | --- | --- | +| Claude Code | 2.1.295 | 2026-10-09 | `--dangerously-skip-permissions` | Live canary verified | +| Codex | 0.162.0 | 2026-10-09 | `--dangerously-bypass-approvals-and-sandbox`, with invocation-scoped hook trust bypass | Live canary verified | +| OpenCode | 1.19.5 | 2026-10-29 | `--auto` | Live canary verified | +| Antigravity | Live version not checked | — | Documented `run_command` protocol | Adapter/configuration tests only | + +Claude Code and Codex have not been retested since 2026-10-09. Their listed +versions are the older tested versions, not a claim about current releases. ## What the live result establishes @@ -22,10 +27,11 @@ All three agents exited successfully without working around the block. The recorded host tool names were `Bash` for Claude/Codex and `bash` for OpenCode. This verifies enforcement under the tested permissive mode on that shell path. -The Claude and Codex canaries exercised the direct Node hook. The OpenCode canary -used its in-process plugin. The native resident path has separate parity and -failure-mode tests plus a benchmark; it has not yet been exercised through a -live agent in this run. +The Claude and Codex canaries exercised the direct Node hook. The OpenCode canaries +used its in-process plugin. The 2026-10-29 OpenCode run observed both the allowed +control and blocked disposable deletion, and preserved the sentinel. The native +resident path has separate parity and failure-mode tests plus a benchmark; it has +not yet been exercised through a live agent. This is not certification for every native tool, code-mode call, background process, shell continuation, remote tool, or future client version. The two diff --git a/docs/PUBLISHING.md b/docs/PUBLISHING.md index e8e16bf..749e682 100644 --- a/docs/PUBLISHING.md +++ b/docs/PUBLISHING.md @@ -8,31 +8,31 @@ The handoff itself does not publish a package or change repository visibility. | Area | Status | | --- | --- | -| Source | `main`; implementation last changed before this documentation handoff | -| Package | `0.0.1`, with `"private": true`; publishing is disabled | +| Source | `chore/public-launch`, release-preparation changes based on `main` | +| Package | `0.1.0`, publishing enabled in the release branch | | GitHub | Repository is private; no release or version tag exists | -| npm | No package found when checked on 2026-10-27; recheck before release | +| npm | Package returned 404 on 2026-10-29; this release machine is not logged in to npm | | CI | Latest `Check` run did not start its jobs because of a billing/spending-limit block | -| Live compatibility | Results dated 2026-10-09; refresh for the clients named in the launch | -| Public-content review | Basic text/history scan completed; dedicated secret scan, video, and Actions-log review remain | +| Live compatibility | OpenCode 1.19.5 verified 2026-10-29; Claude Code 2.1.295 and Codex 0.162.0 remain tested 2026-10-09; Antigravity is adapter-only | +| Public-content review | Gitleaks and Actions-log scans clean; artifact inspected; visual sampling every 2 seconds found only scripted demo content; audio review and signed-out link review remain | -Local verification on 2026-10-27 passed against commit `cdddb08`: +Local verification on 2026-10-29 passed on `chore/public-launch` with Node.js +22.23.4, npm 10.9.9, and Go installed: -- Typecheck and all 86 tests. -- Packed-package installation test: 33 files, approximately 38 KiB compressed. -- All eight native-transport tests. -- Evaluation corpus, including its explicitly documented coverage gaps. -- npm audit: zero reported vulnerabilities. +- `npm ci`, `npm run check` (80 passed, 6 native tests skipped pending the separate native run), and all eight native-transport tests. +- Packed-package installation test: 34 files, approximately 42 KiB compressed. +- Evaluation corpus: 16 benign cases, 17 covered hazards, and three explicit coverage gaps. +- `npm run demo -- --auto` and `npm pack --dry-run`; packed files exclude local reports, fixtures, native binaries, and the demo video. +- `npm audit`: zero reported vulnerabilities. `npm outdated` found no newer compatible versions; `npm update` made no dependency changes. +- `gitleaks git --redact .`: seven commits scanned, no leaks found. -These results are a baseline. Rerun verification after release changes and on the -personal laptop. The earlier pattern scan covered six commits and found no -obvious personal paths, internal domains, account IDs, or credential patterns; -it was not a complete secret or media review. +Rerun verification on the exact final `main` commit. Gitleaks does not replace +the remaining audio and signed-out link review. ## 1. Set up the personal laptop -- [ ] Install Git, Node.js 22 or 24 with npm, and the GitHub CLI. -- [ ] Authenticate the GitHub CLI with an account that can access this private +- [x] Install Git, Node.js 22 or 24 with npm, and the GitHub CLI. +- [x] Authenticate the GitHub CLI with an account that can access this private repository. Run `gh auth login` if needed, then clone: ```sh @@ -42,9 +42,9 @@ git status --short --branch npm ci ``` -- [ ] Install Go if validating the optional native transport. The standard npm +- [x] Install Go if validating the optional native transport. The standard npm package does not require Go; see [setup](SETUP.md#optional-fast-transport). -- [ ] Install and authenticate any agent clients used for live compatibility +- [x] Install and authenticate any agent clients used for live compatibility checks. Do not copy credentials or agent settings into this repository. - [ ] Confirm access to the npm account that will own the package: @@ -60,19 +60,18 @@ package name and update documentation and packaging tests before continuing. ## 2. Finish the public-content review -- [ ] Run a history-aware secret scan, for example `gitleaks git --redact .` +- [x] Run a history-aware secret scan, for example `gitleaks git --redact .` after installing Gitleaks, and inspect any findings. -- [ ] Review tracked files and commit metadata for personal paths, internal +- [x] Review tracked files and commit metadata for personal paths, internal URLs, account IDs, customer details, and secrets. Keep scan reports private. - [ ] Watch `docs/assets/nomeatproxy-video.mov` and inspect the embedded README video for private terminal content, notifications, paths, and identifiers. -- [ ] Review existing Actions logs and artifacts before changing visibility; +- [x] Review existing Actions logs and artifacts before changing visibility; they can become publicly accessible with the repository. -- [ ] Check links as an outside reader. `NOTICE` references PlanSentry, whose - repository was private at the previous review. Preserve the copyright and - license attribution; clarify source availability or publish the upstream - separately if intended. This release does not require making another - repository public. +- [ ] Check links as an outside reader. The PlanSentry source repository remains + private; its source availability is clarified in `NOTICE`. Preserve the + copyright and license attribution. This release does not require making + another repository public. Remove sensitive material from history as well as the current checkout if any is found, and rotate exposed credentials before publishing. @@ -92,11 +91,11 @@ git diff -- package.json package-lock.json `npm outdated` can exit nonzero when it finds newer versions. Review the output before continuing; do not treat every newer major as required release work. -- [ ] Confirm `package.json` and `package-lock.json` both report `0.1.0`, with +- [x] Confirm `package.json` and `package-lock.json` both report `0.1.0`, with publishing enabled. -- [ ] Review every dependency change and commit the lockfile. -- [ ] Keep Node types aligned with the minimum supported runtime. -- [ ] If changing the supported Node versions, update `engines`, documentation, +- [ ] Commit the reviewed lockfile. +- [x] Keep Node types aligned with the minimum supported runtime. +- [x] If changing the supported Node versions, update `engines`, documentation, and the CI matrix together. The handoff baseline uses TypeScript `5.9.3` and locked Node types `22.20.5`. @@ -110,16 +109,16 @@ matrix to pass. Action modernization can follow the first release. ## 4. Prepare the release documentation -- [ ] Update the quickstart in [README](../README.md) and [setup](SETUP.md) to +- [x] Update the quickstart in [README](../README.md) and [setup](SETUP.md) to use the registry installation below when the package is published. -- [ ] Update retained tarball examples from `0.0.1` to `0.1.0`. -- [ ] Add a root `CHANGELOG.md` entry for `0.1.0`, including supported operations, +- [x] Update retained tarball examples from `0.0.1` to `0.1.0`. +- [x] Add a root `CHANGELOG.md` entry for `0.1.0`, including supported operations, agent integrations, installation, and known limitations. - [ ] Add a root `SECURITY.md` with a working private reporting route. Configure that route before advertising it. -- [ ] Keep the prototype label, POSIX-shell coverage limits, and Antigravity's +- [x] Keep the prototype label, POSIX-shell coverage limits, and Antigravity's experimental status unless fresh evidence supports changing them. -- [ ] Keep benchmark claims tied to their measured runtime and transport. +- [x] Keep benchmark claims tied to their measured runtime and transport. The advertised native/resident timing is not the default Node CLI timing. - [ ] Update the npm milestone in [roadmap](ROADMAP.md) after publication succeeds. @@ -146,15 +145,15 @@ node scripts/compat.mjs codex node scripts/compat.mjs opencode ``` -- [ ] Verify each advertised integration observes the allowed control, blocks +- [x] Verify each advertised integration observes the allowed control, blocks the disposable deletion canary, and preserves the sentinel. -- [ ] Record actual client versions, test date, mode, and results in +- [x] Record actual client versions, test date, mode, and results in [compatibility](COMPATIBILITY.md). -- [ ] Sanitize any results copied to `docs/compatibility.local.json`; keep raw +- [x] Sanitize any results copied to `docs/compatibility.local.json`; keep raw transcripts, temporary paths, and authentication details out of Git. -- [ ] If a client cannot be validated, state the older tested version or narrow +- [x] If a client cannot be validated, state the older tested version or narrow the launch claim. Do not label an inconclusive run as a pass. -- [ ] Leave Antigravity experimental unless live enforcement is validated. +- [x] Leave Antigravity experimental unless live enforcement is validated. The harness invokes real clients and can consume their configured model usage. Its requests target a disposable test fixture. Follow the full scope and limits @@ -178,8 +177,8 @@ Run `test:native` on macOS/Linux with Go installed. If the optional transport is not tested on this machine, retain the earlier dated evidence and do not claim it was freshly validated. -- [ ] All applicable checks pass. -- [ ] Inspect the package file list: compiled JavaScript, declarations, +- [x] All applicable local checks pass. +- [x] Inspect the package file list: compiled JavaScript, declarations, documentation, and licensing are present; secrets, local reports, fixtures, native binaries, and the demo video are absent. - [ ] Review and commit release changes with a conventional commit message. diff --git a/docs/SETUP.md b/docs/SETUP.md index 2653fcc..90ac095 100644 --- a/docs/SETUP.md +++ b/docs/SETUP.md @@ -6,31 +6,30 @@ has its own requirements below. ## Install the CLI -An npm registry release is planned. Build and install from a checkout: +Install the published package from npm: ```sh -git clone https://github.com/RobeyBeswick/nomeatproxy.git -cd nomeatproxy -npm ci -npm pack -npm install --global ./nomeatproxy-0.0.1.tgz +npm install --global nomeatproxy ``` Already have a checkout? Start with `npm ci`. -For a prebuilt package, download and unzip the `nomeatproxy-npm` artifact from a -successful **Check** run in GitHub Actions, then run the `npm install --global` -line above. The tarball includes compiled JavaScript and declarations, so -installing it requires no compiler. Use the packed tarball for global -installation. +For a prebuilt tarball, download `nomeatproxy-0.1.0.tgz` from the +[v0.1.0 GitHub Release](https://github.com/RobeyBeswick/nomeatproxy/releases/download/v0.1.0/nomeatproxy-0.1.0.tgz), +then install it with: + +```sh +npm install --global ./nomeatproxy-0.1.0.tgz +``` + +The tarball includes compiled JavaScript and declarations, so installing it +requires no compiler. Use the packed tarball for global installation. These npm commands work in a POSIX shell, PowerShell, or cmd.exe. Ensure the npm global executable directory is on your PATH, then check `nomeatproxy --version`. If PowerShell's execution policy blocks the npm shim, use `npm.cmd` and `nomeatproxy.cmd`, or use cmd.exe; no execution-policy change is required. -After the first npm release, the installation command will be -`npm install --global nomeatproxy`. That registry release is **not available yet**. Homebrew is a possible additional route for macOS/Linux, but no tap or formula has been published. npm is the first distribution route. diff --git a/docs/compatibility.local.json b/docs/compatibility.local.json index 7e571e0..d139ce1 100644 --- a/docs/compatibility.local.json +++ b/docs/compatibility.local.json @@ -57,10 +57,10 @@ }, { "agent": "opencode", - "version": "1.18.30", + "version": "1.19.5", "mode": "--auto", - "date": "2026-10-09T08:27:05.788Z", - "durationMs": 16564, + "date": "2026-10-29T16:35:15.179Z", + "durationMs": 13824, "exitCode": 0, "timedOut": false, "outcome": "canary-verified", @@ -72,13 +72,13 @@ "tool": "bash", "command": "printf NMP_ALLOWED", "denied": false, - "engineAndAdapterMs": 0.5539159999989351 + "engineAndAdapterMs": 0.8755409999994299 }, { "tool": "bash", "command": "rm -f '/do-not-delete.txt'", "denied": true, - "engineAndAdapterMs": 62.62275000000045 + "engineAndAdapterMs": 56.028582999999344 } ], "scope": "One benign control and one disposable deletion canary. Not a full tool-path or latency certification." diff --git a/package-lock.json b/package-lock.json index ca41ee8..0d94f5d 100644 --- a/package-lock.json +++ b/package-lock.json @@ -1,12 +1,12 @@ { "name": "nomeatproxy", - "version": "0.0.1", + "version": "0.1.0", "lockfileVersion": 3, "requires": true, "packages": { "": { "name": "nomeatproxy", - "version": "0.0.1", + "version": "0.1.0", "license": "MIT", "bin": { "nomeatproxy": "dist/cli.js" diff --git a/package.json b/package.json index ee311b9..c5bc3f4 100644 --- a/package.json +++ b/package.json @@ -1,7 +1,6 @@ { "name": "nomeatproxy", - "version": "0.0.1", - "private": true, + "version": "0.1.0", "description": "A local safety net for autonomous coding agents.", "type": "module", "license": "MIT", From 7e30fa2743af2e63ec81c251c10c7fbaeab2d589 Mon Sep 17 00:00:00 2001 From: Robey Beswick <88316323+RobeyBeswick@users.noreply.github.com> Date: Thu, 29 Oct 2026 17:46:44 +0100 Subject: [PATCH 2/5] docs(release): update checklist progress --- docs/PUBLISHING.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/PUBLISHING.md b/docs/PUBLISHING.md index 749e682..f92d209 100644 --- a/docs/PUBLISHING.md +++ b/docs/PUBLISHING.md @@ -93,7 +93,7 @@ before continuing; do not treat every newer major as required release work. - [x] Confirm `package.json` and `package-lock.json` both report `0.1.0`, with publishing enabled. -- [ ] Commit the reviewed lockfile. +- [x] Review dependency changes and commit the lockfile. - [x] Keep Node types aligned with the minimum supported runtime. - [x] If changing the supported Node versions, update `engines`, documentation, and the CI matrix together. @@ -181,7 +181,7 @@ it was freshly validated. - [x] Inspect the package file list: compiled JavaScript, declarations, documentation, and licensing are present; secrets, local reports, fixtures, native binaries, and the demo video are absent. -- [ ] Review and commit release changes with a conventional commit message. +- [x] Review and commit release changes with a conventional commit message. Stage specific intended files rather than generated reports or credentials. - [ ] Push the branch and merge through a reviewed pull request: From 44fdf3fa4c1862c00b8bd17a70108506342ac43d Mon Sep 17 00:00:00 2001 From: Robey Beswick <88316323+RobeyBeswick@users.noreply.github.com> Date: Thu, 29 Oct 2026 17:49:47 +0100 Subject: [PATCH 3/5] fix(package): exclude publishing checklist from npm tarball --- README.md | 2 +- docs/PUBLISHING.md | 13 +++++++------ package.json | 15 ++++++++++++++- scripts/test-package.mjs | 2 ++ 4 files changed, 24 insertions(+), 8 deletions(-) diff --git a/README.md b/README.md index 9177efb..f91bf5d 100644 --- a/README.md +++ b/README.md @@ -241,7 +241,7 @@ npm run evaluate # labeled examples, including known coverage gaps npm run bench # measure engine and hook overhead ``` -[Design](docs/DESIGN.md) · [Roadmap](docs/ROADMAP.md) · [Developer setup](docs/SETUP.md#development) · [Publishing checklist](docs/PUBLISHING.md) +[Design](docs/DESIGN.md) · [Roadmap](docs/ROADMAP.md) · [Developer setup](docs/SETUP.md#development) · [Publishing checklist](https://github.com/RobeyBeswick/nomeatproxy/blob/main/docs/PUBLISHING.md) ## 📄 License diff --git a/docs/PUBLISHING.md b/docs/PUBLISHING.md index f92d209..d383713 100644 --- a/docs/PUBLISHING.md +++ b/docs/PUBLISHING.md @@ -20,11 +20,11 @@ Local verification on 2026-10-29 passed on `chore/public-launch` with Node.js 22.23.4, npm 10.9.9, and Go installed: - `npm ci`, `npm run check` (80 passed, 6 native tests skipped pending the separate native run), and all eight native-transport tests. -- Packed-package installation test: 34 files, approximately 42 KiB compressed. +- Packed-package installation test: 35 files, approximately 39 KiB compressed. - Evaluation corpus: 16 benign cases, 17 covered hazards, and three explicit coverage gaps. -- `npm run demo -- --auto` and `npm pack --dry-run`; packed files exclude local reports, fixtures, native binaries, and the demo video. +- `npm run demo -- --auto` and `npm pack --dry-run`; the package includes the changelog and security policy, excludes this publishing checklist, local reports, fixtures, native binaries, and the demo video. - `npm audit`: zero reported vulnerabilities. `npm outdated` found no newer compatible versions; `npm update` made no dependency changes. -- `gitleaks git --redact .`: seven commits scanned, no leaks found. +- `gitleaks git --redact .`: nine commits scanned, no leaks found. Rerun verification on the exact final `main` commit. Gitleaks does not replace the remaining audio and signed-out link review. @@ -178,9 +178,10 @@ not tested on this machine, retain the earlier dated evidence and do not claim it was freshly validated. - [x] All applicable local checks pass. -- [x] Inspect the package file list: compiled JavaScript, declarations, - documentation, and licensing are present; secrets, local reports, fixtures, - native binaries, and the demo video are absent. +- [x] Inspect the package file list: compiled JavaScript, declarations, product + documentation, changelog, security policy, and licensing are present; the + publishing checklist, local reports, fixtures, native binaries, and demo video + are absent. - [x] Review and commit release changes with a conventional commit message. Stage specific intended files rather than generated reports or credentials. - [ ] Push the branch and merge through a reviewed pull request: diff --git a/package.json b/package.json index c5bc3f4..82ed27c 100644 --- a/package.json +++ b/package.json @@ -17,7 +17,20 @@ ".": { "types": "./dist/engine.d.ts", "default": "./dist/engine.js" }, "./opencode": { "types": "./dist/adapters/opencode.d.ts", "default": "./dist/adapters/opencode.js" } }, - "files": ["dist/**/*.js", "dist/**/*.d.ts", "docs/*.md", "README.md", "LICENSE", "NOTICE"], + "files": [ + "dist/**/*.js", + "dist/**/*.d.ts", + "docs/BENCHMARKS.md", + "docs/COMPATIBILITY.md", + "docs/DESIGN.md", + "docs/ROADMAP.md", + "docs/SETUP.md", + "README.md", + "CHANGELOG.md", + "SECURITY.md", + "LICENSE", + "NOTICE" + ], "scripts": { "build": "node scripts/build.mjs", "prepare": "npm run build", diff --git a/scripts/test-package.mjs b/scripts/test-package.mjs index d8217b6..471d247 100644 --- a/scripts/test-package.mjs +++ b/scripts/test-package.mjs @@ -23,6 +23,8 @@ try { assert.ok(files.includes('dist/cli.js')); assert.ok(files.includes('dist/adapters/opencode.js')); assert.ok(files.includes('dist/engine.d.ts')); + assert.ok(files.includes('CHANGELOG.md') && files.includes('SECURITY.md')); + assert.ok(!files.includes('docs/PUBLISHING.md')); assert.ok(files.includes('LICENSE') && files.includes('NOTICE')); assert.ok(!files.some(f => /nomeatproxy-hook|\.local\.json|node_modules|^test\/|^src\//.test(f)), files.join('\n')); const prefix = join(stage, 'prefix with spaces'); From be30fdcc2349862a308f997a55a5d3ecb0e9bbb8 Mon Sep 17 00:00:00 2001 From: Robey Beswick <88316323+RobeyBeswick@users.noreply.github.com> Date: Thu, 29 Oct 2026 18:36:54 +0100 Subject: [PATCH 4/5] docs(release): refresh public status and demo link --- README.md | 2 -- docs/PUBLISHING.md | 38 +++++++++++++++++++------------------- 2 files changed, 19 insertions(+), 21 deletions(-) diff --git a/README.md b/README.md index f91bf5d..2a39373 100644 --- a/README.md +++ b/README.md @@ -103,8 +103,6 @@ faster hook transport. Homebrew distribution is not published yet. ## 🎬 Demo -https://github.com/user-attachments/assets/b013d012-d3b3-4b5c-8163-b9f8041cd38a - [Download the MOV](docs/assets/nomeatproxy-video.mov) Run the repeatable walkthrough from a checkout: diff --git a/docs/PUBLISHING.md b/docs/PUBLISHING.md index d383713..77449e7 100644 --- a/docs/PUBLISHING.md +++ b/docs/PUBLISHING.md @@ -10,24 +10,24 @@ The handoff itself does not publish a package or change repository visibility. | --- | --- | | Source | `chore/public-launch`, release-preparation changes based on `main` | | Package | `0.1.0`, publishing enabled in the release branch | -| GitHub | Repository is private; no release or version tag exists | -| npm | Package returned 404 on 2026-10-29; this release machine is not logged in to npm | -| CI | Latest `Check` run did not start its jobs because of a billing/spending-limit block | +| GitHub | Repository is public; no release or version tag exists | +| npm | Package returned 404 on 2026-10-29; npm authentication is now confirmed, but the package is not published | +| CI | Five of six PR matrix jobs pass; macOS 22 is queued for a runner | | Live compatibility | OpenCode 1.19.5 verified 2026-10-29; Claude Code 2.1.295 and Codex 0.162.0 remain tested 2026-10-09; Antigravity is adapter-only | -| Public-content review | Gitleaks and Actions-log scans clean; artifact inspected; visual sampling every 2 seconds found only scripted demo content; audio review and signed-out link review remain | +| Public-content review | Gitleaks and Actions-log scans clean; artifact inspected; visual sampling every 2 seconds and user audio review found no private demo content; signed-out link check found a broken attachment URL, removed in this branch | Local verification on 2026-10-29 passed on `chore/public-launch` with Node.js -22.23.4, npm 10.9.9, and Go installed: +22.23.4/npm 10.9.9 and Node.js 24.22.2/npm 11.19.1, with Go installed: -- `npm ci`, `npm run check` (80 passed, 6 native tests skipped pending the separate native run), and all eight native-transport tests. -- Packed-package installation test: 35 files, approximately 39 KiB compressed. +- `npm ci` and `npm run check` passed on both Node versions. Node 22: 80 tests passed, 6 native tests skipped; separate native run passed all 8. Node 24: all 86 tests passed, plus all 8 native tests. +- Packed-package installation test: 35 files, approximately 39 KiB compressed, on both Node versions. - Evaluation corpus: 16 benign cases, 17 covered hazards, and three explicit coverage gaps. - `npm run demo -- --auto` and `npm pack --dry-run`; the package includes the changelog and security policy, excludes this publishing checklist, local reports, fixtures, native binaries, and the demo video. - `npm audit`: zero reported vulnerabilities. `npm outdated` found no newer compatible versions; `npm update` made no dependency changes. -- `gitleaks git --redact .`: nine commits scanned, no leaks found. +- `gitleaks git --redact .`: history scan and current-file scan found no leaks. -Rerun verification on the exact final `main` commit. Gitleaks does not replace -the remaining audio and signed-out link review. +Rerun verification on the exact final `main` commit and repeat the signed-out +link check after the release PR is merged. ## 1. Set up the personal laptop @@ -46,7 +46,7 @@ npm ci package does not require Go; see [setup](SETUP.md#optional-fast-transport). - [x] Install and authenticate any agent clients used for live compatibility checks. Do not copy credentials or agent settings into this repository. -- [ ] Confirm access to the npm account that will own the package: +- [x] Confirm access to the npm account that will own the package: ```sh npm login @@ -64,8 +64,8 @@ package name and update documentation and packaging tests before continuing. after installing Gitleaks, and inspect any findings. - [x] Review tracked files and commit metadata for personal paths, internal URLs, account IDs, customer details, and secrets. Keep scan reports private. -- [ ] Watch `docs/assets/nomeatproxy-video.mov` and inspect the embedded README - video for private terminal content, notifications, paths, and identifiers. +- [x] Watch `docs/assets/nomeatproxy-video.mov` and inspect the README video for + private terminal content, notifications, paths, and identifiers. - [x] Review existing Actions logs and artifacts before changing visibility; they can become publicly accessible with the repository. - [ ] Check links as an outside reader. The PlanSentry source repository remains @@ -114,7 +114,7 @@ matrix to pass. Action modernization can follow the first release. - [x] Update retained tarball examples from `0.0.1` to `0.1.0`. - [x] Add a root `CHANGELOG.md` entry for `0.1.0`, including supported operations, agent integrations, installation, and known limitations. -- [ ] Add a root `SECURITY.md` with a working private reporting route. Configure +- [x] Add a root `SECURITY.md` with a working private reporting route. Configure that route before advertising it. - [x] Keep the prototype label, POSIX-shell coverage limits, and Antigravity's experimental status unless fresh evidence supports changing them. @@ -190,18 +190,18 @@ it was freshly validated. git push -u origin chore/public-launch ``` -- [ ] Resolve the Actions billing/spending-limit block and obtain a successful - `Check` run for the final release commit. All six combinations of macOS, - Linux, Windows, and Node 22/24 should pass. +- [ ] Obtain a successful `Check` run for the final release commit. The latest + PR run passed five matrix jobs; macOS 22 is queued due runner capacity. All six + combinations of macOS, Linux, Windows, and Node 22/24 must pass. If changing visibility before rerunning CI is necessary, complete the public review first. Still require passing CI before publishing the package or post. ## 7. Make the source public and build the final tarball -- [ ] In GitHub repository settings, use **General → Danger Zone → Change +- [x] In GitHub repository settings, use **General → Danger Zone → Change visibility → Public** when ready to expose the reviewed source and history. -- [ ] Check the repository, README, embedded video, and documentation links in a +- [ ] Check the repository, README, video download, and documentation links in a signed-out browser. - [ ] After the release branch is merged, use the exact verified commit on main: From 8712645a83639f11f90c78379a7f007e68dc306c Mon Sep 17 00:00:00 2001 From: Robey Beswick <88316323+RobeyBeswick@users.noreply.github.com> Date: Thu, 29 Oct 2026 18:39:33 +0100 Subject: [PATCH 5/5] docs(release): record public launch readiness --- docs/PUBLISHING.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/PUBLISHING.md b/docs/PUBLISHING.md index 77449e7..9738bb5 100644 --- a/docs/PUBLISHING.md +++ b/docs/PUBLISHING.md @@ -12,7 +12,7 @@ The handoff itself does not publish a package or change repository visibility. | Package | `0.1.0`, publishing enabled in the release branch | | GitHub | Repository is public; no release or version tag exists | | npm | Package returned 404 on 2026-10-29; npm authentication is now confirmed, but the package is not published | -| CI | Five of six PR matrix jobs pass; macOS 22 is queued for a runner | +| CI | All six PR matrix jobs passed on release head `be30fdc` on 2026-10-29 | | Live compatibility | OpenCode 1.19.5 verified 2026-10-29; Claude Code 2.1.295 and Codex 0.162.0 remain tested 2026-10-09; Antigravity is adapter-only | | Public-content review | Gitleaks and Actions-log scans clean; artifact inspected; visual sampling every 2 seconds and user audio review found no private demo content; signed-out link check found a broken attachment URL, removed in this branch | @@ -190,9 +190,9 @@ it was freshly validated. git push -u origin chore/public-launch ``` -- [ ] Obtain a successful `Check` run for the final release commit. The latest - PR run passed five matrix jobs; macOS 22 is queued due runner capacity. All six - combinations of macOS, Linux, Windows, and Node 22/24 must pass. +- [x] Obtain a successful `Check` run for the release candidate. All six jobs + passed on `be30fdc`; rerun after any additional release-content changes. The + matrix covers macOS, Linux, Windows, and Node 22/24. If changing visibility before rerunning CI is necessary, complete the public review first. Still require passing CI before publishing the package or post.