docs/outreach/awesome-lists.md (added in #178) was written against main before #174 landed, and #174 closed the very issue its blocking verdict is gated on. Two rows are now false:
1. The "still instructs npx" claim is stale.
The doc states:
Root README still instructs npx paragent record … / npx paragent compile ….
As of 14397c1 the README does not. #174 replaced the Quick Start with the clone + npm run recorder / npm run compile path. The only surviving mention of npx paragent is the explicit callout that it is not available yet:
> **`npx paragent` is not available yet.** The package is publishable (`bin`, `files`, ...
2. The verdict is gated on a closed issue.
Verdict: blocked until [#167] merges … After #167 lands with a clone-based Quick Start that works, re-run this checklist.
#167 is CLOSED (2026-08-21T20:47:55Z, by #174), and the Quick Start is clone-based now. The precondition the doc names as blocking has been met.
What is genuinely still blocking
The other half of that row is still true and should stay: npm view paragent returns 404 — the package is not on the registry. #174 added .github/workflows/release.yml but cutting a release still needs an NPM_TOKEN secret. So the submission is still reasonably blocked; it is blocked on publication, not on README honesty.
Suggested fix
Re-run the preconditions checklist against current main and rewrite the install-path row + verdict so the blocker is "package not published (needs NPM_TOKEN)" rather than "README is dishonest (#167)". Keep the no-metrics constraint and the draft entries as-is.
Found while reviewing #178. Does not block merging #178 — the document's structure and its "don't submit yet" conclusion are both still correct, only the stated reason is out of date.
docs/outreach/awesome-lists.md(added in #178) was written againstmainbefore #174 landed, and #174 closed the very issue its blocking verdict is gated on. Two rows are now false:1. The "still instructs npx" claim is stale.
The doc states:
As of
14397c1the README does not. #174 replaced the Quick Start with the clone +npm run recorder/npm run compilepath. The only surviving mention ofnpx paragentis the explicit callout that it is not available yet:2. The verdict is gated on a closed issue.
#167 is CLOSED (2026-08-21T20:47:55Z, by #174), and the Quick Start is clone-based now. The precondition the doc names as blocking has been met.
What is genuinely still blocking
The other half of that row is still true and should stay:
npm view paragentreturns 404 — the package is not on the registry. #174 added.github/workflows/release.ymlbut cutting a release still needs anNPM_TOKENsecret. So the submission is still reasonably blocked; it is blocked on publication, not on README honesty.Suggested fix
Re-run the preconditions checklist against current
mainand rewrite the install-path row + verdict so the blocker is "package not published (needsNPM_TOKEN)" rather than "README is dishonest (#167)". Keep the no-metrics constraint and the draft entries as-is.Found while reviewing #178. Does not block merging #178 — the document's structure and its "don't submit yet" conclusion are both still correct, only the stated reason is out of date.