Decide policy for docs/superpowers/ — agent-workflow artifacts committed to the repo

[RealiCZ]

docs/superpowers/ holds 4 files that came out of the local agent (superpowers) dev workflow. They're a mixed bag, so this is a "decide a convention" issue rather than a straight delete:

File	Type	Referenced?
specs/2026-06-29-evm-session-spec-alignment-design.md	Design doc	✅ linked from docs/mpp-session-current-scheme.md:17
specs/2026-05-13-mpp-charge-design.md	Design doc	❌ not referenced
plans/2026-05-13-mpp-charge.md	Agent execution plan	❌ not referenced
plans/2026-05-14-mpp-gasless-charge.md	Agent execution plan	❌ not referenced

Why clean this up

• The plans/* files are implementation TODO checklists addressed to agents — they open with > For agentic workers: REQUIRED SUB-SKILL: Use superpowers:executing-plans .... They're build-time scaffolding, go stale the moment the feature ships, and nothing links to them.
• The folder is named after the agent tooling (superpowers) rather than its content, advertising an internal workflow detail in a public reference repo.
• The design specs are more defensible (a read-me-to-learn demo benefits from "why" docs), and one is actively linked — so this is not a blanket delete.

Proposed resolution

1. git rm docs/superpowers/plans/ — drop the two agent execution plans.
2. Keep the design specs, but move them to a neutral path (e.g. docs/design/) and update the link at docs/mpp-session-current-scheme.md:17.
3. Add docs/superpowers/ to .gitignore so future workflow output isn't re-committed.

Caveat: moving/removing specs/2026-06-29-evm-session-spec-alignment-design.md requires updating docs/mpp-session-current-scheme.md:17 or that link 404s.

No secrets are exposed — this is a tidiness / staleness call. Filing to agree on a convention before more plans/ accumulate.