Deployment Script, Postgres migration, UX improvements

CLAUDE.MD

@@ -1247,4 +1247,43 @@ approval workflow
 Power BI-ready outputs
 ```
 
-That gives the client safer data entry, gives the consultancy control and visibility, and gives Power BI a clean source instead of fragile workbook logic.
+That gives the client safer data entry, gives the consultancy control and visibility, and gives Power BI a clean source instead of fragile workbook logic.
+
+---
+
+# Frontend layout debugging notes
+
+## Full-height layouts inside padded shells
+
+When a child layout uses negative margins to cancel a parent container's padding, `height: 100%` is often not enough to visually fill the container.
+
+Example pattern:
+
+```css
+.parent {
+  --content-padding: 1.34rem;
+  padding: var(--content-padding);
+}
+
+.child {
+  margin: calc(var(--content-padding) * -1);
+  height: 100%;
+}
+```
+
+This can leave a visible gap at the bottom because the child is still only `100%` tall while being visually expanded outward by the negative margins.
+
+Preferred fix:
+
+```css
+.child {
+  margin: calc(var(--content-padding) * -1);
+  height: calc(100% + (var(--content-padding) * 2));
+  min-height: calc(100% + (var(--content-padding) * 2));
+}
+```
+
+Worker reasoning rule:
+
+- If a panel "almost" fills the viewport but leaves a strip equal to parent padding, inspect negative margins and the nearest padded scroll container before changing inner child heights.
+- In this app, `AppSecondaryRailLayout.svelte` sits inside `ClientShell.svelte`'s padded `.content` container, so full-height fixes should account for `--content-padding`.