Files
CASAN/AINative_OKR_CASAN5/packages/casan-harness/scripts/bash/dashboard-serve.sh
T
thanhnvandClaude Opus 4.8 3adc48ed82 feat(plan-01): Phase 4a — make harness location-independent (facade-free capable)
Resolve every root by marker walk-up instead of a fixed depth that only lands on the
app via the .specify compat symlink, so the harness runs correctly when invoked by its
real packages/casan-harness path — proven by a full gate run via that path: 64/0/0.

- 95 scripts/tests: PROJECT_ROOT/ROOT "$SCRIPT_DIR/../.."-style computations -> $CASAN_APP_ROOT.
- 6 leaf scripts (infra-lab, context-validate, secrets-scan, path-guard, toolchain-verify,
  phase2-sourcegen) now source casan-paths + use CASAN_APP_ROOT.
- run-casan4: source casan-paths as a package sibling (facade-independent), PROJECT_ROOT=CASAN_APP_ROOT.
- 8 Python files: project_root()/REPO_ROOT/bundle_root walk UP for the .specify marker
  (control-plane-settings, loop_common, model-call, context-compress, test-integrity,
  bundle-integrity, traceability-matrix; generate-* fixed earlier).
- evidence-pack-build.py + traceability-matrix.py: domain refs -> apps/okr/domain
  (input/, corpus/redteam-vectors.jsonl, traceability-map.json).
- ci-harness-gate.sh: export CASAN_TESTS_DIR/CASAN_TEST_MANIFEST/CASAN_BUNDLE_ROOT so the
  integrity Python resolves via the harness root regardless of invocation path; ROOT=CASAN_APP_ROOT.
- Remove the domain compat symlinks from packages/casan-harness/security (redteam-corpus,
  redteam-vectors, benign-corpus) — packages now holds NO domain data.

Both invocation paths pass (compat facade still present): .specify/... and packages/...

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-07-08 10:50:50 +09:00

73 lines
2.4 KiB
Bash

#!/usr/bin/env bash
set -uo pipefail
# CASAN H6 — hosted AgentOps dashboard (D3).
# Regenerates the dashboard then serves it over HTTP (dashboard-server.py)
# with a stale-aware /healthz probe. MVP hosting: local HTTP daemon with a
# pid file; production swaps in a real host (nginx/container) same routes.
#
# Usage:
# dashboard-serve.sh start [port] regenerate + serve (default port 8787)
# dashboard-serve.sh stop stop the running server
# dashboard-serve.sh status curl /healthz of the running server
#
# Env: CASAN_DASHBOARD_STALE_S, CASAN_DASHBOARD_METRICS, CASAN_DASHBOARD_HTML,
# CASAN_AGENTOPS_DIR (pid-file location)
#
# Greppable outputs: DASHBOARD_HOSTED | DASHBOARD_STOPPED | DASHBOARD_NOT_RUNNING
SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
source "$SCRIPT_DIR/casan-paths.sh"
PROJECT_ROOT="$CASAN_APP_ROOT"
AGENTOPS_DIR="${CASAN_AGENTOPS_DIR:-$CASAN_HARNESS_ROOT/agentops}"
PID_FILE="$AGENTOPS_DIR/dashboard.pid"
PORT_FILE="$AGENTOPS_DIR/dashboard.port"
GENERATOR="$CASAN_HARNESS_ROOT/tests/generate-agentops-dashboard.py"
CMD="${1:-start}"
mkdir -p "$AGENTOPS_DIR"
case "$CMD" in
start)
PORT="${2:-8787}"
if [[ -f "$GENERATOR" ]]; then
python "$GENERATOR" >/dev/null 2>&1 || true
fi
python "$SCRIPT_DIR/dashboard-server.py" "$PORT" &
SERVER_PID=$!
echo "$SERVER_PID" > "$PID_FILE"
echo "$PORT" > "$PORT_FILE"
for _ in 1 2 3 4 5 6 7 8 9 10; do
if curl -sS -m 2 -o /dev/null "http://127.0.0.1:$PORT/healthz" 2>/dev/null; then
echo "DASHBOARD_HOSTED url=http://127.0.0.1:$PORT/ healthz=http://127.0.0.1:$PORT/healthz pid=$SERVER_PID"
exit 0
fi
sleep 0.3
done
echo "DASHBOARD_START_FAILED port=$PORT (server did not come up)" >&2
kill "$SERVER_PID" 2>/dev/null
rm -f "$PID_FILE" "$PORT_FILE"
exit 1
;;
stop)
if [[ -f "$PID_FILE" ]] && kill "$(cat "$PID_FILE")" 2>/dev/null; then
echo "DASHBOARD_STOPPED pid=$(cat "$PID_FILE")"
rm -f "$PID_FILE" "$PORT_FILE"
exit 0
fi
echo "DASHBOARD_NOT_RUNNING" >&2
rm -f "$PID_FILE" "$PORT_FILE"
exit 1
;;
status)
if [[ -f "$PORT_FILE" ]]; then
curl -sS -m 3 "http://127.0.0.1:$(cat "$PORT_FILE")/healthz" && echo "" && exit 0
fi
echo "DASHBOARD_NOT_RUNNING" >&2
exit 1
;;
*)
echo "Usage: dashboard-serve.sh start [port] | stop | status" >&2
exit 64
;;
esac