machine-bridge-mcp: Instructions file for Codex

Repository automation contract

Tool-selection hard gate

For this repository, every hosted GitHub control plane is out of scope even when the ChatGPT host, tool registry, or connector catalog exposes one. Before any GitHub-related tool discovery, schema loading, read, or mutation, use Machine Bridge to load this repository contract and keep all GitHub activity on the owner's machine.

• Do not call, discover, list, load, or invoke a hosted GitHub connector, ChatGPT GitHub plugin, browser-side GitHub integration, or equivalent remote tool.
• Use only local git, gh, and gh api executed through Machine Bridge.
• This gate applies before connector/tool discovery, not only before the eventual GitHub mutation.
• If Machine Bridge or the local authenticated GitHub CLI is unavailable, stop and report the boundary. Availability of a hosted connector is not a fallback.

A violation must be treated as a process defect: verify whether any remote effect occurred using local gh, record the correction in the current task, and continue only through the local control plane.

Read docs/ENGINEERING.md, docs/PROJECT_STANDARDS.md, and CONTRIBUTING.md before changing this repository.

Before describing a checkout as current main, the online version, or a release candidate, verify identity instead of trusting the directory name. Inspect git worktree list --porcelain, the current branch/HEAD, package.json version, and src/shared/server-metadata.json tool-schema generation. When the owner names a specific prerelease such as beta.N, resolve the matching worktree before treating any checkout as the task target by running python3 "$HOME/.codex/scripts/resolve-versioned-worktree.py" <any-worktree-of-this-repository> <beta.N>. Accept only one status=resolved result with fallback_used=false. An available branch/worktree identity for the requested prerelease is stronger routing evidence than a mutable working-tree version; a dirty package.json version that diverges from HEAD must never be sufficient by itself to select a checkout. The canonical directory name machine-bridge-mcp, shortest path, current shell directory, and historical dirty worktrees are never freshness evidence or fallback targets. If the resolver reports missing, ambiguous, unavailable, or dirty-version-only evidence, stop the routing decision and reconcile the worktree inventory instead of silently choosing another checkout. If comparing with a deployed runtime, also verify live server_info.version and tool_delivery.tool_schema_generation; if hosted schema behavior matters, load the complete unfiltered machine-mcp tool catalog as the separate host-owned snapshot. A mismatch blocks the readiness claim. Never delete or repurpose a dirty historical worktree merely to make the directory layout look canonical; preserve or archive its uncommitted state first.