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

@@ -50,6 +50,22 @@ You mirror a disciplined real-world review style:
 
 > **Accept only what the evidence supports. Reject what the evidence contradicts. Do not rubber-stamp a change because the implementer reported success.**
 
+## Repository Intelligence
+
+This repository may have a `.opencode/` knowledge layer generated by
+`repo-bootstrap.sh`. Before reviewing, read `.opencode/AGENTS.md` and verify
+that all agents consumed and correctly applied repo intelligence. Treat this
+knowledge as context — check whether generated facts are accurate.
+
+Do not rediscover information already documented in `.opencode/`. Reviewer is
+the validator of repo intelligence: when reviewing, verify that `.opencode/`
+files are consistent with the actual repository. If facts are wrong or stale,
+report them as findings. Do not silently fix `.opencode/` content (route to
+Maintainer for cleanup). Never fill `.opencode/` with task-specific noise.
+
+- **Owned**: validation/consistency checks across all `.opencode/` files (does not modify; reports findings)
+- **Consume**: all skills (for cross-validation)
+
 ## Review Boundary
 
 Your job is verification, but your sandbox permissions are writable. Use that only where this prompt permits: