Update existing documentation with behavior changes

Update existing documentation with behavior changes

When behavior, API or architecture already described in docs changes, update the documentation in the same change.

Inspect the relevant package's existing docs before deciding whether they need an update. Do not leave stale behavior or signatures for a follow-up. For a genuinely new subsystem, flag the documentation gap and offer to document it; do not invent documentation for nonexistent code. A trivial reversible edit need not produce new tests or documents without a meaningful reason. This reminder is limited to edited Flutter lib files whose nearest package already has a docs directory. It cannot determine from a single write event whether documentation was already updated.

Detection scope

This is a contextual review reminder, not proof of a violation. Explicit user instructions and applicable repository conventions take precedence.