Static route contract
Every registry-backed canonical document carries the same crawlable noindex directive; the redirect-only alias is covered by the response header; the hold sitemap contains no indexable URLs.
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 — THREE 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 current release tests its publishing toolchain and a browser-facing integrity module. All rigs are public, versioned, and explicitly marked as not independently reviewed.
Every registry-backed canonical document carries the same crawlable noindex directive; the redirect-only alias is covered by the response header; the hold sitemap contains no indexable URLs.
Inspect FT-01The matching manifest installed offline. A deliberate mismatch stopped with ERR_PNPM_OUTDATED_LOCKFILE.
Inspect FT-02The browser-facing core matched known vectors, normalized line endings, Unicode input, and a separate Node crypto implementation.
Inspect FT-03The 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.