fix(docs): install SDK packages in V2 deploy for legacy builder

.aiassistant/rules/aida.md

@@ -0,0 +1,12 @@
+# You must follow this guidance only if AIDA MCP tools are available.
+Call AIDA MCP `get_rules` at every task start and after every scope change; the `query` must match the current requested task.
+Reuse one stable `session_id` for the whole conversation when calling `get_rules`.
+When a `get_rules` response returns `delta.cursor`, pass it as `delta_cursor` on the next `get_rules` call in the same conversation.
+You must always follow instructions returned by the `get_rules` MCP tool.
+Do not perform Git or GitHub management unless the user explicitly asks for it.
+If the user asks for code or docs changes only, stop before commit, push, or PR actions.
+For commit and push workflow, do not call `get_rules`.
+When the user explicitly asks for a commit, call the AIDA MCP `commit_command` tool.
+The tool executes the commit server-side. If it returns `ok=true`, the commit is done — do not run any git commit commands.
+If it returns `status=needs_more_input`, infer the missing policy-controlled values from the current changes and retry instead of asking the user.
+Do not handcraft `git commit` arguments.

.aida/.gitignore

@@ -0,0 +1,2 @@
+rules_selection.local.yaml
+git_policy.local.yaml

.aida/change_domains.yaml

@@ -0,0 +1,44 @@
+# (C) 2026 GoodData Corporation
+# AIDA change domain classification
+#
+# Define how changed paths map to validation domains.
+# See `.aida/validation_policy.yaml` for mapping domains to pipelines.
+version: 1
+domains:
+  - id: python-package
+    description: Any workspace Python package under packages/*
+    match_globs:
+      - "packages/*/src/**/*.py"
+      - "packages/*/tests/**/*.py"
+      - "packages/*/pyproject.toml"
+      - "packages/*/tox.ini"
+      - "packages/*/Makefile"
+    root_depth: 2
+
+  - id: api-client
+    description: Generated API client package and its local config
+    match_globs:
+      - "gooddata-api-client/**/*.py"
+      - "gooddata-api-client/requirements.txt"
+      - "gooddata-api-client/test-requirements.txt"
+      - "gooddata-api-client/setup.py"
+      - "gooddata-api-client/tox.ini"
+    root_depth: 1
+
+  - id: repo-tooling
+    description: Root-level shared tooling and workspace configuration
+    match_globs:
+      - "pyproject.toml"
+      - "Makefile"
+      - "project_common.mk"
+      - "ci_tests.mk"
+    root_depth: 0
+
+  - id: aida-config
+    description: AIDA workflow configuration and local MCP wiring
+    match_globs:
+      - ".aida/**/*.yaml"
+      - ".aida/**/*.mdc"
+      - ".mcp.json"
+      - ".claude/CLAUDE.md"
+    root_depth: 0

.aida/git_policy.yaml

@@ -0,0 +1,27 @@
+# (C) 2026 GoodData Corporation
+# AIDA git policy
+#
+# Configure commit and git workflow policy used by AIDA tools.
+version: 1
+git_policy:
+  commit:
+    subject_max_chars: 70
+    risk_values:
+    - nonprod
+    - low
+    - high
+    require_co_authored_by: false
+    ticket_prefix: JIRA
+    risk_prefix: risk
+    template_file: templates/commit-message.txt
+    pre_commit_guidance: false
+    ticket_enabled: true
+    risk_enabled: true
+  workflow:
+    prefer_force_with_lease: true
+    autosquash_unpublished_only: true
+  pr:
+    title_template_file: templates/pr-title.txt
+    body_template_file: templates/pr-body.md
+  enforcement:
+    mode: "off"

.aida/migrate-backups/20260307-133351/.aiassistant/rules/aida.md

@@ -0,0 +1,4 @@
+# You must follow this guidance only if AIDA MCP tools are available.
+Call AIDA MCP `get_rules` at every task start and after every scope change; the `query` must match the current requested task.
+Call AIDA MCP `get_rules` again before entering commit/push workflow with query: "How to commit/push".
+You must always follow instructions returned by the `get_rules` MCP tool.

.aida/migrate-backups/20260307-133351/.claude/CLAUDE.md

@@ -0,0 +1,57 @@
+---
+apply: always
+---
+
+# AIDA Development Workflow
+
+This file contains only:
+- the mandatory workflow, and
+- which MCP tools to use in each phase.
+
+Do not duplicate detailed “how to” guidance here. Always rely on MCP tool descriptions and `get_rules(...)`.
+
+## Editing this file (template-driven)
+
+This file is generated by `aida-mcp init` from templates shipped in the `aida-mcp` package.
+
+- **Do not hand-edit** `.cursor/rules/aida.mdc` or `.claude/CLAUDE.md` in a repo.
+- To change the content, **update the templates in the `aida-mcp` package** and then rerun `aida-mcp init` in the repo.
+
+## Post-init check
+
+- After `aida-mcp init`, if MCP tools like `get_rules` or `validate` are missing, run `aida-mcp doctor`.
+
+## Workflow (mandatory)
+
+### 1) Get rules
+
+- At the start of every task (and again on scope change), call `get_rules(query="...")`.
+- Follow the rules returned by `get_rules` for the task.
+
+### 2) Implement
+
+- Make the requested change(s) following repository rules returned by `get_rules`.
+
+### 3) Validate (blocking)
+
+- If you changed code, you must validate before responding about code changes.
+- Prefer the narrowest validation that is still correct (use `test_filter` when appropriate).
+- Use the MCP validation tool `validate` (prefer this over raw `./gradlew` / `make`).
+- If you changed `.proto` files, do not run proto regeneration manually; `validate` will run it when needed.
+- If unsure what validation to run, call `get_rules(query="validation workflow")` and follow the returned guidance.
+
+### 4) Commit / PR (if asked)
+
+- Ask for the JIRA ticket if unknown.
+- Before committing or creating a PR, call `get_rules(query="git")` and follow the returned guidance.
+- For commit creation, use `aida-mcp commit` (do not use raw `git commit`).
+
+## When to create/update rules
+
+If any of these happen, propose updates to repo rules/config by following `get_rules(query="rules authoring")`:
+- repeated friction (“how do I … in this repo?” keeps coming up)
+- user dissatisfaction (“wrong”, “not what I meant”, “stop doing that”)
+- recurring validation failures of the same kind
+- large/risky cross-cutting changes
+
+Before creating/updating files under `.aida/` (including `.aida/rules/**` and `.aida/*.yaml`), ask the user for explicit permission and proceed only after approval.

.aida/migrate-backups/20260307-133351/.junie/guidelines.md

@@ -0,0 +1,4 @@
+# You must follow this guidance only if AIDA MCP tools are available.
+Call AIDA MCP `get_rules` at every task start and after every scope change; the `query` must match the current requested task.
+Call AIDA MCP `get_rules` again before entering commit/push workflow with query: "How to commit/push".
+You must always follow instructions returned by the `get_rules` MCP tool.

.aida/migrate-backups/20260307-133351/AGENTS.md

@@ -0,0 +1,4 @@
+# You must follow this guidance only if AIDA MCP tools are available.
+Call AIDA MCP `get_rules` at every task start and after every scope change; the `query` must match the current requested task.
+Call AIDA MCP `get_rules` again before entering commit/push workflow with query: "How to commit/push".
+You must always follow instructions returned by the `get_rules` MCP tool.

.aida/migrate-backups/20260307-140805/.aiassistant/rules/aida.md

@@ -0,0 +1,6 @@
+# You must follow this guidance only if AIDA MCP tools are available.
+Call AIDA MCP `get_rules` at every task start and after every scope change; the `query` must match the current requested task.
+You must always follow instructions returned by the `get_rules` MCP tool.
+For commit and push workflow, do not call `get_rules`.
+Before any commit, call the AIDA MCP `commit_command` tool and execute the returned raw `git commit` command exactly.
+Do not handcraft `git commit` arguments or rewrite the returned command.

.aida/migrate-backups/20260307-140805/.claude/CLAUDE.md

@@ -0,0 +1,10 @@
+---
+apply: always
+---
+
+# You must follow this guidance only if AIDA MCP tools are available.
+Call AIDA MCP `get_rules` at every task start and after every scope change; the `query` must match the current requested task.
+You must always follow instructions returned by the `get_rules` MCP tool.
+For commit and push workflow, do not call `get_rules`.
+Before any commit, call the AIDA MCP `commit_command` tool and execute the returned raw `git commit` command exactly.
+Do not handcraft `git commit` arguments or rewrite the returned command.

.aida/migrate-backups/20260307-140805/.junie/guidelines.md

@@ -0,0 +1,6 @@
+# You must follow this guidance only if AIDA MCP tools are available.
+Call AIDA MCP `get_rules` at every task start and after every scope change; the `query` must match the current requested task.
+You must always follow instructions returned by the `get_rules` MCP tool.
+For commit and push workflow, do not call `get_rules`.
+Before any commit, call the AIDA MCP `commit_command` tool and execute the returned raw `git commit` command exactly.
+Do not handcraft `git commit` arguments or rewrite the returned command.

.aida/migrate-backups/20260307-140805/AGENTS.md

@@ -0,0 +1,6 @@
+# You must follow this guidance only if AIDA MCP tools are available.
+Call AIDA MCP `get_rules` at every task start and after every scope change; the `query` must match the current requested task.
+You must always follow instructions returned by the `get_rules` MCP tool.
+For commit and push workflow, do not call `get_rules`.
+Before any commit, call the AIDA MCP `commit_command` tool and execute the returned raw `git commit` command exactly.
+Do not handcraft `git commit` arguments or rewrite the returned command.

.aida/rules/packages/gooddata-dbt.mdc

@@ -0,0 +1,38 @@
+# (C) 2026 GoodData Corporation
+---
+description: GoodData dbt package - bridge from dbt metadata to GoodData semantic model
+alwaysApply: false
+---
+
+# GoodData dbt Package
+
+**Location**: `packages/gooddata-dbt/`
+
+## Owns
+
+- CLI workflow for dbt-oriented GoodData operations (`gooddata-dbt`)
+- Conversion of dbt models/profiles into GoodData LDM and analytics deployment inputs
+- Workspace and data source provisioning helpers driven by `gooddata.yaml`
+
+## Does NOT Own
+
+- Core GoodData SDK domain/client services → `gooddata-sdk`
+- Generic orchestration or storage automation → `gooddata-pipelines`
+- dbt runtime implementation itself (provided by dbt tooling)
+
+## Architecture
+
+**Entry point**: `gooddata_dbt.main:main`
+
+**Primary package**: `src/gooddata_dbt`
+
+**Depends on**: `gooddata-sdk`
+
+## Testing
+
+Use package-local pytest suites under `packages/gooddata-dbt/tests`.
+
+## Dependencies
+
+Required: technologies/python, packages/gooddata-sdk
+Related: technologies/testing, packages/gooddata-pipelines

.aida/rules/packages/gooddata-fdw.mdc

@@ -0,0 +1,38 @@
+# (C) 2026 GoodData Corporation
+---
+description: GoodData FDW package - PostgreSQL foreign data wrapper integration
+alwaysApply: false
+---
+
+# GoodData FDW Package
+
+**Location**: `packages/gooddata-fdw/`
+
+## Owns
+
+- PostgreSQL FDW integration for exposing GoodData data as SQL-accessible foreign tables
+- Translation layer between FDW execution flow and GoodData SDK calls
+- Import/execute FDW command behavior used by package tests and docs
+
+## Does NOT Own
+
+- Core API/service client behavior → `gooddata-sdk`
+- Flight RPC server infrastructure → `gooddata-flight-server`
+- FlexConnect function runtime → `gooddata-flexconnect`
+
+## Architecture
+
+**Primary package**: `src/gooddata_fdw`
+
+**Runtime dependency**: multicorn/PostgreSQL FDW environment
+
+**Depends on**: `gooddata-sdk`
+
+## Testing
+
+Use package-local pytest suites under `packages/gooddata-fdw/tests`.
+
+## Dependencies
+
+Required: technologies/python, packages/gooddata-sdk
+Related: technologies/testing

.aida/rules/packages/gooddata-flexconnect.mdc

@@ -0,0 +1,38 @@
+# (C) 2026 GoodData Corporation
+---
+description: GoodData FlexConnect package - custom data source framework for GoodData
+alwaysApply: false
+---
+
+# GoodData FlexConnect Package
+
+**Location**: `packages/gooddata-flexconnect/`
+
+## Owns
+
+- FlexConnect framework for authoring custom table-function style data sources
+- Runtime contract for mapping custom function outputs into GoodData datasets
+- Integration layer combining GoodData SDK interactions with Flight server hosting
+
+## Does NOT Own
+
+- Generic Flight server infrastructure and CLI → `gooddata-flight-server`
+- Core GoodData Cloud domain/catalog/compute APIs → `gooddata-sdk`
+- PostgreSQL FDW integration → `gooddata-fdw`
+
+## Architecture
+
+**Primary package**: `src/gooddata_flexconnect`
+
+**Depends on**: `gooddata-flight-server`, `gooddata-sdk`
+
+**Typical usage**: external FlexConnect projects consume this package as a framework dependency
+
+## Testing
+
+Use package-local pytest suites under `packages/gooddata-flexconnect/tests`.
+
+## Dependencies
+
+Required: technologies/python, packages/gooddata-flight-server, packages/gooddata-sdk
+Related: technologies/testing

.aida/rules/packages/gooddata-flight-server.mdc

@@ -0,0 +1,38 @@
+# (C) 2026 GoodData Corporation
+---
+description: GoodData Flight Server package - pluggable Flight RPC server foundation
+alwaysApply: false
+---
+
+# GoodData Flight Server Package
+
+**Location**: `packages/gooddata-flight-server/`
+
+## Owns
+
+- Reusable Flight RPC server runtime and CLI (`gooddata-flight-server`)
+- Server bootstrap, lifecycle handling, observability, and auth/token integration
+- Configuration patterns for running custom Flight method providers
+
+## Does NOT Own
+
+- Core GoodData Cloud domain/catalog/compute SDK APIs → `gooddata-sdk`
+- Product-specific data source functions and semantic model mapping → `gooddata-flexconnect`
+- Lifecycle provisioning and backup workflows → `gooddata-pipelines`
+
+## Architecture
+
+**Entry point**: `gooddata_flight_server.cli:server_cli`
+
+**Primary package**: `src/gooddata_flight_server`
+
+**Key stack**: `pyarrow.flight`, `dynaconf`, telemetry/metrics integrations
+
+## Testing
+
+Use package-local pytest suites under `packages/gooddata-flight-server/tests`.
+
+## Dependencies
+
+Required: technologies/python
+Related: technologies/testing, packages/gooddata-flexconnect

.aida/rules/packages/gooddata-pandas.mdc

@@ -0,0 +1,43 @@
+# (C) 2026 GoodData Corporation
+---
+description: GoodData Pandas package - pandas integration layer for GoodData SDK
+alwaysApply: false
+---
+
+# GoodData Pandas Package
+
+**Location**: `packages/gooddata-pandas/`
+
+## Owns
+
+- Pandas Series and DataFrame creation from GoodData data
+- Integration layer between GoodData SDK and pandas
+
+## Does NOT Own
+
+- Core SDK functionality → gooddata-sdk package
+- API client → gooddata-api-client (generated)
+
+## Architecture
+
+**Dependency**: Depends on `gooddata-sdk` core package.
+
+**Main class**: `GoodPandas` - extends SDK with pandas-specific operations
+
+## Usage
+
+```python
+from gooddata_pandas import GoodPandas
+
+gp = GoodPandas(host="https://example.gooddata.com", token="...")
+df = gp.data_frames(workspace_id="demo", insight_id="...")
+```
+
+## Testing
+
+Uses vcrpy cassettes. See `technologies/testing` rule for workflow.
+
+## Dependencies
+
+Required: technologies/python, packages/gooddata-sdk
+Related: technologies/testing