So who owns the bugs and defects in the code?

What you describe sounds like unconstraint convention based coding — which will always fail at some point. Our only chance to push deterioration far into the future is enforcing simplicity, by engineering the right constraints.

What you describe has nothing to do with engineering but sounds like your team is handling themself as a bunch of teenagers.