Description
Phase 1 of #448. Correct the Bazel inventory, remove stale Bazel documentation, and
define the nested-module exception contract.
Not every nested module is in scope. nvsnap stays nested because its base image is
not publicly pullable, and there is a deliberate helper module and a vendored module.
The Phase 2 guard therefore needs an allowlist rather than a blanket ban.
Every retained exception must record:
- Owner and rationale.
- The retained module and its CI entry point.
- How that component sources first-party dependencies.
- Residual correctness risk, specifically whether it can still test against a stale
published copy of an in-repository library.
- A dated revisit or removal trigger.
An exception without this evidence is a deferral, not a decision.
Definition of Done
- Exception allowlist exists, with the evidence above recorded for every entry.
- Stale Bazel documentation removed.
tools/ci/bazel-consolidation-inventory output matches the plan.
Resources
Description
Phase 1 of #448. Correct the Bazel inventory, remove stale Bazel documentation, and
define the nested-module exception contract.
Not every nested module is in scope.
nvsnapstays nested because its base image isnot publicly pullable, and there is a deliberate helper module and a vendored module.
The Phase 2 guard therefore needs an allowlist rather than a blanket ban.
Every retained exception must record:
published copy of an in-repository library.
An exception without this evidence is a deferral, not a decision.
Definition of Done
tools/ci/bazel-consolidation-inventoryoutput matches the plan.Resources