kevinveenbirkenbachandClaude Opus 5.5
6e776a5780
- Declare `__all__` in every package `__init__.py` whose `PROJECT_ROOT` is imported by its modules (163 packages), so the constant counts as exported; list every public name where the package defines more. - Empty the 15 package `__init__.py` files whose `PROJECT_ROOT` no module imports. - Declare the public API of `utils.github.variant.axes` in `__all__`, re-exports included, instead of silencing them with `noqa: F401`; the list matches the one `feature/store-i18n` already carries. - Use `import unittest.mock as mock` in `test_applications.py`, as the rest of the suite does. - Spell `_NON_PRINTABLE` in `utils/yaml_bootstrap.py` as the equivalent BMP-only positive class; it matches exactly the same 2111 code points as the old negated class across U+0000..U+10FFFF. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Application Role Tests 📦
Integration tests that enforce rules about roles which represent deployable applications: web-app-* roles MUST ship a README.md (required for the Web App Dashboard), every literal name compared against group_names in playbooks/roles MUST resolve to a real application_id, every applications['…'] / applications.get('…') / applications.name / get_domain('…') reference MUST name an existing application, and roles MUST NOT reach into applications[...] by subscript; they MUST use lookup('applications', …) or utils.roles.applications.config.get instead.
Tests in this directory MUST only cover application-level role rules. Identity checks tied to the application_id variable itself (presence, uniqueness, deprecation, folder-name prefix, ports/domain/run_after/dependency consistency) MUST live under id/. Generic structural role checks MUST live one level up under ../.
For framework, directory layout, and make test-integration usage see integration.md.