Audit and polish CommandLayer public site

[GsCommand]

Motivation

• Shorten and focus the homepage title and hero to make the product message clearer and prioritize Claim/Verify/Live Proof CTAs.
• Remove or replace stale/internal customer-facing copy and ensure Claim page copy accurately reflects ERC-8004 tracking vs confirmed onchain registration.
• Make the verification stack explicit (ENS, ERC-8004, agent card, CLAS, VerifyAgent) and add basic SEO and discovery artifacts for consistent public previews.

Description

• Updated public/index.html to change the <title>, homepage meta description, Open Graph and Twitter metadata, add a compact hero (Verifiable proof for AI agent actions.), new hero subheadline, and prioritized CTAs (/claim.html, /verify.html, /proof.html).
• Inserted a concise verification stack section and five-card/row explanation and added homepage SoftwareApplication JSON-LD structured data plus small CSS for the stack layout.
• Added canonical, og:*, and twitter:* tags to the requested key pages (index, claim, verify, proof, receipts, protocol, capabilities, docs, sdk-records, runtime, mcp, schemas, integrations) and updated navigation to surface the Verifier link while preserving existing routes and demos.
• Cleaned public-facing copy across public/ to remove internal phrases and replace with customer-safe language (kept Claim Beta truth about prepared/pinned/tracking vs confirmed registration and ENSIP-25 verification); preserved Claim UI IDs/classes and JS behavior.
• Added public/robots.txt and public/sitemap.xml containing only the approved public pages and avoided admin/API/private or preview URLs.

Testing

• Ran npm test: 165 tests passed and 4 tests failed; the failing tests relate to ERC-8004 registration/pinning and test fixtures (agent-registrations.test.js, two api-admin-pin-agent-cards.test.js cases, and claim-activation-pipeline.test.js) and are unrelated to static public-site content changes.
• Ran npm run check:links: passed; all local links and assets resolved across the site.
• Ran grep/rg checks for prohibited phrases and they were not found under public/ (passed).
• Validated sitemap.xml parse and ran a simple SEO presence check showing required canonical/OG/Twitter tags present on required pages (passed).
• Could not perform live production validation of https://www.commandlayer.org/claim.html from this environment because outbound HTTPS CONNECT returned 403 and DNS resolution was unavailable, so no deployment staleness root cause could be determined here.

---

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	Jul 21, 2026 3:10am
commandlayer-org	Ready	Preview, Comment	Jul 21, 2026 3:10am
commandlayer-org111	Ready	Preview, Comment	Jul 21, 2026 3:10am

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 9d73405fbf

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Add the referenced social preview image

When social crawlers render any of the newly tagged pages, this URL resolves to no deployed asset: a repo-wide search and the commit tree show no public/og-image.png. Consequently both the Open Graph and Twitter large-image cards point at a 404, defeating the preview metadata added here; add the asset under public/ or reference an existing image.

Useful? React with 👍 / 👎.

[chatgpt-codex-connector]

Wrap the expanded navigation at tablet widths

On pages that rely on public/css/site.css, the navigation remains a non-wrapping flex row until the max-width: 900px breakpoint. Adding another top-level item makes the roughly 204px-wide logo, grid gaps, and ten links exceed the 90vw container across an additional band of tablet/small-desktop widths; because body also sets overflow-x:hidden, the trailing Claim/GitHub links are clipped rather than wrapped. Apply the responsive layout earlier or allow .nav-links to wrap.

Useful? React with 👍 / 👎.

[chatgpt-codex-connector]

Describe ERC-8004 as discovery rather than proof

For namespaces created through the current Claim Beta flow, this headline overstates what ERC-8004 establishes: claim.html says the flow only prepares discovery tracking and marks registration verified after onchain confirmation, while the cards immediately below label ENS as identity and ERC-8004 as discovery. Saying ERC-8004 unconditionally “proves who the agent is” can therefore present an unregistered, merely tracked agent as identity-proven; align the headline with the discovery/registry semantics used elsewhere on the site.

Useful? React with 👍 / 👎.