refactor: add numeric prefixes to prompt files for workflow order

Renamed prompts to reflect natural workflow sequence:
- 01-setup-dev-env.prompt.md (first-time setup)
- 02-build-ddbc.prompt.md (build C++ extension)
- 03-run-tests.prompt.md (run pytest)
- 04-create-pr.prompt.md (submit work)

Updated all cross-references between prompts

Author: bewithgaurav

.github/prompts/setup-dev-env.prompt.md …ithub/prompts/01-setup-dev-env.prompt.md.github/prompts/setup-dev-env.prompt.md renamed to .github/prompts/01-setup-dev-env.prompt.md .github/prompts/setup-dev-env.prompt.md renamed to .github/prompts/01-setup-dev-env.prompt.md

@@ -486,7 +486,7 @@ echo "✅ Setup complete!"
 
 Once setup is complete, you can:
 
-1. **Build DDBC extensions** → Use `#build-ddbc`
-2. **Run tests** → Use `#run-tests`
+1. **Build DDBC extensions** → Use `#02-build-ddbc`
+2. **Run tests** → Use `#03-run-tests`
 
 > 💡 You typically only need to run this setup prompt **once** per machine or after major changes.

.github/prompts/build-ddbc.prompt.md .github/prompts/02-build-ddbc.prompt.md.github/prompts/build-ddbc.prompt.md renamed to .github/prompts/02-build-ddbc.prompt.md

@@ -8,7 +8,7 @@ You are a development assistant helping rebuild the DDBC C++ pybind11 extensions
 ## PREREQUISITES
 
 > ⚠️ **This prompt assumes your development environment is already set up.**
-> If you haven't set up your environment yet, use `#setup-dev-env` first.
+> If you haven't set up your environment yet, use `#01-setup-dev-env` first.
 
 **Quick sanity check:**
 ```bash
@@ -308,6 +308,6 @@ cd mssql_python/pybind && rm -rf build && ./build.sh && cd ../.. && python -c "f
 
 Once the build succeeds:
 
-1. **Run tests** → Use `#run-tests`
+1. **Run tests** → Use `#03-run-tests`
 2. **Test manually** with a connection to SQL Server
-3. **Create a PR** with your C++ changes → Use `#create-pr`
+3. **Create a PR** with your C++ changes → Use `#04-create-pr`

.github/prompts/run-tests.prompt.md .github/prompts/03-run-tests.prompt.md.github/prompts/run-tests.prompt.md renamed to .github/prompts/03-run-tests.prompt.md

@@ -251,7 +251,7 @@ pip install -e .
 # Check venv is active
 echo $VIRTUAL_ENV
 
-# If empty, activate it (run `#setup-dev-env`)
+# If empty, activate it (run `#01-setup-dev-env`)
 # If active, install pytest
 pip install pytest pytest-cov
 ```
@@ -302,7 +302,7 @@ python -m pytest tests/test_000_dependencies.py tests/test_001_globals.py tests/
 **Cause:** C++ extension not built or Python version mismatch
 
 **Fix:**
-Use `#build-ddbc` to rebuild the extension:
+Use `#02-build-ddbc` to rebuild the extension:
 ```bash
 cd mssql_python/pybind && ./build.sh && cd ../..
 python -c "from mssql_python import connect; print('OK')"
@@ -397,9 +397,9 @@ addopts = -m "not stress"
 
 Based on test results:
 
-1. **All passed** → Ready to create/update PR → Use `#create-pr`
+1. **All passed** → Ready to create/update PR → Use `#04-create-pr`
 2. **Some failed** → Review failures, fix issues, re-run
 3. **Coverage decreased** → Add tests for new code paths
 4. **Need to debug** → Use `-s` flag to see print output, or `--pdb` to drop into debugger
 
-> 💡 **Tip:** If you made C++ changes, ensure you've rebuilt using `#build-ddbc` first!
+> 💡 **Tip:** If you made C++ changes, ensure you've rebuilt using `#02-build-ddbc` first!

.github/prompts/create-pr.prompt.md .github/prompts/04-create-pr.prompt.md.github/prompts/create-pr.prompt.md renamed to .github/prompts/04-create-pr.prompt.md

@@ -8,9 +8,9 @@ You are a development assistant helping create a pull request for the mssql-pyth
 ## PREREQUISITES
 
 Before creating a PR, ensure:
-1. ✅ All tests pass (use `#run-tests`)
+1. ✅ All tests pass (use `#03-run-tests`)
 2. ✅ Code changes are complete and working
-3. ✅ If C++ changes, extension is rebuilt (use `#build-ddbc`)
+3. ✅ If C++ changes, extension is rebuilt (use `#02-build-ddbc`)
 
 ---