[highb]

Squire (openai/gpt-6.1-sol):

Declare api_key_v2 on the existing encrypted Datadog action outputs before dispatch. The real action handlers retain their canonical JSON payloads, granted-scope semantics, and provider handles. Native IssueCredential selectors continue to return raw bytes.

Dependencies: existing action source #51 and SDK #1192, pinned by immutable pseudo-version. This branch integrates current main to preserve upstream fixes. Canonical schema/export: Multipass #975; C1 canonical consumer: C1 #28031. No released SDK, connector activation or live-provider acceptance is claimed.

TestDatadogDeclaredSecretProof executes actual connector registration, schema lookup, action handler, provider HTTP client, payload encoding and SDK JWE. The random-loopback provider fixture asserts requested scopes and returns different granted scopes; the decrypted payload preserves the granted scopes. Old opaque/generic context and wrong purpose/version refuse before any provider HTTP call. A test-only file port accepts actual C1-prepared requests and exports actual schema/JWE for the cross-repository proof.

Validation: full go test -p 2 -v ./... -count=1 passes, including existing scope/credential/pagination and raw-byte controls. Two live-provider lifecycle tests are intentionally skipped because no provider credentials or operations are authorized; those skips are not acceptance evidence. Source and vendored SDK output are separate commits.

Remaining draft acceptance: execute this actual connector through the replacement C1 frozen-type/member/Store/reveal stack and real Multipass codec/renderer. Current C1 synthetic-handler evidence does not satisfy that provider demonstration. Existing generic transports are refused for these explicitly typed custom actions; generic SDK behavior itself remains unchanged.