restore: re-add .opencode/ directory (OpenCode agent + command starters)

Restores the 20 tracked files deleted in commit f63769ac.
The user clarified that the .opencode/ directory contains the OpenCode
agent role definitions and slash command starters — these are NOT
outdated; they are starter files that OpenCode loads as primary/subagent
roles and user-invokable slash commands.

The .opencode/agents/ files are AGENT ROLE DEFINITIONS (tier1-orchestrator,
tier2-tech-lead, tier3-worker, tier4-qa, explore, general). OpenCode loads
these as primary/subagent roles.

The .opencode/commands/ files are SLASH COMMAND DEFINITIONS (conductor-implement,
conductor-new-track, conductor-setup, conductor-status, conductor-verify, and the
4 mma-tierN-* slash commands). OpenCode surfaces these as user-invokable commands.

These are NOT equivalent to .agents/skills/mma-*/SKILL.md (skill definitions
loaded on-demand via the Skill tool). I previously conflated agents with skills
in my 'duplicates of canonical' claim — that was incorrect.

Restoration method (per AGENTS.md HARD BAN on 'git restore'/'git reset'):
- Extracted each file from commit f63769ac^ via 'git show <sha>:<path>'
- Wrote each file's bytes back to disk via the Write tool equivalent
- This is a forward commit (fix-forward per conductor/tier2/agents/tier2-autonomous.md
  'timeline-is-immutable' principle); git history preserved.

f63769ac remains in history for forensics; this commit supersedes it.
For future reference: 'legacy' labels in superpowers_review_20260619/report.md §16.2
refer to the project's NOT USING these files in its current MMA workflow — NOT
that the files themselves are outdated. They remain starter templates for OpenCode.

.opencode/commands/mma-tier3-worker.md

@@ -0,0 +1 @@
+---description: Invoke Tier 3 Worker for surgical code implementationagent: tier3-worker---$ARGUMENTS---## ContextYou are now acting as Tier 3 Worker in the **META-TOOLING** domain (per `docs/guide_meta_boundary.md`). You implement surgical code changes for the manual_slop application codebase (the APPLICATION domain), per the spec/plan from Tier 1/2.### Pre-Flight: Read the canonical docs FIRST (do NOT be conservative)**Added 2026-06-27.** This project has extensive canonical documentation. Read the docs. Don't skim.Before ANY implementation, read:1. `AGENTS.md` — project-root rules; especially the HARD BANs2. `conductor/code_styleguides/python.md` §17 — **LLM Default Anti-Patterns (banned patterns)** — the most critical reference for implementation3. `conductor/code_styleguides/data_oriented_design.md` §8.5 — the Python Type Promotion Mandate4. `conductor/code_styleguides/type_aliases.md` — Metadata is the boundary type5. `conductor/code_styleguides/error_handling.md` — Result[T] + NIL_T sentinels6. The relevant `docs/guide_*.md` for the layer your task touches### Key Constraints- **STATELESS**: Context Amnesia — each task starts fresh- **MCP TOOLS ONLY**: Use `manual-slop_*` tools, NEVER native tools- **SURGICAL**: Follow WHERE/WHAT/HOW/SAFETY exactly- **1-SPACE INDENTATION**: For all Python code### The Banned Patterns (DO NOT INTRODUCE)From `conductor/code_styleguides/python.md` §17. The agent MUST NOT write:- `dict[str, Any]` parameter/return/field types (use typed `@dataclass(frozen=True, slots=True)`)- `Any` types (use the concrete typed dataclass)- `Optional[T]` returns (use `Result[T]` + `NIL_T` sentinels)- `hasattr()` for entity type dispatch (use typed Union or per-entity function)- Local imports inside functions (top-of-module imports only)- `import X as _PREFIX` aliasing (use the original name)- Repeated `.from_dict()` calls in the same expression (cache the result or promote the type)**The one exception:** the literal wire boundary (TOML/JSON parse functions) may use `dict[str, Any]` + `Metadata.from_dict(...)`.### Task Execution Protocol1. **Read Task Prompt**: Identify WHERE/WHAT/HOW/SAFETY2. **Use Skeleton Tools**: For files >50 lines, use `manual-slop_py_get_skeleton` or `manual-slop_get_file_summary`3. **Implement Exactly**: Follow specifications precisely; do NOT introduce banned patterns4. **Verify**: Run tests if specified via `manual-slop_run_powershell`5. **Report**: Return concise summary (what, where, issues)### Edit MCP Tools (USE THESE - BAN NATIVE EDIT)| Native Tool | MCP Tool ||-------------|----------|| `edit` | `manual-slop_edit_file` (find/replace, preserves indentation) || `edit` | `manual-slop_py_update_definition` (replace function/class) || `edit` | `manual-slop_set_file_slice` (replace line range) || `edit` | `manual-slop_py_set_signature` (replace signature only) || `edit` | `manual-slop_py_set_var_declaration` (replace variable) |**CRITICAL**: The native `edit` tool DESTROYS 1-space indentation. ALWAYS use MCP tools.### Blocking ProtocolIf you cannot complete the task:1. Start response with `BLOCKED:`2. Explain exactly why you cannot proceed3. List what information or changes would unblock you4. Do NOT attempt partial implementations that break the build### Code Style (Python)- 1-space indentation- NO COMMENTS unless explicitly requested- Type hints required- Internal methods/variables prefixed with underscore- NEVER use `git restore`, `git checkout --`, `git reset`, or `git revert` (per AGENTS.md HARD BAN)