Problem
Non-interactive monorepo selection can require the exact discovered display name. Common inputs such as --app apps/api or --app api fail when the discovered name differs, even when the target is unambiguous.
This behavior was bundled into draft PR #1418, but it is independent from existing-Sentry detection and should be handled separately.
Expected behavior
- Prefer an exact app name or exact normalized full path.
- Accept a unique path basename as an alias.
- If a basename matches multiple apps, fail and list the matching paths instead of choosing one.
- Keep path matching scoped to the discovered apps.
- Cover nested paths, duplicate basenames, and exact-match precedence in tests.
Problem
Non-interactive monorepo selection can require the exact discovered display name. Common inputs such as --app apps/api or --app api fail when the discovered name differs, even when the target is unambiguous.
This behavior was bundled into draft PR #1418, but it is independent from existing-Sentry detection and should be handled separately.
Expected behavior