CASAN/AINative_OKR_CASAN5/packages/casan-harness/scripts/bash/guideH4-H5-H6.md at f2ea5590b1976d52dbf159f0c581dbb4fa853285

Files

T

thanhnvandClaude Opus 4.8 664bd1f00c 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>

2026-07-08 00:06:00 +09:00

516 B

Raw Blame History

INPUT ↓ security-check.sh input (H4: prompt injection, PII, secret) ↓ governance-check.sh (H5: risk, approval, hash-chain audit) ↓ agent-metrics.sh (H6: latency, tokens, cost, retry, status, alert) ↓ security-check.sh output (H4: output redaction/filter) ↓ OUTPUT ↓ LOG + TRACE + METRICS + AUDIT

Unified wrapper:

.specify/scripts/bash/casan-harness.sh input.txt output.txt agent_step

Verification:

bash .specify/tests/run-casan4-harness-tests.sh

516 B Raw Blame History

516 B

Raw Blame History