You are preparing this workspace for a future implementation in LANGUAGE.

The target machine is a MacBook Pro running macOS. Your only job in this run is to make sure this workspace is ready to build a real application in LANGUAGE with these capabilities:

- CLI argument parsing
- HTTP client and, if practical, a small local HTTP server
- SQLite persistence
- config-file parsing, preferably TOML; JSON, INI, or another idiomatic config format is acceptable if TOML support is weak
- tests
- formatter or style checker, if one exists for this language
- a repeatable build command
- a repeatable test command

Do not implement the final application yet. The application spec will be provided in a later run.

Work to perform:

1. Inspect the current system and workspace.
2. Determine the idiomatic compiler/interpreter, build tool, package manager, and test tool for LANGUAGE on macOS.
3. Install or configure the missing language tooling only as needed.
4. Prefer Homebrew or the language’s official installer/package manager.
5. Avoid global changes unless they are normal and necessary for the LANGUAGE toolchain.
6. If an action modifies anything outside the workspace, explain why it is necessary before doing it.
7. Create a minimal smoke-test project in this workspace.
8. Add the smallest possible example that proves the workspace can:
   - parse CLI arguments,
   - make or expose an HTTP request/endpoint,
   - open SQLite and run a simple query,
   - read a config file,
   - run a test.
9. Add a README.md documenting:
   - installed tools,
   - project layout,
   - build command,
   - test command,
   - run command,
   - any limitations or missing pieces.
10. Run the build and tests.
11. Leave the workspace clean and ready for the later application implementation prompt.

Important constraints:

- Keep this setup idiomatic for LANGUAGE.
- Do not quietly substitute another implementation language.
- Shell scripts are acceptable only for setup convenience.
- If a dependency is unavailable or broken on macOS, choose the closest practical idiomatic alternative and document the tradeoff.
- Prefer simple, boring dependencies over clever or obscure ones.
- The final result of this run should be a verified LANGUAGE project skeleton, not the finished application.