Static route contract
Fourteen generated HTML files, twelve canonical sitemap entries, and no redirect or error route leaked into discovery.
Inspect FT-01Developer tools are easy to praise and hard to evaluate. DevAwesome publishes the setup, the failure, and the evidence needed to disagree with a verdict.
// No verdict without a declared rig
{
"surface": "developer tool",
"environment": "required",
"failure_case": "required",
"reviewer": "not independent"
}
// Publication gate
STATUS PASS — TWO RIGS PUBLISHEDA useful test shows where the claim stops. Versions, inputs, costs, failures, limitations, and conflicts belong beside the conclusion, not in a footnote.
The first release tests the toolchain that publishes this site. Both rigs are public, versioned, and explicitly marked as not independently reviewed.
Fourteen generated HTML files, twelve canonical sitemap entries, and no redirect or error route leaked into discovery.
Inspect FT-01The matching manifest installed offline. A deliberate mismatch stopped with ERR_PNPM_OUTDATED_LOCKFILE.
Inspect FT-02The former newsletter is not republished. Two old issue URLs have relevant live links, so each now answers that specific click with a new, independently written project note and an explicit ownership boundary.
Unknown issue paths stay unresolved. We only rebuild a target when its topic, live source, rights boundary, and reader intent are documented.
The domain changed hands. Former issues, authors, subscribers, consent, audience figures, and endorsements did not.