> That is not how most engineers define bad code.

The engineers I have worked with most definitely define "bad code" as having intrinsic limitations and/or latent defects which impact successful system functionality/operation. Indicators provided to stakeholders such as yourself which support this assessment are, but not limited to:

  - the system doesn't work that way
  - the system lacks test coverage, so changes take longer
  - adding feature "X" is not feasible
  - there is no repeatable way to onboard team members
  - the backlog grows exponentially
  - that "one point task" is going to take a couple weeks

All of the above impacts a business.

It is up to you, the "technical product manager", to understand what your team is trying to tell you.