Bzlmod module resolution transition from WORKSPACE in Bazel 6+

Repeatable development environments in Bazel depend on hermetic sandboxing, toolchain pinning, and deterministic dependency resolution.

Bazel 6 and later prioritize MODULE.bazel over WORKSPACE, and mixed WORKSPACE and MODULE.bazel mode is supported in recent releases with version-sensitive semantics. The lack of a finalized deprecation or removal timeline for WORKSPACE creates uncertainty about whether to maintain dual configuration for reproducible builds across clean clones.

What compatibility boundary defines module mode activation when both files exist? Is repository name and resolution order guaranteed to be deterministic across supported Bazel versions in mixed mode? Has Bazel published an official deprecation or removal timeline for WORKSPACE?