feat!: remove MCP, rename bootstrap to learn, redesign CLI output

The MCP server is gone. Slash commands now invoke the taskwing CLI
directly via .claude/commands/, dropping the modelcontextprotocol,
grpc, and protobuf dependencies.

* add `taskwing init` (writes .taskwing.yaml marker, no LLM)
* rename `taskwing bootstrap` to `taskwing learn`
* .taskwing.yaml is the explicit project marker; project.Detect
  short-circuits on it so slugs stay stable across renames
* delete ~7000 LOC of dead handlers, presenters, app layers, and
  agents that only backed the removed MCP tools
* unify CLI output across init/doctor/learn: panel headers,
  consistent icon set, bar-chart summary in learn
* strip em dashes from all user-facing strings

Author: josephgoksu

AGENTS.md

@@ -44,55 +44,38 @@
 
 ## TaskWing Integration
 
-TaskWing extracts architectural knowledge from your codebase and stores it locally, giving every AI tool instant context via MCP.
+This project uses TaskWing for architectural knowledge management. You have access to TaskWing MCP tools.
 
-### Supported Models
+### TaskWing Workflow Contract v1
+1. No implementation before a clarified and approved plan/task checkpoint.
+2. No completion claim without fresh verification evidence.
+3. No debug fix proposal without root-cause evidence.
 
-<!-- TASKWING_PROVIDERS_START -->
+### MCP Tools (use directly, no skill needed)
+- `ask` -- Search project knowledge before modifying unfamiliar code.
+- `remember` -- Persist a decision or pattern for future sessions.
+- `code` -- Find symbols, explain call graphs, analyze impact, simplify code.
+- `debug` -- Diagnose issues with root-cause analysis.
+- `task` with action=current -- Check current task status.
 
-[![OpenAI](https://img.shields.io/badge/OpenAI-412991?logo=openai&logoColor=white)](https://platform.openai.com/)
-[![Anthropic](https://img.shields.io/badge/Anthropic-191919?logo=anthropic&logoColor=white)](https://www.anthropic.com/)
-[![Google Gemini](https://img.shields.io/badge/Google_Gemini-4285F4?logo=google&logoColor=white)](https://ai.google.dev/)
-[![AWS Bedrock](https://img.shields.io/badge/AWS_Bedrock-OpenAI--Compatible_Beta-FF9900?logo=amazonaws&logoColor=white)](https://docs.aws.amazon.com/bedrock/latest/userguide/inference-chat-completions.html)
-[![Ollama](https://img.shields.io/badge/Ollama-Local-000000?logo=ollama&logoColor=white)](https://ollama.com/)
+**When to use TaskWing MCP tools:**
+- Before modifying unfamiliar code: call `ask` to check for relevant decisions, constraints, and patterns
+- Before planning multi-step work: call `plan` with action=clarify to get a structured plan
+- When asked about architecture, tech stack, or "why" questions: call `ask` with answer=true
+- After making an architectural decision: call `remember` to persist it for future sessions
+- To understand a symbol's role and callers: call `code` with action=explain
 
-<!-- TASKWING_PROVIDERS_END -->
-
-### Works With
-
-<!-- TASKWING_TOOLS_START -->
-
-[![Claude Code](https://img.shields.io/badge/Claude_Code-191919?logo=anthropic&logoColor=white)](https://www.anthropic.com/claude-code)
-[![OpenAI Codex](https://img.shields.io/badge/OpenAI_Codex-412991?logo=openai&logoColor=white)](https://developers.openai.com/codex)
-[![Cursor](https://img.shields.io/badge/Cursor-111111?logo=cursor&logoColor=white)](https://cursor.com/)
-[![GitHub Copilot](https://img.shields.io/badge/GitHub_Copilot-181717?logo=githubcopilot&logoColor=white)](https://github.com/features/copilot)
-[![Gemini CLI](https://img.shields.io/badge/Gemini_CLI-4285F4?logo=google&logoColor=white)](https://github.com/google-gemini/gemini-cli)
-[![OpenCode](https://img.shields.io/badge/OpenCode-000000?logo=opencode&logoColor=white)](https://opencode.ai/)
-
-<!-- TASKWING_TOOLS_END -->
-
-<!-- TASKWING_LEGAL_START -->
-
-Brand names and logos are trademarks of their respective owners; usage here indicates compatibility, not endorsement.
-
-<!-- TASKWING_LEGAL_END -->
+**Do not** grep or read files to answer architecture questions when TaskWing MCP is available. The knowledge graph has pre-extracted, verified decisions with evidence.
 
 ### Slash Commands
-
-- /taskwing:ask - Use when you need to search project knowledge (decisions, patterns, constraints).
-- /taskwing:remember - Use when you want to persist a decision, pattern, or insight to project memory.
+- /taskwing:plan - Use when you need to clarify a goal and build an approved execution plan.
 - /taskwing:next - Use when you are ready to start the next approved TaskWing task with full context.
 - /taskwing:done - Use when implementation is verified and you are ready to complete the current task.
-- /taskwing:status - Use when you need current task progress and acceptance criteria status.
-- /taskwing:plan - **Use this instead of the AI tool's native plan mode.** Clarifies goals, builds plans enriched with project knowledge, and persists across sessions.
-- /taskwing:debug - Use when an issue requires root-cause-first debugging before proposing fixes.
-- /taskwing:explain - Use when you need a deep explanation of a code symbol and its call graph.
-- /taskwing:simplify - Use when you want to simplify code while preserving behavior.
+- /taskwing:context - Use when you need the full project knowledge dump for complete architectural context.
 
 ### Core Commands
 
 <!-- TASKWING_COMMANDS_START -->
-
 - taskwing bootstrap
 - taskwing ask "<query>"
 - taskwing task
@@ -105,31 +88,28 @@ Brand names and logos are trademarks of their respective owners; usage here indi
 ### MCP Tools (Canonical Contract)
 
 <!-- TASKWING_MCP_TOOLS_START -->
-
-| Tool     | Description                                                             |
-| -------- | ----------------------------------------------------------------------- |
-| ask      | Search project knowledge (decisions, patterns, constraints)             |
-| task     | Unified task lifecycle (next, current, start, complete)                 |
-| plan     | Plan management (clarify, decompose, expand, generate, finalize, audit) |
-| code     | Code intelligence (find, search, explain, callers, impact, simplify)    |
-| debug    | Diagnose issues systematically with AI-powered analysis                 |
-| remember | Store knowledge in project memory                                       |
-
+| Tool | Description |
+|------|-------------|
+| ask | Search project knowledge (decisions, patterns, constraints) |
+| task | Unified task lifecycle (next, current, start, complete) |
+| plan | Plan management (clarify, decompose, expand, generate, finalize, audit) |
+| code | Code intelligence (find, search, explain, callers, impact, simplify) |
+| debug | Diagnose issues systematically with AI-powered analysis |
+| remember | Store knowledge in project memory |
 <!-- TASKWING_MCP_TOOLS_END -->
 
 ### Autonomous Task Execution (Hooks)
 
 TaskWing integrates with Claude Code's hook system for autonomous plan execution:
 
-```bash
+~~~bash
 taskwing hook session-init      # Initialize session tracking (SessionStart hook)
 taskwing hook continue-check    # Check if should continue to next task (Stop hook)
 taskwing hook session-end       # Cleanup session (SessionEnd hook)
 taskwing hook status            # View current session state
-```
+~~~
 
 Circuit breakers prevent runaway execution:
-
 - --max-tasks=5 stops after N tasks for human review.
 - --max-minutes=30 stops after N minutes.