👋 Hi! Thank you for contributing to vLLM support on Spyre.
Just a reminder: Make sure that your code passes all the linting checks, otherwise your PR won't be able to be merged. To do so, first install the linting requirements, then run format.sh and commit the changes. This can be done with uv directly:

uv sync --frozen --group lint

Or this can be done with pip:

uv pip compile --group lint > requirements-lint.txt
pip install -r requirements-lint.txt
bash format.sh

Now you are good to go 🚀

Overall, I think that this doc could get split up a bit. 🤔

• For example, the installation part could be part of the general Installation doc but denoting that it's different way to install (for local dev on mac).
• Running the tests could be a section in the Contributing guide. See https://docs.vllm.ai/en/stable/contributing/overview.html#developing for inspiration.
• Running the examples are a bit straightforward and I'm not really sure they require extra documentation except maybe in a future quickstart doc or in the Contributing guide too?

Thanks for the review Rafael!

1. Yeah I was avoiding touching the installation.md file until you made your changes in your PR. I also don't understand the difference between installing spyre via uv sync (like in this PR) vs using uv pip install -e (like in installation.md). As far as I can tell, both are installing a local editable version of spyre in the venv. The additional advantage of using uv sync is that it also installs all the dev dependencies. If there's no difference, we can probably replace the installation.md content with what I have in local_development.md completely 🤷
2. For the tests I agree they could be in the contributing section. Then we could eventually add other variations of running the tests, for example, on the CI or on a machine with an actual spyre card.
3. The thing with examples is that there is some caveat of running the examples on a CPU (like setting the HF_HUB_OFFLINE variable) so that's why I had it in this section. Possibly I can move that in the quickstart doc and add a note. Or actually I can write a condition in the example files itself which checks for the current architecture and changes the variables accordingly 🤔