Move the harness-config files out of the mixed .specify/level5 and .specify/agentops
dirs (which also hold governance/domain/state) into packages/casan-harness, leaving a
per-file compat symlink at each old path. Runtime state and governance stay in place.
Moved (+ .specify symlink each):
level5: drift-policy.yaml kpi-schema.yaml model-fallback.yaml tool-registry.yaml
harness-package.json project-registry.json provider-usage-sample.json
agentops: alerts.yaml hallucination-tracking.yaml metrics.yaml rate-limits.yaml tracking.yaml
top: init-options.json
Stays in .specify: level5/central-governance (governance), level5/golden-runs (domain,
Phase 3), agentops/alerts.log (state), traceability-map.json (domain, Phase 3).
Full gate: PASS=64 FAIL=0 SKIP=3 (CASAN_CI_STEP_TIMEOUT_SEC=1200).
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
25 lines
563 B
JSON
25 lines
563 B
JSON
{
|
|
"package": "fpt-casan-sdd-harness",
|
|
"version": "1.0.0",
|
|
"capabilities": [
|
|
"H4-security",
|
|
"H5-governance",
|
|
"H6-agentops",
|
|
"L5-drift-detection",
|
|
"L5-model-fallback",
|
|
"L5-tool-registry",
|
|
"L5-rollback",
|
|
"L5-business-feedback"
|
|
],
|
|
"compatibility": {
|
|
"speckit": ">=1.0.0",
|
|
"shell": "bash",
|
|
"python": ">=3.9"
|
|
},
|
|
"entrypoints": {
|
|
"wrapper": ".specify/scripts/bash/casan-harness.sh",
|
|
"test": ".specify/tests/run-casan4-harness-tests.sh",
|
|
"dashboard": "docs/output/casan/agentops-dashboard.html"
|
|
}
|
|
}
|