pacman

Require a concrete change explanation and explicit user approval before modifying a repository, then implement and verify the approved scope. Use whenever Codex is asked to create, edit, delete, generate, format, refactor, fix, upgrade, or otherwise mutate repository files, dependencies, configuration, tests, documentation, build artifacts, or version-control state.

Repository layout for the pacman Go PostgreSQL HA cluster manager.

Use when inspecting GitHub Actions, CI failures, failed Go tests, workflow logs, or build/lint/test errors. Avoid reading full logs; summarize failed jobs and inspect only relevant snippets.

Maintain PACMAN-native and Patroni-compatible API contracts.

PACMAN domain rules for cluster state transitions and operation history.

Rules for PACMAN control-plane quorum, leases, epochs, fencing, and split-brain prevention.

Minimal Go build, test, debug, and lint workflow for pacman.

PACMAN distributed-systems testing rules for Jepsen-style failures and invariants.

Kubernetes and operator design rules for PACMAN deployment topology and member behavior.

Rules for PACMAN node agent PostgreSQL observation, lifecycle actions, and state reporting.

PostgreSQL backup, WAL, recovery, and rejoin context for pacman.

Lightweight review checklist for Go HA and distributed-systems code.

Choose the smallest relevant pacman test set from changed files.