Why is 'a service per database' considered a core microservices principle rather than an implementation detail?

If two services share one database, they're still coupled at the schema level — one team can't change a table without coordinating with every other service reading it, which defeats the independent-deployability goal microservices exist for. Each service owning its own database forces communication to happen through versioned APIs or events instead of a shared schema.