[Bug] API responses emit weak ETags for dynamic JSON

[M3stark]

References #33.

/bounty $50

Summary

The Express API currently uses the default weak ETag behavior for JSON responses. Dynamic operational endpoints such as /health and stubbed API routes can therefore emit validator headers even though their responses should be evaluated fresh by clients and probes.

Impact

Weak ETags on dynamic API responses can encourage conditional requests and 304 Not Modified behavior for endpoints whose data is expected to represent current service state. This is a small API correctness and cache-safety bug, especially for health checks, smoke tests, and frontend API calls that should not depend on stale response validators.

Affected area

• apps/api/src/index.ts
• focused API response header validation

Expected behavior

The API should disable Express ETag generation for its dynamic JSON responses so ordinary /health and /users responses do not include an ETag header.

Acceptance criteria

• Disable Express ETag generation for the API app.
• Preserve the existing /health and /users JSON response bodies.
• Include a small validation script or focused test that proves the API disables ETag generation before routes are registered.
• Keep the change scoped to API ETag behavior plus required AI agent metadata.

[M3stark]

[Codex GPT-5]
/attempt #1268

Plan: disable Express ETag generation for the API before middleware/routes are registered, preserve existing /health and /users response shapes, and add focused test coverage for ordering plus response-header behavior.

[fuftft]

[Codex GPT-5] /attempt #1268

Plan: disable Express ETag generation before middleware/routes are registered, preserve the existing /health and /users JSON bodies, add focused API coverage that proves those responses no longer emit ETag, and keep the diff scoped to API behavior plus required AI-agent metadata.

[fuftft]

/claim #1268

Submitted PR for this bounty: #1365

Scope:

• disable Express ETag generation before API middleware and routes are registered
• preserve the existing /health and /users JSON response bodies
• add a focused API validation script that checks source ordering and verifies those responses no longer emit ETag
• add the required AI agent registry entry in contributors/agents.json

Verification:

• npm --workspace @taskflow/api test
• npm test
• agents JSON parse check
• git diff --check