FabledScribe

The lesson editor now asks the question the create tool asks, while the
writer still has the situation in mind. It offers three answers:
- an instance of a rule, ticked from the rules the lesson resembles;
- "No rule fits", with a required reason;
- leave it open.

The rules are fetched before the save from a new GET
/api/lessons/rule-candidates. It runs the same rule_candidates search the
create door replies with, and passes "search unavailable" through as null,
apart from "nothing resembles it".

An edit sends an answer only when it changed. Re-sending the same rules
would re-stamp their judgments. Worse, a shared editor who cannot see the
owner's rule would reject it by sending a list without it. Leaving a linked
lesson open sends rule_ids=[], which is what clears the links.

"Leave it open" is not offered once "no rule fits" is on file: the server
has no way to take that answer back except by naming a rule. When "no rule
fits" completes a convergence group, the editor says so in a toast, since
the page it goes to does not recompute it.

Guards check that the payload uses the names both routes read, that the
three answers are offered, that the candidates route sits above the id route
and keeps null apart from [], and that the editor reuses .rule-chip.

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

2026-10-01 16:36:43 -04:00

public

refactor(ui): Phase 7 — strip chat/voice/journal/workspace/home surfaces

2026-05-27 15:14:00 -04:00

src

feat(lessons): the web editor records which rule a lesson is an instance of (milestone 440, #4658 )

2026-10-01 16:36:43 -04:00

.npmrc

Upgrade all major frontend dependencies

2026-03-09 21:30:55 -04:00

index.html

refactor: rename Fabled Assistant to Fabled Scribe