v0.2.36

ADDED

• ▸dvt martin — Martin in your terminal, and it is literally the same agent as :46104: MARTIN'S WORK streams line by line as each tool finishes, answers arrive as markdown with the SQL and an aligned result table, and every proposal becomes an [a]pply / [d]ismiss prompt through the same file jail and verb whitelist as the web cards. /model lists your gateway's catalog, /plan and /execute switch modes, /errors diagnoses the last run, /sql runs the guarded no-AI lane, @file mentions are read by Martin's own jailed reader.
• ▸generate-sources --all (CLI) and ALL CONNECTIONS (the /generate-sources picker): one sweep across every database connection in the profile — one sources.yml per connection, a per-connection ledger with honest skips for buckets, and in the chat each connection lands as its own APPLY card, so nine successes are never hostage to one failure. -s/-x patterns apply across the sweep.
• ▸Martin manages the project — behind your click, as always: propose_scheduler_job puts a dvt command on a validated cron via the scheduler's own store; list_scheduler_jobs and job_history read the schedule; connection_health probes one connection read-only (engine, mapping, live metadata ping); and propose_run now covers the maintenance verbs (sync, docs generate, retract — proposed only on explicit request, described as the data-dropper it is). One hard line, by design: Martin never touches profiles.yml or credentials — connection setup lives in hub Settings.
• ▸The DVT mark in every app's topbar — catalog, api-portal, chat, profiling, scheduler, dashboards, hub — clickable, always one step from the hub. The reserved port range grows once to 46100–46119: the suite outgrew ten seats.