dirextalk-deployer: Instructions file for Codex

AGENTS.md

dirextalk-deployer is a cross-platform deployment product and agent skill, not a Linux-only script collection. Maintain it as a portable orchestration layer driven by Git Bash on native Windows and Bash on Linux/macOS/WSL while deploying a Linux-based Dirextalk server.

Development

• This vNext repository is being built from zero. Implement the best target contract directly. Do not retain historical-version compatibility code.
• Do not add dual paths, version negotiation, compatibility shims, or fallback branches for superseded designs. Replace the old contract and migrate test or development data directly; a frozen external boundary requires an explicit product decision, not a second production path.
• Prioritize core product behavior and real device/node evidence. Do not add anti-counterfeit or exhaustive adversarial-observer machinery beyond the required release provenance unless a concrete product threat or gate needs it.
• Review the final production path strictly; model and fixture tests do not substitute for executable integration evidence.

Product Scope

• Deploy, resume, verify, destroy, and locally wire a production Dirextalk message server.
• Install the independently released YingSuiAI/dirextalk-updater host binary from the deployer-owned immutable version/commit/SHA pin. The deployer does not embed or build updater Go source.
• Own the production split Compose topology, host lifecycle and image-update wrappers under scripts/cloud-init/split/runtime, together with their operational tests and canonical bundle. Message Server and Agent repositories own only their application image builds and formal version-tag publication.
• Fresh deployment installs the updater control plane with its resident watchdog disabled. Direct-version upgrades are client initiated; do not reintroduce the retired daily updater GitHub discovery timer or service.
• Treat SKILL.md as the compact agent-facing entrypoint. Detailed runbooks belong in references/; scripts/ are the stable implementation entrypoints.
• SKILL.md is a user-facing runbook that must remain usable by less capable models. Its Freshness Gate, step-by-step onboarding, semantic confirmation policy, AWS promotional/billing reminders, and repeated safety guidance are intentional product behavior; preserve them unless the product owner explicitly changes that onboarding contract.
• The supported local conversation bridge is dirextalk-connect, installed from dirextalk-connect@latest by default or built from YingSuiAI/dirextalk-connect.
• MCP support is capability-driven and is separate from bridge-agent support. Declared MCP consumers connect directly to the deployed message server's HTTP endpoint; unknown runtimes never receive a generic fallback.
• Supported local agent targets are the dirextalk-connect agent providers, treated as peers: acp, antigravity, claudecode, codex, copilot, cursor, devin, gemini, iflow, kimi, opencode, pi, qoder, reasonix, and tmux.
• Do not reintroduce legacy local gateway installation flows or third-party chat platform wiring.
• Do not hard-code one developer's home directory, shell, agent executable path, AWS region, domain, node id, token, or password.