[jmagar]

Summary

• stop HTTP and MCP transports from injecting runtime owner/origin fields into gateway actions that do not consume them
• centralize the mutation-only runtime owner policy in labby-gateway
• add API/MCP regression coverage so strict gateway.skills.list params remain untouched while mutation provenance is preserved

Root cause

The transport layers enriched every gateway action with internal runtime provenance. gateway.skills.list intentionally uses deny_unknown_fields and only accepts upstream, so the injected owner field made the Skills page fail with invalid gateway params: unknown field owner.

Verification

• cargo test -p labby-gateway runtime_owner_metadata_is_limited_to_actions_that_consume_it
• cargo test -p labby gateway_owner_injection
• cargo test -p labby gateway_origin_tests
• cargo test -p labby --features skills gateway_owner_injection
• cargo clippy -p labby-gateway --all-targets --features skills -- -D warnings
• cargo clippy -p labby --all-targets --features skills -- -D warnings
• cargo fmt --all -- --check
• git diff --check

[jmagar]

Superseded by #467, which incorporated this strict gateway-parameter fix and has already merged to main.