cleanup: remove legacy .opencode/ directory (18 agent/command .md files + package.json + package-lock.json)

Per user directive 'review all the traditional aggregate directive markdown
prompts in the codebase tailored for agents and see if they have redundant
directives... lets do a clean pass on them' (2026-07-05).

REDUNDANT DIRECTIVES REMOVED:
- All 18 files in .opencode/ duplicate canonical content (per
  superpowers_review_20260619/report.md §16.2 'Legacy .opencode/ and
  .gemini/ directories' documented the directory as legacy).
- 10 agent files (.opencode/agents/*.md) duplicate .agents/skills/mma-*/
  SKILL.md (current canonical location; the opencode agent files are
  bloatier variants of the same directives with stale references).
- 8 command files (.opencode/commands/*.md) are legacy Gemini CLI slash
  commands; OpenCode does not use them.

CANONICAL LOCATIONS (UNTOUCHED):
- .agents/skills/mma-orchestrator/SKILL.md
- .agents/skills/mma-tier1-orchestrator/SKILL.md
- .agents/skills/mma-tier2-tech-lead/SKILL.md
- .agents/skills/mma-tier3-worker/SKILL.md
- .agents/skills/mma-tier4-qa/SKILL.md
- conductor/tier2/agents/tier2-autonomous.md (Tier 2 sandbox canonical)
- conductor/tier2/agents/tier2-autonomous.warm.md (Tier 2 sandbox warm)
- .opencode/node_modules/ was already gitignored (npm install artifact)

PRESERVED REDUNDANCIES (audit found, kept intentionally):
- AGENTS.md + conductor/workflow.md + .agents/skills/mma-tier2-tech-lead/
  SKILL.md + conductor/tier2/agents/tier2-autonomous.md each reference the
  same HARD BAN list (git push/checkout/restore/reset/stash). Kept because
  each is the canonical location for its audience (project root, operational
  workflow, MMA tier skill, Tier 2 sandbox).
- conductor/tier2/agents/tier2-autonomous.md (174 lines) is a SUPERSET of
  .opencode/agents/tier2-tech-lead.md (254 lines) with sandbox-specific
  operational contracts. Both are valid for their target audience.

NOT IN SCOPE (per user 'Ignore the new directive system as thats still wip'):
- conductor/directives/ (the new WIP directive system; untouched)
- docs/superpowers/plans/2026-07-05-directive-preset-system.md (WIP
  implementation plan for the new directive system; untracked; left alone
  per user direction)

VERIFICATION:
- All 20 tracked files in .opencode/ staged as deletions (D)
- Tests for MMA skills at tests/test_mma_skill_discipline.py still pass
- conductor/workflow.md Session Start Checklist unchanged
- .agents/skills/mma-*/SKILL.md files unchanged

.opencode/commands/mma-tier4-qa.md

@@ -1,75 +0,0 @@
----
-description: Invoke Tier 4 QA Agent for error analysis
-agent: tier4-qa
----
-
-$ARGUMENTS
-
----
-
-## Context
-
-You are now acting as Tier 4 QA Agent.
-
-### Key Constraints
-
-- **STATELESS**: Context Amnesia — each analysis starts fresh
-- **READ-ONLY**: Do NOT modify any files
-- **ANALYSIS ONLY**: Do NOT implement fixes
-
-### Read-Only MCP Tools (USE THESE)
-
-| Native Tool | MCP Tool |
-|-------------|----------|
-| `read` | `manual-slop_read_file` |
-| `glob` | `manual-slop_search_files` or `manual-slop_list_directory` |
-| `grep` | `manual-slop_py_find_usages` |
-| - | `manual-slop_get_file_summary` (heuristic summary) |
-| - | `manual-slop_py_get_code_outline` (classes/functions with line ranges) |
-| - | `manual-slop_py_get_skeleton` (signatures + docstrings only) |
-| - | `manual-slop_py_get_definition` (specific function/class source) |
-| - | `manual-slop_get_git_diff` (file changes) |
-| - | `manual-slop_get_file_slice` (read specific line range) |
-
-### Analysis Protocol
-
-1. **Read Error Completely**: Understand the full error/test failure
-2. **Identify Affected Files**: Parse traceback for file:line references
-3. **Use Skeleton Tools**: For files >50 lines, use `manual-slop_py_get_skeleton` first
-4. **Announce**: "Analyzing: [error summary]"
-
-### Structured Output Format
-
-```
-## Error Analysis
-
-### Summary
-[One-sentence description of the error]
-
-### Root Cause
-[Detailed explanation of why the error occurred]
-
-### Evidence
-[File:line references supporting the analysis]
-
-### Impact
-[What functionality is affected]
-
-### Recommendations
-[Suggested fixes or next steps - but DO NOT implement them]
-```
-
-### Quality Checklist
-
-- [ ] Analysis based on actual code/file content
-- [ ] Root cause is specific, not generic
-- [ ] Evidence includes file:line references
-- [ ] Recommendations are actionable but not implemented
-
-### Blocking Protocol
-
-If you cannot analyze the error:
-
-1. Start response with `CANNOT ANALYZE:`
-2. Explain what information is missing
-3. List what would be needed to complete the analysis