Stabilize site direction before more page edits

[GsCommand]

We are moving across too many surfaces at once. Freeze direct page redesigns until the site is organized into a small execution plan.

Context from audit:

• Core product funnel: /index.html, /capabilities.html, /how-it-works.html, /verify.html, /docs.html, /quickstart.html
• Developer docs: /docs/wrap-your-agent.html, /sdk-records.html
• Protocol/reference: /trust-verification.html, /commons.html, /commercial.html, /agent-cards.html, /runtime.html, /licensing.html, /repositories.html
• Demo/dev-only: /verify-badge-demo.html, /ambient-verification.html, /demo.html
• No hard-delete candidates yet. Merge overlaps first.

New rule:
Do not delete pages yet.
Do not redesign random pages out of order.
Do not overwrite full HTML files unless the task explicitly requires a full page rebuild.

Execution order:

1. Restore capabilities.html to the last full good version and fix only nav if needed.
2. Lock the global nav labels and logo pattern.
3. Upgrade verify.html only: move "What gets checked" above verifier panel and convert proof links into a serious Proof Surfaces section.
4. Upgrade ambient-verification.html only after verify.html is stable.
5. Create /claim.html scaffold.
6. Create /agents.html scaffold.
7. Then revisit remaining reference pages for merge/cleanup.

Acceptance criteria:

• No PLACEHOLDER text anywhere.
• No REVERT_TO_PREVIOUS_VERSION_PLACEHOLDER anywhere.
• No accidental meta refresh pages.
• Main nav remains stable: Home, Capabilities, Verifier, SDK, Docs, GitHub.
• Page changes are small and scoped.
• Run available tests or report if none exist.

[GsCommand]

Yes, we can do it now. Scope is locked to two pages only: public/verify.html and public/ambient-verification.html.

Implementation plan:

1. verify.html

• Keep existing verifier JS and all IDs intact.
• Move the existing “What gets checked” section from the bottom to directly under the hero.
• Remove the soft inline Proof URLs row from the hero.
• Add a stronger “Proof surfaces” section with cards for:
  • Proof URLs: demo valid / demo tampered
  • Badge Demo
  • Ambient Verification
  • Wrap Your Agent / SDK
• Keep the verifier input/results panel below these sections.

2. ambient-verification.html

• Keep this as the automatic/ambient verification narrative.
• Make it explain automatic verification through URLs, badges, webhooks, SDKs, and agent-to-agent flows.
• Add the ambient flow: receipt reference → fetch receipt → verify checks → accept/reject action.
• Keep careful wording: schema-valid is not necessarily cryptographically valid; ENS/ERC-8004 assist discovery/identity but CLAS remains network-agnostic.

Do not touch other pages.
Do not edit capabilities.html in this pass.
Do not change global nav beyond keeping existing labels consistent.
Do not delete files.
Do not add /claim or /agents yet.

Acceptance criteria:

• /verify.html still imports /js/verify.js.
• IDs remain: loadSampleBtn, loadTamperedBtn, clearBtn, verifyBtn, receiptInput, resultCard, resultState, resultNote, checksList, metaRows.
• /ambient-verification.html links to /verify.html, /verify/r/demo-valid-receipt, /verify/r/demo-tampered-receipt, /verify-badge-demo.html, /how-it-works.html, and /docs/wrap-your-agent.html.
• No placeholder text.
• Run available tests or report if no test script exists.