Register the approver client now its callback exists

informed-decision submitted client_id informed-decision-approver and redirect
https://decisions.coulomb.social/auth/callback, with the origin already live and
verified by them rather than reported: both / and /auth/callback return 200 on a
Let's Encrypt certificate valid to 2026-12-09. The host is decisions, not the
decide of an earlier draft. Its path serves a placeholder for now, which does not
matter -- the redirect is matched as an exact string and never fetched.

Published as a public authorization_code client with S256 PKCE, audience
approval-engine, scopes openid/approval:read/approval:approve, mfaRequired true
and a declared tenant:platform. No secretRef, since PKCE is the whole proof.

TestApproverRegistrationShapeIsExact pins every field, so widening a scope or
relaxing MFA fails the build rather than reading as an edit, and asserts the
registration passes startup validation -- proving the KEY-WP-0028 tenant
exemption holds for the registration that actually depends on it.

Two existing guards fired on the way in and neither was loosened. The tenant pin
refused an unreviewed client carrying a tenant, which is its purpose, so the
approver was added to its reviewed set deliberately. And the audience test
panicked slicing secretRef[4:], an assumption that held while the fixture had
only confidential clients; the approver is the first public one, so the loop now
guards on the env: prefix.

The declared tenant reaches the token by the GH-DEC-2026-013 gap route by
construction, and tenant_source says so: registration, never directory.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01NV9oijZukGyGbRQGGKnK4P

Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 713576@bnt-lap001
Assistant-Session: 384c511d-9bce-4cb8-a676-2aef6c0c8df6

config/service-clients.example.yaml

@@ -67,3 +67,37 @@ clients:
     tenant: "tenant:platform"
     roles: ["approval-operator"]
     tokenLifetime: "15m"
+
+  # Human approver browser client. Submitted by informed-decision 2026-09-10
+  # (INFD-WP-0001-T07) with the origin already live: both / and /auth/callback
+  # return 200 from 92.205.62.239 on a Let's Encrypt certificate
+  # CN=decisions.coulomb.social valid 2026-09-10 to 2026-12-09, deployed by
+  # railiance-apps. The host is decisions.coulomb.social, NOT the
+  # decide.coulomb.social an earlier draft proposed; register the string verbatim.
+  #
+  # The path currently serves an nginx placeholder while their surface is gated on
+  # APPROVAL-WP-0002-T01. That does not affect this registration: the redirect is
+  # matched as an exact string at /authorize and never fetched.
+  #
+  # No secretRef: this is a public client and authenticates with PKCE alone. No
+  # serviceSubject or roles either — on a browser client both are silently ignored
+  # and config validation rejects them (KEY-WP-0028); the subject and roles come
+  # from the directory user.
+  - clientId: "informed-decision-approver"
+    displayName: "informed-decision approver surface"
+    audience: "approval-engine"
+    redirectUris:
+      - "https://decisions.coulomb.social/auth/callback"
+    allowedScopes: ["openid", "approval:read", "approval:approve"]
+    grantTypes: ["authorization_code"]
+    clientType: "public"
+    # Declared, not inherited. Nothing populates domain.User.Tenant for approver
+    # users, so this reaches the token by the GH-DEC-2026-013 declared-gap route
+    # by construction, and the token says so: tenant_source is "registration",
+    # never "directory". Admissible for approval-engine's store-isolation gate;
+    # NOT admissible for any doctrine turning on this person's membership of the
+    # zone. See docs/tenant-claim-contract.md.
+    tenant: "tenant:platform"
+    # Approval is a human-in-the-loop control, so MFA is required rather than
+    # left to the provider default.
+    mfaRequired: true