[fjlopez]

Why

Profile databases need the geometry code lists, and the stack needs the admin, backend, and viewer commits that publish the service protocol and the layer geometry.

What changed

• Development changelog 88, and PostgreSQL and Oracle changelog 32, add the geometry code lists and format Geometry.
• Submodule pointers move to the merge commits on each dev.

Scope

Covers the profile changelogs and the three submodule pointers. Leaves GeometryCollection and name-only geometry for later work.

Blast Radius

New Liquibase includes on development, PostgreSQL, and Oracle. The pointers also include the other dev commits that were not yet recorded in the stack.

Verification

• Backend code-list tests passed in the backend pre-commit run and in CI on feat(profile): publish service type and layer geometry sitmun-backend-core#353.
• A prior layers-form run passed 54 tests. Admin CI build passed on feat(layers): show service protocol and geometry parameters sitmun-admin-app#512.
• Viewer CI build passed on feat(map): pass geometryName and geometryType to SITNA sitmun-viewer-app#217.
• The changelog immutability script passed in a prior check. Front and backend images were healthy in that prior check.