Safely update classic enhancements in transportable packages

[Augusto42]

What changed

• adds verified update support for existing classic source-code enhancements (ENHO/XH) through ZADT_VSP and SAP's Enhancement Framework
• blocks source mutations before any write when the target package requires a transport and none was supplied
• rejects transport/request mismatches, including parent-request versus task ownership in CTS
• preserves omitted RFC import defaults and validates worker inputs before executing the isolated enhancement update
• updates the support matrix and MCP tool descriptions

Root cause

The unified write workflow validated configured transport policy, but it did not first inspect the target package's transport metadata. Classic enhancements also lacked a supported mutation backend, and the generic RFC bridge bound omitted import parameters to initial values, overriding SAP function-module defaults.

Impact

Transportable-package operations now fail closed before partial creation or update. Existing ENHO/XH objects can be updated safely when the current ZADT_VSP bridge is installed; creation remains intentionally unsupported because source alone does not identify the host, anchor, subtype, and spot metadata.

Validation

• go test ./...
• go vet ./...
• git diff --check
• privacy scan of the complete diff
• live SAP NPL checks using only synthetic ZVSP_* objects: local class update, local ENHO update with active read-back, transportable class/ENHO without request, correct owner request, and mismatched request preservation