Tell Cursor which package actually owns a change in a multi-root monorepo

Why this works

Multi-root workspace support means Cursor's indexer sees several package roots at once and its semantic code search treats them as one searchable space by default — that's the point of the feature, but it also means a similarly named file or function in another root is a plausible edit target unless the agent is told which root actually owns the change. Without OWNING PACKAGE stated explicitly, a 'closest semantic match' search across roots can surface a same-named helper in a sibling package as the thing to edit, or the model can duplicate a type that already exists in a package it was never told to treat as read-only. Naming shared-file boundaries closes a second, more damaging gap: monorepo root config (workspace manifests, base tsconfig) affects every package silently, so an edit there is exactly the kind of change an agent should never make without an explicit ask, even though nothing about the task description would obviously exclude it. Requiring package-scoped commands over workspace-wide ones prevents a slower but real failure mode: a workspace-level build or test run silently exercising and reporting on packages the change never touched.