static.bridgic.ai

Static data source for bridgic clients. No build step — a repo path is the published path.

Probing endpoints…

Data contract

• A path in JSON is always repo-relative (e.g. static/logo.png), never a full URL. Clients join base + path — so moving to another domain or CDN later means changing one client constant instead of every file.
• The entry point is api/index.json; its endpoints map lists everything else. Clients hardcode only that one address and discover the rest from the response.
• Every asset has a primary and a mirror URL. Fall back to the mirror on timeout — github.io gets its transfers cut mid-stream on mainland-China networks (measured: 1 failure in 3).
• Responses are cached for 600s: cache-control: max-age=600, and ?v=2-style busting does not work (the query string is stripped out of the cache key). After replacing a file in place, clients may see stale bytes for up to 10 minutes.
• These are API endpoints, so clients must not cache them locally. Request with cache: 'no-cache' to revalidate every read — the origin sends an ETag, so an unchanged response costs a 304. This matters most on the mirror, which advertises max-age=604800: one fallback response would otherwise sit in the local cache for a week. The mirror's own 12h CDN cache is purged automatically on every publish.
• A missing path returns a 9379-byte HTML 404, not JSON. Clients must check res.ok first, or res.json() throws an opaque parse error.

Endpoints

Static assets

Mirror

Fallback for when the primary origin is unreachable. Append any repo-relative path.

To bypass the 600s cache and verify production immediately, replace @main with a specific commit sha — that URL is permanently immutable.

Client usage

Full implementation in examples/staticBridgicClient.ts, ready to copy into apps/electron/src/renderer/lib/.