Implement self-contained runtime: install runtime tree, git-root memory, canonical agent paths, + 4 suites

- install.sh: install runtime tree under OPENCODE_DEV_AGENT_TEAM
  (bin/, 12 skills, improvements/, install-manifest.json), idempotent
  shell-rc export, --uninstall (preserves improvements/ user data) and
  --migrate; preserves 13-agent copy, .backup retention, KEEP_BACKUPS=5,
  count gate, cmp -s integrity, install-time permission gate
- memory-lifecycle.sh: resolve MEMORY_DIR from project git root + OPENCODE_MEMORY_DIR
- all 13 agents: canonical runtime sentence + env-resolved runtime paths;
  project-scoped refs unchanged
- tests: new test-install (15), test-runtime (10), test-path-resolution (12),
  test-memory-isolation (12); TEAM_ROOT override on existing 4 suites;
  test-all.sh registers 8 suites (100 checks total)

agents/explorer.md

@@ -47,7 +47,7 @@ READ → UNDERSTAND → TRACE → DISTINGUISH EVIDENCE FROM INFERENCE → REPORT
 ## Repository Intelligence
 
 This repository may have a `.opencode/` knowledge layer generated by
-`repo-bootstrap.sh`. Before investigating, read `.opencode/AGENTS.md` and
+`"${OPENCODE_DEV_AGENT_TEAM:-$HOME/.config/opencode/dev-agent-team}"/bin/repo-bootstrap.sh`. Before investigating, read `.opencode/AGENTS.md` and
 `.opencode/skills/repo-context/SKILL.md`. Treat this knowledge as context —
 verify it against the actual repository when it contradicts what you observe.
 
@@ -81,18 +81,20 @@ Your primary evidence is the system map with `file:line` references. Separate ob
 
 Stop when your deliverable is complete and verified per your Completion Rule; escalate when required evidence is missing or the question is ambiguous.
 
+Global runtime: always resolve via `"${OPENCODE_DEV_AGENT_TEAM:-$HOME/.config/opencode/dev-agent-team}"`. Runtime-owned artifacts live under `bin/` (scripts), `skills/` (12 skills), `improvements/`. Project-scoped artifacts (`memory/`, `.opencode/`, `./AgentsReport/`) stay relative to this project.
+
 ## Memory & Skills Awareness
 
 Before investigating, check project memory for relevant context:
-- `scripts/memory-lifecycle.sh recall lessons <keywords>` — for similar past investigations
-- `scripts/memory-lifecycle.sh recall failures <keywords>` — for related incidents
-- `scripts/memory-lifecycle.sh recall decisions <keywords>` — for established architectural decisions
+- `"${OPENCODE_DEV_AGENT_TEAM:-$HOME/.config/opencode/dev-agent-team}"/bin/memory-lifecycle.sh recall lessons <keywords>` — for similar past investigations
+- `"${OPENCODE_DEV_AGENT_TEAM:-$HOME/.config/opencode/dev-agent-team}"/bin/memory-lifecycle.sh recall failures <keywords>` — for related incidents
+- `"${OPENCODE_DEV_AGENT_TEAM:-$HOME/.config/opencode/dev-agent-team}"/bin/memory-lifecycle.sh recall decisions <keywords>` — for established architectural decisions
 
 After completing substantial investigation, store durable findings:
-- New system understanding → `scripts/memory-lifecycle.sh store lessons <file>`
-- Related incidents found → `scripts/memory-lifecycle.sh store failures <file>`
+- New system understanding → `"${OPENCODE_DEV_AGENT_TEAM:-$HOME/.config/opencode/dev-agent-team}"/bin/memory-lifecycle.sh store lessons <file>`
+- Related incidents found → `"${OPENCODE_DEV_AGENT_TEAM:-$HOME/.config/opencode/dev-agent-team}"/bin/memory-lifecycle.sh store failures <file>`
 
-Load relevant skills when your brief includes a skill path (e.g., `skills/repository-analysis/SKILL.md`).
+Load relevant skills when your brief includes a skill path (e.g., `"${OPENCODE_DEV_AGENT_TEAM:-$HOME/.config/opencode/dev-agent-team}"/skills/repository-analysis/SKILL.md`).
 Do NOT re-derive patterns already documented in memory or skills.
 
 ## Investigation Boundary