Bug: Unable to pass config to CLI after command

[colinrsmall]

Description

Using advanced alchemy/alembic/litestar for the first time (porting a project from Django). I've been unable to use the alchemy CLI, with all commands erroring out Missing option '--config' even if the config flag is passed to a command.

It appears that calling the config argument before the command works, but this would make the documentation inaccurate if intentional.

Steps to reproduce (in a project using uv)

uv run alchemy check --config <path to alchemy config>`

➜  litestar-fullstack git:(main) alchemy check --config <path to config>

 Usage: alchemy [OPTIONS] COMMAND [ARGS]...

 Try 'alchemy --help' for help
╭─ Error──────────────────────────────────────────────────────────────╮
│ Missing option '--config'.                                          │                                                                                         
╰─────────────────────────────────────────────────────────────────────╯

Package Version

advanced-alchemy 1.8.0
zsh 5.9 (arm64-apple-darwin25.0)
MacOS 26.1

Platform

• Linux
• Mac
• Windows
• Other (Please specify in the description above)

[Sreekant13]

I dug into this. --config is a required option on the top-level alchemy group, so click only accepts it before the subcommand (alchemy --config X check), while the docs and natural usage put it after (alchemy check --config X) - hence "Missing option '--config'".

A few ways to fix it, depending on your preference:

1. Make --config position-flexible (a small custom Group that accepts it before or after the command. It would need to stay compatible with the rich-click group).
2. Add --config as a per-command option and resolve the config lazily.
3. If the before-command position is intentional, correct the docs to match.

Happy to open a PR. Which direction would you prefer? Leaning (1).
@colinrsmall