EMS LAN Support

End-to-end developer runbook

1. Step 1 - Confirm the API area: Identify the product area, route module, endpoint path, and consumer before writing or calling code.
2. Step 2 - Read the endpoint contract: Check method, auth, parameters, response, errors, side effects, and related docs.
3. Step 3 - Prepare authentication and input: Use the right session, bearer token, webhook secret, or internal header. Validate body and query data before sending it.
4. Step 4 - Make the request: Call the endpoint from the correct origin and environment. Keep credentials and secrets out of logs.
5. Step 5 - Verify response, side effects, and records: Confirm status code, response shape, database records, external side effects, and audit evidence.
6. Step 6 - Add tests, docs, and handoff notes: Update route inventory, consumer notes, and certification checks before depending on the change.

Family summary

Hosted LAN release proxy behavior and release download support.

Modules audited

• lanSystemReleases.ts: 2 generated endpoint entries.

Endpoint table

Method	Path	Module	Auth scan	Source
GET	/api/lan-system/releases/assets/:assetId	lanSystemReleases.ts	Unknown from source scan; inspect middleware and handler body before use.	partners-api/src/routes/lanSystemReleases.ts:154
GET	/api/lan-system/releases/latest	lanSystemReleases.ts	Unknown from source scan; inspect middleware and handler body before use.	partners-api/src/routes/lanSystemReleases.ts:99

Endpoint contract notes

1. Action 1 - Verify unknowns: The table is source-generated, but fields marked unknown need manual handler review.
2. Action 2 - Check source line: Use the source line as the starting point for exact request, response, and side-effect behavior.
3. Action 3 - Review consumers: Search dashboard, rego, EMS LAN, and webhook callers before changing a path or response.
4. Action 4 - Update inventory: Regenerate after any route change.