Charles BochetandGitHub
3eeaebb0cc
## Summary The `--light` flag of `workspace:seed:dev` was supposed to seed a single workspace for thin dev containers, but it was only filtering the rich workspaces (Apple, YCombinator) — the `Empty3`/`Empty4` fixtures introduced in #19559 for upgrade-sequence integration tests were always seeded. So `--light` actually produced **3** workspaces: - Apple - Empty3 - Empty4 In single-workspace mode (`IS_MULTIWORKSPACE_ENABLED=false`, the default for the `twenty-app-dev` container), [`WorkspaceDomainsService.getDefaultWorkspace`](https://github.com/twentyhq/twenty/blob/main/packages/twenty-server/src/engine/core-modules/domain/workspace-domains/services/workspace-domains.service.ts) returns the most recently created workspace — Empty4 — which has no users. The prefilled `tim@apple.dev` therefore cannot sign in, which breaks flows that depend on the default workspace such as `yarn twenty remote add --local`'s OAuth handshake against the dev container. This PR makes `--light` actually skip the empty fixtures so the dev container ends up with a single workspace (Apple). The default (no flag) invocation, used by `database:reset` for integration tests, still seeds all four workspaces, so `upgrade-sequence-runner-integration-test.util.ts` keeps working unchanged.