🌱 refactor: adopt PageShell across ladder/leaderboard/partners + fix shell DOM

[hivecommons-hive]

Refactor

Two things in one PR because they must land together:

1. Fix PageShell DOM shape. The shell shipped in refactor: introduce PageShell for the shared page scaffold (#7106) [architect] #7107 used
   absolute -z-10 with no opaque base — subtly different from the
   canonical scaffold every existing page uses:

   <div className="bg-[#0a0a0a] text-white overflow-x-hidden min-h-screen">
     <Navbar />
     <div className="fixed inset-0 z-0">
       <div className="absolute inset-0 bg-[#0a0a0a]" />
       <StarField density="medium" showComets cometCount={3} />
       <GridLines horizontalLines={21} verticalLines={18} />
     </div>
     <div className="relative z-10 pt-7">{children}</div>
     <Footer />
   </div>

   Since nothing had adopted the shell yet, this PR corrects it before
   the first callers land. New knobs: baseLayerClassName (pass false
   to omit), contentClassName (pass null to omit — for pages with
   their own content wrappers).

2. Adopt PageShell in the 4 pages that share the exact default
   scaffold + content wrapper (relative z-10 pt-7):

   • src/app/[locale]/ladder/page.tsx
   • src/app/[locale]/leaderboard/page.tsx
   • src/app/[locale]/leaderboard/[username]/page.tsx
   • src/app/[locale]/partners/page.tsx

   Net: −127 / +187 (of which +115 is the shell interface fix +
   expanded tests).

Validation

• npx tsc --noEmit clean on all four ported pages
• npx vitest run src/__tests__/PageShell.test.tsx → 13/13 pass
• Two pre-existing ESLint jsx-a11y warnings inside the ported pages
  are unrelated (untouched interactive elements)

Not in this PR

3 canonical pages have custom content wrappers and get a follow-up:

• src/app/[locale]/products/page.tsx — "relative z-10 text-center px-2 sm:px-4 pt-16 sm:pt-20 pb-2"
• src/app/[locale]/programs/page.tsx — "relative z-10 text-center px-4 pt-20 pb-2"
• src/app/[locale]/programs/[slug]/ProgramPageClient.tsx — variant outer + custom wrapper

Plus the coming-soon-*-page.tsx files listed in #7106.

Refs #7106 (partial: 3 variant-wrapper pages + coming-soon-* remain)

---

Filed by architect agent (ACMM L6 — full mode)

— hive: agent=architect backend=copilot model=claude-opus-4.7 copilot=1.0.88

[kubestellar-prow]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign clubanderson for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[netlify]

✅ Deploy Preview for kubestellar-docs ready!

Name	Link
🔨 Latest commit	5267322
🔍 Latest deploy log	https://app.netlify.com/projects/kubestellar-docs/deploys/6ab913cdb81e210008d78aeb
😎 Deploy Preview	https://deploy-preview-7108--kubestellar-docs.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[kubestellar-prow]

Hi @hivecommons-hive[bot]. Thanks for your PR.

I'm waiting for a kubestellar member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[github-actions]

Thank you for your contribution! Your PR has been merged.

Check out what's new:

• KubeStellar Console — Live multi-cluster dashboard
• Marketplace — Community extensions
• Knowledge Base — Troubleshooting and how-tos

Stay connected: Slack #kubestellar-dev | Multi-Cluster Survey