chore(seed): consolidate requirements into pyproject.toml, bump to Python 3.13

[ktursunov]

What

Consolidate deploy/seed's Python dependencies into pyproject.toml and standardize the seeder on Python 3.13.

Changes

• pyproject.toml — add [build-system] (setuptools), [project] metadata with requires-python = ">=3.13", runtime deps in [project.dependencies] (PyMySQL, clickhouse-connect, unpinned dbt-clickhouse with its rationale preserved), dev tooling in [project.optional-dependencies].dev (mypy, ruff, types-PyMySQL), and [tool.setuptools] flat-layout packaging (top-level modules + generators/). Existing ruff/mypy config unchanged (already py313).
• Dockerfile — python:3.12-slim → python:3.13-slim; install via pip install . from pyproject.toml instead of pip install -r requirements.txt (single source of truth).
• README.md — dev setup now pip install -e '.[dev]'; dependency-location note and layout table updated.
• Removed requirements.txt and requirements-dev.txt. No references remain elsewhere in the repo.

Validation

• uv build --wheel succeeds: Requires-Python: >=3.13, runtime deps in core metadata, dev deps under extra == "dev", all 4 top-level modules + generators/ packaged correctly — validating the pip install . the Dockerfile now runs.
• Docker image build not run in this change; the packaging half of pip install . is validated by the wheel build.

Note

The previous Dockerfile comment claimed dbt-clickhouse was validated against 3.12 to match src/ingestion/tools/toolbox/Dockerfile. This image now moves to 3.13; if toolbox parity matters, that's a follow-up to confirm.

Summary by CodeRabbit

• Chores
  • Updated the seeding environment to Python 3.13.
  • Consolidated runtime and development dependency configuration in pyproject.toml.
  • Simplified container and local development setup to install the project directly.
  • Removed legacy requirements files and updated setup documentation accordingly.

[coderabbitai]

📝 Walkthrough

Walkthrough

The seed project now uses pyproject.toml for package metadata and dependencies, installs development extras in editable mode, and builds its container with Python 3.13 using pip install ..

Changes

Seed packaging migration

Layer / File(s)	Summary
Package metadata and development setup deploy/seed/pyproject.toml, deploy/seed/README.md	Defines setuptools metadata, runtime dependencies, development extras, and package discovery; updates local setup and layout documentation to use pyproject.toml.
Container build installation deploy/seed/Dockerfile	Updates the image to Python 3.13 and installs the packaged seed project from copied source files with pip install ..

Estimated code review effort: 3 (Moderate) | ~20 minutes

Possibly related PRs

• constructorfabric/insight#1758: Related deploy/seed Docker and dependency wiring changes.

Suggested reviewers: cyberantonz

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately summarizes the main changes: moving seed dependencies into pyproject.toml and updating the seeder to Python 3.13.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@deploy/seed/pyproject.toml`:
- Line 5: Add the required cf-studio-path configuration to the TOML project
settings in pyproject.toml, setting its value to .cf-studio as specified by the
coding guidelines.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 93812089-de5c-47ee-9eb6-0b6135569b25

📥 Commits

Reviewing files that changed from the base of the PR and between 635f834 and e9a076a.

📒 Files selected for processing (5)

• deploy/seed/Dockerfile
• deploy/seed/README.md
• deploy/seed/pyproject.toml
• deploy/seed/requirements-dev.txt
• deploy/seed/requirements.txt

💤 Files with no reviewable changes (2)

• deploy/seed/requirements.txt
• deploy/seed/requirements-dev.txt

[coderabbitai]

📐 Maintainability & Code Quality | 🟠 Major | ⚡ Quick win

Add cf-studio-path configuration.

As per coding guidelines, TOML configuration files must set cf-studio-path to .cf-studio.

🛠️ Proposed fix

 # package straight from here.
 
+cf-studio-path = ".cf-studio"
+
 [build-system]
 requires = ["setuptools>=61"]

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	# package straight from here.
	cf-studio-path = ".cf-studio"
	[build-system]
	requires = ["setuptools>=61"]

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@deploy/seed/pyproject.toml` at line 5, Add the required cf-studio-path
configuration to the TOML project settings in pyproject.toml, setting its value
to .cf-studio as specified by the coding guidelines.

Source: Coding guidelines