Keep public authority versions aligned with their manifests

[rmcdaniel]

Problem

The 2.0 Platform Conformance Suite page says its linked durable-workflow.v2.platform-conformance.suite manifest is version 38, while /platform-conformance-contract.json declares version 40. Its immediate Platform Protocol Specs neighbor says the protocol catalog is version 15, while /platform-protocol-specs.json declares version 16. The human-readable authority identity therefore disagrees with the public machine-readable authority.

Acceptance criteria

• Both 2.0 authority pages display the version declared by their corresponding published manifest.
• Build validation detects semantic authority-version drift without depending on headings, paragraph order, or Markdown layout.
• Public discovery links and catalog entries remain consumer-resolvable.

Delete when the deployed pages and both public manifests agree and the semantic drift validation is enforced.