Expand description
Re-materialise the authz catalog after a profile edit.
Gateway route ids are content-addressed, so changing a route’s pattern or
provider mints a new id with no access_control_entities row — the next
request would fail closed with UnknownEntity. After a gateway/catalog edit
we upsert the route entities from the freshly-saved profile and re-apply the
YAML grants, so the resolver reflects the edit without a restart or a wait
for the boot-time governance pass.
Reconciliation is best-effort: the profile write is the source of truth and has already succeeded. If the database is unreachable (an offline edit), we warn and return — the next app start reconciles the catalog.