Add Repository Intelligence Bootstrap: repo-bootstrap.sh, all 13 agents updated, docs, tests

- scripts/repo-bootstrap.sh: generic idempotent bootstrap tool (status/bootstrap/refresh)
  - creates .opencode/ with repo-context, architecture, build-and-test, conventions, deployment skills
  - relevance-based skill generation (only creates what the repo actually has)
  - staleness detection via .bootstrap-meta (key=value, SHA-256 fingerprints)
  - marker-based manual protection (never overwrites unmarked files)
  - accepts --root flag for explicit repo targeting

- scripts/test-repo-bootstrap.sh: 11 tests covering all 10 acceptance criteria
  - creation, idempotency, manual preservation, relevance detection
  - orchestrator/agent structural checks, staleness, genericness
  - install.sh workflow compatibility, malformed handling

- agents/orchestrator.md: first-class Repository Intelligence Bootstrap stage
  - 10-step workflow, ownership rules table, staleness signals
  - consumption rules, backward compatibility, fallback procedure

- All 12 subagent files: role-adapted Repository Intelligence section
  - architect: owns architecture skill
  - builder/tester: own build-and-test skill (shared)
  - explorer: owns repo-context skill
  - maintainer: owns conventions skill + audits .opencode/
  - reviewer: validates consistency (consumer/reporter)
  - designer/detective/philosopher/toolsmith/workflow-architect/writer: consume-only

- docs/REPOSITORY_INTELLIGENCE.md: full architecture documentation
- README.md: updated layout, bootstrap usage, requirements
- 13/13 agents installed, permission-engine verifier PASS

agents/detective.md

@@ -50,6 +50,22 @@ You mirror a disciplined real-world troubleshooting style:
 
 > **Do not guess when evidence can be obtained. Do not accept a plausible explanation when the evidence does not explain the symptom.**
 
+## Repository Intelligence
+
+This repository may have a `.opencode/` knowledge layer generated by
+`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.
+
+Do not rediscover information already documented in `.opencode/`. Detective is
+a consumer of repo intelligence; use existing knowledge to narrow the failure
+domain, but always verify root cause against the actual source. Do not modify
+`.opencode/` files. Never fill `.opencode/` with task-specific noise.
+
+- **Owned**: none (consumer role)
+- **Consume**: repo-context, build-and-test (when debugging test/build failures),
+  architecture (when tracing across modules)
+
 ## Investigation Boundary
 
 Your job is diagnosis, and your sandbox permissions are writable. Use that only where this prompt permits: