[Draft] Update README with recent highlights, benchmarks, and support matrix …

[trvachov]

…fixes

Add new Recent News entries for Qwen3, ESM2 low-precision (NVFP4/MXFP8), Mixtral MoE, ESM2 PEFT, and Llama3 context parallelism. Add benchmark figures for ESM2 low-precision on B300 and Llama3 70B CP on GB300. Update support matrix with new model/recipe rows and fix stale WIP statuses. Fix typos ("bionemo2" → "BioNeMo Framework") and remove stray character in amplify README.

Description

Usage

TODO: Add code snippet

Type of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Refactor
• Documentation update
• Other (please describe):

CI Pipeline Configuration

Configure CI behavior by applying the relevant labels. By default, only basic unit tests are run.

• ciflow:skip - Skip all CI tests for this PR
• ciflow:notebooks - Run Jupyter notebooks execution tests for bionemo2
• ciflow:slow - Run slow single GPU integration tests marked as @pytest.mark.slow for bionemo2
• ciflow:all - Run all tests (unit tests, slow tests, and notebooks) for bionemo2. This label can be used to enforce running tests for all bionemo2.
• ciflow:all-recipes - Run tests for all recipes (under bionemo-recipes). This label can be used to enforce running tests for all recipes.

Unit tests marked as @pytest.mark.multi_gpu or @pytest.mark.distributed are not run in the PR pipeline.

For more details, see CONTRIBUTING

Note

By default, only basic unit tests are run. Add appropriate labels to enable an additional test coverage.

Authorizing CI Runs

We use copy-pr-bot to manage authorization of CI
runs on NVIDIA's compute resources.

• If a pull request is opened by a trusted user and contains only trusted changes, the pull request's code will
  automatically be copied to a pull-request/ prefixed branch in the source repository (e.g. pull-request/123)
• If a pull request is opened by an untrusted user or contains untrusted changes, an NVIDIA org member must leave an
  /ok to test comment on the pull request to trigger CI. This will need to be done for each new commit.

Triggering Code Rabbit AI Review

To trigger a code review from code rabbit, comment on a pull request with one of these commands:

• @coderabbitai review - Triggers a standard review
• @coderabbitai full review - Triggers a comprehensive review

See https://docs.coderabbit.ai/reference/review-commands for a full list of commands.

Pre-submit Checklist

• I have tested these changes locally
• I have updated the documentation accordingly
• I have added/updated tests as needed
• All existing tests pass successfully

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 37988de6-4fb2-45cc-b686-29006d9a44dc

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch trvachov/README-march-26

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[trvachov]

@jomitchellnv @pstjohn can we get the raw numbers for these figures so that we can use @jwilber 's tools to unify style?

Also @jomitchellnv is it possible to could get the mxfp8/nvfp4 ESM2 benchmarks in the same units as the front page benchmarks?

[zoeyz101]

It would be great to add a bit of context here as to what BioNeMo features these benchmarks relate to for a new user reading this. Are we planning to add more than 3 benchmark figures here as well? If there is more than 3, it might be nice to add a subheading for them.