From f1ae05e829ca3cb208e10962279361838331122d Mon Sep 17 00:00:00 2001 From: "Marcus R. Brown" Date: Fri, 29 May 2026 16:19:40 -0700 Subject: [PATCH] docs(gateway): document add-project Discord-only limitation for v1 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Records that /add-project has no programmatic invocation surface — the orchestration is bound to a Discord interaction, and recovery is via idempotent retry rather than agent-callable primitives. A Discord-independent primitive is deferred until a non-Discord caller exists. --- packages/gateway/AGENTS.md | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/packages/gateway/AGENTS.md b/packages/gateway/AGENTS.md index 152be6f0..dd4a6b69 100644 --- a/packages/gateway/AGENTS.md +++ b/packages/gateway/AGENTS.md @@ -74,6 +74,17 @@ Existing deployments that need the privileged set must set this on the next deploy. The allowlist is intentionally narrow — operators cannot enable arbitrary Discord intents via this knob. +## Known limitations (v1) + +- **`add-project` is Discord-only.** The orchestration runs inside the slash + command handler and requires a `ChatInputCommandInteraction`; there is no + programmatic surface (HTTP endpoint, CLI, or agent tool) that triggers the same + outcome. An autonomous agent cannot bind a repo without going through Discord. + Recovery is via idempotent retry — re-running the command resumes a partial + setup — rather than agent-callable recovery primitives. Extracting a + Discord-independent `addProject(request, deps)` primitive is deferred until a + non-Discord caller exists. + ## Build ```bash