{"version":"2.1.236","anchor":"query-handling-moved-out-of-the-repl-component","canonical_anchor":"query-handling-moved-out-of-the-repl-component","heading":"Query handling moved out of the REPL component","tier":"internal","area":"REPL","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.236\/e\/query-handling-moved-out-of-the-repl-component","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.236","markdown":"### Query handling moved out of the REPL component\n\nQuery setup moved out of the main session view into an engine object.\n\n**What**\n\nSeveral hundred lines of query and tool-context setup in the REPL were replaced by a single binding step that hands the session, registries and callbacks to an engine object, and the fleet view's state became a store with methods. No behaviour change was identified, but almost every fleet and REPL key binding now goes through the store.\n\n**Details**\n\n- Fleet state is read through a snapshot getter and changed through named calls such as `setGroupPickIdx`, `abandonRespawnAttempt`, `nextRespawnAttempt` and `closeResumePicker`.\n\n**Evidence**\n\n`abandonRespawnAttempt`\n\n- Area: REPL\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}