[its-janghoon]

What's done

• apps/redrob-query/src/app_bridge.rs: the Redrob Code app bridge. redrob-app-bridge is started on its own thread once the egui context exists and registers as app:query; a daemon that cannot be reached is logged and the app runs without it. Handlers run on the bridge's threads and push BridgeRequests onto a channel, ask for a repaint and block on the reply (30 s). QueryApp::serve_bridge drains the queue once per frame (after the panels polled) and runs each request against the real app state through the same ProfilesPanel / Workspace / tab functions the UI uses; engine Pending answers are polled on the following frames and replied to the moment they land, so the UI thread never waits on a database.
• Tools: list_connections (id, name, driver, connected), connect {id} (id or name; answers once the profiles panel reports it up, so the schema tree and the query tab open as if clicked), list_tables {connection?, schema?}, describe_table {connection?, table} (roots then columns, schema.table accepted, ambiguous names refused with candidates), run_sql {connection?, sql, max_rows?} (TSV header + rows, default 200, max 10 000, summary line with count / ms / "more rows exist" / rows affected; the status line notes the run), open_in_editor {sql, connection?} (new tab bound to the given or active connection, or an unbound tab), export_result {path, format: csv|tsv} (last run_sql page, else the active tab's grid).
• app.rs: the bridge field, Bridge::start in new, serve_bridge() after poll() in ui(), bridge.stop() in on_exit, and pub(crate) on the fields and helpers (workspace, profiles, tabs, active, tab_counter, notify, active_profile, push_tab, open_tab_for) the bridge module shares. main.rs: mod app_bridge. Cargo.toml: the git dependency (branch feat/channels-app-bridge, TODO pin to the release tag).
• README.md / README.ko.md: "Control from Redrob Code" / "Redrob Code에서 조작" sections listing the tools.

What's not done

• No cargo run of any kind (per the stage rules; the one build is the release). rustfmt was run on the touched files only.
• run_sql does not run writes. The engine's execute_query admits exactly one read-only statement (is_single_read_only_statement) and the Workspace exposes no arbitrary-mutation path (prepare_mutation / apply_mutation are on DataService, which the shell cannot reach); the README's "No free-form write SQL" boundary stands. A write reaches the agent as the engine's own ReadOnlyViolation text. Lifting that needs a core change outside this piece's file scope.
• Cargo.lock untouched; the release build resolves the git dependency.
• No history entry for bridged runs (the history list is per tab); the status line reports them instead.

What to review

• app_bridge.rs bridge_advance: the connect job resolves from ProfilesPanel::is_connected / is_connecting rather than holding its own Pending, so the panel's Connected event path (schema load, tab open) stays the single one.
• The MetadataStep continuation (describe_table is two loads in a row) and that step.then is a FnOnce with explicit &Workspace parameter types for the higher-ranked bound.
• page_as_delimited escaping: TSV escapes tabs / newlines inside a field, CSV quotes per RFC 4180.
• Thread safety of the handler closure: it captures a Sender<BridgeRequest> and an egui::Context only.

Intentions

Let the Redrob Code agent drive Redrob Query from any surface with the same bounds the UI has, without a mock or an unimplemented tool, and without putting the egui state behind a mutex.