test-framework-architecture-audit

What this owns, and what it does not

This audit owns the framework's internal structure: how many tests reach the UI through an object model, how deep the inheritance chains run, how fixtures are scoped, how far helpers have sprawled, whether one naming convention is in force, whether waits and retries are consistent, whether the written conventions still describe the code, and whether CI is wired the way the framework assumes. Every finding is a cross-file pattern, invisible from inside a single test file, which is what separates this from any review that opens one spec and argues about a locator or an assertion.

Three neighbouring capabilities own adjacent ground. Do not duplicate them: