chore: bump the cluster context pin

[ExtraToast]

Bumps the cluster context pin from e839b908 to 95dc39fc (JorisJonkers-dev/workspace#53).

Both contexts were pulled and diffed: cluster-context-public.yml and adapter-compat.yaml are byte-identical. The only substantive change is the sourceSha provenance field, 22b9d332 → 7ee477c1.

Proven on a control first — JorisJonkers-dev/auth-ui#36 rendered with all scorecard checks passing, including context_pinned, before this went out to the rest.

Read the deploy-preview render rather than the green tick.

[github-actions]

Deploy Preview — agents-api

Environments: production
Context ref: ghcr.io/jorisjonkers-dev/cluster-deploy-context-public@sha256:95dc39fc695694c8fb4b0c538d7fe13038d407c7302c3725c98f0496c6a83499
Workloads: 1 | Routes: 1 | Gatus endpoints: 1

Image refs

• agents-api: ghcr.io/jorisjonkers-dev/agents-api/agents-api@sha256:0000000000000000000000000000000000000000000000000000000000000000

SC-11 Readiness Scorecard

	Check	Status	Detail
✅	schema_pinned	pass
✅	context_pinned	pass
✅	no_latest_images	pass
✅	health_declared	pass
✅	route_owner_authmode_declared	pass
✅	rollback_retention_acknowledged	pass
✅	no_raw_secrets	pass
➖	stateful_policy_declared	not_applicable	deployment declares no stateful workloads
➖	raw_manifests_guarded	not_applicable	no workload enables rawManifests
➖	npm_signatures_verified	not_applicable	provenance is only evaluated when publishing an artifact

pass = ready · fail = blocks deployment · not_applicable = check does not apply

➖ 3 check(s) not applicable: stateful_policy_declared, raw_manifests_guarded, npm_signatures_verified

---

Updated by deploy-check on push to this PR.