The load-bearing spec (admin/specs/canonical-document-v1.md) plus a working signer/verifier pair. <page-info> now runs Web Crypto verification against vb:signature and updates the trust badge to verified, failed, or key-unavailable.
- Added
src/lib/canonicalize.js — single shared library imported by both signer and verifierscripts/sign-pages.js — Node CLI signer (lenient by default; --strict opt-in)scripts/generate-key.js — keypair generatorscripts/demo-keys/vb-release-demo.private.jwk — explicitly-labeled DEMO keypair so round-trip works out of the box/.well-known/content-keys/vb-release-demo.jwk + content-authenticity.json<page-info> #verifySignature replaces the stub trust assessment
Frontmatter-driven provenance metadata, JSON-LD mirroring, and four reference lens pages (changelog, glossary, sitemap, keyword index). <page-info auto> renders site-wide on doc pages with provenance frontmatter.
- Added
- generate-provenance-meta Cook plugin: emits §A public-standard meta tags + §B vb:* meta tags + JSON-LD from frontmatter
- /changelog/ — versioned release history (this page)
- /glossary/ — alphabetical term reference
- /sitemap/ — HTML sitemap for navigation
- /index-of/ — keyword/topic index across the docs
- Fixed
- page-info auto-mode now reads vb:provenance, vb:review, vb:status, vb:ai-tools, vb:version-url per meta-tag-contract-v1 (was reading the pre-Stage-0 content-* names and silently rendering blank)
Split the single data-trust attribute into three orthogonal dimensions: data-provenance (how content was made), data-review (review level), and data-status (publication state). data-trust is now reserved for runtime verification tier on the page-info badge. Retired <page-meta> in favour of <page-info>.
- Added
- admin/specs/meta-tag-contract-v1.md
- Changed
page-meta retired; use page-info insteaddata-trust="ai-assisted" → data-provenance="ai-assisted"