google-jules-mcp: Instructions file for Codex

🛸 AGENTS.md — Directives for Autonomous & Pair-Programming AI Agents

Context: This document is the primary machine-readable operational manifest for all AI coding agents (Google Jules, Antigravity, Cursor, Claude Code, Devin, and NovaNodes collective bots) operating within this repository.

---

🏛️ PART 1: NOVANODES CORE INVARIANTS (Universal Standard)

1. Strict Git Flow (ПРАВИЛА КРОВИ)

• 🛑 NEVER push directly to main or master branches.
• All changes (features, bugfixes, refactorings, documentation) MUST go through dedicated branch naming (feat/..., fix/..., refactor/..., docs/...) and a formal Pull Request (PR).
• NEVER merge PRs without explicit approval from ЗавЛаб.
• No Force-Push: Never rewrite public commit history (git push -f) on upstream branches.

2. Security & Credential Hygiene

• 🛑 Zero-Leakage Policy: NEVER hardcode API keys, tokens, passwords, or credentials into source code, unit tests, commit messages, or PR bodies.
• All secrets must be loaded dynamically from environment variables (e.g., os.Getenv("JULES_API_KEY")).
• Never echo or log secret values in command stdout/stderr.

3. Deadlock, Timeout & Process Safety

• Network Timeouts: Every outbound network call or HTTP client must configure explicit timeouts (default: 60s total, connection pooling with 90s idle timeout).
• Command Timeouts: When running auxiliary shell commands, always enforce hard timeouts (timeout -k 2s 15s ...) to prevent zombie processes.
• Stdio Redirection: When spawning background processes or smoke-testing MCP stdio servers, always redirect stdin (< /dev/null) to avoid terminal SIGTTIN hangs.
• No Infinite Polling: Never loop endlessly (while true: sleep(1)) waiting for external events. Use scheduled checks or event-driven wakeups.

4. Continuous Verification (No Blind Reports)

• Pre-PR Native Minimum: Never claim a task is complete without running the project's native test suite and linters locally.
• Verification without Absurdity: Use native project tools directly (go test, go vet, make); do not pull heavy emulator containers.
• Post-PR Cloud CI: After creating a PR, monitor the actual GitHub Actions CI (gh pr checks <id>). Do not report success until all cloud checks are green.