feat(desktop): project (design) management — list / create / switch / rename / duplicate / delete

[hqhq1025]

Summary

Adds first-class project management. Users can create new designs, browse history, switch / rename / duplicate / soft-delete past work. Each project carries its own message history and preview snapshot.

Built on top of #29 (snapshots SQLite + IPC). Targets main as base — merge order should be #29 → this PR.

Addresses user feedback: there was no obvious way to start a new project or see history.

What ships

• TopBar breadcrumb dropdown (DesignSwitcher) — current design name + recent 5 + new + rename + view-all
• DesignsView grid overlay — search, hover actions, gradient placeholder cards
• Soft delete with confirm modal (cascade behaviour explained in copy)
• Auto-name from first prompt (Claude Design / Lovable pattern)
• Cmd+N for new design; command palette gains "Browse all designs" + "Rename current design"
• Per-design state: switching swaps messages + preview from SQLite

Schema (additive, non-breaking)

• designs.thumbnail_text and designs.deleted_at columns added via additive migration (PRAGMA-detected, idempotent).
• New design_messages table with ON DELETE CASCADE and a composite primary key on (design_id, ordinal).

IPC (snapshots:v1:* namespace)

get-design, rename-design, set-thumbnail, soft-delete-design, duplicate-design (with snapshot parent rewiring), list-messages, replace-messages.

Why no real iframe thumbnails yet

A sandboxed iframe-thumbnail pipeline is the eventual goal but is expensive to build correctly (per-card srcdoc + import map + GC). For v1 we ship hash-derived gradient cards + first-prompt snippet, with the thumbnail_text column already in place to keep the upgrade path clean. See docs/research/26-project-management-ux.md for the rationale and competitor scan.

PRINCIPLES §5b

• Compatibility: additive SQLite migration; messages table is new.
• Upgradeability: every new payload carries schemaVersion: 1; thumbnails column reserved for the upgrade.
• No bloat: 0 new dependencies. ~+1.9k LOC, mostly UI + tests + i18n.
• Elegance: single Zustand slice for designs, no parallel store.

Test plan

• vitest: 26 new tests across snapshots-db (rename / soft-delete / duplicate / set-thumbnail / messages / migration idempotency / cascade) and snapshots-ipc (rename / set-thumbnail / soft-delete / duplicate / list+replace messages / get-design)
• vitest: store tests for switchDesign isolation, createNewDesign reset, generation-block-on-switch toast
• pnpm typecheck clean
• pnpm lint clean (8 pre-existing warnings, 0 errors)
• manual: Cmd+N → new design → first prompt → design auto-names from prompt
• manual: switch design → messages reset / preview restored from latest snapshot
• manual: delete design → cascade snapshots + confirm modal
• manual: duplicate design → new copy with cloned messages and parent-rewired snapshots

[github-actions]

Findings

• [Blocker] DesignMessage schema rejects persisted system messages — this creates an internal contract break: DB and IPC both allow system, but shared schema narrows to user|assistant, which can cause invalid typed data and downstream regressions. Evidence packages/shared/src/snapshot.ts:31, apps/desktop/src/main/snapshots-db.ts:65, apps/desktop/src/main/snapshots-db.ts:377, apps/desktop/src/main/snapshots-ipc.ts:329
  Suggested fix:

  export const DesignMessageV1 = z.object({
    schemaVersion: z.literal(1).default(1),
    designId: z.string().min(1),
    role: z.enum(['user', 'assistant', 'system']),
    content: z.string(),
    ordinal: z.number().int().nonnegative(),
    createdAt: z.string(),
  });

• [Major] Silent persistence failure in persistDesignState violates the project hard constraint (no silent fallbacks) and risks unnoticed data loss in design/message history. Evidence apps/desktop/src/renderer/src/store.ts:228
  Suggested fix:

  } catch (err) {
    const msg = err instanceof Error ? err.message : tr('errors.unknown');
    get().pushToast({
      variant: 'error',
      title: tr('projects.notifications.saveFailed'),
      description: msg,
    });
    set({ lastError: msg, errorMessage: msg });
  }

• [Major] loadDesigns swallows IPC/DB errors and marks designsLoaded=true without surfacing failure, which is another silent fallback and can hide broken project loading state. Evidence apps/desktop/src/renderer/src/store.ts:737
  Suggested fix:

  } catch (err) {
    const msg = err instanceof Error ? err.message : tr('errors.unknown');
    set({ designsLoaded: true, errorMessage: msg, lastError: msg });
    get().pushToast({
      variant: 'error',
      title: tr('projects.notifications.loadFailed'),
      description: msg,
    });
  }

Summary

• Review mode: initial
• 3 issues found (1 blocker, 2 major), all introduced in modified lines.
• Not found in repo/docs: docs/VISION.md, docs/PRINCIPLES.md (review used CLAUDE.md + diffed files).

Testing

• Not run (automation)

open-codesign Bot

[github-actions]

role is narrower than the producer/DB contract in this PR (system is accepted and persisted). This introduces a schema/type mismatch. Please include system in the enum to keep shared types aligned with IPC + DB.

[github-actions]

This catch currently logs only, which is a silent fallback for persistence failures. Project constraints require surfacing every error in UI (or throwing with context). Please surface this via toast + lastError/errorMessage.

[github-actions]

loadDesigns failure is swallowed and state is marked loaded, leaving users without error visibility. Please surface this error (toast and/or state error) instead of console-only logging.

[github-actions]

Findings

• [Major] Silent fallback on persistence failure can hide data-loss conditions — persistDesignState only logs to console and does not surface any UI/throw context, which violates the no-silent-fallback constraint and leaves users unaware that messages/thumbnail were not saved. Evidence apps/desktop/src/renderer/src/store.ts:228
  Suggested fix:

  } catch (err) {
    const msg = err instanceof Error ? err.message : tr('errors.unknown');
    get().pushToast({
      variant: 'error',
      title: tr('projects.notifications.saveFailed'),
      description: msg,
    });
    set({ errorMessage: msg, lastError: msg });
    throw new Error(`persistDesignState failed: ${msg}`);
  }

• [Major] loadDesigns failure is swallowed while marking data as loaded — setting designsLoaded=true in the catch branch without surfacing an error can render an empty/stale project list with no user-visible failure signal. Evidence apps/desktop/src/renderer/src/store.ts:737
  Suggested fix:

  } catch (err) {
    const msg = err instanceof Error ? err.message : tr('errors.unknown');
    set({ designsLoaded: true, errorMessage: msg, lastError: msg });
    get().pushToast({
      variant: 'error',
      title: tr('projects.notifications.loadFailed'),
      description: msg,
    });
    throw new Error(`loadDesigns failed: ${msg}`);
  }

• [Major] Hardcoded UI color token bypass (text-white) violates the token-only UI constraint — this introduces a raw color instead of a design token-backed value. Evidence apps/desktop/src/renderer/src/components/DeleteDesignDialog.tsx:47
  Suggested fix:

  className="h-9 px-3 rounded-[var(--radius-md)] bg-[var(--color-error)] text-[var(--color-text-on-accent)] text-[var(--text-sm)] font-medium hover:opacity-90 transition-opacity"

Summary

• Review mode: follow-up after new commits
• 3 issues found (Major), all on added/modified lines in this PR diff.
• Not found in repo/docs: docs/VISION.md, docs/PRINCIPLES.md (repo indicates docs/ is gitignored in public clone).

Testing

• Not run (automation)

open-codesign Bot

[github-actions]

This catch introduces a silent fallback (console-only). Please surface this in UI and keep context by throwing.

} catch (err) {
  const msg = err instanceof Error ? err.message : tr('errors.unknown');
  get().pushToast({
    variant: 'error',
    title: tr('projects.notifications.saveFailed'),
    description: msg,
  });
  set({ errorMessage: msg, lastError: msg });
  throw new Error(`persistDesignState failed: ${msg}`);
}

[github-actions]

loadDesigns currently swallows IPC/DB errors and marks data as loaded; this hides failure state from users. Please surface + throw with context.

} catch (err) {
  const msg = err instanceof Error ? err.message : tr('errors.unknown');
  set({ designsLoaded: true, errorMessage: msg, lastError: msg });
  get().pushToast({
    variant: 'error',
    title: tr('projects.notifications.loadFailed'),
    description: msg,
  });
  throw new Error(`loadDesigns failed: ${msg}`);
}

[github-actions]

This adds a hardcoded color (text-white) instead of a token-backed value. Please use a semantic UI token class.

className="h-9 px-3 rounded-[var(--radius-md)] bg-[var(--color-error)] text-[var(--color-text-on-accent)] text-[var(--text-sm)] font-medium hover:opacity-90 transition-opacity"

[github-actions]

Findings

• [Major] Silent fallback hides persistence failures and violates the "no silent fallbacks" constraint — persistDesignState catches DB/IPC errors and only logs to console, so users can continue without any signal that messages/thumbnail were not saved. Evidence apps/desktop/src/renderer/src/store.ts:228.
  Suggested fix:

  } catch (err) {
    const msg = err instanceof Error ? err.message : tr('errors.unknown');
    get().pushToast({
      variant: 'error',
      title: tr('projects.notifications.saveFailed'),
      description: msg,
    });
    set({ errorMessage: msg, lastError: msg });
    throw new Error(`persistDesignState failed: ${msg}`);
  }

• [Major] Silent fallback on designs load can leave stale/empty UI state — loadDesigns sets designsLoaded=true even when the fetch fails and surfaces no user-visible error, which also violates the no-silent-fallback rule. Evidence apps/desktop/src/renderer/src/store.ts:737.
  Suggested fix:

  } catch (err) {
    const msg = err instanceof Error ? err.message : tr('errors.unknown');
    set({ designsLoaded: true, errorMessage: msg, lastError: msg });
    get().pushToast({
      variant: 'error',
      title: tr('projects.notifications.loadFailed'),
      description: msg,
    });
    throw new Error(`loadDesigns failed: ${msg}`);
  }

• [Major] Hardcoded color token bypass in UI — text-white introduces a raw color instead of a token-backed semantic value, conflicting with the UI token constraint. Evidence apps/desktop/src/renderer/src/components/DeleteDesignDialog.tsx:47.
  Suggested fix:

  className="h-9 px-3 rounded-[var(--radius-md)] bg-[var(--color-error)] text-[var(--color-on-accent)] text-[var(--text-sm)] font-medium hover:opacity-90 transition-opacity"

Summary

• Review mode: follow-up after new commits
• 3 Major issues found on added/modified lines.
• Not found in repo/docs: docs/VISION.md, docs/PRINCIPLES.md.

Testing

• Not run (automation)

open-codesign Bot

[github-actions]

This catch is a silent fallback (console only). Per project constraints, surface to UI and throw with context so save failures are explicit.

} catch (err) {
  const msg = err instanceof Error ? err.message : tr('errors.unknown');
  get().pushToast({
    variant: 'error',
    title: tr('projects.notifications.saveFailed'),
    description: msg,
  });
  set({ errorMessage: msg, lastError: msg });
  throw new Error(`persistDesignState failed: ${msg}`);
}

[github-actions]

loadDesigns currently swallows failure and still marks as loaded. Please surface a user-visible error and throw so callers can react.

} catch (err) {
  const msg = err instanceof Error ? err.message : tr('errors.unknown');
  set({ designsLoaded: true, errorMessage: msg, lastError: msg });
  get().pushToast({
    variant: 'error',
    title: tr('projects.notifications.loadFailed'),
    description: msg,
  });
  throw new Error(`loadDesigns failed: ${msg}`);
}

[github-actions]

This adds a hardcoded color (text-white) instead of a token-backed semantic color. Please switch to the design token class.

className="h-9 px-3 rounded-[var(--radius-md)] bg-[var(--color-error)] text-[var(--color-on-accent)] text-[var(--text-sm)] font-medium hover:opacity-90 transition-opacity"

[github-actions]

Findings

• [Major] New snapshots:v1:* project-management payloads are not schema-versioned end-to-end, breaking the project’s upgradeability contract and making protocol evolution brittle. Evidence apps/desktop/src/preload/index.ts:200, apps/desktop/src/main/snapshots-ipc.ts:267.
  Suggested fix:

  // preload
  ipcRenderer.invoke('snapshots:v1:rename-design', { schemaVersion: 1, id, name });
  
  // main
  const r = raw as Record<string, unknown>;
  requireSchemaV1(r, 'snapshots:v1:rename-design');

• [Major] persistDesignState still swallows persistence failures with console-only logging, which is a silent fallback and can hide message/thumbnail data loss from users. Evidence apps/desktop/src/renderer/src/store.ts:301.
  Suggested fix:

  } catch (err) {
    const msg = err instanceof Error ? err.message : tr('errors.unknown');
    get().pushToast({
      variant: 'error',
      title: tr('projects.notifications.saveFailed'),
      description: msg,
    });
    set({ errorMessage: msg, lastError: msg });
    throw new Error(`persistDesignState failed: ${msg}`);
  }

• [Major] loadDesigns still marks designsLoaded=true after failure without surfacing an actionable UI error, leaving the app in a misleading loaded state. Evidence apps/desktop/src/renderer/src/store.ts:888.
  Suggested fix:

  } catch (err) {
    const msg = err instanceof Error ? err.message : tr('errors.unknown');
    set({ designsLoaded: true, errorMessage: msg, lastError: msg });
    get().pushToast({
      variant: 'error',
      title: tr('projects.notifications.loadFailed'),
      description: msg,
    });
    throw new Error(`loadDesigns failed: ${msg}`);
  }

• [Minor] Hardcoded text-white bypasses tokenized UI color constraints. Evidence apps/desktop/src/renderer/src/components/DeleteDesignDialog.tsx:47.
  Suggested fix:

  className="h-9 px-3 rounded-[var(--radius-md)] bg-[var(--color-error)] text-[var(--color-on-accent)] text-[var(--text-sm)] font-medium hover:opacity-90 transition-opacity"

Summary

• Review mode: follow-up after new commits
• 4 issues found (3 Major, 1 Minor) on added/modified lines.
• Not found in repo/docs: docs/VISION.md, docs/PRINCIPLES.md.

Testing

• Not run (automation)

open-codesign Bot

[github-actions]

This new snapshots:v1:* handler path skips schemaVersion validation, while existing v1 handlers enforce it. Please gate this payload with requireSchemaV1(...) (and mirror that in other new handlers) to preserve protocol upgradeability and avoid mixed v1 contract behavior.

const r = raw as Record<string, unknown>;
requireSchemaV1(r, 'snapshots:v1:rename-design');

[github-actions]

This still silently falls back to console logging on persistence failure. Please surface a user-visible error and throw with context so failed message/thumbnail writes are explicit.

} catch (err) {
  const msg = err instanceof Error ? err.message : tr('errors.unknown');
  get().pushToast({
    variant: 'error',
    title: tr('projects.notifications.saveFailed'),
    description: msg,
  });
  set({ errorMessage: msg, lastError: msg });
  throw new Error(`persistDesignState failed: ${msg}`);
}

[github-actions]

loadDesigns still swallows failure and marks loaded, which can leave stale/empty UI with no actionable signal. Please surface an error toast/state and throw with context.

} catch (err) {
  const msg = err instanceof Error ? err.message : tr('errors.unknown');
  set({ designsLoaded: true, errorMessage: msg, lastError: msg });
  get().pushToast({
    variant: 'error',
    title: tr('projects.notifications.loadFailed'),
    description: msg,
  });
  throw new Error(`loadDesigns failed: ${msg}`);
}

[github-actions]

text-white is a hardcoded color class and bypasses tokenized semantic color usage. Please switch to the token-backed foreground color.

className="h-9 px-3 rounded-[var(--radius-md)] bg-[var(--color-error)] text-[var(--color-on-accent)] text-[var(--text-sm)] font-medium hover:opacity-90 transition-opacity"

[github-actions]

Findings

• [Major] persistDesignState swallows persistence failures with console-only logging, which violates the no-silent-fallback constraint and can hide message/thumbnail data loss. Evidence apps/desktop/src/renderer/src/store.ts:301
  Suggested fix:

  } catch (err) {
    const msg = err instanceof Error ? err.message : tr('errors.unknown');
    get().pushToast({
      variant: 'error',
      title: tr('projects.notifications.saveFailed'),
      description: msg,
    });
    set({ errorMessage: msg, lastError: msg });
    throw new Error(`persistDesignState failed: ${msg}`);
  }

• [Major] maybeAutoRename suppresses rename failures with console.error only, so rename persistence errors are invisible to users. Evidence apps/desktop/src/renderer/src/store.ts:318
  Suggested fix:

  } catch (err) {
    const msg = err instanceof Error ? err.message : tr('errors.unknown');
    get().pushToast({
      variant: 'error',
      title: tr('projects.notifications.renameFailed'),
      description: msg,
    });
    set({ errorMessage: msg, lastError: msg });
    throw new Error(`maybeAutoRename failed: ${msg}`);
  }

• [Major] loadDesigns marks designsLoaded=true after failure without surfacing actionable UI error state, creating a misleading loaded state. Evidence apps/desktop/src/renderer/src/store.ts:888
  Suggested fix:

  } catch (err) {
    const msg = err instanceof Error ? err.message : tr('errors.unknown');
    set({ designsLoaded: true, errorMessage: msg, lastError: msg });
    get().pushToast({
      variant: 'error',
      title: tr('projects.notifications.loadFailed'),
      description: msg,
    });
    throw new Error(`loadDesigns failed: ${msg}`);
  }

• [Minor] Hardcoded text-white bypasses tokenized semantic color usage. Evidence apps/desktop/src/renderer/src/components/DeleteDesignDialog.tsx:47
  Suggested fix:

  className="h-9 px-3 rounded-[var(--radius-md)] bg-[var(--color-error)] text-[var(--color-on-accent)] text-[var(--text-sm)] font-medium hover:opacity-90 transition-opacity"

Summary

• Review mode: follow-up after new commits
• 4 issues found on modified lines (3 Major, 1 Minor).
• Not found in repo/docs: docs/VISION.md, docs/PRINCIPLES.md.

Testing

• Not run (automation)

open-codesign Bot

[github-actions]

persistDesignState currently logs and continues on persistence failure, which makes data-write failure invisible. Please surface UI error state and throw with context.

} catch (err) {
  const msg = err instanceof Error ? err.message : tr('errors.unknown');
  get().pushToast({
    variant: 'error',
    title: tr('projects.notifications.saveFailed'),
    description: msg,
  });
  set({ errorMessage: msg, lastError: msg });
  throw new Error(`persistDesignState failed: ${msg}`);
}

[github-actions]

This catch suppresses rename failures with console logging only. Please surface the failure to the user and propagate context.

} catch (err) {
  const msg = err instanceof Error ? err.message : tr('errors.unknown');
  get().pushToast({
    variant: 'error',
    title: tr('projects.notifications.renameFailed'),
    description: msg,
  });
  set({ errorMessage: msg, lastError: msg });
  throw new Error(`maybeAutoRename failed: ${msg}`);
}

[github-actions]

loadDesigns marks loaded after failure but does not surface actionable UI error state. Please set error state + toast and throw with context.

} catch (err) {
  const msg = err instanceof Error ? err.message : tr('errors.unknown');
  set({ designsLoaded: true, errorMessage: msg, lastError: msg });
  get().pushToast({
    variant: 'error',
    title: tr('projects.notifications.loadFailed'),
    description: msg,
  });
  throw new Error(`loadDesigns failed: ${msg}`);
}

[github-actions]

text-white is a hardcoded color utility and bypasses tokenized semantic color usage. Please switch to the token-backed foreground color.

className="h-9 px-3 rounded-[var(--radius-md)] bg-[var(--color-error)] text-[var(--color-on-accent)] text-[var(--text-sm)] font-medium hover:opacity-90 transition-opacity"

[github-actions]

Findings

• [Major] Inline-comment edits are not persisted per design, which can lose user changes after switching designs. switchDesign restores state from SQLite (apps/desktop/src/renderer/src/store.ts:968), but persistence is only wired in the generate-success path (apps/desktop/src/renderer/src/store.ts:373). The inline-comment success path updates in-memory state without persisting it.
  Suggested fix:

  // after applyInlineComment success updates state
  const designId = get().currentDesignId;
  if (designId) {
    void persistDesignState(get, designId, get().messages, get().previewHtml);
  }

• [Minor] A hardcoded overlay color was introduced instead of using token-based UI values, violating the UI token constraint. Evidence apps/desktop/src/renderer/src/components/DesignsView.tsx:158.
  Suggested fix:

  className="absolute inset-0 flex items-end p-3 text-[var(--text-xs)] text-[var(--color-text-primary)] bg-[color-mix(in_srgb,var(--color-background)_10%,transparent)]"

Summary

• Review mode: follow-up after new commits
• 2 issues found on modified lines (1 Major, 1 Minor).
• Not found in repo/docs: docs/VISION.md, docs/PRINCIPLES.md.

Testing

• Not run (automation)
• Suggested: add a store test that verifies applyInlineComment persists messages/preview and survives switchDesign reload.

open-codesign Bot

[github-actions]

[Major] Persistence is currently only triggered on the generate-success path. Since design switching restores from SQLite, inline-comment edits can be lost unless that success path also persists.

Suggested fix:

const designId = get().currentDesignId;
if (designId) {
  void persistDesignState(get, designId, get().messages, get().previewHtml);
}

[github-actions]

[Minor] from-black/10 is a hardcoded color utility and bypasses tokenized UI values.

Suggested fix:

className="absolute inset-0 flex items-end p-3 text-[var(--text-xs)] text-[var(--color-text-primary)] bg-[color-mix(in_srgb,var(--color-background)_10%,transparent)]"

[github-actions]

Findings

• [Major] Deleting the current design is allowed while generation is active, which can write generation output into the wrong design after the store auto-switches. softDeleteDesign has no isGenerating guard (apps/desktop/src/renderer/src/store.ts:1050), while applyGenerateSuccess persists to whatever currentDesignId is at completion time (apps/desktop/src/renderer/src/store.ts:377).
  Suggested fix:

  async softDeleteDesign(id: string) {
    if (!window.codesign) return;
    if (get().isGenerating) {
      get().pushToast({
        variant: 'info',
        title: tr('projects.notifications.switchBlockedGenerating'),
      });
      return;
    }
    // existing delete flow...
  }

• [Minor] Hardcoded color utility from-black/10 bypasses tokenized UI values, violating the UI token constraint. Evidence apps/desktop/src/renderer/src/components/DesignsView.tsx:158.
  Suggested fix:

  className="absolute inset-0 flex items-end p-3 text-[var(--text-xs)] text-[var(--color-text-primary)] bg-[color-mix(in_srgb,var(--color-background)_10%,transparent)]"

Summary

• Review mode: follow-up after new commits
• 2 issues found on modified lines (1 Major, 1 Minor).
• Not found in repo/docs: docs/VISION.md, docs/PRINCIPLES.md.

Testing

• Not run (automation)
• Suggested: add a store test that deletes the active design during an in-flight generation and asserts no cross-design message/preview persistence.

open-codesign Bot

[github-actions]

[Major] softDeleteDesign can run while a generation is active. If the current design is deleted, the store switches/creates another design, and when the in-flight generation resolves, applyGenerateSuccess persists into the new currentDesignId, causing cross-design contamination.

Suggested fix:

if (get().isGenerating) {
  get().pushToast({
    variant: info,
    title: tr(projects.notifications.switchBlockedGenerating),
  });
  return;
}

[github-actions]

[Minor] from-black/10 is a hardcoded color utility and bypasses tokenized UI values.

Suggested fix:

className="absolute inset-0 flex items-end p-3 text-[var(--text-xs)] text-[var(--color-text-primary)] bg-[color-mix(in_srgb,var(--color-background)_10%,transparent)]"

[github-actions]

Findings

• [Major] Non-tokenized UI values are introduced in new renderer components, which violates the hard UI-token constraint and can drift from theme/system tokens. Evidence apps/desktop/src/renderer/src/components/DesignSwitcher.tsx:54 (also :64, :68, :90, :93, etc.).
  Suggested fix:

  className="inline-flex items-center gap-[var(--space-1_5)] max-w-[var(--size-chip-max)] rounded-[var(--radius-md)] px-[var(--space-2)] py-[var(--space-1)] text-[var(--text-sm)] text-[var(--color-text-primary)] hover:bg-[var(--color-surface-hover)] transition-colors"

• [Major] createNewDesign silently no-ops while generation is active (if (get().isGenerating) return null;), so user-triggered actions from hotkey/command palette appear broken with no surfaced error/toast. Evidence apps/desktop/src/renderer/src/store.ts:935.
  Suggested fix:

  if (get().isGenerating) {
    get().pushToast({
      variant: 'info',
      title: tr('projects.notifications.createBlockedGenerating'),
    });
    return null;
  }

Summary

• Review mode: follow-up after new commits
• 2 issues found on modified lines (2 Major).
• Not found in repo/docs: docs/VISION.md, docs/PRINCIPLES.md.

Testing

• Not run (automation)
• Suggested: add a store test that asserts createNewDesign() during active generation emits an info toast and does not mutate current design state.

open-codesign Bot

[github-actions]

[Major] This new class string introduces hardcoded layout values (max-w-[260px], numeric spacing, and related raw px usage nearby) instead of packages/ui tokens, which violates the hard UI-token constraint.

Suggested fix:

className="inline-flex items-center gap-[var(--space-1_5)] max-w-[var(--size-chip-max)] rounded-[var(--radius-md)] px-[var(--space-2)] py-[var(--space-1)] text-[var(--text-sm)] text-[var(--color-text-primary)] hover:bg-[var(--color-surface-hover)] transition-colors"

[github-actions]

[Major] User-invoked createNewDesign silently returns during active generation, so shortcuts/palette actions look broken with no feedback. This conflicts with the no-silent-fallback behavior expected in this project.

Suggested fix:

if (get().isGenerating) {
  get().pushToast({
    variant: 'info',
    title: tr('projects.notifications.createBlockedGenerating'),
  });
  return null;
}