[Milestone 2] tycoon.yml schema + config singleton replacement

[JesuFemi-O]

Part of: #81

Mission

Evolve tycoon.yml to express runtimes: and metadata: sections. Replace the global config singleton with proper project-loading dependency injection at the command layer. This milestone is the foundation every downstream milestone builds on.

Current state

src/tycoon/config.py exports config = TycoonConfig(), a singleton constructed at import time. It is imported by 25+ production files. src/tycoon/project.py TycoonProject has no runtimes: or metadata: sections.

Definition of done

tycoon.yml can express runtimes: and metadata: sections. Ingestion-path commands receive project via load_project() call, not via from tycoon.config import config. The config.py singleton still exists for non-ingestion commands (not deleted in this milestone).

Tasks

• T2-1: Add runtimes: and metadata: to TycoonProject model #90 T2-1: Add runtimes: and metadata: to TycoonProject model
• T2-2: Schema migration helper #92 T2-2: Schema migration helper
• T2-3: Replace config singleton in ingestion commands with load_project() injection #94 T2-3: Replace config singleton in ingestion commands with load_project() injection
• T2-4: tycoon.yml version field enforcement #96 T2-4: tycoon.yml version field enforcement

[JesuFemi-O]

Jira ticket split — for the PM

Epic name: Project Config Schema v2

---

Task 1 of 2 — Extend tycoon.yml to support runtimes and metadata config

Suggested Jira summary: [Ingestion Rewrite] Add runtimes and metadata sections to tycoon.yml

What this delivers:
The project config file (tycoon.yml) gains two new optional sections: runtimes: (declares which ingestion engines are attached) and metadata: (declares where run history is stored). Existing project files load without any changes — the new sections simply default in.

Work included:

• Add runtimes: and metadata: fields to the project model with safe defaults
• Write a one-time migration helper that upgrades existing tycoon.yml files in place (preserves all existing fields and comments)
• Version field enforcement: if a project file is on an older schema version, show a warning and tell the user to run tycoon init --upgrade
• Add --upgrade flag to tycoon init

GitHub tasks covered: #90, #92, #96

Acceptance (plain English): An existing project opens without errors. tycoon init --upgrade adds the new sections. A project with version: "0.1.0" shows a warning on any command.

Dependencies: None — can be done in parallel with Milestone 1.

---

Task 2 of 2 — Remove global config singleton from ingestion commands

Suggested Jira summary: [Ingestion Rewrite] Replace global config singleton with load_project() in ingestion commands

What this delivers:
The four ingestion-path commands (sources, run-all, sync, explore) currently read config from a global variable set at startup. This makes them hard to test and means the project path is baked in at import time. This task makes each command load the project file itself when invoked.

Work included:

• Replace the module-level from tycoon.config import config import in sources.py, run_all.py, sync_cmd.py, explore.py with a local load_project() call inside each command function

GitHub tasks covered: #94

Acceptance (plain English): The test suite for sources passes without needing to mock a global variable. tycoon data sources list works correctly in a fresh directory with a valid tycoon.yml.

Dependencies: Task 1 must be merged first.