# Coordinator rules for the 2026-11-07 open-points waves (read together with agent-brief.md)

- You are one of several agents working in parallel on ~/projects/llamamod. Read notes/dev/agent-brief.md fully,
  INCLUDING the "EDITOR phase-3" merge rules – they apply to every agent in this wave, not only editor agents:
  own copy under $CLAUDE_JOB_DIR/tmp/<agent>/llamamod, a pristine baseline copy (<copy>.base via rsync), and at
  copy-back every shared file you changed is merged with `diff -u base copy | patch` onto the main tree's
  current version (never blindly overwrite a file another agent may have changed meanwhile).
- Do NOT commit (the coordinator commits after each package). Do not touch git in the main tree.
- Build in your own copy: `JAVA_HOME=/usr/lib/jvm/java-21-openjdk-amd64 ./gradlew spotlessApply build fatJar`.
  NEVER run gradle in ~/projects/llamamod itself (parallel builds clash in build/test-results). After copy-back,
  verify with a fresh snapshot: `rsync -a --exclude build --exclude .gradle --exclude re/proj --exclude out
  ~/projects/llamamod/ $CLAUDE_JOB_DIR/tmp/<agent>/snap/` and build/test there (then delete the snapshot).
  If it fails only because of another agent's half-merged change, wait a few minutes and retry. The coordinator
  runs the main-tree build.
- Every behaviour change needs a test (unit test where possible) and, for UI, a screenshot check on YOUR display;
  for game-side changes an in-game check with tools/apptest.py (your display, session names prefixed with your name).
- Keep user-facing texts English, short and plain. Update the relevant notes/*.md and, if users see the change,
  the manual (docs/manual) briefly.
- Out of scope for everyone: Windows hardware test, texture packs, German translation of the UI, a launcher
  manual/help window, a OneDrive warning, git remotes.
- At the end delete your copy's build/, .gradle/, the .base copy and your apptest session dirs (disk is tight).
- REPORT (final message, English, concise): what you changed (files), how verified (tests, screenshots paths),
  shared/framework files you touched, and a list "NEW ISSUES / NOT DONE" with anything you found but did not fix
  (the coordinator turns those into follow-up tasks).