## Problem `setup-site` is the default command, but the config source has to be passed as a named flag: ``` drupalaibp --config-url https://git.drupalcode.org/project/foo ``` The config source is the most common thing a caller hands the installer, so it should be the first positional argument. `drupalaibp <source>` reads better than `drupalaibp --config-url <source>` and matches how most installers accept "what to install" positionally. ## Proposed behaviour Resolve the first positional argument in this order: 1. **It matches a known command** (`install`, `delete`, `setup-site`): run that command, as today. 2. **It is not a known command**: treat it as a config source, detect what kind, and route it to `setup-site`: - a git URL or a `project/<name>` style repo -> `--config-url` - a local directory path -> `--config-path` - (optionally, a saved global config name -> `--global-config`) 3. **None of the above**: error with "command not found". So these pairs become equivalent: ``` drupalaibp https://git.drupalcode.org/project/foo drupalaibp --config-url https://git.drupalcode.org/project/foo drupalaibp ./team-config drupalaibp --config-path ./team-config ``` The named flags stay for explicitness and backwards compatibility. ## Multiple named configs in a `.drupalaibp/` directory Today a source carries exactly one config: a `.drupalaibp.json` at its root (auto-detected in `src/setup_site_command.sh`, required by `load_config_url.sh` / `load_config_path.sh`). Allow a source to carry several configs instead, as JSON files inside a `.drupalaibp/` directory: ``` .drupalaibp/config1.json .drupalaibp/config2.json ``` When a source is pointed at: - **exactly one config** in `.drupalaibp/`: use it, no prompt. - **more than one**: the first step is to pick which one — interactively (a select menu of the available configs), or non-interactively via a parameter. - **none**: fail loudly, as the missing-config case does today. Selection parameter (name open — the `--config-*` namespace is already crowded): e.g. `--config <name>` picks `.drupalaibp/<name>.json`. It composes with the positional source and with a git ref: ``` drupalaibp https://git.drupalcode.org/project/foo --config config2 drupalaibp https://git.drupalcode.org/project/foo@1.2.x --config config2 ``` Under `--yolo`, multiple configs with no `--config` is ambiguous and should error (there is no safe default among named configs); a single config still builds unattended. ### Remove the root `.drupalaibp.json` Configs should live only in `.drupalaibp/`. Drop the root `.drupalaibp.json` entirely: - the auto-detect in `src/setup_site_command.sh` looks in `.drupalaibp/` for `*.json` instead of at the root `.drupalaibp.json`. - `load_config_url.sh` / `load_config_path.sh` require a `.drupalaibp/` directory with at least one config, not a root file. This is a breaking change; note it in the change record and give a migration path (a single `.drupalaibp/config.json` replaces the old root `.drupalaibp.json`). **Watch the naming collision:** `.drupalaibp/config/` is already used for Drupal config YAML import (`src/lib/steps/step_import_config.sh`), and `.drupalaibp/` already holds hook scripts (`agent-extras.sh`, `seed-content.sh`). The installer configs are `*.json` files directly under `.drupalaibp/`; the selector must consider only those, not the `config/` subdir or the hook scripts. This mirrors the existing saved-config convention `~/.drupalaibp/configs/<name>.json` (`--global-config`). ## Git references (branch / MR / fork) `--config-url` currently runs a fixed `git clone --depth 1 <url>` (see `src/lib/config/load_config_url.sh`), so it always builds from the default branch HEAD. Add a way to point at a specific ref, so a build can start from a branch, a merge request, or a fork: - a branch: `git clone -b <branch>` - a merge request: fetch `refs/merge-requests/<iid>/head` and check it out - a fork: a full URL to the fork already works as the source; document that this is how you build from a fork Suggested syntax (open to alternatives): a `@<ref>` suffix on the source: ``` drupalaibp https://git.drupalcode.org/project/foo@1.2.x drupalaibp https://git.drupalcode.org/project/foo@refs/merge-requests/12/head ``` or a separate `--ref` flag. Both the positional form and the `--config-url` flag should accept it. ## Notes - Keep `--config-url` / `--config-path` / `--global-config` mutually exclusive as they are today; the positional form just picks one of them based on detection. - `setup-site` is `default: force` in `src/bashly.yml`, so the positional argument has to be wired into the default-command dispatch, not only into an explicit `setup-site` invocation. - A source that looks like a path but does not exist, or a URL that does not clone, should fail loudly (as `--config-url` / `--config-path` already do), not fall through to "command not found". - Order of resolution once a source is loaded: pick the config (single / prompt / `--config`), then apply the git ref, then run the build.