feat(plan-01): Phase 1 — relocate harness code to packages/casan-harness (symlink facade)

Physically move the pure-code subtrees out of .specify into the package, leaving
compat symlinks at the old .specify/<dir> paths so every existing reference (internal
CASAN_HARNESS_ROOT + external CI/docker/mjs) keeps resolving. Runtime state stays put.

Moved (git mv): scripts/ tests/ security/ templates/ config/ governance/ memory/
  .specify/<dir>  ->  packages/casan-harness/<dir>   (+ .specify/<dir> symlink)
Stays in .specify (state/governance/domain, handled later): logs/ agentops/ level5/
  init-options.json traceability-map.json

Python `.resolve()` self-location followed the compat symlink into packages and lost
the app root; generate-casan-demo-context.py, generate-agentops-dashboard.py and
dashboard-server.py now walk UP for the `.specify` state marker instead of a fixed
parent depth (fixes "missing trace files" in run-casan4).

Full gate: PASS=64 FAIL=0 SKIP=3 (CASAN_CI_STEP_TIMEOUT_SEC=1200 — track-a ~450s runs
close to the 600s default and can tip over under load; this is timing variance, not a
regression — it passed cleanly with headroom). Runtime log/audit artifacts kept unstaged.

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

AINative_OKR_CASAN5/packages/casan-harness/scripts/bash/tool-exec.sh

@@ -0,0 +1,47 @@
+#!/usr/bin/env bash
+set -uo pipefail
+
+# CASAN H4 tool-execution guard.
+# Runs a command under a hard wall-clock timeout so a runaway/hung tool call
+# cannot block the pipeline indefinitely. Portable (uses `timeout` if present,
+# else a perl alarm) — macOS has no coreutils `timeout` by default.
+#
+# Scope (honest): this enforces a TIMEOUT only. True kernel sandboxing
+# (namespaces/seccomp/network isolation) requires running the tool inside a
+# container and is documented as a production requirement — it is NOT emulated
+# here. Do not present this as full sandboxing.
+#
+# Usage: tool-exec.sh <timeout-seconds> -- <command...>
+# Exit: command's exit code, or 124 on timeout.
+
+TIMEOUT="${1:-${CASAN_TOOL_TIMEOUT_SECONDS:-30}}"
+shift || true
+if [[ "${1:-}" == "--" ]]; then shift; fi
+if [[ "$#" -eq 0 ]]; then
+  echo "Usage: tool-exec.sh <timeout-seconds> -- <command...>" >&2
+  exit 64
+fi
+
+if command -v timeout >/dev/null 2>&1; then
+  timeout "$TIMEOUT" "$@"
+  rc=$?
+elif command -v perl >/dev/null 2>&1; then
+  perl -e 'my $t=shift; $SIG{ALRM}=sub{exit 124}; alarm($t); exec @ARGV or exit 127;' "$TIMEOUT" "$@"
+  rc=$?
+else
+  # SEC-15: no timeout backend. In enforced mode REFUSE (fail-closed) rather than
+  # run a command that could hang the pipeline; dev warns and proceeds.
+  if [[ "${CASAN_PROFILE:-}" == "prod" || "${CASAN_TOOL_EXEC_STRICT:-}" == "1" ]]; then
+    echo "TOOL_EXEC_NO_TIMEOUT_BACKEND refusing (fail-closed: install coreutils timeout or perl)" >&2
+    exit 2
+  fi
+  echo "TOOL_EXEC_NO_TIMEOUT_BACKEND (dev: running without timeout)" >&2
+  "$@"
+  rc=$?
+fi
+
+if [[ "$rc" -eq 124 || "$rc" -eq 142 ]]; then
+  echo "TOOL_EXEC_TIMEOUT after ${TIMEOUT}s" >&2
+  exit 124
+fi
+exit "$rc"