Skip to content
Universal Manifest

Endpoint Smoke

Endpoint smoke checks verify adopter-visible behavior for:

  • standards/docs endpoints
  • resolver contract behavior (myum.net/{UMID}-style)

These checks complement journey proof; they do not replace it.

Local environment check

Section titled “Local environment check”

Prerequisites:

  • docs site available (default local base: http://127.0.0.1:4300)
  • resolver available (default local base: http://127.0.0.1:8787)

Run:

  • cd packages/universal-manifest && npm run smoke:endpoints:dev

Production environment check

Section titled “Production environment check”

Run:

  • cd packages/universal-manifest && npm run smoke:endpoints:prod

This additionally asserts:

  • published spec artifact URL(s), e.g. /ns/universal-manifest/v0.1/schema.jsonld
  • /404.html exists as a static output page

Resolver checks

Section titled “Resolver checks”

The smoke checks verify:

  • /health returns 200
  • /.well-known/myum-resolver.json returns 200
  • resolving by UMID and by b64u:{base64url(umid)} returns 200
  • contract headers exist (X-UM-Resolver-Contract, ETag, Cache-Control)
  • ETag revalidation yields 304

Reference contract:

  • Conformance → Resolver

Portability note

Section titled “Portability note”

The commands above use this repository’s reference tooling. Any equivalent smoke implementation is acceptable if it validates the same contract semantics and records auditable results.