Fake-3D Height Everywhere, 2-Top Table Rule
Applied the approved wall/table height mockup to every object: every station now sits on a visible plinth via one shared container change (no per-icon edits needed), and the whole draw order became Y-sorted (farther-back rows first, nearer rows last) since a fixed pass order can no longer guarantee correct occlusion once objects have height that extends into the row above them. Added a new house rule — no single table exceeds 2 seats, so every 4-top in the default layout is now two 2-tops physically pushed together (2x1) via a new Restaurant.pairTables(), merged into one bookable unit rather than two independently seatable halves.
Verified this session:
- 52/52 automated tests pass, including 4 new ones for the table-pairing rule.
- A genuine mistake in the first Y-sort attempt — seated customers were pinned to always draw in front of their own table, which is backwards for a customer on the table's far side — was caught by the user looking at the actual screenshot, not by any test, and corrected. Worth remembering: this class of "internally consistent but wrong about visual intent" mistake needs a human eye on the image, not more automated checks.
- Live-verified every station's raised plinth, the wall's brick-coursed thickness, all four table groups rendering as genuine 2x1 pairs, and correct far-side/near-side seating depth.
---
A note on Iterations 9-13 below: WORKLOG.md stops at the same point as this file did before this pass — "chair shape redesign," 2026-09-14 — even though progress/ holds 38 further screenshots (2026-09-14_09_... through 2026-09-15_46_...) documenting real, shipped work well past that point, and this project has no git history to fall back on either. There is no contemporaneous narrative for any of it — no "what was found, why, what broke" for this stretch, only the end-state screenshots themselves and their filenames. These five milestones are reconstructed from that evidence — each screenshot's actual pixel content checked against its filename and against current code, grouped into iterations by rough time-of-capture clustering — not from a WORKLOG entry the way every other milestone in this file is. Treat the "what changed" prose as inferred, not as a first-hand account; the screenshots themselves are genuine contemporaneous captures (not fabricated after the fact), just never linked or written up at the time. See the corresponding WORKLOG.md entry (2026-09-15, "documentation blackout found and PROGRESS.md reconstructed") for how this was put together.
