Contributor coordination

This issue is the shared coordination noticeboard for matching work in this
repository: it exists so that contributors and their AI agents do not
duplicate each other's work.

It is a lightweight noticeboard only — not a task queue, campaign register,
reservation database, match proof, or a source of truth for completed work. The
repository and master remain authoritative.

The walls met while matching are tracked separately, in the
wall register.

Every active contributor keeps one comment

Each contributor working on the project must have exactly one persistent
comment below.

• If you are beginning work and do not already have your own comment here,
  create one before starting matching work.
• Edit your own comment in place as your scope changes. Do not create a new
  comment every time work changes, and do not modify another contributor's
  comment.
• List only your own current reservations. Do not copy other contributors'
  reservations, add lists of scopes you promise not to touch, or describe
  another contributor's scope as still reserved. Those copies become stale
  when its owner finishes or releases the work.
• Before choosing work, check the other contributors' current comments for
  overlap. Each contributor's own comment is the reference for that
  contributor's active reservations; another person's comment does not reserve
  work on their behalf.
• AI agents acting on behalf of a contributor must verify that their
  contributor has a coordination comment before beginning or assigning
  matching work. If no comment exists, create one before continuing.

Scope-first claims

Coordination uses scopes whenever possible — one level module, one
authored body file, one compiler profile, or a related group of bodies that
share the same retail bytes:

owner: <name>
updated: <ISO 8601 timestamp>

scope:
  - LEVEL_05.REL
  - src/levels/bodies/LEVEL_01_122D10.c

A body is one distinct retail body. It counts once, whatever the number of
placements it carries: the 416-byte Quat_Slerp body is one body at twenty
placements, and the placement count is the placement count.

Individual bodies are a fallback when a scope cannot be expressed.

Claims stay active until the work reaches master or their owner explicitly
releases them in their own comment. Reservation and queue state is not
committed to the repository.

The full workflow is in AGENTS.md.