dev: update CLAUDE.md with new commands

Author: S1M0N38

CLAUDE.md

@@ -12,6 +12,9 @@ ruff check .
 ruff check --select I --fix .
 ruff format .
 
+# Run markdown formatter
+mdformat --number docs/index.md docs/installation.md docs/developing-bots.md docs/protocol-api.md docs/contributing.md README.md
+
 # Run type checker
 basedpyright
 ```
@@ -25,7 +28,7 @@ basedpyright
 pytest -x
 
 # Run specific test file - stops after first failure
-pytest -x tests/test_api_functions.py
+pytest -x tests/lua/test_api_functions.py
 
 # Run tests with verbose output - stops after first failure
 pytest -vx
@@ -35,42 +38,45 @@ pytest -vx
 
 1. **Always start Balatro first**:
 
-   ```bash
-   # Check if game is running
-   ps aux | grep -E "(Balatro\.app|balatro\.sh)" | grep -v grep
+  ```bash
+  # Check if game is running
+  ps aux | grep -E "(Balatro\.app|balatro\.sh)" | grep -v grep
 
-   # Start if not running
-   ./balatro.sh > balatro.log 2>&1 & sleep 10 && echo 'Balatro started and ready'
-   ```
+  # Start if not running
+  ./balatro.sh > balatro.log 2>&1 & sleep 10 && echo 'Balatro started and ready'
+  ```
 
 2. **Monitor game startup**:
 
-   ```bash
-   # Check logs for successful mod loading
-   tail -n 100 balatro.log
+  ```bash
+  # Check logs for successful mod loading
+  tail -n 100 balatro.log
 
-   # Look for these success indicators:
-   # - "BalatrobotAPI initialized"
-   # - "BalatroBot loaded - version X.X.X"
-   # - "TCP socket created on port 12346"
-   ```
+  # Look for these success indicators:
+  # - "BalatrobotAPI initialized"
+  # - "BalatroBot loaded - version X.X.X"
+  # - "TCP socket created on port 12346"
+  ```
 
 3. **Common startup issues and fixes**:
-   - **Game crashes on mod load**: Review full log for Lua stack traces
-   - **Steam connection warnings**: Can be ignored - game works without Steam in development
-   - **JSON metadata errors**: Normal for development files (.vscode, .luarc.json) - can be ignored
+
+  - **Game crashes on mod load**: Review full log for Lua stack traces
+  - **Steam connection warnings**: Can be ignored - game works without Steam in development
+  - **JSON metadata errors**: Normal for development files (.vscode, .luarc.json) - can be ignored
 
 4. **Test execution**:
-   - **Test suite**: 55 tests covering API functions and TCP communication
-   - **Execution time**: ~160 seconds (includes game state transitions)
-   - **Coverage**: API function calls, socket communication, error handling, edge cases
+
+  - **Test suite**: 102 tests covering API functions and TCP communication
+  - **Execution time**: ~210 seconds (includes game state transitions)
+  - **Coverage**: API function calls, socket communication, error handling, edge cases
 
 5. **Troubleshooting test failures**:
-   - **Connection timeouts**: Ensure TCP port 12346 is available
-   - **Game state errors**: Check if game is responsive and not crashed
-   - **Invalid responses**: Verify mod loaded correctly by checking logs
-   - **If test/s fail for timeout the reasons is that Balatro crash because there was an error in the Balatro mod (i.e. @balatrobot.lua and @src/lua/ ). The error should be logged in the `balatro.log` file.**
-   - **Balatro app crashes**: When the Balatro app crashes during testing, **do not run the remaining tests**. The crash usually indicates an issue with the Lua mod code that causes cryptic errors in `balatro.log`. Stop test execution and investigate the crash logs before continuing. Before running the tests again, ALWAYS kill the current Balatro instance running and start it again.
+
+  - **Connection timeouts**: Ensure TCP port 12346 is available
+  - **Game state errors**: Check if game is responsive and not crashed
+  - **Invalid responses**: Verify mod loaded correctly by checking logs
+  - **If test/s fail for timeout the reasons is that Balatro crash because there was an error in the Balatro mod (i.e. @balatrobot.lua and @src/lua/ ). The error should be logged in the `balatro.log` file.**
+  - **Balatro app crashes**: When the Balatro app crashes during testing, **do not run the remaining tests**. The crash usually indicates an issue with the Lua mod code that causes cryptic errors in `balatro.log`. Stop test execution and investigate the crash logs before continuing. Before running the tests again, ALWAYS kill the current Balatro instance running and start it again.
 
 ### Documentation
 
@@ -107,7 +113,7 @@ I keep the old code around for reference.
 
 ### Python Code Style (from `.cursor/rules/`)
 
-- Use modern Python 3.12+ syntax with built-in collection types
+- Use modern Python 3.13+ syntax with built-in collection types
 - Type annotations with pipe operator for unions: `str | int | None`
 - Use `type` statement for type aliases
 - Google-style docstrings without type information (since type annotations are present)