[godelski]

  > but they don't seem to be signs of technical debt

  > they also might be the results of strategic product decisions to make more money. That isn't technical debt, that's enshittification for money.
  > that's a bad product decision, not technical debt.

  | technical debt refers to the implied cost of additional work in the future resulting from choosing an expedient solution over a more robust one.
  - Wiki[0]

I think these suggestions fall under this category. At the core, technical debt is myopia. "Technical" refers to more than code. Ultimately, the bad code is generally the result of poor decision making. "Tech debt" is a broad word, but I don't think the things I mentioned here are in direct contention with the wiki definition nor the examples they give under "Frequent causes of technical debt". It's all about planning, and that process begins even before any code is written.

[0] https://en.wikipedia.org/wiki/Technical_debt