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/project-registry.json

@@ -1,26 +0,0 @@
-{
-  "registry": "fpt-casan-harness-adoption",
-  "projects": [
-    {
-      "project_id": "AINative_OKR_CASAN4",
-      "domain": "SDD OKR",
-      "harness_package": "fpt-casan-sdd-harness",
-      "harness_version": "1.0.0",
-      "status": "active"
-    },
-    {
-      "project_id": "CASAN_DEMO_PROJECT_A",
-      "domain": "Demo SDLC",
-      "harness_package": "fpt-casan-sdd-harness",
-      "harness_version": "1.0.0",
-      "status": "registered"
-    },
-    {
-      "project_id": "CASAN_DEMO_PROJECT_B",
-      "domain": "Demo QA",
-      "harness_package": "fpt-casan-sdd-harness",
-      "harness_version": "1.0.0",
-      "status": "registered"
-    }
-  ]
-}

AINative_OKR_CASAN5/.specify/level5/project-registry.json

@@ -0,0 +1 @@
+../../packages/casan-harness/level5/project-registry.json