arnes/spec/acceptance.md

Acceptance Spec

F-001 — Document and move legacy PHP app into ARNES project layout

Acceptance criteria

• Legacy PHP app structure is documented in SDD files.
• Repo layout decision is recorded in one ADR.
• Legacy code moves from project/new to project/web/index/new with no file loss.
• SQL dump moves from project/db-25052026.sql to project/sql/db-25052026.sql.
• ./scripts/verify.sh stays green after the move.

Evidence targets

• spec/sdd/architecture.md
• spec/sdd/components/*.md
• spec/sdd/decisions/001-store-legacy-app-under-project-web.md
• spec/bdd/features/layout/legacy-app-layout.feature
• work/artifacts/F-001/architect.md

F-002 — Remove secrets and externalize config

Acceptance criteria

• No hard-coded API or DB secrets stay in versioned PHP files.
• Config values load from one local config source for the legacy module.
• Production URLs and external endpoints are configurable.
• Legacy PHP entry points use config helper keys instead of inline values.
• ./scripts/verify.sh stays green after the change.

Evidence targets

• project/web/index/new/bootstrap.php
• project/web/index/new/config/local.example.php
• project/web/index/new/config/README.md
• spec/sdd/components/legacy-config-loader.md
• spec/sdd/decisions/002-use-local-config-loader-for-legacy-module.md
• spec/bdd/features/config/legacy-config.feature
• work/artifacts/F-002/architect.md
• work/artifacts/F-002/implementer.md