Binary Size Analysis for agent-data-plane

You are performing a standalone binary size analysis of the agent-data-plane binary. Your goal is to identify the top 3-5 contributors to binary size and assess whether each can feasibly be reduced.

Step 1: Build with optimized-release profile

Build the binary using the production release profile. Warn the user this may take several minutes due to fat LTO and single codegen unit.

cargo build --profile optimized-release -p agent-data-plane

The optimized-release profile is defined in the workspace root Cargo.toml and inherits from release with lto = "fat" and codegen-units = 1. This matches what ships to users.

Step 2: Separate debug info and strip the binary