Refresh transcription route knowledge

This commit is contained in:
Franz Rolfsvaag 2026-07-22 15:51:53 +02:00
parent 02bdec7584
commit cc8d455b4e

View File

@ -22,6 +22,7 @@ Default state: enabled
- GET /plugins/lumi_transcription/api/status
- POST /plugins/lumi_transcription/api/pairing-package
- POST /plugins/lumi_transcription/api/companion/download
- GET /plugins/lumi_transcription/api/companion/update
- POST /plugins/lumi_transcription/api/pair
- GET /plugins/lumi_transcription/api/devices
- POST /plugins/lumi_transcription/api/devices/:id/revoke
@ -78,6 +79,15 @@ Default state: enabled
- Side effects: Action route; side effects were not detected statically.
- Limits/notes: Generated from static route source analysis; confirm exact behavior in the handler before changing integrations. Errors are caught and usually returned as a flash message, JSON error, or error page. Most non-API POST routes are browser form submissions and usually redirect after completion. API consumers should expect JSON unless the response format says otherwise.
### GET /plugins/lumi_transcription/api/companion/update
- Purpose: Renders or serves the lumi_transcription plugin page for api companion update.
- Inputs: query: `current_version`
- Response format: JSON response
- Access: No explicit access guard detected in the route handler; check surrounding router/mount middleware.
- Side effects: writes or mutates server-side state
- Limits/notes: Generated from static route source analysis; confirm exact behavior in the handler before changing integrations. Input length or numeric bounds are enforced by helper functions in the handler. API consumers should expect JSON unless the response format says otherwise.
### POST /plugins/lumi_transcription/api/pair
- Purpose: Processes the lumi_transcription plugin action for api pair.