Resolve all `//TODO` or turn them into issues

Currently this codebase contains several `// TODO` comments. It's considered bad practice to have TODO's in (production) code as it's hard to keep track.

Instead, we should either resolve these TODO's or turn them into issues that are visible at the repository level.

Search the repository for `// TODO` comments and review each occurrence in context. For every TODO, either complete the work or create a visible repository issue that tracks it; done means no unaddressed TODOs remain in production code.

Written by the indexing model from the issue text.