|SUCCESS| examples/l3fwd: sync cli options with documentation

[dpdklab at iol.unh.edu]

Test-Label: ai-code-review
Test-Status: SUCCESS
https://dpdk.org/patch/172733

_AI Code Review_

=== Patch Review: series.patch (via Claude) ===
Review date: 2026-11-09

# DPDK Patch Review

## INFO

**Pre-existing documentation:**
The documentation updates look accurate based on the command-line parsing code visible in the patch. The synchronization effort appears thorough.

**Verification script in commit message:**
The shell script demonstrating that all options now appear at least twice in both files is a good practice for proving completeness. This is informative but not required by guidelines.

## Code Quality

**Atomic doc/code update:**
The patch correctly updates both the code (`main.c`) and documentation (`l3_forward.rst`) together, satisfying the requirement that "code and documentation must be updated atomically in same patch."

**Release notes:**
This patch does not require a release notes update. It only fixes existing documentation/help text to match the code -- it does not change functionality, add features, or modify API. The omission is correct per the guideline: "Release notes are NOT required for... Internal implementation changes that don't affect public API."

**`.mailmap` update:**
The `.mailmap` addition follows DPDK practice for mapping multiple email addresses for the same contributor. This is not subject to AI review per the guidelines but appears correctly formatted.

**Documentation style:**
The `.rst` additions use a consistent format matching the existing list structure. Each option is documented with its parameter syntax and a brief description. The style is appropriate for this context (a reference list of command-line options).

**C code additions:**
The `main.c` additions to `print_usage()` are straightforward string literals appended to the usage message. No executable code changes, no correctness concerns.

**Completeness:**
All options mentioned in the commit message as missing are now present in both files. The grep counts in the commit message confirm no omissions remain (each option appears >= 2 times in both files).

Review-Result: CLEAN