Drop devin-tools.md — not needed for correct operation

Re-ran the clean-session acceptance test with the mapping file and the
SKILL.md Platform Adaptation pointer removed: using-superpowers and
brainstorming still auto-trigger first, and the full workflow chain
(writing-plans, executing-plans, TDD, verification) resolves every action
to Devin's native tools. Devin CLI's own system prompt already documents
its tools (skill invocation, subagent profiles, todo tracking, question
prompts), so the mapping was redundant. Test now validates the manifest only.

skills/using-superpowers/SKILL.md

@@ -57,7 +57,6 @@ If your harness appears here, read its reference file for special instructions:
 - Pi: `references/pi-tools.md`
 - Antigravity: `references/antigravity-tools.md`
 - Hermes Agent: `references/hermes-tools.md`
-- Devin CLI: `references/devin-tools.md`
 
 ## User Instructions
 

skills/using-superpowers/references/devin-tools.md

@@ -1,18 +0,0 @@
-# Devin CLI Tool Mapping
-
-Skills speak in actions ("dispatch a subagent", "create a todo", "read a file"). On Devin CLI these resolve to the tools below.
-
-| Action skills request | Devin CLI equivalent |
-| --- | --- |
-| Invoke a skill | The native `skill` tool (skills also appear as `/superpowers:<skill>` slash commands) |
-| Dispatch a subagent (`Subagent (general-purpose):` template) | `run_subagent` with the `subagent_general` profile; use `subagent_explore` for read-only exploration |
-| Task tracking ("create a todo", "mark complete") | `todo_write` |
-| Ask the user / present options | `ask_user_question` (native multiple-choice prompts; fall back to plain text in non-interactive mode) |
-
-## Subagents
-
-`run_subagent` subagents are stateless and cannot ask clarifying questions — front-load the full context and exact instructions in the task prompt, as the subagent-driven-development templates already do. Run independent tasks in parallel with `is_background: true`; keep dependent tasks sequential.
-
-## File, shell, and search tools
-
-Devin CLI exposes native tools for reading, writing, and editing files, running shell commands, and searching (grep/glob). Exact tool names can vary by session mode — use whichever file/shell/search tools your session exposes rather than names remembered from another harness.

tests/devin/test-devin-plugin.sh

@@ -3,25 +3,22 @@
 # reads `.devin-plugin/plugin.json` and auto-discovers the co-located `skills/`
 # directory; Devin CLI surfaces every installed skill's name + description in
 # the system prompt at session start and invokes them via its native `skill`
-# tool, so there is no hook or injector scaffold to test. What IS Devin-specific
-# is the manifest and the tool mapping — subagent dispatch via run_subagent
-# profiles and task tracking via todo_write — and SKILL.md pointing at it.
+# tool, and its system prompt already documents its own tools (subagent
+# profiles, todo tracking, question prompts), so there is no hook, injector,
+# or tool-mapping scaffold to test. What IS Devin-specific is the manifest.
 #
-# Mirrors tests/kimi/test-plugin-manifest.sh (manifest) and
-# tests/antigravity/test-antigravity-tools.sh (mapping). CI-safe: does not
-# require `devin` installed.
+# Mirrors tests/kimi/test-plugin-manifest.sh. CI-safe: does not require
+# `devin` installed.
 set -euo pipefail
 
 SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
 REPO_ROOT="$(cd "$SCRIPT_DIR/../.." && pwd)"
 
 MANIFEST="$REPO_ROOT/.devin-plugin/plugin.json"
-MAPPING="$REPO_ROOT/skills/using-superpowers/references/devin-tools.md"
-SKILL="$REPO_ROOT/skills/using-superpowers/SKILL.md"
 
 fail() { echo "FAIL: $*" >&2; exit 1; }
 
-echo "test-devin-plugin: checking Devin CLI manifest and tool mapping"
+echo "test-devin-plugin: checking Devin CLI manifest"
 
 # --- Manifest is valid and matches the repo version -------------------------
 [ -f "$MANIFEST" ] || fail "manifest missing at $MANIFEST"
@@ -63,23 +60,4 @@ if not isinstance(entries, list) or not any(
 print("Devin plugin manifest looks good")
 PY
 
-# --- Mapping exists ----------------------------------------------------------
-[ -f "$MAPPING" ] || fail "tool mapping missing at $MAPPING"
-
-# --- Core action→tool mappings are documented --------------------------------
-for tool in skill run_subagent todo_write ask_user_question; do
-  grep -q "$tool" "$MAPPING" \
-    || fail "mapping does not document the '$tool' tool"
-done
-
-# --- Subagents use the built-in profiles --------------------------------------
-grep -q 'subagent_general' "$MAPPING" \
-  || fail "mapping does not document the 'subagent_general' profile"
-grep -q 'subagent_explore' "$MAPPING" \
-  || fail "mapping does not document the 'subagent_explore' profile"
-
-# --- SKILL.md Platform Adaptation links the mapping ---------------------------
-grep -q "devin-tools.md" "$SKILL" \
-  || fail "SKILL.md Platform Adaptation does not reference devin-tools.md"
-
-echo "PASS: Devin CLI plugin valid (manifest, tool mapping, SKILL.md link)"
+echo "PASS: Devin CLI plugin valid (manifest)"