The problem with saying "technical debt" in these situations is it makes you look unserious. If you use "technical debt" to mean "a problem we didn't realize would be there when we made this decision" it makes you look like you take on debt without reading term sheets.
I always think of Tech Debt as the work you should do but aren’t doing, usually by management choice.
Stuff like, “we really should refactor this to make it easy to work on” and “we should really clean out the obnoxious deps that we pull in but don’t really need here” and “we really should clean up this function that appears is 6 different places in 2 different versions” and so on.
Essentially anything that would make maintenance and enhancement easier but that you aren’t given the time to do and it just piles up.