fix(home): reposition title and compact account entry

This commit is contained in:
鲨鱼辣椒 committed 2026-10-13 13:55:24 +08:00
1 parent 886b4589a1
commit a9fa221d7a
6 files changed
+80 -13

No files matched your search

@@ -8,7 +8,7 @@
- Worktree: /Users/chillishark/Makelore 麦洛/.codex-worktrees/makelore/20261013-combined-trial-update-c42d19a7
- Base commit: 8289f27f3e53ef455b656f1c43d2620d235d5014
- Owner: codex
- Status: Ready for Integration
- Status: Planning
## Scope
@@ -17,6 +17,17 @@
- Follow-up: restore access to the existing account controls on the standalone module homepage and update the current trial.
- Latest follow-up: restore the desktop title-left / three-card vertical layout with the Code card centered on the title; retain Robot hiding and account controls.
## Homepage Position / Compact Account Follow-up · 2026-10-13
- Concurrent / Planning Gates: Passed on same-task resume, exact owner/task/worktree/branch/feature/base verified after successful start and structure check. Reread current task/source; retain unchanged startup/positioning/decisions/architecture/domain/evidence/reflection/commitment context. Peer delta review found only compatible un-deployed knowledge and Tool/Skill copy changes, outside this scope; no new homepage dependency and no automatic import. Latest current runtime remains Renderer/effective 383ce71 over Main 7c51bb4, PID 9968 / port 58003.
- User requests title “网友移动1.5cm”, interpreted and communicated as the homophone typo for “往右移动1.5cm”, and the pictured account entry at half its current visual size, moved left 1.5cm toward the lower-left corner. Preserve three-card equal geometry and Code/title vertical alignment, Robot hiding, account menu behavior and current recovery source.
- Plan: move the desktop intro right by CSS 1.5cm (~56.7px), measure the actual h1 text box rather than its full grid column; narrow widths retain centered heading to avoid overflow. Render the trigger surface at half scale in an unchanged 50px keyboard/click footprint; menu/wallet remain unscaled. Move the account controls left up to 1.5cm with a 16px window inset limit and down to a 16px bottom inset; retain the footer flow reservation and normal scrolling.
- Verification: focused account/module/wallet units, typecheck/lint/build, existing Electron account/layout scenarios plus visual geometry assertions at four widths and screenshots. Compare before/after live title and trigger rectangles in Renderer-only update, with complete Main/resource/package byte proof and current-pointer binding. Fresh saved-state guards remain; do not save/discard for the user or perform real account/payment/Agent operations.
- Source implemented and frozen: three product files only (ModuleSelection, globals, HomeAccountMenu), README and focused geometry assertions. Existing handlers, menus/dialog lifecycle, module permissions, Code alignment/card stack and Main are unchanged.
- Verification complete before activation: 25 focused units / 3 files, typecheck, scoped source/test ESLint and full build passed. Two Electron scenarios passed, with title displacement, actual text-range width, half-size surface/avatar, unchanged click footprint, full-size menu/gap, 16px bottom inset, desktop left shift/mobile screen safety and prior navigation/menu/wallet behavior. Layout measured at 1440/1024/768/375; desktop and mobile account screenshots plus 1024/375 layout screenshots visually inspected. Independent Main proof: dist-electron 8 files/resources 57 files/package exact original 7c snapshot.
- Renderer-only update prepared next, current-pointer baseline remains active 383ce71; source commit and final live receipt to be recorded after clean-state activation.
## Homepage Vertical Layout Follow-up · 2026-10-13
- Concurrent / Planning Gates: Passed on same-task resume; successful start and matching feature / task / branch / absolute worktree / base ownership verified. Retain unchanged startup, positioning, architecture, domain, accepted decisions, evidence/reflection/commitment context from the previous gate; reread the active record, startup, planning gate and local AGENTS. Source task records stay read-only; primary checkout remains untouched.