metabase modular embedding version upgrade

Engineering Community

Skill notes

Execution contract

Follow the workflow steps in order — do not skip any step. Create the checklist first, then execute each step and explicitly mark it done with evidence. Each step's output feeds into the next, so skipping steps produces wrong migrations. If you cannot complete a step due to missing info or tool failure, you must: record the step as ❌ blocked, explain exactly what is missing / what failed, stop (do not proceed to later steps).

Required output structure

Your response should contain these sections in this order: Step 0: Upgrade Plan Checklist Step 1 Results: Project Scan Step 2 Results: d.ts Diff / Target Docs (primary or fallback) Step 3: Change Catalog

Evidence requirements

Step 1: list every matched file path and the matching grep lines (SDK imports or Modular embedding API calls/script tags). Full file analysis happens in Step 4. Step 2 (primary path): show the diff output between d.ts files. (hybrid/fallback path): list each fetched URL + confirm files are loaded in context. Do not analyze or resolve types here — that's Step 3's job. Step 3: the structured change catalog — every changed/removed/added symbol with its fully resolved concrete type.

Performance

The workflow is designed as a pipeline that maximizes parallelism: In Claude Code, use parallel tool calls or run_in_background: true for sub-agents. Do not parse repo branches, commits, PRs, or issues — they're noisy and irrelevant to version diffing.

Tool-call round budget for Steps 1+2

Steps 1+2 must complete in 3 tool-call rounds. Round 1 — discovery (all concurrent, single message): Grep for @metabase/embedding-sdk-react imports (returns file paths — do not read files yet) Glob for lock files (yarn.lock, pnpm-lock.yaml, package-lock.json) Read package.json (for current version)

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Engineering
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@metabase · no license declared
Token usage
Heavy
Setup complexity
Manual integration
External API key
Not required
Operating systems
Docker
Runtime requirements
Docker
Detected file/system behavior
  • Read-only
  • Write / modify
  • Shell exec
  • Env read
Network behavior
External requests
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

Output preview metabase-modular-embedding-version-upgrade.preview
# Required output structure

1. **Step 0: Upgrade Plan Checklist**
2. **Step 1 Results: Project Scan**
3. **Step 2 Results: d.ts Diff / Target Docs** (primary or fallback)
4. **Step 3: Change Catalog**
5. **Step 4: Per-File Migration** (one subsection per file)
6. **Step 5: Typecheck Validation**

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.