Polish Claim Beta copy for ERC-8004 tracking

[GsCommand]

Motivation

• Bring the public Claim page copy in line with current product capabilities by reflecting ENS signer records, agent card pinning, and ERC-8004 discovery tracking without implying that onchain registration or ENSIP-25 verification are complete.
• Remove internal PR/dev language and fragile “Session 1” phrasing so the page reads like a customer-facing Claim Beta experience.
• Keep all activation flows, wallet auth, key generation, agent card preview, and activation pipeline logic intact while clarifying status semantics (prepared/pinned/tracking/registered/verified).

Description

• Update the hero copy and subheadline to Claim Beta · ENS + ERC-8004 discovery tracking · CLAS-ready agents and to a customer-facing subheadline describing activation, signer records, pinning, and ERC-8004 metadata preparation.
• Add a new ERC-8004 discovery panel under the hero (.discovery-panel + .discovery-status) that explains current status items (cards can be generated/pinned, tracking rows prepared, onchain registration pending, ENSIP-25 unverified).
• Replace internal/examples and host-namespace examples with customer-facing acme examples and soften managed/assisted activation copy to state operator-reviewed provisioning and that onchain writes/registration/verifications are marked complete only after confirmation.
• Replace the pricing grid with a clear Claim Beta framing and remove messaging that implied immediate checkout availability; update the activation checklist and agent-card/ENS instruction copy accordingly.
• Make small JS string adjustments where copy was embedded (for example the activationModeInstruction text and the conditional string used by buildENSRecords) and add responsive CSS for the new panel, while leaving IDs, classes, function names, API paths, and wizard flow unchanged.

Testing

• Ran npm test: 165 of 169 tests passed and 4 tests failed; failures are related to ERC-8004/pinned-card orchestration and registry/pinning configuration (these failures are unrelated to the public/claim.html copy changes).
• Ran npm run check:links which passed and confirmed local links/assets resolve.
• Executed a structural Python check that validated the wizard still contains 8 steps and required UI elements (IDs such as walletConnectBtn, keygenResult, ensRecords, sdkConfig, agentCardJson, summaryGrid, and activationPipeline).
• Performed node --check /tmp/claim-inline.js to ensure inline script syntax is valid and ran git diff --check to ensure no whitespace/errors introduced; both checks passed; a browser screenshot check was not possible due to no headless browser binary in the 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	Jul 21, 2026 2:35am
commandlayer-org	Ready	Preview, Comment	Jul 21, 2026 2:35am
commandlayer-org111	Ready	Preview, Comment	Jul 21, 2026 2:35am

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 860f5d3c7d

ℹ️ 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]

Render ERC-8004 status before promising it in the pipeline

After a user submits or imports a claim with pinned cards, /api/claims/status returns the registration records in data.registrations, but renderActivationPipeline() only renders the existing nine pipeline fields and never reads those records. Consequently, the public Claim flow cannot display the advertised ERC-8004 registration, agent ID, or ENSIP-25 status—even when that status is available—so this text promises a tracking view that users do not receive.

Useful? React with 👍 / 👎.