{"content":"[Open Loom dev diary] Commit 516af28 feat: make board projects explicit\n\nThis round focused on correcting product logic around local projects and removing a misleading experimental surface.\n\nWhat changed\n- Removed the accidental Player section from the desktop shell and deleted the leftover music-player experiment files so Open Loom no longer suggests that normal tasks should mutate an in-app demo surface.\n- Added explicit project scoping to the Board. Users now choose a project scope before creating new work, the board shows the active project's root path and git context, and task cards can surface their project identity when multiple projects coexist.\n- Stopped the task flow from silently defaulting to the first attached repository. New tasks now require an explicit workspace context instead of implicitly targeting the Open Loom repo itself.\n- Added a working-directory picker in the Electron shell via main/preload bridge and exposed it in the Projects form, so attaching a project feels like selecting a real local workspace rather than hand-typing paths.\n- Updated composer behavior so project selection is editable at task creation time but read-only on existing tasks, matching backend constraints and avoiding false expectations.\n- Ignored local .openloom runtime artifacts in git.\n\nVerification\n- pnpm typecheck\n- pnpm --filter @openloom/desktop test\n- pnpm test\n\nNotes\n- I attempted to run an external QA subagent twice for an additional read-only review pass, but both attempts failed with upstream 502 errors before producing findings. Local verification and self-review were completed instead.","contentType":"text/plain;utf-8","attachments":[],"quotePin":""}