# v0.1.24

- added `resourcePaths` support so consumers can standardize on the numbered resource structure:
  - `resources/1-payload`
  - `resources/2-actual`
  - `resources/3-expected`
  - `resources/4-config`
  - `resources/5-input`
  - `resources/features`
- config loading now prefers `resources/4-config/bdd-ui.config.json`, with support for `BDD_UI_CONFIG_PATH`
- form JSON steps now resolve feature-scoped input files from `resources/5-input/<feature-name>/...`
- screenshot defaults now align with the numbered resource roots under `resources/2-actual` and `resources/3-expected`
- added feature-name-aware runtime resource resolution helpers and regression coverage
- legacy `test-data/...` resource paths are now rejected with a clear migration error
- login submit flow now uses `Promise.all(...)` so waits are registered before the submit click
