Point the canonical entry points at the new package layout; the .specify compat facade
is retained as an intentional backward-compat layer (see below).
- .gitea/workflows/{ci,harness-ci}.yml: invoke packages/casan-harness/scripts/bash|tests
(state paths .specify/logs kept). CI now runs on the new structure.
- infra/local-prod/docker-compose.yml: dashboard-server.py -> packages path (logs/alerts
env stay under .specify state).
- scripts/casan-step.mjs + run-casan-pipeline.mjs: resolve the harness under
packages/casan-harness, falling back to .specify so the adversarial/sourcegen sandboxes
(which stage a .specify/ tree) keep working; requirement input prefers apps/okr/domain/input.
- project-registry.json: record the new layout (harness_root, state_root, governance_root,
per-project domain_root) so Plan-06 can register a second app with its own domain.
verify-harness-reuse.sh already resolves via CASAN_HARNESS_ROOT -> HARNESS_REUSE_VALID (3 projects).
Facade decision: the .specify/{scripts,tests,security,...} symlinks are KEPT as a
documented compat layer. A full hard cutover (removing them) still needs ~15 literal
`.specify/...` refs repointed (loop_common/evidence-pack/secrets-scan config+test paths,
run-casan-pipeline step scripts, and the signed policy-bundle.yaml path list which then
needs manifest regen + re-sign). That is a scoped follow-up; the physical separation
(code in packages/, domain in apps/, packages holds no domain data, single CASAN_* path
indirection) is complete and the full gate is green via BOTH entry paths: PASS=64 FAIL=0 SKIP=3.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
The checkout action clones from http://gitea:3000/admin/casan5 — hostname 'gitea'
only resolves on the docker-compose network (gitea_default), not on the default
Docker bridge. Changing container.network: bridge → gitea_default fixes DNS.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Sequential jobs (security-gate needs frontend-tests) mean only one container
runs at a time. 768MB + Gitea/Vault/OS ~300MB fits within 1GB+swap headroom.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
act_runner automatically passes /var/run/docker.sock from its own mounts
to job containers. Explicitly adding it in container.options caused
"Duplicate mount point" error, preventing all job containers from starting.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
