agents: one item only -- the title's animation timing -- and split work into human-checkable units

Two new findings from the human, both about WHEN a title animation starts, and
both handed over rather than guessed:

F5 Does (A) SNAP the title to finished, or ACCELERATE it? The human says they
   cannot tell and is right that they cannot -- a three-frame acceleration and a
   one-frame cut look identical to an eye. Two routes that should agree: a
   per-frame capture (acceleration shows intermediate alphas, a cut shows none)
   and the code (assigning a target time and raising a rate multiplier are
   different instructions). Their "looks more like a snap on multiple attempts"
   is recorded as a PRIOR, not a result.

F6 The title's sweeping white glow -- ptloop01/ptloop02, the blue PCB-like lines
   -- starts only when the plate appears in the real game, and starts earlier in
   the port. A lead from the exported declaration, mine and unverified: those
   elements are keyed at t = 0, 70, 100, 238, 250 while the plate reaches full
   alpha at 236, with pteff02 keyed at exactly 236 and ptlogo_back2eff and
   ptcopyright at 238. 236-238 is a synchronisation point in the declared data
   and a human just reported a behaviour change there. Flagged AGAINST itself
   too: 238...250 looks equally like an exit ramp -- ptcopyright uses that shape
   and starts nothing -- and the sweep lives in a nested .rat leaf with its own
   timeline.

F6 bears on clock: "shared" and on F4: if a title element does not move until
the plate arrives, either the declared data says so and our keyframe reading is
wrong, or something at the plate's arrival STARTS it, which is a mechanism
nobody has proposed.

And the process change, which is the human's and outlives this item:

  "attacking the 'whole' mission was too big for them to handle. Split the given
   missions and tasks into even smaller tasks which they can tackle and give to
   a human for feedback."

PROTOCOL.md gains "Work in units a human can check in a minute". A milestone is
not a unit of work, it is a bag of them. A unit is right-sized when it ends in
something a person can judge in under a minute WITHOUT READING ANYTHING, and
each one states its question, what the human looks at, and what it does NOT
cover. Do one, hand it over, stop -- an unverified fix under a second change
makes a regression two-variable.

The evidence for the rule is this week: the splash sat through a whole milestone
and took one day once scoped to "does it animate?". The bar is a HUMAN check,
not a green tool -- three instruments passed a frozen screen.

docs/agents/decoder-loop.md

@@ -1,6 +1,40 @@
 You are the **Decoder**. Answer the open questions the Godot menu port is
 blocked on, one at a time.
 
+## 🔴🔴 SOLE FOCUS, 2026-09-02: **THE TITLE'S ANIMATION TIMING — F5 and F6, nothing else**
+
+**Work only these two.** Not the pipeline, not the audio mix, not the repeat
+rate — they stay queued in
+[`PLAYTEST-2026-09-02-menus.md`](PLAYTEST-2026-09-02-menus.md).
+
+> *"Let's have the agents focus on this item and only this only."*
+
+**F6 first** — it is the one with a lead. A human reports that the title's
+sweeping white glow (**`ptloop01` / `ptloop02`**, the blue PCB-like lines) **only
+starts when the plate appears** in the real game, while the port starts it
+earlier. `title.json` declares those elements at `t = 0, 70, 100, 238, 250` and
+the plate reaches full alpha at **`t = 236`** — with `pteff02` keyed at exactly
+236 and `ptlogo_back2eff`/`ptcopyright` at 238. **236–238 is a synchronisation
+point in the declared data and a human just reported a behaviour change there.**
+⚠️ `238…250` may equally be an **exit ramp** (`ptcopyright` uses that shape and
+starts nothing), and the sweep lives in a nested `.rat` leaf with its own
+timeline. Establish which of the two the human is watching.
+
+**F5 second** — does Ⓐ **snap** the title to finished, or **accelerate** it? The
+human says they cannot tell, and is right that they cannot: a three-frame
+acceleration and a one-frame cut look identical to an eye. Two routes, and they
+should agree: a **per-frame capture** (an acceleration shows intermediate alphas,
+a cut shows none) and **the code** (assigning a target time and raising a rate
+multiplier are different instructions). Their *"looks more like a snap"* is a
+**prior, not a result** — say so if the measurement disagrees.
+
+### And split it before you start
+
+**Read the new "Work in units a human can check in a minute" section of
+[`PROTOCOL.md`](PROTOCOL.md).** The human's diagnosis is that whole missions have
+been too big to hold. Break even F6 down, write the question and the
+look-at-this-and-you-will-see before working, do one, hand it over, stop.
+
 ## ✅ THE LOGO SPLASHES ARE DONE — signed off by the human, 2026-09-02
 
 > *"Looks good! Cannot notice any obvious difference from the actual game.