v1.2 + v1.2.1

QUBEai v1.2: Validation Gate for Real User Behavior

This release made browser-based human-path validation a release requirement for UI-facing changes.

Changelog (What Was Added)

Validation Gate policy: no UI release without browser evidence.
Validation report script with blocking detection.
Daily queue now includes validation readiness view.
v1.2.1 helper command to update validation status + artifacts in one call.

How You Leverage It

Use this as a quality firewall. If a button exists but does not work (like prior mic/push-to-talk issues), the release should not pass.

Quality gain: catches “works in code, fails in UX” defects

Operational gain: standard evidence format

Use This Now

control-plane/qubeai-ops/scripts/qubeai_validation_gate_report.sh

control-plane/qubeai-ops/scripts/qubeai_update_validation_status.sh \
  --id feat-YYYY-MM-DD-example \
  --browser-status pass \
  --code-test-status pass \
  --artifact "/tmp/browser-proof.png" \
  --note "Validated critical user path"

Run validation report before release decisions.
Attach browser evidence with helper command.
Ship only when browser-required items are pass.

Picture: Release Decision Rule

For UI-impacting work: Code Pass + Browser Pass = Release Eligible.