Feat/m3 optimizer and prism#1
Merged
Merged
Conversation
- WorkspaceApiKey.base_url and Migration progress/cost tracking fields, threaded through llm_context.py/settings.py for self-hosted endpoints. - packages/core/optimizer/: in-house prompt optimizer with two strategies selected by run_optimizer(strategy=...): "simple" (one-shot mutation + param/format sweep) and "prism" (our own implementation of PromptWizard's published mutate/critique/refine technique, built entirely on this engine's own provider-agnostic llm/client.py rather than depending on their package - see DEV_TRACKER.md for the full rationale). - 18 new tests (packages/core: 273 passed, 2 skipped overall). - DEV_TRACKER.md: detailed, phase-by-phase M0-M5 project status and M3 build plan for pickup at any point. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
scripts/setup.sh installs both Python packages, generates the BYOK encryption key, creates the DB via Alembic (not the API's own dev auto-create, which never stamps alembic_version and breaks a later `alembic upgrade head`), and installs the web app - verified against a truly fresh (no existing test.db) run. No Postgres/Docker required. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
…d into the app yet
So a developer picking this up cold (including future-me) has an unambiguous starting checklist and finish line: verify current test counts first, scope Phase 4 to strategy selection only (don't gold-plate with new per-migration tuning controls), and a concrete checklist of what "done" means before moving to Phase 4b. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Previous version only said to update TESTING.md. Now explicit about the full before-you-commit checklist: update DEV_TRACKER.md's status and current-state paragraph, keep this file's own status in sync, re-run tests, and leave a clear "where I left off" note - not just "what changed" but "what's next." Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Covers claiming a phase before starting it, which phases have real dependencies vs. can run in parallel (Phase 5 docs vs 4/4b code), how to resolve merge conflicts in this file without silently discarding someone else's completed work, and reiterating the never-push-without-go-ahead rule applies per session, not just per developer. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.