chore: bootstrap repo with chunks 1 and 2

Establishes the global AI development config repo from scratch:

- Chunk 1: repo skeleton, install.sh, statusline, deploy manifest
- Chunk 2: core instructions (coding/git/testing), CLAUDE.md rewrite
  (always-on + content index two-tier model), docs restructure,
  6 ADRs, ROADMAP.md, .gitkeep placeholders
- Bootstrap skills in .claude/skills/ (to be catalogued and migrated
  to .agents/skills/ in Chunk 3)

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

core/instructions/coding.md

@@ -0,0 +1,7 @@
+# Coding conventions
+
+- Automate anything repeatable. If done manually twice, it belongs in a script, hook, or pipeline step.
+- No comments unless the why is genuinely non-obvious. Names carry meaning; git history carries context.
+- No defensive code at internal boundaries. Validate only at system edges: user input, external APIs, git hooks.
+- Prefer explicit over implicit. Code must be readable without inferring intent from convention.
+- No abstractions, features, or cleanup beyond what the task requires.

core/instructions/git.md

@@ -0,0 +1,7 @@
+# Git conventions
+
+- Never skip hooks with `--no-verify`. Hooks are the automated QA gate; bypassing them breaks the pipeline.
+- Never force-push main or master.
+- Commit messages explain why, not what. Written for both humans and changelog generators.
+- Never commit secrets, credentials, or environment-specific config.
+- Use conventional commits: `feat:`, `fix:`, `docs:`, `chore:`, `refactor:`, `test:`

core/instructions/testing.md

@@ -0,0 +1,6 @@
+# Testing conventions
+
+- Prefer integration tests over mocks. Mocks mask production divergence; real systems catch real failures.
+- Automate everything automatable. Manual testing only for nuanced UI/UX or agent interaction behaviour requiring human judgment.
+- Test observable end-state, not implementation internals. Tests must survive refactoring.
+- No test is better than a wrong test. A passing mock that masks a real failure is actively harmful.