Warriors stun Lakers in overtime thriller to take 3-2 series lead
NBA • 2 hours agoLionel Messi scores twice in MLS Cup rematch to lift Inter Miami
Soccer • 3 hours agoPanthers clinch playoff berth with overtime winner against Lightning
NHL • 5 hours agoRory McIlroy fires record-tying 63 at Augusta to lead Masters by two strokes
Golf • 6 hours agoJon Jones announces comeback fight for October pay-per-view card
MMA • 8 hours ago
Dedicated governance surface for the shared /api/versions/*
contract. This redesign keeps every existing section and control in place,
but recasts the page in the Admin Console portal language so registry,
timeline, compare, retention, and health read as one operator workflow.
Inspect resource coverage, pilot posture, and known-good milestone snapshots.
Review the append-only audit chain, pilot history, and snapshot deltas from one flow.
Admin now owns retention review, sweep execution, and the drill-down folder links for snapshot content.
Validate append-only evidence, manifest integrity, and live-path readiness before expansion.
Inspect the shared registry, pilot control, and rollout posture from the first dedicated versioning surface. This page keeps the Monitoring shell while giving version history and retention work the same operator polish as Admin.
Phase 1 is still centered on filter-settings, but this table is
already driven by the shared registry so the next Tier A resources can drop
into the same surface without another bespoke admin view.
| Resource | Tier | Head | Updated | Versions | Disk | Health |
|---|---|---|---|---|---|---|
| Loading version registry... | ||||||
filter-settings.
The pilot resource already writes through versioned_write().
Use the inline control here for the common operator flow: inspect recent
history, compare snapshots, tag a known-good state, download payloads, or
perform a safe forward-write rollback.
magnetar-admin.html#versioning, where the Admin-owned left rail can expose sweep controls and folder drill-down links.The shared component below is the same contract mounted on the Listings Pipeline writer surface. Here it gets the room it needs for timeline review, rollback, tagging, and payload download before the same control spreads to more writers.
| Time | Action | Version | Actor | Message |
|---|---|---|---|---|
| Loading audit... | ||||
Compare now ships both structural JSON deltas and table-aware row changes. Pick any governed resource and inspect the same shared diff contract used by writer surfaces.
GET /api/versions/filter-settings/diff.
Structured row lanes render when a list-shaped table payload changes. Raw JSON remains visible as the canonical source of truth.
Loading compare options...
Queued restore jobs are now production-backed. Stage restores from any shared version-control surface, review them here, then execute, cancel, or undo them without breaking the append-only forward-write contract.
Queue requests come from the shared <version-control> component.
Each job preserves head immutability: execution always replays an older payload
as a new forward version instead of rewriting history.
Every tag, rollback, purge, and retention sweep records here. The log stays append-only and resource-agnostic so later rollouts do not need their own custom audit pages.
| Time | Resource | Action | Version | Actor | Message |
|---|---|---|---|---|---|
| Loading audit... | |||||
Health checks validate live-path reachability, snapshot readability, and SHA integrity. This is the operational readiness view that should stay green before the versioning rollout broadens.