# W38 — `/alchemy-help` Discord slash command (#47)

Operator bagged #47 with direction: the command answers with content more or less
identical to the process-guide `operator-discord` section, nicely md-formatted for
Discord. The original sketch's second half (prompting-guidance section) stays in the
shell guide (`process-guide operator-agent`) — out of scope here.

## Scope

- `/alchemy-help`: guild-scoped slash command, registered idempotently at Ready
  beside `/alchemist`, `/new-milestone`, `/pick-milestone`.
- Answers **ephemeral**, anywhere in the guild (help is read-only — no Alchemist
  gate, no Project-channel gate).
- Content: `guide::discord_help()` — the `operator-discord` doctrine, reformatted
  with Discord markdown (bold headers, bullets, inline code). Same facts, same
  vocabulary; must stay under Discord's 2000-char message limit.

## Open design questions

None — the Operator direction pins content and surface; gating resolved as "none"
(informational, ephemeral, zero writes).

## Tasks

1. `traceable-reqs.toml`: new `REQ-DISCORD-HELP-COMMAND` (impl+unit), W38 group.
2. `src/guide.rs`: `discord_help()` + unit tests (feature-coverage sync with
   `OPERATOR_DISCORD`, ≤2000 chars).
3. `src/daemon/run.rs`: register + handle the command.
4. Board: #47 eval → W38 milestone → greenlit → wip; close before publish; sweep +
   `release v0.15.0`.

## Gate

`cargo test` + `traceable-reqs check` green, then RELEASE-RUNBOOK v0.15.0
(manifest+Cargo bump, CHANGELOG section, pack, tag, publish, install, sweep+release,
reap target/verify).