More details for Execution Context usage

[apitukh]

Minor changes according to previous discussions:

• only include the header in 2xx responses (discussed here https://spscommerce.slack.com/archives/C029RUC519Q/p1718958374062669)
• clarify 400/404 usage for resources that have data depending on context (discussed here https://github.com/SPSCommerce/sps-api-design/issues/138#issuecomment-2344376636)

[apitukh]

Watched the last recording about 400/404 responses (REDACTED) See 18:38 to 32:27 . As I understand there wasn't a decision to use 400 in all cases. It was discussed, that it might be 400 in Lookup Store, but 404 in ODO Bridge. Also, there was a discussion between using 400 for Search endpoints and 404 for get-by-id endpoints (GET, PUT, PATCH?).

[travisgosselin]

@apitukh - please be advised this is an open source repo, I have redacted your comment to remove noted recordings / passwords, etc.

[travisgosselin]

After reviewing, I'm not clear if this nuance needs to be represented in the API Standards, or if this is a reflection of the behavior being added for some of those internal APIs.

[travisgosselin]

Going to close this for now and instead we can open up further discussion if this is actually a broader API Standard we want to discuss first to gain alignment.