Document protected release guidance surfaces

This commit is contained in:
axiomlogicnexus 2026-06-25 09:46:55 +00:00
parent e8b27022e8
commit 73bbf33c3d
2 changed files with 21 additions and 1 deletions

View file

@ -603,6 +603,20 @@ Latest same-day browser/distribution continuity follow-up still on `2026-06-24`:
- protected-route loading with preserved next-target sign-in and support escape hatches
- dashboard auth-health and release-authority fallback continuity
- public download and protected release-lane fallback continuity
- the next same-family protected release follow-through packet now also keeps
the signed-in dashboard, protected download center, and protected account
lane on one shared release-action decision surface driven by:
- live manifest viewer entitlement
- live checkout-target availability
- configured packaged-release targets
- degraded release-authority posture
- that shared protected surface now resolves the next operator move explicitly
instead of leaving it implicit across separate panels:
- direct package download when live entitlement plus a target URL are both ready
- operator or studio checkout when billing/provisioning is the real gap
- notices, release notes, pricing, or support when package publication or
launch configuration is the limiting factor
- a bounded degraded-authority recovery path when live manifest authority is unavailable
- the same bounded follow-up then reran the HyperTwist-owned refactor tools on
the current public-route continuity state:
- `scripts/run-hypertwist-sentrux-source-only.sh`

View file

@ -295,7 +295,13 @@ Current consolidated milestone snapshot:
shared browser auth layer now also refreshes and persists the local session
snapshot from that fresher manifest viewer truth and the protected dashboard
plus account surfaces now surface a compact live-authority sync notice
summarizing what changed, and the same auth layer now also clears stale
summarizing what changed, and the protected dashboard, protected
`/app/downloads`, and protected account lane now also resolve that same live
manifest plus checkout truth into one explicit operator-facing release-action
surface that chooses between direct package download, checkout or
provisioning, notices or release follow-through, and degraded-authority
recovery instead of leaving the next move implicit across separate panels,
and the same auth layer now also clears stale
stored sessions when shared auth is configured and `/api/auth/me` returns
`401` instead of preserving a false authenticated protected-shell posture,
and the runtime-readiness verifier now also probes the live anonymous