Publish dbt-core release

Problem

Dataface's open-source core runtime is not published as an installable package. External users cannot pip install it, there is no compatibility matrix documenting which dbt versions and database adapters are supported, and there are no changelog or release notes tracking what changed between versions. Without a proper release artifact, external adoption requires cloning the repo and manually resolving dependencies, which is a non-starter for production use.

Context

• External adoption requires a packaged release, compatibility story, and documented install path.
• The release must cover both artifact publication and operational expectations like supported dbt/adapters.
• Recent CLI/bootstrap work provides pieces of the user journey, but not a formal release contract.

Possible Solutions

• A - Publish a package quickly and defer compatibility and release docs: fastest, but risky for trust.
• B - Keep distribution source-only until the project is more mature: safer, but delays external validation.
• C - Recommended: ship a first formal release with packaging, compatibility matrix, install docs, and a repeatable release checklist.

Plan

1. Audit packaging readiness, dependency boundaries, and missing release metadata.
2. Define the supported version matrix for dbt, Python, and target adapters.
3. Publish a release candidate with docs, changelog, and install validation steps.
4. Convert the candidate process into a repeatable release playbook for future versions.

Implementation Progress

• Confirm scope and acceptance with milestone owner.

• Milestone readiness signal is updated.

• Track blockers and mitigation owner.

Review Feedback

• [ ] Review cleared