feat: plan-01 Phase 0 — restructure skeleton (packages/casan-harness + apps/okr/domain)

Empty package/app skeleton for the harness restructure. No harness files moved yet; full gate baseline stays PASS=64 FAIL=0 SKIP=3. Subdirs materialize via git mv in Phases 1-5.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

AINative_OKR_CASAN5/apps/okr/domain/README.md

@@ -0,0 +1,9 @@
+# apps/okr/domain (skeleton)
+
+OKR-domain data consumed by the CASAN harness, kept separate from the reusable harness package.
+Populated in Plan-01 Phase 5. Referenced by scripts via `CASAN_DOMAIN_ROOT` (default this dir).
+
+Planned contents (moved from `.specify/` / `docs/` in Phase 5):
+- `golden-runs/` — golden baselines for drift/H7 (from `.specify/level5/golden-runs/`)
+- `input/` — requirement/architecture specs (from `docs/input/`)
+- `corpus/` — redteam + benign corpora (from `.specify/security/redteam-*.jsonl`, `benign-corpus/`)

AINative_OKR_CASAN5/packages/casan-harness/README.md

@@ -0,0 +1,17 @@
+# casan-harness (package skeleton)
+
+Core CASAN harness (gate H1→H7) as a reusable package, independent of domain data.
+Populated incrementally by Plan-01 (Phase 0→6). During migration, files move here from
+`.specify/` wave-by-wave; the full harness gate must stay green (`PASS=64 FAIL=0`) after each phase.
+
+Layout:
+- `scripts/` — bash + powershell gate logic (H1→H7), path resolver `casan-paths.sh`
+- `security/` — filter/policy rules (prompt-filter, pii-rules, output-policy, ...)
+- `governance/`, `agentops/` — H5/H6 code
+- `level5/` — L5 config (drift/kpi/model-fallback/tool-registry YAMLs)
+- `templates/`, `config/` — spec/plan templates, loop-policy
+- `tests/` — reproducible harness test suites + integrity manifest
+
+Runtime state (logs, audit chain, tenant state) is NOT part of this package — it stays with
+the app under `CASAN_STATE_ROOT`. Domain data (golden-runs, corpus, input) lives in
+`apps/okr/domain/` under `CASAN_DOMAIN_ROOT`.