RAGE #44: repair real-stack E2E baseline after unified graph shell #46

Merged

lost-rob0t merged 11 commits from rage/44-real-stack-e2e-baseline into main

2026-08-25 10:45:55 +00:00

lost-rob0t commented

2026-08-25 10:13:17 +00:00

(Migrated from github.com)

Fixes #44.

The diagnostics captured by PR #45 / CI run 32830522781 prove the current main E2E tail is stale against the unified graph shell rather than an Auto-Dig lifecycle regression.

This candidate repairs only the failing repository-native E2E contract and retains failure artifacts while the baseline is being corrected:

assert the current Maltego graph layout control instead of the hidden legacy Graph layout label;
target exact radial category actions so Layout does not collide with Layout: ... commands;
use the current desktop Focus control;
expect the UI's locale-formatted large corpus counts (2,001);
dismiss an unrelated existing conflict notification before exercising bottom-of-workspace full-viewport controls, because the notice demonstrably intercepts pointer events;
carry the blocking Playwright HTML/trace artifact retention from #45 so any remaining RED is diagnosable.

No production graph behavior is changed. No E2E test is skipped, quarantined, marked optional, or allowed to fail. The existing baseline failures are the RED evidence for this CI-defect issue; exact-head CI must pass the entire repository suite, including packaged production smoke, before merge.

Related: #41, PR #43, PR #45.

Fixes #44. The diagnostics captured by PR #45 / CI run 32830522781 prove the current `main` E2E tail is stale against the unified graph shell rather than an Auto-Dig lifecycle regression. This candidate repairs only the failing repository-native E2E contract and retains failure artifacts while the baseline is being corrected: - assert the current `Maltego graph layout` control instead of the hidden legacy `Graph layout` label; - target exact radial category actions so `Layout` does not collide with `Layout: ...` commands; - use the current desktop `Focus` control; - expect the UI's locale-formatted large corpus counts (`2,001`); - dismiss an unrelated existing conflict notification before exercising bottom-of-workspace full-viewport controls, because the notice demonstrably intercepts pointer events; - carry the blocking Playwright HTML/trace artifact retention from #45 so any remaining RED is diagnosable. No production graph behavior is changed. No E2E test is skipped, quarantined, marked optional, or allowed to fail. The existing baseline failures are the RED evidence for this CI-defect issue; exact-head CI must pass the entire repository suite, including packaged production smoke, before merge. Related: #41, PR #43, PR #45.