Move secrets between users and computers without the model seeing them

A new personal env scope (paradigm user: one user's secret for one bot)
beats every other scope, reaches only that user's runs of that bot, and
is redacted like any secret. Bots take secrets in with request_secret,
which puts a [secret-request:ID] card in the chat: the user types the
value into a masked input there, never into a message, and the bot is
told only the key. Bots show secrets with capture_secret (a task's
computer tool that saves a file or a command's output straight to a
personal env, then redacts it from the rest of the run) and show_secret
(an env by key): both give a [secret:ID] chip whose Reveal and Copy fetch
the value on click, for its own user (personal) or a super admin
(anything else), logged by key. Values never go into messages, page
props, history, Copy chat or logs. Users manage their own secrets on
Settings > Secrets; the Environment page lists everyone's, remove only.
Deleting a bot or user removes its personal secrets, and SecretsNote
tells bots never to ask for or print secrets in chat.

Co-Authored-By: Claude Opus 5.5 <[email protected]>

src/functions/backend/db/envs/delete-user-secret.ts

@@ -0,0 +1,24 @@
+import AppError from "@/src/utils/app-error";
+import deleteEnv from "./delete-env";
+import grabAllEnvs from "./grab-all-envs";
+
+type Params = {
+    user_id: number | string;
+    env_id: number | string;
+};
+
+/**
+ * Removes one of the user's own personal secrets. Returns its key, for the
+ * log. Computers drop it on their next run.
+ */
+export default async function deleteUserSecret({ user_id, env_id }: Params) {
+    const env = (await grabAllEnvs()).find(
+        (e) => e.id == Number(env_id) && e.paradigm == "user" && e.user_id == Number(user_id),
+    );
+
+    if (!env) throw new AppError(`That secret no longer exists.`);
+
+    await deleteEnv({ env_id: env.id });
+
+    return env.key;
+}