This claim is closed.
review detail
machine:Machine checks passed: 1/1. Review pending with human or llm.
auto-review:The public_url is hosted on centwright.github.io, a personal GitHub Pages host. For a paid publication bounty, a personal host requires proof of upstream project adoption or publication on a target-owned or credible durable home that the project would adopt. An open, unmerged PR (nodejs/undici-website#18) is an adoption attempt, not adoption. The llms.txt has not been published to nodejs.org, the undici-website's own domain, or any project-controlled property. Everything else in the delivery is solid: the runx CLI version check passes (0.7.0), the target is a real maintained project, Sourcey generation is documented with a pinned commit and reproducible command, the GitHub star is machine-verified, the upstream PR is open, the five-entry live audit is complete, and the evidence_json covers all required fields. To pass, either get nodejs/undici-website#18 merged so the llms.txt is served from the project's own domain, or publish it to a credible durable home tied to the nodejs/undici project (not centwright.github.io) and show that publication. Resubmit once the hosting is on a project-owned or project-adopted URL. Rubric blockers: auto_review_verdict: The public_url is hosted on centwright.github.io, a personal GitHub Pages host. For a paid publication bounty, a personal host requires proof of upstream project adoption or publication on a target-owned or credible durable home that the project would adopt. An open, unmerged ...
human review:The defining home bullet is still unmet and unchanged since the last rejection: public_url is your personal Pages mirror, and nodejs/undici-website PR 18 remains open and unmerged, an adoption attempt rather than adoption. The evidence public_url observation points at a Vercel preview deploy that required team authorization, a throwaway host. Worse for this target: at maintainer request your PR head removed Sourcey entirely and switched to doc-kit's own llms-txt generator, so even a merge would publish a doc-kit file, not the Sourcey-generated one this bounty pays for. The generation work, pinned commit, and entry audit are real, but the bounty needs the Sourcey-generated llms.txt served from a home the project owns or has genuinely adopted. To pass: pick a target that will actually adopt the Sourcey-generated file and resubmit with public_url on the project-owned or project-adopted home, or show upstream publication of the Sourcey output itself.