docs: publish licensing, retract the standards-conformance claim, and clear the remaining claims

[LKSNDRTMLKV]

The last of the published-claim work. Stacked on #15.

The standards claim

The site said Odal "tracks them clause by clause in a maintained conformance matrix" and that its semantics "align to the published texts" — measured against a conformance document whose every verdict is formally withdrawn under the words "Nobody here has read these standards." The EN texts are paid and have not been purchased.

It now says we are tracking the series and not claiming conformance, and says why: no text purchased, no matrix, no basis on which alignment could be asserted. What we do build to are the open specifications anyone can read and check — GS1 Digital Link, W3C VC, did:web, AAS.

The unsourced publication dates went too: three mutually inconsistent internal dates exist for the EN series and none is pinned, so the page no longer names any.

Licensing is published

The launch gate was narrowed months ago so documentation of self-hosted software ships freely; this page was withheld anyway, and six references pointed at the resulting 404.

Its dependency-licence table is gone rather than corrected. It asserted "Redis — BSD 3-Clause", false since 2024. Only two of the six entries were verifiable from the local registry cache, and reconstructing the rest from memory is exactly the failure this whole pass exists to remove. A restated licence list is a claim that goes stale on someone else's schedule. The page now points at cargo license / cargo deny over the committed lockfile, which answers the question for the version a reader actually intends to deploy.

Everything else

• /api was the only docs page with no alpha banner, while its own comment claimed it had one through a Scalar plugin slot. The plugin was disabled. The banner is now static markup in the page, which no upgrade to the bundled reference can silently drop.
• Scalar's request client defaulted to relaying through proxy.scalar.com — a reader trying an endpoint against their own node would send it, and any API key they typed, through a third party. Now set to the no-proxy sentinel. Worth a runtime check before launch; this was read off the bundle's resolution logic, not observed.
• "Self-host in minutes. One compose file" contradicted the quick start, which builds the CLI from source. "GS1 Digital Link 1.2" had no version constant behind it. "or your ERP" read as a connector that does not exist.
• An orphaned component printed docker compose up commands contradicting the tested path — while its own header stated the rule it broke.
• Two unbuilt pages claimed "a small team" and offered "a supervised pilot — managed node, onboarding". Neither is true and both are one character from being live.
• A working-plan claim published as bare fact now records in its verify note that the primary text has not been read.
• Dead @types/react in a site with no React; an unclosed <Section> in the privacy policy that Astro's parser was silently repairing; a viteStaticCopy step publishing a duplicate favicon at a path nothing referenced, plus the two READMEs describing the arrangement it replaced.

Cross-repo

Carries a resync that picks up a corrected credential-standard version from dpp-engine — that PR must merge first, or CI's drift check will fail here.

Verification: build green · check 0/0/5 · 803 links across 44 pages resolve · leakage clean · spec matches.

[cloudflare-workers-and-pages]

Deploying odal-node-docs with    Cloudflare Pages

Latest commit:	bbea8d8
Status:	✅  Deploy successful!
Preview URL:	https://de294a03.odal-node-docs.pages.dev
Branch Preview URL:	https://docs-remaining-claims.odal-node-docs.pages.dev

View logs

[cloudflare-workers-and-pages]

Deploying odal-node-landing with    Cloudflare Pages

Latest commit:	bbea8d8
Status:	✅  Deploy successful!
Preview URL:	https://b03bee7f.odal-node-landing.pages.dev
Branch Preview URL:	https://docs-remaining-claims.odal-node-landing.pages.dev

View logs