FabledGrimoire

build_prompt_rule_hint, build_tool_rule_hint and build_write_path_hint
each ran the rule arm and then the via-lesson step by hand, the first two
passing the query between them through a _via_query key on the payload.
They now call one composer, _rule_moment, and the split helpers
(_prompt_rule_hint, _tool_rule_hint, _add_rules_via_lessons) and the side
channel are deleted. Output shapes are unchanged: the prompt builder
returns no checkpoint key, the tool builder always does, and
shown_rule_ids stays the direct band.

A structural test pins that only _rule_moment runs a rule arm or the
via-lesson step, and that the three builders are its only callers.

plugin_context.py: 2,418 -> 2,361 lines this step; 3,558 when the
milestone began.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

2026-10-05 20:25:47 -04:00

mcp

feat(moments): a mount that keeps arriving where it does not apply proposes its own removal (milestone 458 step 7b, #4955 )

2026-10-05 18:19:59 -04:00

models

feat(moments): a mount that keeps arriving where it does not apply proposes its own removal (milestone 458 step 7b, #4955 )

2026-10-05 18:19:59 -04:00

routes

feat(moments): mount the corpus by proposal - a pass and an open-after-moment signal, both stopping at the operator (milestone 458 step 7, #4925 )

2026-10-05 16:03:53 -04:00

services

refactor(retrieval): the rule builders compose one moment - _rule_moment runs the arm and its via-lesson step for all three (milestone 456 step 6, #4908 )