Rewrite Phase 3 plan with verified literal pixel-match gaps #538
Loading…
Reference in a new issue
No description provided.
Delete branch "docs/pixel-match-phase3-literal-gaps"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Docs-only. Rewrites Phase 3 of the mockup pixel-match plan to reflect a verified, region-by-region gap assessment run on 2026-07-10 against the six comps and the static reference, and records the direction decision (LITERAL pixel-match).
Why: the original Phase 3 framed the remaining work as "fine spacing/radii/typography nudging." The assessment shows that is an undercount. Four regions (rail, right column, composer, and to a lesser degree header/sidebar) have structural/archetype mismatches that require markup restructuring, not token tweaks. The running app is also deliberately feature-richer than the comps, so a literal match requires hiding or relocating shipped affordances (enclave switcher, huddles, catch-me-up, polls, scheduling, semantic search, the 7-row nav section, per-message overflow menus). That is a product decision, so each feature-hide is called out as needing its own LC-553 sub-ticket rather than being folded silently into a CSS pass.
What changed in the doc:
.lc-sidebarremaps--accent-surfaceto--sidebar-elevated, which prevents the comp's solid-accent active row from ever rendering.No code, CSS, or i18n touched. Confirmed against the current templates on main; the shell widths, amethyst palette, and connection-status banner already match and are marked so.
#LC-569