remote-vibe-codinglisted

# Remote Vibe Coding Use this skill when a human wants an AI agent to work on a remote or managed host while preserving consent, host-local policy, interrupts, evidence, and revocation. ## Current MCP Boundary The MCP server exposes only the eight `rdev.sessions.*` tools documented in `docs/operations/MCP_STDIO.md`: `create`, `connect`, `status`, `events`, `task`, `interrupt`, `artifacts`, and `close`. Do not call legacy dotted names such as legacy support-session, invite, or connection-entry dotted names through MCP. Workflows that are not session tools are CLI-only and must use their corresponding `rdev ...` command. ## Non-Negotiables - Read before guessing: inspect existing source, contracts, schemas, docs, MCP tools, and host state before choosing commands. - Ask when unclear: for ambiguous or high-impact work, ask one human question at a time until the goal, constraints, authority, and success criteria are about 95% clear. - Keep reasoning disciplined but private: use requirement decomposition, multiple hypotheses, assumption checks, risk-scaled analysis, and progress tracking; share concise reasoning summaries, assumptions, confidence, and verification evidence instead of private internal reasoning. - Stay path/config neutral: never assume a checkout path, user home, temp directory, framework directory, gateway URL, repo id, workspace root, release artifact, ticket code, root key, or interrupt policy. Resolve values from the active Skillkit manif