fix: simplify coding project card rail

This commit is contained in:
inman
2026-09-06 16:12:24 +08:00
parent faf751be5e
commit ce90f57ce7
5 changed files with 32 additions and 23 deletions

View File

@@ -22,6 +22,8 @@
- Apply the user's follow-up correction: the lower landing surface is a standalone
`新增项目` CTA followed by horizontally arranged existing-project cards, not a
composer-shaped project starter.
- Apply the user's final copy correction: remove the visible `已有项目` heading and
`选择一个项目继续` helper while retaining the horizontal project-card rail.
## Intent And Constraints
@@ -47,7 +49,8 @@
- The no-project view uses the existing Makelore M vector asset and a large
centered guide sentence while retaining the Makelore sidebar and light visual
system. Its lower surface now uses the user's clarified standalone orange
`新增项目` CTA followed by an overflow-safe horizontal row of existing projects.
`新增项目` CTA followed directly by an overflow-safe horizontal row of existing
projects, without the redundant visible project-section heading or helper copy.
- Project creation reuses the Sidebar's existing dialog through a renderer-local
event bridge; project-card selection uses the same bridge to invoke the
Sidebar's validated entry flow instead of duplicating project activation.
@@ -69,6 +72,12 @@
- Follow-up focused run:
`corepack pnpm exec vitest run tests/unit/coding-chat-panel.test.tsx tests/unit/coding-project-entry.test.ts tests/unit/module-navigation.test.tsx tests/unit/app-module-provider-gate.test.tsx --maxWorkers=4`
— 4 files, 48 tests passed.
- Final-copy focused run:
`corepack pnpm exec vitest run tests/unit/coding-chat-panel.test.tsx tests/unit/coding-project-entry.test.ts --maxWorkers=2`
— 2 files, 23 tests passed, including assertions that `已有项目` and
`选择一个项目继续` stay absent while real cards remain.
- `corepack pnpm exec eslint src/pages/Chat/CodingChatPanel.tsx tests/unit/coding-chat-panel.test.tsx tests/e2e/main-navigation.spec.ts`
— passed with no output.
- `corepack pnpm test` — 223 files passed; 1,863 tests passed and 3 skipped.
- `corepack pnpm run lint:check` — passed with 0 errors and the repository's 5
pre-existing warnings in `src/pages/Home/index.tsx` and
@@ -79,14 +88,15 @@
- `corepack pnpm exec playwright test tests/e2e/main-navigation.spec.ts --grep
"offers a create CTA|returns to the module chooser"` — 2 tests passed against
the built Electron app, covering empty and remembered-project entry states,
horizontal card order, direct card entry, `/chat`, and project-dialog launch.
absent section/helper copy, horizontal card order, direct card entry, `/chat`,
and project-dialog launch.
- `git diff --check` — passed.
- Visual comparison:
`/Users/inmanx/.codex/visualizations/2026/09/06/01a0756a-b6f5-7892-a11c-1c1608ebe592/codex-reference-vs-makelore-v2.png`
`/Users/inmanx/.codex/visualizations/2026/09/06/01a0756a-b6f5-7892-a11c-1c1608ebe592/codex-reference-vs-makelore-v3.png`
plus the focused lower crop
`/Users/inmanx/.codex/visualizations/2026/09/06/01a0756a-b6f5-7892-a11c-1c1608ebe592/codex-reference-vs-makelore-v2-bottom.png`
— the user-identified composer/CTA mismatch is resolved and no actionable
P0/P1/P2 differences remain.
`/Users/inmanx/.codex/visualizations/2026/09/06/01a0756a-b6f5-7892-a11c-1c1608ebe592/codex-reference-vs-makelore-v3-bottom.png`
— the user-identified composer/CTA and redundant-copy mismatches are resolved,
and no actionable P0/P1/P2 differences remain.
## Follow-ups
@@ -101,9 +111,9 @@
`.project-docs/40-domain/business-rules.md`.
Proposal: record that entering Code with no active local project remains on
`/chat`, presents the branded hero, a standalone `新增项目` CTA, and real local
projects as a horizontal card row. Creation and project-card entry route through
the single existing Sidebar flows; empty Conversations share the same brand
hero until their first entry.
projects as an unlabeled horizontal card row. Creation and project-card entry
route through the single existing Sidebar flows; empty Conversations share the
same brand hero until their first entry.
Evidence: focused unit coverage, the passing Electron navigation regression,
production build, and the passed side-by-side visual QA.
Future impact: future routing or setup work must not restore the configuration