The "Locating runfiles with Bzlmod" proposal consists of the following individual steps:

• Add the RunfilesLibraryInfo provider (Add RunfilesLibraryInfo #16125)
• Collect repository names and mappings of the transitive closure of a target ([DRAFT] plumb transitive packages to RuleContext #16278)
• Emit a repository mapping manifest for every executable (Write a repo mapping manifest in the runfiles directory #16321 and Stage repository mapping manifest as a root symlink #16652)
• Revert RunfilesLibraryInfo
• Expose the current repository name in rules
  • Bash (Make Bash runfiles library repo mapping aware #16693)
  • C++ (Provide BAZEL_CURRENT_REPOSITORY local define in cc_* rules  #16216)
  • Java (Expose current repository name to Java with @AutoBazelRepository  #16534)
  • Python (Add CurrentRepository() to Python runfiles library #16341)
• Parse and use the repository mapping manifest in runfiles libraries (Runfiles workspace directories use wrong workspace name if repository renaming is in effect #15029)
  • Bash (Make Bash runfiles library repo mapping aware #16693)
  • C++ (Make C++ runfiles library repo mapping aware #16623 and Use _repo_mapping in C++ runfiles library #16701)
  • Java (Make Java runfiles library repo mapping aware #16549)
  • Python has been updated in rules_python
• Use the Java runfiles library to make Stardoc work with repository mappings (Bzlmod: stardoc is broken by repo mappings #14140)

Status of runfiles libraries in third-party rulesets:

• rules_go (Make Go runfiles library repo mapping aware bazel-contrib/rules_go#3347)
• rules_rust (???)
• rules_haskell (???)