Add Cache-Control: no-store to mutating and audit response headers

[Jagadeeshftw]

📌 Description

middleware/securityHeaders.ts sets defensive headers (X-Content-Type-Options, X-Frame-Options, etc.) per the README, but doesn't appear to set Cache-Control — meaning responses from GET /api/v1/audit (recent mutating request history) or settlement/anchor detail views could be cached by an intermediary proxy or the browser's back-forward cache, exposing potentially sensitive operational data longer than intended.

🧩 Requirements and context

• Set Cache-Control: no-store on all mutating (POST/PUT/PATCH/DELETE) responses and on GET /api/v1/audit.
• Leave caching headers for genuinely cacheable read endpoints (if any) unaffected — this should be a targeted addition, not global.
• Confirm no existing test asserts the absence of this header (would need updating if so).

🛠️ Suggested execution

• Extend middleware/securityHeaders.ts or add a small targeted middleware applied to the relevant routers.
• Add tests in middleware/securityHeaders.test.ts and/or the affected route test files.
• Update the README's security-headers bullet list.

✅ Acceptance criteria

• Mutating responses and GET /api/v1/audit include Cache-Control: no-store.
• Other endpoints are unaffected.
• Documented in README.

🔒 Security notes

Reduces the window during which sensitive operational responses could be retained by intermediary caches.

📋 Guidelines

• Minimum 95% test coverage
• Clear documentation
• Timeframe: 96 hours

[GBOYEE]

Hey, I'd like to help with this (Add Cache-Control: no-store to mutating and audit response headers). I'll write the missing test coverage and wire it in. I'll open a PR referencing this shortly once assigned.

[Jagadeeshftw]

@GBOYEE thanks for the interest — you're currently at the 6 open-issue assignment cap for this repo, so I can't assign this one right now (backfill automation). Please finish or release one of your existing assigned issues, then request this one again and it'll be picked up.

[grantfox-oss]

🦊 GrantFox — @GBOYEE has been assigned to this issue as part of the Official Campaign | FWC26 campaign!

Next steps:

1. Open a Pull Request referencing this issue (e.g., Closes #99)
2. Your PR will be reviewed by the AnchorNet-Org maintainers

Good luck! Track your progress on GrantFox.