Skip to content

fix(docs): serve README images via jsDelivr (raw.githubusercontent 503s) - #514

Merged
cobusgreyling merged 1 commit into
mainfrom
fix/readme-images-jsdelivr-cdn
Aug 13, 2026
Merged

fix(docs): serve README images via jsDelivr (raw.githubusercontent 503s)#514
cobusgreyling merged 1 commit into
mainfrom
fix/readme-images-jsdelivr-cdn

Conversation

@cobusgreyling

Copy link
Copy Markdown
Owner

Summary

  • GitHub’s raw.githubusercontent.com CDN is intermittently returning 503 for every image under assets/visuals/, so the README and showcase show broken images even though the files are fine in git.
  • Point README, showcase (docs/index.html), and star-history page image URLs at jsDelivr (cdn.jsdelivr.net/gh/...@main/...), which consistently returns 200 for the same files.
  • After automated star-history SVG updates, purge jsDelivr cache so the chart does not stay stale.

Test plan

  • curl all README asset URLs on jsDelivr → 200
  • Same URLs on raw.githubusercontent.com → 503 (reproduces outage)
  • After merge: hard-refresh https://github.com/cobusgreyling/loop-engineering and confirm logo, LE5 hero, demo GIF, primitives, loop-cycle, patterns, star-history load

raw.githubusercontent.com is returning intermittent 503s for repo assets,
so GitHub-rendered README images fail to load. Point README, showcase, and
star-history pages at jsDelivr (cdn.jsdelivr.net/gh/...@main/...), which
consistently returns 200. Purge jsDelivr cache after star-history updates.
@cobusgreyling
cobusgreyling enabled auto-merge (squash) August 13, 2026 18:02
@github-actions

Copy link
Copy Markdown
Contributor

Thanks @cobusgreyling for contributing a docs improvement — visible, reviewable PRs like this grow the reference for everyone.

What happens next

  • Maintainer aims for same-day review on story, adopter, and scoped docs/example PRs (CONTRIBUTING.md).
  • good first issue PRs: comment on the linked issue so we can assign and close on merge.

More ways to help

— loop-engineering maintainers

@github-actions

Copy link
Copy Markdown
Contributor

Loop Readiness Audit

Score: 100/100 (L3)

Strong loop readiness — good candidate for L3 with explicit gates.

Top suggestions

  • Loop Ready 80+: version this loop for a fleet — npx @cobusgreyling/loop-init . --with-fleet
  • Loop Ready 80+: version this loop's memory — npx @cobusgreyling/loop-init . --with-memory
  • Loop Ready 80+: version this loop as a harness — npx @cobusgreyling/loop-init . --with-foundry · showcase https://github.com/cobusgreyling/harness-foundry/blob/main/docs/showcase.md
  • Scaffold a harness: npx @cobusgreyling/loop-init . --with-foundry (or npx @cobusgreyling/harness-foundry init --from loop-engineering:daily-triage)
  • Scaffold memory tiers: npx @cobusgreyling/loop-init . --with-memory

Posted by audit.yml · loop-audit docs

@cobusgreyling
cobusgreyling merged commit b449b4f into main Aug 13, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant