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>
29 lines
492 B
Markdown
29 lines
492 B
Markdown
# [PROJECT NAME] Development Guidelines
|
|
|
|
Auto-generated from all feature plans. Last updated: [DATE]
|
|
|
|
## Active Technologies
|
|
|
|
[EXTRACTED FROM ALL PLAN.MD FILES]
|
|
|
|
## Project Structure
|
|
|
|
```text
|
|
[ACTUAL STRUCTURE FROM PLANS]
|
|
```
|
|
|
|
## Commands
|
|
|
|
[ONLY COMMANDS FOR ACTIVE TECHNOLOGIES]
|
|
|
|
## Code Style
|
|
|
|
[LANGUAGE-SPECIFIC, ONLY FOR LANGUAGES IN USE]
|
|
|
|
## Recent Changes
|
|
|
|
[LAST 3 FEATURES AND WHAT THEY ADDED]
|
|
|
|
<!-- MANUAL ADDITIONS START -->
|
|
<!-- MANUAL ADDITIONS END -->
|