Move advice crawl and helper resolution to separate resolver

[sarahchen6]

What Does This Do

Extract advice crawl and helper resolution logic from MuzzleGenerator to HelperResolver. The HelperResolver is called once per module. Then from this result, MuzzleGenerator then emits both the $Muzzle reference and module's helperClassNames().

Motivation

Put crawl-related logic in one place - this makes it easier to read and test.

Additional Notes

Contributor Checklist

• Format the title according to the contribution guidelines
• Assign the type: and (comp: or inst:) labels in addition to any other useful labels
• Avoid using close, fix, or any linking keywords when referencing an issue
  Use solves instead, and assign the PR milestone to the issue
• Update the CODEOWNERS file on source file addition, migration, or deletion
• Update public documentation with any new configuration flags or behaviors
• Once approved, use merge queue to merge the PR

Jira ticket: [PROJ-IDENT]

[dd-octo-sts]

🟢 Java Benchmark SLOs — All performance SLOs passed

Suite	Status
Startup	🟢 pass

SLO thresholds are defined here based on automatically generated metrics. A warning is raised when results are within 5% of the threshold.

PR vs. master results

Scenario	Candidate	master	Δ (95% CI of mean)
startup:insecure-bank:iast:Agent	14.00 s	13.95 s	[-0.4%; +1.1%] (no difference)
startup:insecure-bank:tracing:Agent	12.99 s	12.94 s	[-0.5%; +1.2%] (no difference)
startup:petclinic:appsec:Agent	17.42 s	17.29 s	[-0.1%; +1.7%] (no difference)
startup:petclinic:iast:Agent	17.51 s	17.59 s	[-1.3%; +0.4%] (no difference)
startup:petclinic:profiling:Agent	17.36 s	17.44 s	[-1.5%; +0.6%] (no difference)
startup:petclinic:sca:Agent	17.40 s	16.62 s	[+0.4%; +8.9%] (maybe worse)
startup:petclinic:tracing:Agent	16.60 s	16.22 s	[-2.1%; +6.8%] (no difference)

Commit: 8588c007 · CI Pipeline · Benchmarking Platform UI

---

Load and DaCapo benchmarks can be triggered manually in the GitLab pipeline. Results will appear in the Benchmarking Platform UI after completion.

[dd-octo-sts]

Hi! 👋 Thanks for your pull request! 🎉

To help us review it, please make sure to:

• Add at least one type, and one component or instrumentation label to the pull request

If you need help, please check our contributing guidelines.

[datadog-datadog-us1-prod]

More details

Manual helper ordering, inferred dependency order, advice-root exclusion, and generated $Muzzle bytecode remained stable under missing-class, duplicate-advice, and additional-advice inputs. The extraction remains build-time-only and adds no runtime hot path.

Was this helpful? React 👍 or 👎

_{📊 Validated against 8 scenarios · Open Bits AI session}

_{🤖 Datadog Autotest · Commit 8588c00 · What is Autotest? · @DataDog review to ask questions · Any feedback? Reach out in #autotest}