Investigate: what was CommandFromPrompt for, and does #127 still want it #823

New issue

Closed

opened 2026-08-15 17:07:31 +00:00 by coilyco-ops · 0 comments

coilyco-ops commented

2026-08-15 17:07:31 +00:00

Member

The artifact

CommandFromPrompt   promptcommand.go   renders an MCP prompt as a Discord command

Unreachable as a unit. Its only other function, commandNameFor, is called solely from within the same file. Production builds Discord commands in commanddiscord.go:16 from declared commands, not from MCP prompts.

What to establish

Read the commit that introduced it and whatever it referenced. Not the commit subject - the diff and any issue it names.
Whether #127 is the intent. "Expose MCP prompts as Discord slash commands, which adds a summon path the access policy does not model" is an open P3 issue describing exactly what this file does. If it is the same intent, this is groundwork rather than a leftover and #621's question answers itself.
Whether the access-policy gap #127 names is why it was never wired. A summon path the policy does not model is a good reason to stop halfway, and if that is the story it should be written down rather than inferred.

Outcome

Either a line in a doc saying this is deliberate groundwork for #127, or a deletion with the reason recorded. A green test suite over unreachable code reads as delivery, and that is the condition #621 exists to end.

Deleting another seat's groundwork on a call count alone was explicitly declined as a unilateral call, so this issue is the digging that would make either choice defensible.

Parent - #621. Related - #127.

Filed by Delphi (design seat) at Kai's instruction, 2026-08-15. Split from #621, which asked for a per-capability decision and got "write an issue for each one, to dig into what they were probably for". ## The artifact ``` CommandFromPrompt promptcommand.go renders an MCP prompt as a Discord command ``` Unreachable as a unit. Its only other function, `commandNameFor`, is called solely from within the same file. Production builds Discord commands in `commanddiscord.go:16` from declared commands, not from MCP prompts. ## What to establish 1. **Read the commit that introduced it** and whatever it referenced. Not the commit subject - the diff and any issue it names. 2. **Whether #127 is the intent.** "Expose MCP prompts as Discord slash commands, which adds a summon path the access policy does not model" is an open P3 issue describing exactly what this file does. If it is the same intent, this is groundwork rather than a leftover and #621's question answers itself. 3. **Whether the access-policy gap #127 names is why it was never wired.** A summon path the policy does not model is a good reason to stop halfway, and if that is the story it should be written down rather than inferred. ## Outcome Either a line in a doc saying this is deliberate groundwork for #127, or a deletion with the reason recorded. **A green test suite over unreachable code reads as delivery**, and that is the condition #621 exists to end. Deleting another seat's groundwork on a call count alone was explicitly declined as a unilateral call, so this issue is the digging that would make either choice defensible. **Parent** - #621. **Related** - #127.

coilyco-ops referenced this issue

2026-08-15 17:08:03 +00:00

Four unwired capabilities are undocumented, so deleting them is a judgement someone else should make #621

coilyco-ops added the

autonomy

headless

priority

labels

2026-08-15 17:22:40 +00:00

coilyco-ops added the

role/engineer

label