docs(destination-motherduck): improve documentation and fix changelog dates

[devin-ai-integration]

Documentation Confidence Assessment

Overall Confidence: 3/5

Dimension	Score	Rationale
Code Comprehension	2/5	Python CDK destination with custom DuckDB processors and PyArrow integration; config fields verified from spec.json but processor internals required inference.
API Documentation Quality	4/5	MotherDuck has comprehensive official docs with auth guides, status page, and deprecation schedules; minor gaps in rate limit docs.
Change Scope & Risk	4/5	55 lines changed total (31 added, 24 removed) — targeted overview rewrite, config field documentation, and three changelog date corrections.
Existing Doc Maturity	3/5	112-line doc with basic coverage of setup, sync modes, and changelog; functional but not comprehensive.
Connector Sensitivity	4/5	Certified connector with low usage metrics (ql=100, sl=100); recently promoted to certified status.
Triggering Context	5/5	Triggered from merged PR #75645 — a patch version bump to force registry update for supportLevel change to certified.

What I Verified vs. What I Inferred

• Verified from code: All three configuration fields (motherduck_api_key, destination_path, schema) and their defaults/requirements from spec.json; supported sync modes (overwrite, append, append_dedup); Python CDK connector type from cdk:python tag and source structure
• Verified from API docs: MotherDuck authentication uses access tokens; md: prefix database URI format; default database name my_db when no name specified
• Verified from git history: Three changelog dates corrected against merge commit timestamps
• Inferred: Exact UI steps to create a MotherDuck access token ("click organization name > Settings > Create token") — based on docs, not verified against live UI; that /tmp/airbyte_local and LOCAL_ROOT info removed from this doc is adequately covered in DuckDB destination docs

Areas of Concern

• Token creation instructions (line 46): The specific UI navigation steps should be verified against the current MotherDuck interface.
• Removal of local DuckDB file path information assumes the DuckDB destination docs cover it. Reviewer should confirm.

---

What

Improves the MotherDuck destination documentation to be accurate, well-structured, and MotherDuck-focused. Fixes three incorrect changelog dates that were set by /bump-version at PR creation time rather than actual merge dates.

Triggered by commit c343b13 (PR #75645), which promoted MotherDuck to certified support level.

How

Overview rewrite: The old overview described DuckDB first and referenced local filesystem paths (/tmp/airbyte_local, LOCAL_ROOT), which is confusing for a connector named "MotherDuck." Rewrote to lead with MotherDuck as a cloud analytics platform and redirect local-only users to the DuckDB destination.

Structure improvements:

• Replaced the confusing "Use with MotherDuck" section (this is the MotherDuck connector) with a proper "Configuration" section documenting all three spec.json fields (motherduck_api_key, destination_path, schema)
• Added a "Prerequisites" section
• Promoted "Output schema" from a deeply nested H4 to a top-level H2
• Removed inaccurate "Performance consideration" (filesystem speed is irrelevant for a cloud destination)

Changelog date corrections (verified against git merge commit dates):

Version	Old date	Correct date	How verified
0.2.0	2025-12-01	2026-01-06	git show a0091239c93 --format="%cI"
0.2.1	2025-12-19	2026-01-29	git show 68a864b6266 --format="%cI"
0.2.2	2025-02-02	2026-03-17	git show eecb22ac565 --format="%cI"

The v0.2.2 date of 2025-02-02 was clearly wrong — it predates the PR's creation date of 2025-12-08.

Review guide

1. docs/integrations/destinations/motherduck.md — single file changed

Key areas for reviewer attention:

• Changelog dates: Verify the three corrected dates are accurate. The old dates were set by /bump-version at command-run time, not PR merge time.
• Token creation steps (line 46): Instructions say "click your organization name, then Settings, then Create token" — verify this matches the current MotherDuck UI.
• Removed content: The LOCAL_ROOT environment variable info and /tmp/airbyte_local default path were removed. This info belongs in the DuckDB destination docs, not here. Confirm this is acceptable.

User Impact

Users of the MotherDuck destination will see clearer documentation that:

• Correctly describes MotherDuck as the primary use case (not DuckDB)
• Documents all three configuration fields including the previously undocumented schema field
• Shows accurate release dates in the changelog

No negative side effects expected — docs-only change.

Can this PR be safely reverted and rolled back?

• YES 💚
• NO ❌

---

Note: I am an AI assistant (Devin, requested by Andreas Krey (@apk)) and have proposed these documentation updates based on a review of the connector source code and third-party API documentation. Reviewers may merge, modify, or close this PR as they see fit.

Link to Devin session: https://app.devin.ai/sessions/6a5881de97f847f0ab53cd18a9f1b8a4

[devin-ai-integration]

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

• Address comments on this PR. Add '(aside)' to your comment to have me ignore it.
• Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

• Disable automatic comment and CI monitoring

[github-actions]

👋 Greetings, Airbyte Team Member!

Here are some helpful tips and reminders for your convenience.

💡 Show Tips and Tricks

PR Slash Commands

Airbyte Maintainers (that's you!) can execute the following slash commands on your PR:

• 🛠️ Quick Fixes
  • /format-fix - Fixes most formatting issues.
  • /bump-version - Bumps connector versions, scraping changelog description from the PR title.
• ❇️ AI Testing and Review (internal link: AI-SDLC Docs):
  • /ai-prove-fix - Runs prerelease readiness checks, including testing against customer connections.
  • /ai-canary-prerelease - Rolls out prerelease to 5-10 connections for canary testing.
  • /ai-review - AI-powered PR review for connector safety and quality gates.
• 🚀 Connector Releases:
  • /publish-connectors-prerelease - Publishes pre-release connector builds (tagged as {version}-preview.{git-sha}) for all modified connectors in the PR.
  • /bump-progressive-rollout-version - Bumps connector version with an RC suffix (2.16.10-rc.1) for progressive rollouts (enableProgressiveRollout: true).
    • Example: /bump-progressive-rollout-version changelog="Add new feature for progressive rollout"
• ☕️ JVM connectors:
  • /update-connector-cdk-version connector=<CONNECTOR_NAME> - Updates the specified connector to the latest CDK version.
    Example: /update-connector-cdk-version connector=destination-bigquery
• 🐍 Python connectors:
  • /poe connector source-example lock - Run the Poe lock task on the source-example connector, committing the results back to the branch.
  • /poe source example lock - Alias for /poe connector source-example lock.
  • /poe source example use-cdk-branch my/branch - Pin the source-example CDK reference to the branch name specified.
  • /poe source example use-cdk-latest - Update the source-example CDK dependency to the latest available version.
• ⚙️ Admin commands:
  • /force-merge reason="<REASON>" - Force merges the PR using admin privileges, bypassing CI checks. Requires a reason.
    Example: /force-merge reason="CI is flaky, tests pass locally"

📚 Show Repo Guidance

Helpful Resources

• Breaking Changes Guide - Breaking changes, migration guides, and upgrade deadlines
• Developing Connectors Locally
• Managing Connector Secrets
• On-Demand Regression Tests
• #connector-ci-issues
• #connector-publish-updates
• #connector-build-statuses

📝 Edit this welcome message.

[github-actions]

Deploy preview for airbyte-docs ready!

✅ Preview
https://airbyte-docs-inp6usmha-airbyte-growth.vercel.app

Built with commit 77ebf47.
This pull request is being automatically deployed with vercel-action