docs: clarify milestone continuation instructions

Co-authored-by: D <code@dector.space>

Author: DCodeBot

TODO.md

@@ -12,6 +12,6 @@ Agent instructions:
 8. When presenting results or discussing implementation, treat the explanation as one of the most important deliverables. Do not give only a brief summary. Provide a very educational, insightful explanation with concrete examples. Cover what changed, why it exists, how it contributes to the final project goal, and how the relevant part of ADB/the code works. Explain the important protocol or code flow step by step, define project-specific terms when they first appear, include small usage or packet-flow examples where helpful, and connect the implementation to the tests so a reviewer can understand both behavior and intent. Assume the reviewer wants to learn the system, not just approve a diff.
 9. Use a Conventional Commit message matching the milestone.
 10. When an implemented milestone is ready for human review, commit it automatically using the milestone's Conventional Commit message. The human will review the resulting commit instead of reviewing uncommitted changes.
-11. After finishing and committing one milestone, briefly offer to continue with the next incomplete milestone.
+11. After finishing and committing one milestone, briefly identify the next incomplete milestone by number, title, status, commit message, and short purpose, then offer to continue. If there is no next active incomplete milestone, say that explicitly and mention whether only deferred milestones remain.
 
 This file is intentionally stateless. Do not track progress here; update progress only in `PLAN.md`.