Repository navigation
docs(cli): lead with Audit Trail, fix 0.x scaffold pin and localhost default - #289
Merged
Merged
Conversation
…default SCF reviewers open GitHub/npm first and the ask is centered on Audit Trail, so the README now leads with anchor/verify instead of the x402 quickstart. No section content changed, only order, plus one intro sentence. Two real bugs fixed along the way: - `nirium create x402`/`create bot` scaffolded `"nirium": "^0.16.0"`. Under 0.x semver that's `>=0.16.0 <0.17.0` - it silently excludes everything 0.17+ shipped (maxAmountPerPayment, Bazaar discovery). Bumped to ^0.19.0, same as this CLI's own `nirium` dependency. - `status`/`anchor`/`report` defaulted `--url` to `http://localhost:3002`, an agent this repo never runs - a fresh install failed with "unreachable" on every example. Default is now `https://nirium-agent.fly.dev` (testnet), and the stale "the port pnpm dev runs the agent API on in this monorepo" sentence is gone. Telemetry note re-verified against the real published dist/ of nirium 0.19.0 (not just the version bump) - same opt-in behavior as before, only the citation was stale. Verified: npm test (113/113), and `nirium create x402` generating a project that `npm install`s and actually starts (prints "cobrando en http://localhost:3000/premium/signals"). Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Eras256
approved these changes
Nov 12, 2026
Eras256
left a comment
Eras256
left a comment
Collaborator
There was a problem hiding this comment.
Reviewed all five files. The scaffold now pins nirium ^0.19.0 in both templates, the four --url defaults point to https://nirium-agent.fly.dev instead of localhost:3002, and 3.2.2 is consistent across package.json, the lockfile and the CHANGELOG. README leads with Audit Trail. CI green. Approved, thanks Monse.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
SCF #46 reviewers land on GitHub/npm, and the ask is centered on Audit Trail. This reorders the README so
anchor/verifycome first (one intro sentence added, nothing else in those sections changed), ahead of the x402 quickstart. Tone matches #288.Two real bugs found and fixed while in here:
nirium create x402/create botscaffolded"nirium": "^0.16.0". Under 0.x semver that's>=0.16.0 <0.17.0- every new project silently excluded everything 0.17+ shipped (maxAmountPerPayment, Bazaar discovery). Bumped to^0.19.0, matching this CLI's ownniriumdependency (also bumped).status/anchor/reportdefaulted--urltohttp://localhost:3002, an agent this repo doesn't run - every README example failed with "unreachable" on a fresh install. Chose option (a): default is nowhttps://nirium-agent.fly.dev(Nirium's testnet agent), so the CLI works out of the box with zero setup. Removed the now-false "the portpnpm devruns the agent API on in this monorepo" line.Also re-verified the telemetry note against the real
dist/ofnirium0.19.0 (downloaded the tarball, not just bumped the citation) - same opt-in behavior as documented, only the version number was stale.Verification
npm test- 113/113.nirium create x402 --name my-paid-apigenerates a project whosepackage.jsonnow pins^0.19.0;npm installpulls the realnirium@0.19.0, andnpx tsx src/server.tsstarts and prints💸 cobrando en http://localhost:3000/premium/signals.Next step
Once merged, publishing
nirium-cli@3.2.2to npm so the new README shows up there too (version bumped inpackage.jsonandCHANGELOG.mdin this PR already).🤖 Generated with Claude Code