Scope policy
The scope policy decides which indexed files count toward coverage.
It is in skills/auwai/scripts/scope.py.
Scope flow
Only the included set is planned for a full read. Excluded paths remain visible as counts and reasons.
Included
- Source code in the supported languages.
- Tests and fixtures.
- Documentation, including README and design pages.
- Configuration files.
- Infrastructure files.
- Migration and schema files.
- Build and packaging manifests.
Excluded
The policy excludes a path when any parent directory is in EXCLUDED_DIRS.
The current list includes .git, .auwai, node_modules, vendor, third_party,
external, deps, dist, build, target, out, obj, virtual environments,
and tool caches.
It also excludes:
- binary and archive suffixes;
- source maps, minified assets, and generated suffixes;
- lock files such as
package-lock.json,poetry.lock,uv.lock,Cargo.lock, andgo.sum.
Kind and language
Every included path gets a kind tag:
sourcetestsdocsconfiginfradataapiui
The language is derived from the suffix.
Unknown text files use text.
Skip reasons
A skipped file keeps the reason in the ledger. The current reasons include an excluded directory, a generated or lock file, an excluded suffix, an empty path, or a file outside the repository.
A full-read plan does not include an excluded file. The coverage report names the excluded count and the reason counts.
Current limits
The policy is a fixed module, not a project file yet.
A project cannot add a custom exclusion without changing the module.
bin/ is included because it often holds first-party scripts.
A generated file with an unusual name may pass the filter.