ANNOUNCEMENT
Private Testing is planned VERY SOON
Selected candidates will soon be able to give the suite a real world test run and provide their feedback and opinions!
BUILD-BACKED EVIDENCE
CERTIFICATION EVIDENCE
Real build and runtime evidence showing which parts of CRESA have been tested, how they were validated and what the current result means.
Current certification status
Alerts & Engagement
PASS
Certification evidence is build-specific; live/manual evidence may still be required.
What does PASS mean?The defined certification requirements for this feature pack were met by the evidence recorded for this build.
HOW CERTIFICATION WORKS
From code check to certified result
CRESA separates automated proof from checks that need the real runtime or a human visual review.
Code and system behaviour are tested.
The real system is exercised in a running build.
Presentation behaviour is reviewed where required.
The defined requirements for the pack have passed.
PHASE 2 CERTIFIED PACK
Alerts & Engagement
Runtime alert scenarios and required build-specific visual reviews passed
PASS Automated + Runtime + Visual
◈ CORE SYSTEM CHECKS
Can CRESA start, communicate with OBS and run its browser systems correctly?
Core runtime
PASSEngine health endpoint responded
ValidationRuntime
OBS connection/plugin
PASSOBS WebSocket and MNV dock are connected
ValidationRuntime
Browser runtime
PASSEndpoint responded
ValidationRuntime
◈ ALERT FEATURES
Did each supported alert complete its required runtime and presentation lifecycle?
Follow
PASSRuntime and cleanup passed
ValidationRuntime + Visual
Sub
PASSRuntime, cleanup, and supported-preview visual review passed
ValidationRuntime + Visual
Resub
PASSRuntime, cleanup, and supported-preview visual review passed
ValidationRuntime + Visual
Bits
PASSRuntime and cleanup passed
ValidationRuntime
Gift Sub
PASSRuntime and cleanup passed
ValidationRuntime
Redeem
PASSRuntime and cleanup passed
ValidationRuntime
Stacked Alerts
PASSRuntime, cleanup, and supported-preview visual review passed
ValidationRuntime + Visual
Quiet Alerts
PASSRuntime, cleanup, and supported-preview visual review passed
ValidationRuntime + Visual
◈ RELIABILITY & RECOVERY
Does the alert system remain healthy when alerts repeat, transition or finish?
Alert Framework baseline
PASSClean idle baseline established
ValidationRuntime
Stacked Alerts — repeated run
PASSRuntime and cleanup passed
ValidationRuntime
Quiet Alerts — repeated run
PASSRuntime and cleanup passed
ValidationRuntime
Single → Stacked handoff
PASSRuntime and cleanup passed
ValidationRuntime
Quiet → Normal restoration
PASSRuntime and cleanup passed
ValidationRuntime
Browser health during alerts
PASSOBS/browser health remained available before and after alert scenarios
ValidationRuntime
Final alert clean state
PASSFramework idle, queue empty, presentation hidden, Quiet restored
ValidationRuntime
⌁ AUTOMATED RUN TOTALS
Raw automated totals are supporting evidence only. The certification verdict above is the evaluated Phase result.
475Passed
2Raw run failures
0Skipped
These raw totals are intentionally not used as the headline certification result. Certification combines automated, runtime and visual gates, and the public pack verdict reflects that evaluated evidence.
◫ CERTIFICATION HISTORY
Certification packs & runs
Each pack defines a stable test boundary. Every saved run is an immutable sanitised snapshot from a specific build.
PHASE 2
1 RUNAlerts & Engagement
Certification of MNV's Alerts & Engagement system, including alert presentations, routing, lifecycle, handoff, Quiet mode, cleanup and supporting runtime behaviour.
PUBLIC EVIDENCE BOUNDARY
What this page does not expose
Development Live reads only the sanitised public certification payload. Local file paths, private repository data, raw logs, tokens and internal diagnostic artefacts remain outside the public website.
Browse development updates