Fix broken codelab rendering: self-host codelab-elements assets

[Mrc0113]

Problem

All codelabs on https://codelabs.solace.dev render as unstyled raw HTML — the formatting is completely broken. The landing/menu page is unaffected.

Root cause: every codelab's index.html loads its styling + rendering engine from Google's public bucket storage.googleapis.com/claat-public/. Google locked that bucket down and all five assets now return 403 Forbidden:

• codelab-elements.css (styling)
• codelab-elements.js (upgrades the <google-codelab-*> custom elements into the paged layout)
• native-shim.js, custom-elements.min.js, prettify.js

Without the CSS/JS, the custom elements never load or get styled → raw scroll. This is a Google-side change, not a regression in this repo.

Fix

Repoint all five asset URLs in every codelab to the copies the site already self-hosts at /elements/codelab-elements/ (served from solace-dev-codelabs-site, verified returning 200 in production).

In-place URL swap only — deliberately not a claat re-export:

• Each codelab.json updated date is preserved (claat would rewrite them to export time).
• Diff is exactly the 5 asset lines per file, nothing else — easy to review.
• 53 files changed, 265 insertions / 265 deletions, 0 codelab.json touched.

Covers all 53 codelabs, including 13 legacy "Integration Guides" that have no markdown source and therefore can't be regenerated by claat.

Companion change

The claat export template is fixed separately in SolaceDev/google-tools#3 so all future exports emit these self-hosted URLs automatically (CI builds claat from that repo's main). This PR fixes the already-committed HTML.

Deploy note

This is a codelabs/**-only change, so export-codelab.yml / site-update.yml will not auto-trigger (they watch markdown/**). After merge, the solace-dev-codelabs-site submodule pointer must be bumped to redeploy via Netlify.

Verification

• grep -rc "storage.googleapis.com/claat-public" codelabs/ → 0 everywhere.
• All five /elements/codelab-elements/* URLs return 200 in prod.
• Per-file diff confirmed to touch only the 5 asset lines.

🤖 Generated with Claude Code

[solacecommunity-bot]

Thanks for opening up a PR and contributing to our open source codelabs!

Review process Guidelines

Once the PR is opened, tag at least one Technical Reviewer

Technical Reviewer Responsibilities

• Dry-run technical steps
• Review technical positioning/messaging
• Point out typos and potential formatting issues
• Technical Reviewer(s): "Approve" or "Request Changes" by navigating to the Files changed tab and click on the "Review Changes" drop down
  

Post Technical Review

A member of the Developer Advocate Team will review overall structure and merge into master which will push it to production

[Mrc0113]

Admin-merging this PR.

master branch protection requires the Build_Preview status check, but that check comes from netlify.yml, which is path-filtered to paths: markdown/**. This PR only changes generated files under codelabs/** (no markdown), so the Netlify workflow never runs and Build_Preview will never report a status — the PR is deadlocked, not slow.

The two checks that can run both passed (Broken_Link_Checker ✅, guidelines comment ✅). Using an admin override to merge since the required preview build cannot fire for a codelabs-only change.

Note: merging does not deploy on its own — the solace-dev-codelabs-site submodule pointer still needs to be bumped to redeploy via Netlify.