Tech debt

## Description

**Technical debt accumulates over time. It needs to be considered in tandem with delivery as it is critical to product maintainability, reliability, and simplicity.**

## Outcome

- Preventative work before things become blockers
- Healthier, more maintainable codebase
- Reduced operational risk

## Focus

- How might we clean up the code base to reduce the chance of regressions, incidents and unexpected behaviour that is caused by outdated code?

- How might we make it easier to build, test, review, release, without working around aspects that are no longer relevant?

- How might we reduce maintenance effort, to spend less time troubleshooting recurring problems or supporting unnecessarily complex systems?

- How might we improve the developer experience to make the codebase easier to understand, onboard to, and confidently modify?

- How might we strengthen the technical foundation for upcoming product priorities so that features can be delivered more efficiently?

No file, test, or entry point is named. Start by identifying a specific outdated component, workaround, or recurring maintenance problem in the TypeScript/NextJS codebase and agree on a bounded target. Done should mean a defined cleanup that reduces regression, operational, or developer-experience risk.

Written by the indexing model from the issue text.