The NBA API no longer supports this endpoint and returns HTTP 500 errors.
Users should use BoxScorePlayerTrackV3 instead.

Removed:
- src/nba_api/stats/endpoints/boxscoreplayertrackv2.py (endpoint class)
- docs/nba_api/stats/endpoints/boxscoreplayertrackv2.md (documentation)
- docs/nba_api/stats/endpoints_output/boxscoreplayertrackv2_output.md (examples)
- Import from src/nba_api/stats/endpoints/__init__.py
- Reference from docs/table_of_contents.md
- Deferred endpoint from tests/integration/deferred_endpoints.py
- Mapping from tools/stats/library/mapping.py
- Entry from docs/examples/Basics.ipynb endpoint list
- analysis_archive/stats/analysis.json (archive file)

- Remove PlayerFantasyProfile endpoint class and all references
- Remove documentation and test references
- Update endpoint mappings and analysis tools
- Endpoint removed due to NBA.com API discontinuation

)

- Added PLAYER_SLUG and TEAM_SLUG to expected_data in CommonAllPlayers endpoint
- These fields are returned by the NBA API but were previously not included
- Updated CHANGELOG.MD with fix details and note about POSITION field limitation
- Fixed typo in CONTRIBUTING.md (activate -> eval \$(poetry env activate))

Closes swar#550

- Added PlayerFantasyProfile to v1.11.3 Removed section
- Endpoint was removed in commit 0b6a694 but not documented in changelog

- Changed city from "Golden State" to "San Francisco" in static teams data
- Updated both data.py and template.py
- Team name remains "Golden State Warriors" (unchanged)
- Updated data timestamp to Nov 13, 2025

Closes swar#434

…ar#448)

- Added comprehensive class docstring documenting NBA API bug with plus_minus='Y'
- Added runtime UserWarning when plus_minus='Y' is used
- Documented that plus_minus='Y' returns incorrect differential/delta values
- Provided example showing incorrect data (FGM=-0.3 instead of 39.3)
- Recommended workaround: use plus_minus='N' (default)
- Updated CHANGELOG.MD under "Changed" section

Note: This is an NBA.com API bug, not an nba_api issue. The warning helps
users avoid incorrect data by steering them away from the broken parameter.

Closes swar#448

…ion test validation

Restore endpoints:
- TeamGameLog and TeamGameLogs endpoints (retired in v1.11.0) are working again
- Both endpoints fully functional with all parameters
- Added comprehensive unit tests (6 for TeamGameLog, 6 for TeamGameLogs)
- Added integration tests (4 test cases for TeamGameLog, 5 for TeamGameLogs)
- Generated documentation files in docs/nba_api/stats/endpoints/

Enhanced integration test validation:
- Added dataset structure validation to prevent false retirements
- Validates dataset names match expected_data keys
- Validates column structure for each dataset
- Logs per-dataset row counts for better diagnostics
- Opt-in validation via validate_structure flag (default: False)
- Refactored validation logic to reduce code complexity

The enhanced validation catches:
- Missing datasets that should be present
- Column mismatches in expected_data definitions
- API response structure changes
- Empty datasets when data is expected

Root cause analysis:
- Endpoints were incorrectly retired Nov 2, 2025 based on GitHub issue
- Integration test framework was created Nov 5, 2025 (3 days later)
- No automated validation existed at time of retirement
- Enhanced validation prevents similar false retirements in the future

Files changed:
- src/nba_api/stats/endpoints/teamgamelog.py (restored)
- src/nba_api/stats/endpoints/teamgamelogs.py (restored)
- tests/unit/stats/endpoints/test_teamgamelog.py (12 unit tests)
- tests/integration/data/teamgamelog.py (4 test cases)
- tests/integration/data/teamgamelogs.py (5 test cases)
- tests/integration/test_endpoints.py (enhanced validation logic)
- tests/integration/data/README.md (documentation)
- docs/ (endpoint documentation)

Test results:
- All 37 integration tests passing
- All 460 unit tests passing
- All flake8 checks passing