Enhancement: Promote rollups and retention workflows

[smiggleworth]

Audit classification

• Type: Enhancement
• Affected subsystem: Analytical and time-series workloads
• User/operator impact: The capability may exist only as Experimental or an unverified path, limiting operator confidence and making production support boundaries unclear.
• Current behavior: The relevant implementation or workflow is not yet promoted to the requested support level; existing behavior remains bounded by its documented status and evidence.
• Expected behavior/outcome: Verify the behavior against explicit promotion criteria, document supported and unsupported cases, and promote it only when the acceptance criteria are met.
• Deterministic evidence: Source-of-truth: the issue's linked repository documentation, tests, workflows, and benchmark contracts; baseline commit afb23d0. The existing scope and acceptance criteria below are the deterministic work record.
• Confidence and support status: Medium to high, based on repository documentation and existing contracts.; Experimental or promotion candidate; not a claimed bug.
• Related tracker: Audit: Cassie engine and Admin UI/UX gap backlog at afb23d0 #1

Scope

Complete the evidence required to promote rollups and retention from Experimental.

Source of truth

docs/experimental-promotion-criteria.md:20-26.

Acceptance criteria

• Prove refresh/enforcement idempotency, restart hydration, stale fallback, and dependent projection freshness.
• Expose stable metrics and diagnostics for operator windows and maintenance debt.
• Add benchmark evidence for declared fixture sizes and retention/refresh workloads.
• Update support/readiness status only after all common promotion gates pass.

Tracking: #1.

[smiggleworth]

Grouped in PR #44 (#44): promotion evidence matrix records existing local tests, missing same-commit or hosted evidence, and explicit unsupported boundaries. The surface remains not promoted until its row's gates are met.

[smiggleworth]

Local-only acceptance update: rollup refresh, idempotent retention, restart hydration, stale fallback, maintenance debt, and dependent freshness tests pass locally.

[smiggleworth]

Full-history re-audit at current main d0874ff: docs/promotion-evidence-matrix.md explicitly marks issue #23 Not promoted and names missing closure evidence. The prior close recorded only a local correctness slice, while the original issue requires promotion evidence and a support/readiness update. Remaining criteria: retained idempotency and operator-window benchmark evidence at declared fixture sizes, including dependent freshness. Dependency: #7 and/or the relevant compatibility or deployment-profile evidence lane. Next action: retain the named evidence, re-run the focused and full validation gates, and update Feature Support only if every common promotion criterion passes.

[smiggleworth]

Current-main re-audit at 8b84ee936986f586567530a2decee949d2b8f14c: deterministic correctness is strong—retention idempotency, restart lifecycle, stale rollup fallback, dependent projection freshness, rollup refresh after retention, maintenance debt, metrics, and the registered 100k Tier 5 retention/rollup owners are present.

The promotion gate is still incomplete because no retained passing canonical artifact currently proves time_series_retention_enforcement/100k and time_series_rollup_refresh/100k at the declared operator window. Canonical run 32505662069 terminated earlier in Tier 3, so its Tier 5 rows never executed; PR #158 repairs that upstream blocker but is not merged and canonical evidence has not been rerun.

Disposition: keep #23 open and Time-series access Experimental. Dependency: #7 / PR #158, followed by a passing unfiltered same-commit benchmark artifact whose Tier 5 rows and diagnostics are explicitly inspected. Next action after that evidence exists: publish the operator-window contract, add its focused documentation contract, run the required ladder, and promote only the evidenced rollup/retention subset.