Rebuild capabilities page into canonical protocol capability hub

[GsCommand]

Motivation

• Convert public/capabilities.html into an expandable protocol capability hub that prioritizes Trust Verification v1 while preserving the page layout and interactive build-plan functionality.
• Align visible language and outputs with the canonical proof model (metadata.proof, SHA-256, Ed25519, runtime signing) and remove duplicate/overlapping capability groups.
• Fix the footer and update ENS/MCP/SDK manifest outputs to use protocol-first field names and clear trust boundaries (MCP as bridge, runtime as signer).

Description

• Updated hero copy, badge, and CTAs to the requested text and actions (Add Trust Verification, View Proof) and tightened the page intro to the new capability definition.
• Reworked the 6-step grid to: Semantics, Request schema, Runtime execution, Canonical receipt, Discovery surface, Verification and made the copy explicitly mention metadata.proof, runtime signing, MCP bridge, verifier validation, and tamper invalidation.
• Consolidated capability cards into the eight required families with Trust Verification v1 first, removed/merged legacy groups, and updated verbs/badges accordingly.
• Kept and preserved interactive features including the build-panel, add-to-build-plan, export/copy actions, capability card grid, capability detail model, and localStorage build plan behavior.
• Updated programmatic outputs in-page: build manifest now emits type: 'commandlayer.capability_build_plan' and version: '1.0.0' with runtime: 'https://runtime.commandlayer.org', verifier: 'runtime /verify or configured verifier', and proof_model: 'metadata.proof'; SDK config uses privateKeyPem and keyId; ENS records now include cl.sig.pub, cl.sig.kid, cl.sig.canonical, cl.receipt.signer, and agent-endpoint[mcp]; MCP surface lists canonical tool names and states MCP is a bridge. Runtime signs. Verifier validates.
• Adjusted the Capability Detail Model labels/tooltips to the requested taxonomy and clarified that schema-valid is not the same as cryptographically verified, and replaced the small footer with a 3-column homepage-style footer (Product, Developers, Proof).
• Files changed: public/capabilities.html only.

Testing

• Ran npm install successfully in the project and dependency installation completed without errors.
• Ran npm test and all tests passed (26/26 passing).
• npm run build is not present in this repository and reported Missing script: "build".

---

Codex Task

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
commandlayer-commandlayer-org	Ready	Preview, Comment	May 20, 2026 10:59pm
commandlayer-org	Ready	Preview, Comment	May 20, 2026 10:59pm
commandlayer-org111	Ready	Preview, Comment	May 20, 2026 10:59pm