Sessions started by a trigger (first kind: forgejo_conversation) have
nobody to answer permission prompts. Their trigger is persisted per
session and fixes the session for its whole lifetime, including resumes:
the policy's tool list is the complete tool surface (built with
restrictToolNames, since the SDK only gates bash/edit/delete/move), and
per-call checks allow comments only on the triggering issue/PR.

In trigger sessions every approval prompt becomes an "unattended" deny,
explicit deny rules still win over the policy, plan and idea mode are
refused, and resume fails closed when the stored trigger is unreadable.
A trigger session's system prompt carries conversation orientation.

Co-Authored-By: Claude Opus 5.5 via omp-deck

@@ -0,0 +76,4 @@
+	decide(toolName, params, scope) {
+		if (Object.hasOwn(FORGEJO_COMMENT_TOOLS, toolName)) {
+			// Both tools are accepted for issues and PRs alike: PR comments use issue routes.
+			if ((params as { number?: unknown } | null)?.number === scope.number) return "allow";

@@ -0,0 +159,4 @@
+	const longestRun = Math.max(0, ...(body.match(/`+/g) ?? []).map((r) => r.length));
+	const fence = "`".repeat(Math.max(3, longestRun + 1));
+	return [
+		`Forgejo comment on ${t.repo} ${t.isPull ? "PR" : "issue"} #${t.number}: "${issue?.title ?? "?"}"`,

@@ -0,0 +215,4 @@
+			buildConversationSeed({ repo: row.repo, number: row.number, isPull: row.isPull, reason, payload }),
+		);
+		if (outcome === "ok") {
+			finishForgejoTrigger(row.id, "done", reason);

@@ -0,0 +308,4 @@
+		if (api) {
+			const [owner = "", repo = ""] = row.repo.split("/");
+			const body =
+				`omp-deck failed to handle this comment: ${reason}.` +

@@ -0,0 +34,4 @@
+ * `issue_comment` still classifies as an issue comment.
+ */
+export function resolveEventType(eventTypeHeader: string | undefined, eventHeader: string | undefined): string {
+	return eventTypeHeader ?? eventHeader ?? "";

@@ -0,0 +55,4 @@
+
+/** Index a newly registered workspace. No-op until the index has been built. */
+export function noteWorkspaceAdded(ws: Workspace): void {
+	if (!index) return;

@@ -0,0 +8,4 @@
+ * neither the body nor the headers are ever logged.
+ *
+ * Accepted deliveries become `pending` rows in `forgejo_triggers`, deduped by
+ * `X-Forgejo-Delivery` so Forgejo's manual redeliver is safe.

@@ -0,0 +34,4 @@
+		const cfg = readForgejoConfig();
+		if (!secret || !cfg) return c.json({ error: "forgejo webhook not configured" }, 503);
+
+		const body = new Uint8Array(await c.req.arrayBuffer());

@@ -193,0 +196,4 @@
+
+1. In Settings → Forgejo → **Webhook**, click **Generate secret** (stored as `forgejo.webhook_secret`; **Regenerate** replaces it and invalidates the old one).
+2. In Forgejo's repository, organization or system webhook settings, add a **Forgejo** webhook: target URL = the payload URL shown in the panel (`<deck origin>/api/forgejo/webhook`), method POST, content type `application/json`, secret = the generated secret, trigger on custom events **Issue comments** and **Pull request comments**.
+3. Forgejo must be able to reach that URL. `/api/forgejo/webhook` is the one deck route meant for an external caller; exposing it (and exempting it from any front-end auth) is up to your reverse proxy. Its only authentication is the HMAC-SHA256 signature over the body, checked against the secret.

@@ -0,0 +88,4 @@
+			"",
+			`You were started by a comment on ${isPull ? "pull request" : "issue"} #${number}. Nobody is watching this session: your chat output is never read. The only way to answer is a Forgejo comment.`,
+			"- Read the thread first (`forgejo_list_issue_comments`, or `forgejo_list_pr_comments_and_reviews` for a pull request).",
+			`- Reply only with \`forgejo_create_issue_comment\` or \`forgejo_create_pr_comment\` on #${number}.`,