fourward@20260405.1

[smolkaj]

Summary

Initial BCR release of 4ward, a
spec-compliant reference implementation of P4₁₆ and P4Runtime for
dataplane validation and testing.

Depends on #8332 (`grpc@1.80.0.bcr.1`) for BCR presubmit
compatibility — grpc 1.80.0 declares `rules_swift@2.5.0` which
conflicts with Bazel 9's bundled `rules_swift@3.1.2` during the
vendor step (filed #8331).

BCR patch

Strips `git_override` blocks (p4c, grpc, behavioral_model,
bazel_clang_tidy) and non-BCR dev dependencies. Pins grpc to
`1.80.0.bcr.1` (rules_swift fix).

Consumer impact

Consuming	Consumer MODULE.bazel needs
`//simulator`, `//p4c_backend`, `//web`, `//cli`	nothing
`//p4runtime:p4runtime_lib`	`known_contributing_modules = ["grpc-java", "protobuf"]` (example)

Local verification

All steps pass locally before submission:

• `bcr_validation` — all GOOD
• `setup_presubmit_repos` vendor step — passes with Bazel 9 (`USE_BAZEL_VERSION=latest`)
• Full build from `bcr_test_module` — 82 targets pass with Bazel 8
• BCR presubmit CI (blocked on grpc@1.80.0.bcr.1 #8332)

[bazel-io]

Hello BCR maintainers, modules without existing maintainers (fourward) have been updated in this PR.
Please review the changes. You can view a diff against the previous version in the "Generate module diff" check.

[smolkaj]

Gentle ping, this is ready for review.

[smolkaj]

@keith ready to be merged on my end.

[keith]

ci failures

Require module maintainers' approval for newly pushed changes.

[smolkaj]

ci failures

Fixed, ready to merge

[keith]

failed

Require module maintainers' approval for newly pushed changes.

[UebelAndre]

Why not call it 4ward?

[smolkaj]

Why not call it 4ward?

I'd love to, but it seems Bzlmod doesn't allow that: https://github.com/bazelbuild/bazel/blob/master/src/main/java/com/google/devtools/build/lib/bazel/bzlmod/ModuleFileGlobals.java#L72-L74

[smolkaj]

@keith took another crack at it, this time adding a bcr_test_module to my repo first to prefetch potential issue (smolkaj/4ward#475).

[keith]

failed

[smolkaj]

Seems like a BCR issue :/ #8331

Currently hard-blocked, not sure what to do as a workaround :(

Require module maintainers' approval for newly pushed changes.