Problem description
GET /network-access-devices declares a 404 response (code/API_definitions/network-access-devices.yaml, the collection endpoint). A collection endpoint has no identifier to miss: an authorized caller with no devices receives 200 with an empty list, per the empty-list convention documented in both specs. The repo's other collection GETs (/trust-domains, /reboot-requests, /services, /trust-domains/{trustDomainId}/devices) correctly declare no 404.
Expected behavior
GET /network-access-devices declares the same success/error response set as the other collection GETs: 200, 400, 401, 403, 500, 503 — no 404. (404 remains correct on GET /network-access-devices/{networkAccessDeviceId}.)
Alternative solution
Additional context
Broken out of #160 (item 2) so it can be tracked and closed independently. The example-hygiene work resolving the rest of #160 (PR #180) is deliberately shape-neutral — removing a documented response is an API-shape change, so it does not belong in that PR.
Problem description
GET /network-access-devicesdeclares a404response (code/API_definitions/network-access-devices.yaml, the collection endpoint). A collection endpoint has no identifier to miss: an authorized caller with no devices receives200with an empty list, per the empty-list convention documented in both specs. The repo's other collection GETs (/trust-domains,/reboot-requests,/services,/trust-domains/{trustDomainId}/devices) correctly declare no404.Expected behavior
GET /network-access-devicesdeclares the same success/error response set as the other collection GETs:200, 400, 401, 403, 500, 503— no404. (404remains correct onGET /network-access-devices/{networkAccessDeviceId}.)Alternative solution
Additional context
Broken out of #160 (item 2) so it can be tracked and closed independently. The example-hygiene work resolving the rest of #160 (PR #180) is deliberately shape-neutral — removing a documented response is an API-shape change, so it does not belong in that PR.