link: two-step workspace picker + cross-workspace --app-id

[netanelgilad]

Note

Description

Reworks base44 link so it can link apps across any workspace the user can access, not just their personal one. The interactive flow now uses a two-step picker — choose a workspace, then choose an app scoped to it — while an explicit --app-id is validated by fetching the app directly, so linking works cross-workspace regardless of the picker's scope. Managed-source apps are rejected up front with a clear message.

Related Issue

None

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation update
• Refactoring (no functional changes)
• Other (please describe):

Changes Made

• Add resolveExplicitAppId() in link.ts: validates --app-id by calling getApp() directly (works cross-workspace), maps 404/403 to a friendly InvalidInputError with hints, and rejects managed-source apps.
• Add chooseProjectInteractively(): a two-step picker that resolves the target workspace first (skipped when the user has a single workspace) and then lists/selects apps scoped to that workspace.
• Extend resolveWorkspaceId() with an optional promptMessage so link can ask "Which workspace is the app in?" instead of the create-oriented copy; clarify its doc comment.
• Add workspaceId scoping to listProjects() (passes workspace_id to GET /api/apps when provided).
• Fetch and expose is_managed_source_code on getApp() / AppDetailSchema (isManagedSourceCode).
• Update the --workspace flag help to reflect it now scopes the app picker as well as create.
• Testkit: add mockGetApp() keyed off the app's own id; update link tests to mock getApp, and add cases for cross-workspace link, managed-source rejection, and not-found errors.

Testing

• I have tested these changes locally
• I have added/updated tests as needed
• All tests pass (`npm test`)

Checklist

• My code follows the project's style guidelines
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation (if applicable)
• My changes generate no new warnings
• I have updated `docs/` (AGENTS.md) if I made architectural changes

Additional Notes

Behavior change: --app-id no longer needs the app to appear in the personal-workspace project list; it is validated via getApp and thus supports team/cross-workspace apps. Legacy --project-id/--projectId aliases continue to work.

---

_{🤖 Generated by Claude | 2026-07-19 09:09 UTC | 1f028a6}

[github-actions]

🚀 Package Preview Available!

---

Install this PR's preview build with npm:

npm i @base44-preview/cli@0.1.5-pr.568.1f028a6

Prefer not to change any import paths? Install using npm alias so your code still imports base44:

npm i "base44@npm:@base44-preview/cli@0.1.5-pr.568.1f028a6"

Or add it to your package.json dependencies:

{
  "dependencies": {
    "base44": "npm:@base44-preview/cli@0.1.5-pr.568.1f028a6"
  }
}

• 📦 Preview Package: @base44-preview/cli@0.1.5-pr.568.1f028a6
• 🔗 View this commit on GitHub

---

_{Preview published to npm registry — try new features instantly!}