Decide the next step for each pull request

A pull request can take several paths. A docs-only change can merge at once. A code change needs a review. A red build needs a fix. A pending build means the agent waits.

In Rein, the first decision asks one question: does this change touch only documentation? Each answer leads to a different next step. The agent answers from what it sees in the pull request.

CI status is a fixed set of options. Each option gets its own case. If the team adds a new status, the checker reports the gap until someone writes what the agent does next.

Security-sensitive changes can move to a review step with a stricter focus. Pointers keep each rule in its own file, so one rule can change without touching the others.