Normalize public site footers and update status/version line

[GsCommand]

Motivation

• Remove footer drift across all public-facing pages and make the footer content consistent while retaining the existing two-card / links-row / bottom-line layout pattern.
• Update the bottom status/version line to the exact approved text to reflect current published package versions and on-chain registration.

Description

• Updated the footer in 16 files to the shared structure (two upper cards, a single links row, and one bottom status line): public/about.html, public/agent-cards.html, public/commercial.html, public/commons.html, public/composer.html, public/demo-inner.html, public/demo.html, public/docs.html, public/faq.html, public/index.html, public/licensing.html, public/manifest.html, public/quickstart.html, public/repositories.html, public/roadmap.html, and public/runtime.html.
• Normalized upper-card copy to keep the cards short and consistent (CommandLayer summary on the left; Stack status summary on the right) and replaced varied stack copy with: Commons, Commercial, and Agent Cards share one signed execution surface.
• Standardized the footer links row everywhere to exactly: Docs, FAQ, Roadmap, Repositories, and GitHub (including target/rel attributes preserved for external link).
• Replaced all legacy/outdated bottom lines and removed variants such as Protocol v1.1.0 and other inconsistent wording with the exact new bottom line: Commons v1.1.0 · Commercial v1.0.0 · Agent Cards v1.0.0 · ERC-8004 registered, while preserving existing classes, spacing, and styling hooks.

Testing

• Ran automated validation that all pages now share a single footer implementation using a small python check that groups footer blocks and reports unique implementations, and the check found a single shared footer across all 16 pages; the script completed successfully.
• Executed an automated presence-check script (inline python assertions) that verified each footer contains the two-card row, both column titles, the five required links, the GitHub external link, and the exact new status/version line; all assertions passed for every file.
• Searched the site with ripgrep (rg) to confirm the old Protocol v1.1.0 wording no longer appears and to count occurrences of the new exact status line; the searches returned results consistent with the changes and no failures were observed.
• All automated checks passed across the 16 updated public HTML files; a live screenshot visual check was not performed in this environment.

---

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	Mar 19, 2026 2:39am
commandlayer-org	Ready	Preview, Comment	Mar 19, 2026 2:39am
commandlayer-org111	Ready	Preview, Comment	Mar 19, 2026 2:39am