Skip to content

feat(0.42.0)!: gepaDriver + delete legacy orchestration subsystem#103

Merged
drewstone merged 1 commit into
mainfrom
feat/delete-legacy-orchestration
May 25, 2026
Merged

feat(0.42.0)!: gepaDriver + delete legacy orchestration subsystem#103
drewstone merged 1 commit into
mainfrom
feat/delete-legacy-orchestration

Conversation

@drewstone
Copy link
Copy Markdown
Contributor

Summary

BREAKING. Removes the legacy optimization orchestration from the public API so no consumer — or agent reading the substrate — can adopt it; the campaign API (runCampaign / runImprovementLoop / defaultProductionGate / drivers) fully supersedes it.

Deleted (~5,700 LOC, 12 source files)

runProductionLoop, runPromptEvolution, runMultiShotOptimization + the MultiShot* / EvolvableVariant / MutateAdapter adapters, the mutators (code/composite/traced), optimization.ts (+ the ./optimization subpath export), trial-aggregator, jsonl-trial-cache, integration-gates, evolution-telemetry, and the rl/auto-research legacy glue.

Kept (shared primitives — not legacy)

reflective-mutation, llm-client, LabeledScenarioStore, multi-layer-verifier, release-confidence (re-homed ActionableSideInfo/AsiSeverity that had lived in the deleted multishot file).

Added — gepaDriver

A campaign-native reflective ImprovementDriver (sibling to evolutionaryDriver). Surface-agnostic: any string surface in any consumer opts into best-in-class reflective prompt optimization — system prompts, addenda, judge/reviewer prompts, driver prompts — grounded on the 0.41.0 per-candidate dimensional + per-scenario evidence. Built on the kept reflection primitive; zero dependency on the deleted orchestration.

Replaced — RL bridge is now campaign-native

rl/run-record-adapters exposes campaignToRunRecords (CampaignResult cells → RunRecord[]) so the RL bridge consumes campaign output directly. Dropped the TrialResult/VariantAggregate adapters + the analyzeOptimizationResult glue.

Migration for consumers

On bump to 0.42.0, anything importing the removed symbols breaks — that's the forcing function. Replace with the campaign surface-registry pattern (see gtm-agent/creative-agent eval/self-improve.ts). Pinned consumers on 0.41.0 are unaffected until they bump.

Test plan

  • typecheck 0 errors, build green, full suite 1370 pass
  • new gepaDriver + campaignToRunRecords regression tests
  • cascade was tiny (release-confidence + reporting) — confirms legacy was cleanly separable

Version-lock bump 0.41.0 → 0.42.0 (npm + pyproject + python client).

BREAKING: remove the legacy optimization orchestration from the public API so
no consumer (or agent reading the substrate) can adopt it — the campaign API
(runCampaign / runImprovementLoop / defaultProductionGate / drivers) fully
supersedes it. Deleted: runProductionLoop, runPromptEvolution,
runMultiShotOptimization + MultiShot*/EvolvableVariant/MutateAdapter adapters,
the mutators (code/composite/traced), optimization.ts (+ the ./optimization
subpath), trial-aggregator, jsonl-trial-cache, integration-gates,
evolution-telemetry, and the rl/auto-research legacy glue — 12 source files,
~5,700 LOC.

KEPT (shared primitives, not legacy): reflective-mutation, llm-client,
LabeledScenarioStore, release-confidence (re-homed ActionableSideInfo/AsiSeverity
that lived in the deleted multishot file), multi-layer-verifier.

ADD gepaDriver — a campaign-native reflective ImprovementDriver (sibling to
evolutionaryDriver). Surface-agnostic: any string surface in any consumer opts
into best-in-class reflective prompt optimization, grounded on the 0.41.0
per-candidate dimensional + per-scenario evidence. Built on the kept
reflection primitive; zero dependency on the deleted orchestration.

REPLACE the legacy RL glue with a campaign-native path: rl/run-record-adapters
now exposes campaignToRunRecords (CampaignResult cells -> RunRecord[]) so the
RL bridge consumes campaign output directly; dropped trial/variantAggregate
adapters. Full suite green (1370).
@drewstone drewstone merged commit 85284bd into main May 25, 2026
1 check passed
@drewstone drewstone deleted the feat/delete-legacy-orchestration branch May 25, 2026 23:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant