For developers maintaining Theme Elementary itself. Downstream theme developers should start with Getting Started and Local development.
The maintenance guide covers:
Knowledge graph covers optional code-navigation setup and refreshes.
Documentation and smoke results must identify the theme commit and installed dependency revisions. The guides target main and changes built on it; do not assume a separately installed dependency checkout has the same behavior.
The registry-bypass pilot from the former docs/internal-testing.md is retired: the npm declaration installs @rtcamp/wp-tooling from the npm registry, and Composer resolves the framework from Packagist. Local source overrides are only for deliberate dependency development.
The remaining validation workarounds have an applicable revision and a retirement condition. Recheck their status when the theme or its dependencies change.