Skip to content

chore(ai): bump AI workbench to e82e1029 and regenerate scaffolds - #74

Merged
bjoaquinc merged 1 commit into
develfrom
chore/bump-ai-workbench
Jul 8, 2026
Merged

chore(ai): bump AI workbench to e82e1029 and regenerate scaffolds#74
bjoaquinc merged 1 commit into
develfrom
chore/bump-ai-workbench

Conversation

@bjoaquinc

Copy link
Copy Markdown
Collaborator

Overview

Bumps the bundled AI workbench (WORKBENCH_REF f290a9be82e1029) and regenerates the Claude/Codex/Cursor scaffolds via make update-ai. Content-only change from dlt-hub/dlthub-ai-workbench; no CLI logic touched.

Upstream changes

  • New performance toolkit in the router index — "optimize / speed up a slow or memory-heavy pipeline → performanceoptimize-performance".
  • deploy-run-sample-pipeline now tells the user their data loads into a dltHub-hosted playground destination (zero setup, no credentials, playground/onboarding only — not production), and repeats it at "Onboarding complete."
  • dlthub-router / init rule relaxed: agents trust the toolkit install output and only run dlthub ai status when it's ambiguous or MCP hasn't been verified that session, instead of always.

All three agents (claude/codex/cursor) mirror the same content; the config.py ref bump and .dlt/.toolkits sha manifests are bookkeeping for the above.

Tests

  • make check-ai clean, make test (168) + ruff/mypy pass.

🤖 Generated with Claude Code

Bumps WORKBENCH_REF f290a9b -> e82e1029 and regenerates the bundled
Claude/Codex/Cursor scaffolds. Upstream changes:
- adds a `performance` toolkit to the router index
- deploy-run-sample-pipeline explains data loads into a hosted
  playground destination (not for production)
- dlthub-router only runs `dlthub ai status` when the install output is
  unclear, instead of always

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@bjoaquinc
bjoaquinc merged commit 2594f8f into devel Jul 8, 2026
5 checks passed
@bjoaquinc
bjoaquinc deleted the chore/bump-ai-workbench branch July 8, 2026 09:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant