feat(plan-01): Phase 4b — external callers to packages paths + registry (Task 1.7)

Point the canonical entry points at the new package layout; the .specify compat facade
is retained as an intentional backward-compat layer (see below).

- .gitea/workflows/{ci,harness-ci}.yml: invoke packages/casan-harness/scripts/bash|tests
  (state paths .specify/logs kept). CI now runs on the new structure.
- infra/local-prod/docker-compose.yml: dashboard-server.py -> packages path (logs/alerts
  env stay under .specify state).
- scripts/casan-step.mjs + run-casan-pipeline.mjs: resolve the harness under
  packages/casan-harness, falling back to .specify so the adversarial/sourcegen sandboxes
  (which stage a .specify/ tree) keep working; requirement input prefers apps/okr/domain/input.
- project-registry.json: record the new layout (harness_root, state_root, governance_root,
  per-project domain_root) so Plan-06 can register a second app with its own domain.
  verify-harness-reuse.sh already resolves via CASAN_HARNESS_ROOT -> HARNESS_REUSE_VALID (3 projects).

Facade decision: the .specify/{scripts,tests,security,...} symlinks are KEPT as a
documented compat layer. A full hard cutover (removing them) still needs ~15 literal
`.specify/...` refs repointed (loop_common/evidence-pack/secrets-scan config+test paths,
run-casan-pipeline step scripts, and the signed policy-bundle.yaml path list which then
needs manifest regen + re-sign). That is a scoped follow-up; the physical separation
(code in packages/, domain in apps/, packages holds no domain data, single CASAN_* path
indirection) is complete and the full gate is green via BOTH entry paths: PASS=64 FAIL=0 SKIP=3.

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

AINative_OKR_CASAN5/packages/casan-harness/level5/project-registry.json

@@ -1,9 +1,16 @@
 {
   "registry": "fpt-casan-harness-adoption",
+  "layout": {
+    "note": "Plan-01 restructure: reusable harness is a standalone package; each project keeps its domain data separate. A new project (Plan-06) registers here with its own domain_root.",
+    "harness_root": "packages/casan-harness",
+    "state_root": ".specify",
+    "governance_root": ".specify/level5/central-governance"
+  },
   "projects": [
     {
       "project_id": "AINative_OKR_CASAN4",
       "domain": "SDD OKR",
+      "domain_root": "apps/okr/domain",
       "harness_package": "fpt-casan-sdd-harness",
       "harness_version": "1.0.0",
       "status": "active"
@@ -11,6 +18,7 @@
     {
       "project_id": "CASAN_DEMO_PROJECT_A",
       "domain": "Demo SDLC",
+      "domain_root": "apps/demo-sdlc/domain",
       "harness_package": "fpt-casan-sdd-harness",
       "harness_version": "1.0.0",
       "status": "registered"
@@ -18,6 +26,7 @@
     {
       "project_id": "CASAN_DEMO_PROJECT_B",
       "domain": "Demo QA",
+      "domain_root": "apps/demo-qa/domain",
       "harness_package": "fpt-casan-sdd-harness",
       "harness_version": "1.0.0",
       "status": "registered"