Skip to content

fix: include on_recall_mix in ACE and RLM DEFAULT_HOOK_ENTRY#25

Merged
timeleft-- merged 1 commit intomainfrom
fix/default-hook-entry-on-recall-mix
Mar 10, 2026
Merged

fix: include on_recall_mix in ACE and RLM DEFAULT_HOOK_ENTRY#25
timeleft-- merged 1 commit intomainfrom
fix/default-hook-entry-on-recall-mix

Conversation

@timeleft--
Copy link
Copy Markdown
Member

Summary

  • Add on_recall_mix to DEFAULT_HOOK_ENTRY["points"] in both fava_trails.protocols.ace and fava_trails.protocols.rlm
  • Both protocols already implement on_recall_mix (delegating to on_recall), but the CLI setup commands (fava-trails ace setup --write / fava-trails rlm setup --write) would generate config without it

Test plan

  • All 24 CLI tests pass (uv run pytest tests/test_cli.py -v)
  • Run fava-trails ace setup and verify output includes on_recall_mix
  • Run fava-trails rlm setup and verify output includes on_recall_mix

🤖 Generated with Claude Code

The on_recall_mix lifecycle hook was implemented in both protocols
(delegating to on_recall) but missing from their DEFAULT_HOOK_ENTRY
dicts. This meant `fava-trails ace setup --write` and
`fava-trails rlm setup --write` would generate config.yaml entries
without the on_recall_mix hook point, silently omitting cross-trail
recall reranking/sorting.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@timeleft-- timeleft-- merged commit d70f2af into main Mar 10, 2026
7 checks passed
@timeleft-- timeleft-- deleted the fix/default-hook-entry-on-recall-mix branch March 10, 2026 17:10
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