- Updates feature history phases from 2024 to 2026 dates
- Corrects service announcement timeline references
- Aligns API coverage documentation with current project schedule
Phase 4 of the docs portion of the rfc-5737-cleanup. Replaces all
192.168.1.x example IPs in tracked .md / .txt files with the
equivalent last-octet under 192.0.2.x.
192.168.1.x is RFC-1918 private space and routes on real networks,
which leaves readers guessing whether a documented IP is a placeholder
or a documented LAN. 192.0.2.0/24 is reserved by RFC 5737 exclusively
for documentation — readers know on sight that they're examples.
58 files touched, 551 line pairs. Includes .github issue/PR templates,
all docs/ references, example READMEs, and one script doc. No code
changes, no test changes; test files still carry the 192.168.1.x
placeholder pending Phase 2 in _/RFC-5737-cleanup/assessment.md.
Also fixed a small fallout in docs/analysis/ANONYMIZATION-SUMMARY.md
where the explanatory sentence "a reader can't tell whether
192.168.1.10 is a placeholder or a documented LAN address" had
itself been swept by the regex (inverting the point); restored the
literal example and noted the sweep progress inline.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
- Fixed HTTP method mismatch: /playNotification endpoint expects GET, not POST
- Updated PlayNotificationBeep() to use existing c.get() method with StationResponse model
- Resolves HTTP 400 errors when using 'soundtouch-cli sp beep' command
- Verified working with SoundTouch 20 hardware
- Added comprehensive troubleshooting documentation
- Updated feature history with bug fix details
Fixes: go run ./cmd/soundtouch-cli --host <device> sp beep
Previously failed with: 'API request failed with status 400'
Now works correctly alongside: curl http://<device>:8090/playNotification
- Update API-COVERAGE-ANALYSIS.md:
- Add /speaker and /playNotification to official API table
- Update endpoint count from 18/19 to 20/21 (95% coverage)
- Add notification system to conclusion summary
- Update API-Endpoints-Overview.md:
- Add comprehensive speaker endpoints documentation
- Include TTS and URL playback examples with XML
- Document ST-10 Series compatibility and features
- Update UNIMPLEMENTED-ENDPOINTS.md:
- Mark speaker notification system as ✅ IMPLEMENTED
- Update priority counts (14→12 critical, 15→13 high priority)
- Replace implementation notes with CLI and Go client examples
- Update STATUS.md:
- Add Phase 6: Notification System completion
- Update endpoint count from 26→28 total endpoints
- Add speaker notifications to production ready features
- Document recent major updates with speaker implementation
- Update README.md:
- Add 🔔 Smart Notifications feature to features list
- Add speaker CLI examples and Go library usage examples
- Add Speaker Notifications to API coverage table
- Include SPEAKER_ENDPOINT.md in documentation links
- Update CLI-REFERENCE.md:
- Add comprehensive speaker command section
- Include TTS examples with multi-language support
- Document URL content playback and beep notifications
- Add supported languages list and compatibility notes
- Update FEATURE_HISTORY.md:
- Add Phase 8: Speaker Notification System (February 2025)
- Document TTS, URL playback, and beep functionality
- Update endpoint statistics (27→29 total, 100% coverage)
- Add speaker notification test coverage and CLI commands
All documentation now reflects the complete speaker endpoint implementation
with comprehensive examples, usage patterns, and technical details.
- Add CONTRIBUTING.md with detailed contributor guidelines
- Create GitHub issue templates (bug reports, feature requests, device compatibility)
- Add pull request template with comprehensive checklist
- Create FEATURE_HISTORY.md documenting development evolution
- Streamline README.md to focus on overview and usage
- Improve documentation organization and clarity
The project now has proper contribution guidelines following GitHub best practices,
making it easier for new contributors to get started and maintain consistent
quality standards.