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>
This commit is contained in:
thanhnv
2026-07-08 00:06:00 +09:00
co-authored by Claude Opus 4.8
parent 2c765c9a45
commit 664bd1f00c
229 changed files with 268 additions and 3 deletions
@@ -0,0 +1,35 @@
#!/usr/bin/env bash
# CASAN shared log helper (source me, do not execute).
# Taxonomy (shared with scripts/casan-log.mjs): error < warn < info < debug < trace.
# CASAN_LOG_LEVEL selects the threshold (default: info). All log lines go to
# stderr so stdout contracts (CASAN_HARNESS_COMPLETE, cache=..., evidence
# .stdout files) stay byte-identical.
casan_log_num() {
case "$1" in
error) echo 0 ;;
warn) echo 1 ;;
info) echo 2 ;;
debug) echo 3 ;;
trace) echo 4 ;;
*) echo 2 ;;
esac
}
CASAN_LOG_LEVEL="${CASAN_LOG_LEVEL:-info}"
CASAN_LOG_THRESHOLD="$(casan_log_num "$CASAN_LOG_LEVEL")"
# casan_log <level> <component> <message...>
casan_log() {
local lvl="$1" comp="$2"
shift 2
[ "$(casan_log_num "$lvl")" -le "$CASAN_LOG_THRESHOLD" ] || return 0
# SEC-27 (X-02): log messages carry attacker-influenced data (action names, tool
# output snippets). Strip control chars — ESC/CSI (terminal-escape injection that
# rewrites a reviewer's screen) and CR/LF (fake-log-line injection) — keeping tab.
local msg; msg="$(printf '%s' "$*" | tr -d '\000-\010\012-\037\177')"
printf '[%s] %s [%s] %s\n' \
"$(printf '%s' "$lvl" | tr '[:lower:]' '[:upper:]')" \
"$(date -u +"%Y-%m-%dT%H:%M:%SZ")" \
"$comp" "$msg" >&2
}