@open-everywhere/provider-discord 0.1.0

package/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your Exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright 2026 Tommy Long
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/NOTICE

@@ -0,0 +1,21 @@
+Open Everywhere
+Copyright 2026 Tommy Long
+
+This product is licensed under the Apache License, Version 2.0 (see LICENSE).
+
+---
+
+Built on Vercel Eve (https://github.com/vercel/eve), licensed under the
+Apache License, Version 2.0.
+
+@open-everywhere/core also ships a patch that modifies Vercel Eve (the file in
+its patches/ directory), with the oe-eve-patch command that applies it to a
+consumer's own installed copy. The patch is licensed under the Apache License,
+Version 2.0. No modified Vercel Eve files are distributed.
+
+---
+
+Open Everywhere is an independent, open-source project. It is NOT affiliated
+with, endorsed by, or sponsored by Anthropic. "Claude", "Claude Code", and
+"Claude Tag" are referenced only to describe the prior art Open Everywhere is
+inspired by, and are trademarks of their respective owner.

package/README.md

@@ -0,0 +1,47 @@
+# @open-everywhere/provider-discord
+
+Discord channel and DM surfaces for Open Everywhere.
+
+Part of [Open Everywhere](https://github.com/open-everywhere/open-everywhere) — an open, self-hostable autonomous teammate you tag where your
+team works. This package is the Discord provider. It supplies the identity mapper, the capability manifest, the post arm, the wake-origin codec, the read adapter, the reaction surface, the message operations, the approval cards, the gateway wiring and the guild-admin check.
+
+`@open-everywhere/core` owns the runtime — access and approvals, identity, memory, spend, the
+audit chain. This package holds the Discord half. The boundary between them is a vendor-coupling
+one, and `packages/core/scripts/boundary-test.ts` checks it per provider: it names one or more
+vendor fingerprint strings, asserts that **at least one** of them appears under this package, and
+asserts that **every** one of them is absent from `packages/core/agent`. For Discord those strings are
+the Bot API host `discord.com/api`. Core's registries refuse a provider the deployment has not selected.
+
+## Install
+
+```sh
+npm i @open-everywhere/core @open-everywhere/provider-discord eve@0.54.3
+npx oe-eve-patch
+```
+
+**Both commands are required.** Core refuses to boot on an unpatched `eve`. A registry `eve` carries
+no patch, so `npx oe-eve-patch` applies the copy `@open-everywhere/core` ships.
+
+`eve` is a peer dependency, pinned to the exact version above, which is the pin
+`@open-everywhere/core` declares as `peerDependencies.eve`. Node 24 or newer.
+
+## Use
+
+One call registers the bundle:
+
+```ts
+import { registerDiscordProvider } from "@open-everywhere/provider-discord/agent/register.js";
+
+registerDiscordProvider();
+```
+
+Credentials, the webhook and the Discord app setup are in the runbook below.
+
+## Docs
+
+- [Discord runbook](https://github.com/open-everywhere/open-everywhere/blob/main/docs/deploy/surfaces/discord.md)
+- [Documentation index](https://github.com/open-everywhere/open-everywhere/blob/main/docs/README.md)
+
+## Licence
+
+Apache 2.0. The tarball carries `LICENSE` and `NOTICE`.

package/agent/access/discord-grant-click.ts

@@ -0,0 +1,237 @@
+// THE DISCORD HALF OF THE CREDENTIAL-GRANT CARD BUTTON (OPE-1260) — the sibling of
+// identity/discord-link-consent.ts, funnelling through core's own `resolveGrantCardClick` exactly as
+// that file funnels through `resolveLinkConsentClick`. Core decides; this file only reads Discord's
+// envelope and writes Discord's answer.
+//
+// WHAT WAS WRONG BEFORE THIS FILE. The owner's grant card is delivered as a DM with an actions row,
+// and the Discord DM arm renders those actions as real components (channels/discord-post-arm.ts). The
+// front route classified only `oe-approval:` and `oe-link:`, so an `oe_grant:` tap FORWARDED to eve's
+// HITL decoder, which no-ops it. The owner saw four buttons, tapped one, and nothing happened —
+// no approval, no decline, no answer, and the ask then lapsed on its own.
+//
+// 🔴 THE CLICKER IS READ FROM THE ENVELOPE, NEVER FROM A PAYLOAD FIELD. A grant answer is scoped to
+// BEING the owner the card was sent to, so whose hand it was is the whole security content of this
+// file. The front route has already verified Discord's Ed25519 signature over the RAW body, so every
+// field read below is Discord's own statement. Core then compares that clicker to the ask row's
+// `ownerPrincipalId`; an ask id names an ask, it never answers one.
+//
+// 🔴 DM-ONLY, REFUSED RATHER THAN TOLERATED — the same rule, for the same reason, as the consent
+// button. A grant card is only ever delivered through `deliverDirectMessage`, so it only ever lands
+// in a 1:1. A guild click therefore cannot be a tap on a real card: the message was forwarded, or the
+// id was guessed. `interaction.guild_id` present ⇒ refuse, and say so.
+//
+// WHERE THIS DIFFERS FROM THE SLACK DOOR, and why. Slack's `handleGrantCardClick` posts its private
+// answer with a second API call (`chat.postEphemeral`), because a Slack interactivity POST answers
+// with an empty 200. Discord's interaction response IS the private answer — `type 4` + `flags 64` —
+// so the answer rides the click's own reply and no second call is made. The DECISION, the copy and
+// the audit row are core's, identical on both surfaces.
+//
+// ⚠️ THIS FILE NEVER TOUCHES THE CARD — CORE REWRITES IT AFTER THE DECISION (OPE-1278). The answer
+// here is ephemeral, so the handler leaves the owner's message alone. Core's `rewriteGrantCard`
+// (access/credential-grant-card.ts) rewrites that card to a terminal APPROVED or DECLINED body once
+// the CAS has closed the ask, and the Discord edit arm's `components: []` takes the four buttons
+// with it (channels/discord-message-ops.ts). THAT REWRITE IS BEST-EFFORT: an ask row with no pinned
+// card locus, or an edit the surface refuses, still leaves live buttons over a closed request. The
+// CAS is what makes that safe — core's approve is conjunct on `status = 'pending'`, so a second tap
+// mints nothing and is answered "that request is no longer open", which is the truth.
+//
+// NEVER THROWS. Discord's interactions endpoint must answer within three seconds, and a throw there
+// becomes a red "This interaction failed" the person cannot act on.
+//
+// 🔴 THE RESOLUTION IS DEFERRED, BECAUSE IT IS NOT FAST AND DISCORD DOES NOT REDELIVER (OPE-1282).
+// `resolveGrantCardClick` used to be awaited to completion before this returned. An APPROVE inside it
+// reads the owner's own MCP connection before it CASes — a consent probe, a token mint, an MCP
+// handshake and a `tools/list`, all four sharing one `BORROW_APPROVE_READ_BUDGET_MS` deadline (core
+// connections/grant-mcp-borrow.ts, five seconds) — and then does the CAS, the grant insert, the audit rows
+// and an AWAITED post into the requesting room. That can exceed Discord's three seconds.
+//
+// WHAT THAT COST, AND WHY IT WAS WORSE HERE THAN ON SLACK. Slack redelivers an interactivity payload
+// it has not seen answered, so a slow approve there is retried (slack-front.ts's own note). Discord
+// does NOT redeliver an expired interaction token: the owner saw a red "This interaction failed" and
+// this handler's ephemeral answer was never rendered — while the grant really was minted and the
+// requesting room really was told. A second tap then read "that request is no longer open", which is
+// true and reads like a failure. It was never a correctness problem — the approve CAS still yields
+// exactly one grant — but the owner believed their approval had failed while a conversation could
+// already spend their credential.
+//
+// SO THIS DOOR IS NOW "ACK, THEN DECIDE, THEN EDIT": it answers with a DEFERRED ephemeral response
+// (`type 5`, channels/discord-interaction-defer.ts), hands the resolution to the host's `waitUntil`,
+// and edits the placeholder with core's own decision copy when it lands. The ephemeral flag rides
+// the ACK — Discord fixes visibility at the first response — so the answer is still private.
+//
+// 🔴 THE FAST REFUSALS DO NOT DEFER, and that is deliberate. A guild click, an unattributable
+// clicker and an unreadable action id are all decided from the envelope alone, in no time at all.
+// Deferring them would trade an instant answer for a placeholder plus a second round trip, and each
+// one is a `type 4` today because that is the correct shape for an answer that is already known.
+//
+// 🔴 NO `waitUntil` ⇒ NO DEFER. Without somewhere to run the work, a deferred ack would leave the
+// owner on a permanent "thinking…" — strictly worse than the slow answer. The handler falls back to
+// the original await-then-answer shape instead, and says so in the log.
+//
+// ⚠️ approvals/discord-flow.ts IS ONLY HALF THIS SHAPE, and cannot take the other half as written
+// (OPE-1407). Its `deliverDecisionFeedback` — the notice post and the decision wake — now runs under
+// the route's `waitUntil` WHEN THE ROUTE SUPPLIES ONE, which takes that leg out of the three-second
+// budget; a host that supplies none still awaits it inside the budget. Its `resolveApprovalClick`
+// stays on the response path because that door answers with THREE response KINDS chosen by the
+// resolution (`type 7` replaces the card, `type 6` acks silently, `type 4` sends an ephemeral), and
+// Discord fixes a response's kind at the first response. This door answers with one `type 4` on
+// every path, which is what lets it defer as `type 5` and say the same thing later. Closing the
+// other half needs a follow-up MESSAGE rather than the `@original` edit this module provides.
+
+import { OE_GRANT_ACTION_PREFIX, parseGrantCardActionId, resolveGrantCardClick, deploymentOrg } from "@open-everywhere/core/agent/adapter-api.js";
+import { deferredEphemeralResponse, editOriginalInteractionResponse, interactionFollowUp, type InteractionFollowUp } from "../channels/discord-interaction-defer.js";
+
+function log(msg: string): void {
+  console.log(`[open-everywhere:discord-grant] ${msg}`);
+}
+
+// Discord interaction-response wire constants, defined locally for the same reason
+// identity/discord-link-consent.ts and approvals/discord-flow.ts define their own.
+const RESPONSE_CHANNEL_MESSAGE = 4; // CHANNEL_MESSAGE_WITH_SOURCE
+const EPHEMERAL = 64; // MessageFlags.EPHEMERAL — only the clicker sees it
+
+/** The interaction response body this handler returns. Loosely typed, exactly as its two sibling
+ *  handlers type theirs, so the front route can hold one seam type across all three. */
+export type DiscordGrantClickResponse = Record<string, unknown>;
+
+/** The host edges this door needs to defer. Both are injected so a test can drive the whole
+ *  ack-then-edit sequence with no Discord and no host. */
+export interface DiscordGrantClickDeps {
+  /** The route's own `waitUntil` — keeps the resolution alive past the interaction response on a
+   *  serverless host. ABSENT ⇒ no defer (see the header): the handler awaits and answers as before. */
+  readonly waitUntil?: (p: Promise<unknown>) => void;
+  /** The follow-up edit. Live default is {@link editOriginalInteractionResponse}. */
+  readonly edit?: (followUp: InteractionFollowUp, content: string) => Promise<boolean>;
+}
+
+function ephemeral(content: string): DiscordGrantClickResponse {
+  return { type: RESPONSE_CHANNEL_MESSAGE, data: { content, flags: EPHEMERAL } };
+}
+
+function isObject(v: unknown): v is Record<string, unknown> {
+  return typeof v === "object" && v !== null;
+}
+
+/** The clicking user's Discord id, from the envelope's own fields. Discord puts the clicker at
+ *  `interaction.user` in a DM and at `interaction.member.user` in a guild; both are read so the
+ *  guild refusal below is a DELIBERATE refusal rather than an accident of which field was absent. */
+function clickerIdOf(interaction: Record<string, unknown>): string | undefined {
+  const direct = isObject(interaction["user"]) ? interaction["user"]["id"] : undefined;
+  if (typeof direct === "string" && direct.length > 0) return direct;
+  const member = isObject(interaction["member"]) ? interaction["member"]["user"] : undefined;
+  const viaMember = isObject(member) ? member["id"] : undefined;
+  return typeof viaMember === "string" && viaMember.length > 0 ? viaMember : undefined;
+}
+
+/** The channel the click happened in — the audit row's `surface`. Absent on a body that carries
+ *  none, which is a stamp we leave off rather than invent. */
+function channelIdOf(interaction: Record<string, unknown>): string | undefined {
+  const id = interaction["channel_id"];
+  if (typeof id === "string" && id.length > 0) return id;
+  const channel = isObject(interaction["channel"]) ? interaction["channel"]["id"] : undefined;
+  return typeof channel === "string" && channel.length > 0 ? channel : undefined;
+}
+
+/**
+ * Handle one verified `oe_grant:` component click.
+ *
+ * Returns the interaction response body to send, or `null` for anything that is NOT one of ours —
+ * the front route then forwards it, so a click is never silently swallowed. NEVER throws.
+ *
+ * 🔴 ON THE RESOLUTION PATH IT RETURNS BEFORE THE DECISION IS MADE (OPE-1282). The body is a
+ * DEFERRED ephemeral ack; the decision runs under `deps.waitUntil` and edits that placeholder when
+ * it lands. See the header for why, and for the two cases that still answer synchronously.
+ */
+export async function handleDiscordGrantCardInteraction(
+  raw: unknown,
+  deps: DiscordGrantClickDeps = {},
+): Promise<DiscordGrantClickResponse | null> {
+  try {
+    if (!isObject(raw)) return null;
+    const data = isObject(raw["data"]) ? raw["data"] : undefined;
+    const customId = typeof data?.["custom_id"] === "string" ? (data["custom_id"] as string) : undefined;
+    if (!customId?.startsWith(OE_GRANT_ACTION_PREFIX)) return null;
+    const parsed = parseGrantCardActionId(customId);
+    if (parsed === undefined) {
+      // Ours by prefix, unreadable by grammar. Returning null lets the front route forward it rather
+      // than swallow it — the same defensive shape both sibling handlers take.
+      log("grant card custom_id did not parse — forwarding");
+      return null;
+    }
+
+    if (typeof raw["guild_id"] === "string" && raw["guild_id"].length > 0) {
+      // See the header: a grant card only ever lands in a DM, so a guild click is not the owner
+      // answering their own card.
+      return ephemeral(
+        "I only take an answer to a credential request in our direct messages — this one came from a server. Open our DM and answer it there. Nothing was granted.",
+      );
+    }
+
+    const clicker = clickerIdOf(raw);
+    if (clicker === undefined) {
+      log("grant card click carried no attributable user — refusing");
+      return ephemeral("I could not tell who pressed that, so I did nothing and nothing was granted.");
+    }
+
+    const channelId = channelIdOf(raw);
+    const resolve = (): Promise<{ text: string }> =>
+      resolveGrantCardClick({
+        askId: parsed.askId,
+        answer: parsed.answer,
+        // 🔴 NO TENANT RUNG, AND THAT IS THE CORRECT SPELLING RATHER THAN A GAP. Discord is not a
+        // tenant-scoped platform (identity/principal-key.ts), so the owner's key is `discord/<user-id>`
+        // — the exact string the ask row's `ownerPrincipalId` was minted as. Passing a guild here would
+        // compose a three-segment key that matches nobody and refuse every genuine owner.
+        clicker: { platform: "discord", nativeId: clicker },
+        // READ WHEN THE RESOLUTION RUNS, not when the ack is sent — it is the clock the ask's expiry
+        // is judged against, and the defer puts real time between the two.
+        nowMs: Date.now(),
+        // ONE deployment serves ONE org, and the ask row was written under that partition. Reading it
+        // from the deployment rather than the payload is what stops a forged body naming another
+        // tenant's asks — the same reason both sibling handlers read it this way.
+        org: deploymentOrg(),
+        platform: "discord",
+        // A DM has no guild, and the Discord identity mapper's own convention for that partition is the
+        // user's id in the `workspace` rung (channels/discord-identity.ts `guildId ?? userId`). Spelled
+        // the same way here so this audit row files where every other Discord DM row files.
+        workspace: clicker,
+        ...(channelId === undefined ? {} : { surface: channelId }),
+      });
+
+    const followUp = interactionFollowUp(raw);
+    if (deps.waitUntil === undefined || followUp === undefined) {
+      // NO PLACE TO RUN THE WORK, OR NO ADDRESS TO ANSWER AT ⇒ the pre-OPE-1282 shape. Slow, and
+      // still correct: a deferred ack we could not follow up would leave a permanent "thinking…".
+      log(`grant card click answering synchronously (${deps.waitUntil === undefined ? "no waitUntil" : "no follow-up address"}) — a slow approve may outlive the interaction token`);
+      return ephemeral((await resolve()).text);
+    }
+
+    const edit = deps.edit ?? editOriginalInteractionResponse;
+    deps.waitUntil(
+      (async () => {
+        // TOTAL. This runs after the response has gone; a throw here reaches the host's unhandled
+        // rejection handler and tells the owner nothing. Core's resolver is already total, so the
+        // catch is for the edit's own transport and for an impossible throw above it.
+        let text: string;
+        try {
+          text = (await resolve()).text;
+        } catch (err) {
+          log(`deferred grant card resolution failed: ${(err as Error)?.message ?? String(err)}`);
+          text = "That could not be answered right now. Nothing changed, and nothing was granted. Try the button again.";
+        }
+        // 🔴 A FAILED EDIT IS LOUD BUT NOT FATAL: the DECISION has already landed and been audited by
+        // core. What is lost is the owner's explanation, which is exactly what the pre-fix expired
+        // token lost — so this is never a regression, and it must be findable in the log.
+        const shown = await edit(followUp, text);
+        if (!shown) log(`grant card answer could NOT be shown to the owner — the decision landed and is audited, the owner was not told`);
+      })(),
+    );
+    return deferredEphemeralResponse();
+  } catch (err) {
+    // A three-second endpoint: an unhandled throw is a red "interaction failed" the person cannot act
+    // on. Core's resolver is already total and guards every write, so an honest answer here costs the
+    // owner an explanation and never an outcome.
+    log(`grant card click failed: ${(err as Error)?.message ?? String(err)}`);
+    return ephemeral("That could not be answered right now. Nothing changed, and nothing was granted. Try the button again.");
+  }
+}