ahmido/TenantAtlas
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects 1 Releases Wiki Activity
b3e6dfdb7c
TenantAtlas/specs/375-ui-bloat-regression-guard/artifacts/follow-up-recommendations.md
ahmido 8efc8981a4 feat(guard): implement ui bloat regression guard (#446) 
Added UiBloatRegressionGuardTest to enforce known UI bloat and customer/auditor safety regression patterns across configured runtime UI source paths as defined in Spec 375.

Registered the test in Pest.php and added to TestLaneManifest.

Co-authored-by: Ahmed Darrazi <ahmed.darrazi@live.de>
Reviewed-on: #446
2026-06-13 09:03:36 +00:00

1.2 KiB
Raw Blame History

Follow-Up Recommendations

CI Strictness

  • Keep Spec 375 v1 as warn-first and heavy-governance-owned.
  • Consider CI hard-fail expansion only after allowlist cleanup and at least one stable maintenance cycle.
  • Candidate future hard-fail additions: repeated raw/internal customer-surface leaks, missing primary question on customer/auditor defaults, and ambiguous diagnostic entrypoints that misroute users to repair-only surfaces.

Manual Review Leftovers

  • UIBLOAT_ZERO_METRIC_CARD, UIBLOAT_REPEATED_STATUS, UIBLOAT_HEADER_ACTION_OVERLOAD, and diagnostic guidance rules should remain manual-review or warning by default until false-positive behavior is understood.

Evidence/System Browser Fixtures

  • Evidence and system surface browser fixture coverage remains a separate follow-up candidate. Spec 375 does not add browser coverage.

Browser Scorecard Integration

  • Integrating guard output with browser scorecards is deferred. V1 keeps source scanning and browser scoring separate.

Post-Productization Closeout Audit

  • A final browser closeout audit after guard stabilization remains useful, but it should be a separate spec because it would add browser lane cost and screenshot review scope.