@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"