mirror of
https://github.com/gesellix/Bose-SoundTouch.git
synced 2026-08-24 14:47:23 +00:00
Tobias GesellchenandClaude Opus 4.8
d5b298fc43
Two deliberately-unimplemented routes, pinned as "currently ignored" so a future
change to them is conscious:
- GET /v1/blacklist/{deviceId} -> 405 (inline stub)
- POST /alexa/certificate -> 501 (no AWS IoT integration)
App / provisioning surface (app-called, not the speaker data-plane). Shapes come
from the _/mitm capture where one exists, otherwise from the handler (canned /
stub responses):
- GET /streaming/account/{a}/emailaddress -> 200 (<emailAddress>, _/mitm)
- GET /customer/account/{a} -> 200 (<customer> profile, canned)
- POST /customer/account/{a} -> 200 (profile update, stub)
- POST /customer/account/{a}/password -> 200 (password change, stub)
COVERAGE.md gains an app/provisioning section and records the source (mitm vs
handler) for each. make test-http-client: 73 requests, 0 failed.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
16 lines
649 B
HTTP
16 lines
649 B
HTTP
### GET /v1/blacklist/{deviceId} (currently ignored: 405 Method Not Allowed)
|
|
###
|
|
### The speaker probes a notification blacklist endpoint. AfterTouch does not
|
|
### implement it and deliberately returns 405 (inline stub in setupRouter).
|
|
### Pinning the current 405 documents this as a conscious no-op, so any future
|
|
### behaviour change here is deliberate rather than accidental.
|
|
GET {{host}}/v1/blacklist/{{deviceId}}
|
|
User-Agent: Bose_Lisa/27.0.6
|
|
Accept: */*
|
|
|
|
> {%
|
|
client.test("Blacklist probe is the ignored 405 stub", function() {
|
|
client.assert(response.status === 405, "Response status is not 405, got " + response.status);
|
|
});
|
|
%}
|