rikrdo/arnes
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

F-002 fix: Remove secrets and externalize config

Browse Source
This commit is contained in:
rikrdo
2026-05-25 08:00:05 +02:00
parent d3a558352d
commit 3d41579ad3
58 changed files with 1192807 additions and 52 deletions
Download Patch File Download Diff File Expand all files Collapse all files

20
spec/bdd/features/config/legacy-config.feature Normal file
View File

@@ -0,0 +1,20 @@
@F-002 @smoke @security @regression
Feature: Legacy module reads config from one local source
As a maintainer
I want secrets and URLs outside tracked PHP files
So I can run the legacy module without storing sensitive values in source
Scenario: Entry points use shared config helper
Given the legacy PHP module has multiple web and CLI entry points
When feature F-002 is applied
Then tracked PHP files do not contain hard-coded DB credentials
And tracked PHP files do not contain hard-coded OpenAI credentials
And DB and route values are loaded through a shared config helper
Scenario: Local config shape is documented
Given a maintainer needs to set local credentials
When feature F-002 is applied
Then the repo contains a versioned local config example
And the repo ignores the real local config file
And setup notes explain how to create the local config

25
spec/bdd/features/layout/legacy-app-layout.feature Normal file
View File

@@ -0,0 +1,25 @@
@F-001 @smoke @regression
Feature: Legacy app lives in stable ARNES layout
As a maintainer
I want the copied legacy PHP app in a stable repo path
So I can trace design and change code safely
Scenario: Web module path is explicit
Given the repo contains legacy PHP product module files
When feature F-001 is applied
Then the module lives under "project/web/index/new"
And the old temporary path "project/new" is removed
Scenario: Development SQL baseline is explicit
Given the repo contains one SQL dump for local development
When feature F-001 is applied
Then the dump lives under "project/sql/db-25052026.sql"
And the dump is referenced by SDD docs as development baseline only
Scenario: Design trace exists for the move
Given feature F-001 is in progress
When the design stage is complete
Then SDD architecture docs exist for the legacy app
And one ADR records the repo layout move
And architect evidence exists under "work/artifacts/F-001/architect.md"