prts-mcp: Instructions file for Codex

Codex Instructions for PRTS-MCP

1. Branch Model

Never push directly to any long-lived branch. Create a topic branch (<type>/v<version>-<topic>) from the appropriate base branch and open a Pull Request. Human maintainers perform all merges. When porting fixes from lts/2.8 or lts/1.7 to 3.x, reimplement them in Rust on develop — never merge a legacy branch into develop.

2. Startup Reads

Before making non-trivial changes, consult the authoritative guides:

• CLAUDE.md and docs/dev/STYLE.md — collaboration rules, module architecture, Rust conventions, and known pitfalls.
• docs/dev/DOCUMENTING.md — required standards whenever writing, editing, or reviewing public documentation.
• docs/dev/WORKFLOW.md and docs/dev/VERSIONING.md — PR grading, dual-track code review, minimum verification matrix, and SemVer compatibility promises.
• docs/dev/LTS.md — maintenance scope and release rules for lts/2.8 and lts/1.7.
• STATUS.md and ROADMAP.md — current release state, 3.0 migration milestones, and post-3.0 backlog.
• docs/glossary.md — project terminology and abbreviations (single entry point for definitions).
• docs/dev/adr/ — architecture decision records (numbered, status-tracked) since 3.1; consult before revisiting settled decisions.

Documentation task assignment: GPT-family models should focus on fact-based review and small, evidence-backed corrections that preserve the existing writing style. Assign new-document drafting, substantial rewrites, large-scale translation, and prose refinement to a human maintainer or a maintainer-designated non-GPT model. This applies to both primary agents and subagents. Follow docs/dev/DOCUMENTING.md; explicit task-specific authorization takes precedence.