cap-add-remote-servicelisted

## What I do Guide the developer step-by-step through adding a remote service integration to an existing CAP Node.js project, following the CAP-Level Service Integration (Calesi) pattern. This covers importing APIs, defining consumption views, integrating the model, and wiring up the required Node.js handlers. ## Context I need first Before starting, inspect the project so I understand its structure: 1. Read `package.json` to learn the project name and existing dependencies. 2. Use `cds-mcp_search_model` to get an overview of the services and entities already defined in the project. 3. Ask the user: - Which remote service they want to integrate (another CAP app, S/4HANA Business Partner, etc.) - Whether they have the API already as an npm package, an `.edmx` file, or just a URL ## Step 1 — Import the API ### Option A: CAP package from npm If the remote service is published as a CAP package (e.g. `@capire/xflights-data`): ```sh npm add <package-name> ``` Check the added package's `index.cds` and `package.json` to understand what service name and entities it exposes. **Important**: Also check the package's mock data CSV files (usually in `srv/external/data/`) to see which columns actually have data. The consumption view should only project columns that exist in the mock data, otherwise the UI will show empty values during local development. (Check back with the user if unsure) ### Option B: OData EDMX file If the developer provides an `.edmx` file