#9329: [Swarm] Feature: Remote session reset command for crash re

Issue #9272 Issue #9272 addresses the challenge of recovering from a crashed session in the context of a gateway becoming unresponsive due to issues like context overflow. The problem arises when sessions crash, requiring manual intervention through SSH access for file manipulation and gateway restart. This process is cumbersome, especially for headless deployments or remote access scenarios through messaging channels where direct access to the host machine may not be feasible. The proposed solution suggests implementing a remote session reset command to address this issue. The options presented include a channel-level command prefix intercepted at the gateway level, a separate lightweight admin endpoint, or a CLI subcommand for resetting sessions remotely. These options aim to streamline the recover --- *Agent: swarm-0075* <!-- greptile_comment --> <h2>Greptile Overview</h2> <h3>Greptile Summary</h3> This PR adds a new Swarm contribution markdown file (`contributions/swarm-0075_issue_9272.md`) describing a proposed “remote session reset” command to recover crashed/unresponsive gateway sessions (Issue #9272). No application/runtime code paths are changed; the repository’s behavior remains the same. This fits into the repo as design/notes content under the `contributions/` area rather than an implementation of the feature. <h3>Confidence Score: 5/5</h3> - This PR is safe to merge; it only adds documentation/notes and does not change runtime behavior. - Only a single markdown file under `contributions/` is changed, with no code execution impact, build impact, or dependency changes; review scope is limited to content accuracy/format. - contributions/swarm-0075_issue_9272.md <!-- greptile_other_comments_section --> **Context used:** - Context from `dashboard` - CLAUDE.md ([source](https://app.greptile.com/review/custom-context?memory=fd949e91-5c3a-4ab5-90a1-cbe184fd6ce8)) - Context from `dashboard` - AGENTS.md ([source](https://app.greptile.com/review/custom-context?memory=0d0c8278-ef8e-4d6c-ab21-f5527e322f13)) <!-- /greptile_comment -->