/**
 * The index of the toolset, handed to the model at connect time.
 *
 * The client reads it once, on initialize, and puts it in the system prompt
 * before any call is made. It answers "which tool for which question" and the
 * few rules that hold for all of them; what each tool takes and returns lives
 * in the tool itself, so nothing is said twice.
 *
 * Every tool is named here on purpose: one missing from the index is one the
 * model will not choose.
 */
export declare const SERVER_INSTRUCTIONS = "SSH to configured machines. Every call names a profile; there is no default.\n\nCredentials \u2014 key, passphrase or password \u2014 live in the profiles and the server reads them\nitself, and so does the password sudo asks for where it asks for one.\nNever ask anyone for a secret; name the profile. When the person says \"the server\" without\nnaming one, ask ssh_monitor action:list for the names instead of guessing: two profiles can\npoint at the same address and differ only by name.\n\nOn a machine you have not touched yet: ssh_monitor action:test first \u2014 it names the\nstate (ready, limited, no-route, rejected) before anything else runs.\n\nWhich tool for which question:\n  run something          ssh_exec \u2014 for what has no tool of its own\n  slow work              ssh_exec detach:true, then ssh_job_status, ssh_job_output,\n                         ssh_job_list, ssh_job_kill\n  logs, any text search   ssh_log_search to look for something, ssh_log_tail to read the end;\n                          a container is read by name, container: \"web-1\"\n  files                   ssh_file_read to see inside, ssh_file_list to see what is there,\n                          ssh_file_write to put text there\n  move bytes              ssh_upload sends what is already on this machine, ssh_download fetches;\n                          text you can paste goes with ssh_file_write instead\n  how it is doing         ssh_snapshot \u2014 right now\n  how it is set up        ssh_audit_baseline \u2014 settings, not load; ssh_tls_check per domain\n  something is wrong      ssh_service_status for one unit, ssh_disk_breakdown for a full disk\n  the connection          ssh_monitor\n\nReach for the specific tool before ssh_exec: each batches round trips, parses the\nanswer, verifies what it wrote, or says it could not check \u2014 where exec returns a\nblank that reads as zero.\n\nA detached job is followed, not waited for: ssh_job_status names its state and shows the\nlast lines it wrote, so every look says how far the work got. Look again when the work\nwould have moved on. Never sleep on this side and never hold a call open to wait.\n\nAnswers put the outcome in structuredContent wherever a schema is declared, and its\nlegend explains the words it uses. Read the fields; the text holds the detail.\n\nSetup questions: ssh://profiles/current (what is configured here) and\nssh://profiles/example (the shape of the file).\n";