Feat/update

[AriusII]

Outcome and linked issue

Closes

Scope and architectural ownership

Describe resulting behavior, affected contracts, and exclusions. SDK owns CE integration; Client owns workflows and policy.

Dependencies and containing artifacts

Link upstream prerequisites without closing them. Identify the SDK package containing every consumed primitive.

Validation actually performed

Check	Command / profile	Actual result	Evidence
Unit / fixture		Not executed
Packed consumer		Not executed
Live host		Not executed
AOT publication		Not executed

Compatibility, lifetime and partial effects

Explain public API or behavior changes, ownership, target switches, cleanup, cancellation and migration.

Documentation and review checklist

• Scope is focused; existing repository style and contribution rules are preserved.
• Relevant regression evidence is attached; pending gates remain explicit.
• No raw state/owner escapes the normal Client boundary.
• Capability and artifact claims match actual results.
• Documentation and release impact are recorded.
• No automatic merge, release, protection change or unsupported capability activation is requested.