tbenandClaude Opus 5.5
380d3ebb2f
Bots get list_hooks, pause_hook and delete_hook, which act directly since they only take away. A new hook, or a new name, brief or filter, or switching a paused one back on, goes through propose_hook: it stores a hook_proposals row and puts a [hook-proposal:ID] card in the reply, which the user it was proposed to confirms or rejects. The card is read from what Confirm saves, with the bot's reason labelled as its own; confirming checks everything again and saves through the Hooks modal's helpers. A new hook's URL is shown on the card once, to the user only, never in the outcome the bot is told. What calls a hook, its computers and its signing are never proposed. Only chat replies propose, and a hook call's own run gets no hook tools, so a caller's payload can't reach them. Co-Authored-By: Claude Opus 5.5 <[email protected]>
25 lines
754 B
TypeScript
25 lines
754 B
TypeScript
import BunSQLite from "@moduletrace/bun-sqlite";
|
|
import claimHookProposal from "./claim-hook-proposal";
|
|
import grabHookProposal from "./grab-hook-proposal";
|
|
|
|
type Params = {
|
|
user_id: number | string;
|
|
proposal_id: number | string;
|
|
};
|
|
|
|
/**
|
|
* The user rejected a hook proposal from its card: nothing is saved.
|
|
*/
|
|
export default async function rejectHookProposal({ user_id, proposal_id }: Params) {
|
|
const proposal = await grabHookProposal({ proposal_id, user_id });
|
|
|
|
await claimHookProposal({ proposal, status: "rejected" });
|
|
|
|
await BunSQLite.sql({
|
|
sql: `UPDATE hook_proposals SET outcome = 'Rejected. Nothing was saved.', updated_at = ? WHERE id = ?`,
|
|
values: [Date.now(), proposal.id],
|
|
});
|
|
|
|
return proposal;
|
|
}
|