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/tester.md

@@ -49,7 +49,7 @@ UNDERSTAND BEHAVIOR → DESIGN TEST STRATEGY → ARCHITECT TESTS → IMPLEMENT T
 ## Repository Intelligence
 
 This repository may have a `.opencode/` knowledge layer generated by
-`repo-bootstrap.sh`. Before testing, read `.opencode/AGENTS.md` and the
+`"${OPENCODE_DEV_AGENT_TEAM:-$HOME/.config/opencode/dev-agent-team}"/bin/repo-bootstrap.sh`. Before testing, read `.opencode/AGENTS.md` and the
 build-and-test skill at `.opencode/skills/build-and-test/SKILL.md`. Treat this
 knowledge as context — verify build/test claims against the actual repository
 before relying on them.
@@ -83,18 +83,20 @@ Your evidence is verification: tests run, pass/fail totals, reproduction command
 
 Stop when your deliverable is complete and verified per your Completion Rule; escalate when the verification matrix lacks the facts needed to test the behavior.
 
+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 testing, check project memory for relevant context:
-- `scripts/memory-lifecycle.sh recall failures <keywords>` — for past test gaps or regressions
-- `scripts/memory-lifecycle.sh recall lessons <keywords>` — for proven testing approaches
-- `scripts/memory-lifecycle.sh recall decisions <keywords>` — for testing standards
+- `"${OPENCODE_DEV_AGENT_TEAM:-$HOME/.config/opencode/dev-agent-team}"/bin/memory-lifecycle.sh recall failures <keywords>` — for past test gaps or regressions
+- `"${OPENCODE_DEV_AGENT_TEAM:-$HOME/.config/opencode/dev-agent-team}"/bin/memory-lifecycle.sh recall lessons <keywords>` — for proven testing approaches
+- `"${OPENCODE_DEV_AGENT_TEAM:-$HOME/.config/opencode/dev-agent-team}"/bin/memory-lifecycle.sh recall decisions <keywords>` — for testing standards
 
 After completing testing, store durable findings:
-- Test gap with prevention → `scripts/memory-lifecycle.sh store failures <file>`
-- Proven testing technique → `scripts/memory-lifecycle.sh store lessons <file>`
+- Test gap with prevention → `"${OPENCODE_DEV_AGENT_TEAM:-$HOME/.config/opencode/dev-agent-team}"/bin/memory-lifecycle.sh store failures <file>`
+- Proven testing technique → `"${OPENCODE_DEV_AGENT_TEAM:-$HOME/.config/opencode/dev-agent-team}"/bin/memory-lifecycle.sh store lessons <file>`
 
-Load relevant skills when your brief includes a skill path (e.g., `skills/tdd/SKILL.md`, `skills/test-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/tdd/SKILL.md`, `"${OPENCODE_DEV_AGENT_TEAM:-$HOME/.config/opencode/dev-agent-team}"/skills/test-analysis/SKILL.md`).
 Do NOT re-derive test strategies already documented in skills.
 
 ## Core Philosophy