Scope completion notifications to direct children

### Describe the feature or problem you'd like to solve

Orchestrating agents receive completion noise from their entire descendant tree, not just direct children

### Proposed solution

Completions should propagate one level: each agent receives signals only from its direct children. An orchestrator launching 8 sub-agents gets 8 completion signals regardless of how much nested work each spawns — keeping it focused on its own layer and reducing context noise from work it didn't directly delegate.

### Example prompts or workflows

1. An orchestrator runs 8 sub-agents, each using explore agents internally — it receives ~40–50 notifications today when 8 is all it needs.
2. A sub-agent runs shell commands; each completion fires a notification to the orchestrator even though it has no use for them.
3. Orchestrator → coordinators → workers: the orchestrator should hear from coordinators only, not from workers two levels down.

### Additional context

_No response_

El issue no identifica archivos, pruebas ni puntos de entrada. Empieza por localizar cómo se propagan las notificaciones de finalización a través de agentes anidados y, después, rastrea la relación padre-hijo utilizada para la entrega. Se considera terminado cuando cada agente recibe señales de finalización únicamente de sus hijos directos y los descendientes anidados dejan de producir notificaciones adicionales.

Escrito por el modelo de indexación a partir del texto del issue.