List the En Croissant game databases installed on this machine.

Reports each database's title, game count, size, and whether it has a .pgn sidecar. Read-only, and safe to call while En Croissant is running.

List the En Croissant repertoire files and which colour each trains.

Read one repertoire's tree: its main line, orientation, and size.

At every position, the FIRST variation listed is the move En Croissant drills; later variations are recorded alternatives.

Merge a line of SAN moves (from the starting position) into a repertoire.

Joins branches that already exist instead of duplicating them, and never reorders existing variations — the first variation at a position is the answer the user gets drilled on, so reordering would change what they're tested on. New positions are scheduled automatically when the file is next opened; existing cards and review history are untouched.

En Croissant must be closed: it holds repertoire files open and would silently overwrite this change. The previous contents are backed up first.

Read the FSRS training state for a repertoire: what's due, what's never been seen, and what the file would schedule that isn't in the deck yet.

Read-only — never modifies training state. Safe while En Croissant runs, though a session in progress there may not have flushed to disk yet.

Search the user's own rated Lichess games (blitz by default).

Filters are from the USER's side: colour is the colour they played, result is their result ('win', 'loss', 'draw'). Dates are 'YYYY.MM.DD'. Fetches live from the Lichess API, falling back to the local export.

The user's W/D/L record from a position, across their rated blitz games.

Position matching ignores move counters and non-capturable en-passant squares, so transpositions count. Sample sizes here are small — report them, and never rank or conclude from the percentage alone.

What gets played from a position: by players at the user's own rating and speed (source='lichess', the default) or by masters (source='masters').

Defaults come from config so the pool matches the user's actual games — blitz around their rating band, not the site-wide average. Cached locally; a repeated query makes no network call.