Skip to content

fix(optimization): require explicit retrieval methods#77

Merged
drewstone merged 1 commit into
mainfrom
fix/explicit-retrieval-method
Jul 24, 2026
Merged

fix(optimization): require explicit retrieval methods#77
drewstone merged 1 commit into
mainfrom
fix/explicit-retrieval-method

Conversation

@drewstone

Copy link
Copy Markdown
Contributor

Summary

  • require a complete OptimizationMethod for retrieval optimization
  • remove implicit run-level finite-grid fallback and stale bounded result metadata
  • retain finite enumeration only as the explicitly supplied boundedRetrievalConfigMethod()
  • reject missing or malformed methods consistently across knowledge optimization APIs

Verification

  • pnpm test: 441 passed, 10 skipped
  • focused optimization tests: 25 passed
  • pnpm typecheck
  • pnpm lint: 176 files checked
  • pnpm build
  • pnpm verify:package

Upstream status

The revised official GEPA and SkillOpt factories are not yet published. npm latest is @tangle-network/agent-eval@0.123.8; this change depends only on the canonical OptimizationMethod contract.

@tangletools tangletools left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✅ Auto-approved drewstone PR — 88763bf3

This PR was opened by the trusted drewstone account.
The full PR reviewer audit still runs separately and will publish findings if it detects issues.

tangletools · auto-approval · reason: drewstone_author · 2026-07-24T01:46:53Z

@drewstone
drewstone merged commit 95ae682 into main Jul 24, 2026
1 check passed
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.

2 participants