forge-whylisted

# Forge Why Pure read-only deterministic lookup. Translates a Forge identifier into a human-readable explanation. Four input modes: | Target form | Example | Resolves to | | --- | --- | --- | | Gate criterion ID | `G1-001`, `G7-API-002`, `G12-LIB-001` | Description + check type + severity + fix hint | | Stage number (terse or prefixed) | `3` or `stage-3` | Stage name, purpose, artifacts, gate counts | | Lesson tag | `force-advance`, `slow-consumer` | Up to 5 most-recent lessons with that tag | | (empty) | `/forge:why` | Current stage's active blockers + fix hints | ## When to Use - User types `/forge:why <something>` or just `/forge:why` - A gate just failed and the user asks "why?" or "what does that mean?" - User asks "what is Stage N?" or "what does this stage do?" - User asks about lessons: "show me force-advance lessons", "any slow-consumer warnings?" - BEFORE suggesting `/forge:force-advance` — always explain the blocker first ## When NOT to Use - The user is asking a question Forge cannot answer (general programming questions, questions about their domain) — `/forge:why` only resolves Forge IDs and concepts - The user has already heard the explanation — don't repeat it on follow-up ## Steps 1. Identify the target the user is asking about: - Starts with `G` followed by digit → gate criterion ID - Matches `<digit>` or `stage-<digit>` (1-12) → stage number - Empty or "current blockers" → bare invocation - Anything else → lesson tag 2. Run: ```bash