docs: npx paragent works now — retire the "not published" caveats - #185
Merged
Conversation
paragent@0.1.1 is on the registry with SLSA provenance, so three documents that were true this morning are now false. README: restore npx as the headline Quick Start and move the clone path back under the contributor <details>. Verified against the published tarball from a clean directory, not the working tree — `npx paragent record --fixture` writes a 6-step trajectory and `npx paragent compile` turns it into 6 rows, 3 pool-eligible, both exit 0. awesome-lists packet: the install-path precondition row and the "Ready to submit?" verdict both asserted `npm view paragent` returns 404. Flip them, and retire the #167 follow-up in Open questions. The verdict now says the mechanical preconditions are met while keeping the submission itself a founder decision — #138 reserves that, and whether a pre-gate project belongs on a curated list is unchanged by publishing. docs/README.md: the index row called the packet Blocked. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
github-actions
Bot
added
the
documentation
5 tasks
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
1 participant
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.
Closes #179.
Summary
paragent@0.1.1is on the npm registry with SLSA provenance (published by the release workflow on tagv0.1.1). Three documents asserted the opposite and are now false.README.md— restoresnpx paragent …as the headline Quick Start and moves the clone path back under the contributor<details>. This reverts the temporary shape #174 introduced, which was correct at the time:npxgenuinely 404'd then.docs/outreach/awesome-lists.md— the install-path precondition row and the "Ready to submit?" verdict both citednpm view paragent→ 404 as the blocker. Both flipped, plus the#167follow-up in Open questions retired and the staledocs/138-awesome-listsverification line refreshed.docs/README.md— index row called the packet Blocked.What I deliberately did not change
The awesome-lists verdict now reads "mechanical preconditions are met" rather than "ready to submit." Publishing closed the honesty gate; it does not answer whether a pre-gate project with no Track-1 number belongs on a curated list, and #138 reserves the submission for the founder. Flipping that to green would have been the same class of error the packet was written to prevent.
Test plan
npm run lint:docs— clean (68 docs)npx paragent record --fixture --out trajectory.json→ 6-step trajectory, exit 0npx paragent compile --in trajectory.json --out bundle.json→rows=6 pool_eligible=3, exit 0"value":/Set-Cookie/localStorage/sessionStorage→ nonenpm view paragent version→0.1.1;dist.attestations→https://slsa.dev/provenance/v1README.mdordocs/