fix: add Cache-Control no-store header to attestation responses

[sangwa]

Attestation responses are unique per request (fresh timestamp, request ID, hardware-signed evidence) and must not be cached by proxies or clients.

Summary by CodeRabbit

• Bug Fixes
  • Report responses are now configured to prevent caching, ensuring data freshness and improved security.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: cf2e26da-af1a-4db8-8b01-81e8e396faa1

📥 Commits

Reviewing files that changed from the base of the PR and between e18a936 and bc80696.

📒 Files selected for processing (1)

• internal/attestation.go

---

Walkthrough

The sendReport function in internal/attestation.go has been updated to set an additional HTTP response header, Cache-Control: no-store, in addition to the existing Content-Type: application/json header. This ensures that attestation reports are not cached by intermediaries or clients. The change does not affect control flow, error handling, or response body generation.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

🐰 A header so fine, with magic cache-clear,
No-store whispers softly to browsers near,
Attestations stay fresh, no duplication,
One line of wisdom guards data's location! ✨

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately describes the main change: adding a Cache-Control no-store header to attestation responses, which matches the single-line code modification in internal/attestation.go.
Docstring Coverage	✅ Passed	Docstring coverage is 100.00% which is sufficient. The required threshold is 80.00%.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix/no-store

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}