v3.2.0

Owned POM Upgrade Targets — extends the POM-aware upgrade path to platform-managed and build
plugin dependency versions that are directly editable in the caller's POM.

Added

• Root dependency-management upgrade actions: recommend_pom_upgrades now treats direct,
  non-import <dependencyManagement> declarations in the input POM as first-class upgrade targets,
  even when a platform/master POM has no normal <dependencies> usage. New
  managed_decl_bump actions identify whether the client should edit a literal <version> or a
  root-owned backing property (editTarget, propertyName, and declaredIn), so non-LLM clients
  can apply the owning edit directly.
• Build plugin dependency upgrades: direct dependencies under both build/plugins and
  build/pluginManagement now surface as plugin_dep_bump actions. Each action carries the owner
  plugin coordinate and build path in addition to literal/property edit metadata, covering cases
  such as com.puppycrawl.tools:checkstyle inside maven-checkstyle-plugin.

Changed

• POM analysis edit ownership: EffectivePomResult.rootManagedDeclarations exposes only direct
  managed entries with an unambiguous edit site in the input POM. Exact property references are
  included only when the property is declared by that root POM; inherited and compound property
  expressions remain non-deterministic and are excluded.
• Reference updater plugin scoping: literal plugin dependency actions are applied only inside
  their identified owner plugin block; property-backed plugin dependencies update the exact
  server-supplied property.
• Release metadata: aligned the project version, MCP runtime metadata, registry manifest,
  Docker workflow fallbacks, and Unix/Windows build helper fallbacks for 3.2.0.