feat(plan-01): Phase 2 — relocate level5/agentops config + init-options to package

Move the harness-config files out of the mixed .specify/level5 and .specify/agentops
dirs (which also hold governance/domain/state) into packages/casan-harness, leaving a
per-file compat symlink at each old path. Runtime state and governance stay in place.

Moved (+ .specify symlink each):
  level5:   drift-policy.yaml kpi-schema.yaml model-fallback.yaml tool-registry.yaml
            harness-package.json project-registry.json provider-usage-sample.json
  agentops: alerts.yaml hallucination-tracking.yaml metrics.yaml rate-limits.yaml tracking.yaml
  top:      init-options.json
Stays in .specify: level5/central-governance (governance), level5/golden-runs (domain,
  Phase 3), agentops/alerts.log (state), traceability-map.json (domain, Phase 3).

Full gate: PASS=64 FAIL=0 SKIP=3 (CASAN_CI_STEP_TIMEOUT_SEC=1200).

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

AINative_OKR_CASAN5/.specify/level5/kpi-schema.yaml

@@ -1,27 +0,0 @@
-version: 1.0
-description: CASAN Level 5 business KPI feedback schema
-
-kpis:
-  - id: cycle_time_minutes
-    direction: lower_is_better
-    baseline: 180
-    target: 90
-
-  - id: review_rejection_rate
-    direction: lower_is_better
-    baseline: 0.30
-    target: 0.10
-
-  - id: defect_leakage_rate
-    direction: lower_is_better
-    baseline: 0.15
-    target: 0.05
-
-  - id: manual_rework_hours
-    direction: lower_is_better
-    baseline: 12
-    target: 4
-
-evidence:
-  input: docs/output/casan/level5-evidence/business-kpi-input.json
-  output: docs/output/casan/level5-evidence/business-kpi-report.json

AINative_OKR_CASAN5/.specify/level5/kpi-schema.yaml

@@ -0,0 +1 @@
+../../packages/casan-harness/level5/kpi-schema.yaml