Fix shared nav on home and claim pages

[GsCommand]

Motivation

• The previous change only added a class to the claim page nav and did not adopt the shared container-based nav structure, leaving layout conflicts and inconsistent nav behavior across pages.
• The intent is to unify the top navigation across pages using the known-good nav from public/protocol.html/public/sdk-records.html and to remove local CSS that conflicts with the shared pattern.

Description

• Replaced the full <nav>...</nav> block in public/index.html with the shared container-based nav structure used by public/protocol.html/public/sdk-records.html and preserved only Home as the active top-nav item.
• Replaced the full <nav>...</nav> block in public/claim.html with the same shared nav structure and preserved only Claim as the active top-nav item.
• Removed the conflicting width/margin rules from the claim page local .nav-inner CSS, leaving only alignment and sizing rules (min-height, padding, display:flex, align-items, justify-content, gap).
• Verified public/protocol.html was left unchanged and validated that each of public/index.html and public/claim.html contains exactly one <nav> block and the expected active items.

Testing

• Ran npm test, which executed the test suite and produced 35 test runs with 34 passing and 1 failing test; the failing test is POST /api/auth/verify surfaces dependency unavailable when siwe is missing in tests/api-auth.test.js and appears unrelated to the nav changes. (Test run completed; 34 passed, 1 failed.)
• Attempted npm run build and confirmed there is no build script in this repository, so a build step was not run.

---

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 22, 2026 6:17pm
commandlayer-org	Ready	Preview, Comment	May 22, 2026 6:17pm
commandlayer-org111	Ready	Preview, Comment	May 22, 2026 6:17pm