Notify users when execution halts, stagnates, or needs intervention

[iKwesi]

Problem

SpecForge can report review-request status and send notifier events, but it does not yet notify users specifically when a bounded execution loop halts, stagnates, or needs manual intervention.

Why it matters

If the engine detects that progress has stalled or that a human decision is needed, the user should hear about it explicitly instead of discovering it later by manually inspecting artifacts.

Proposed solution

Add notifier events and CLI reporting for halted, stagnating, or manual-intervention execution outcomes.

This should build on the existing notifier adapter boundary and support future channels, including the previously noted Vercel AI Channels direction.

Acceptance criteria

• Execution halt/stagnation outcomes produce notifier-friendly event payloads.
• CLI output clearly distinguishes ordinary completion from manual-intervention states.
• Notification emission remains isolated from the main execution decision path.
• The notifier design remains provider-agnostic and reusable across channels.

Related phase

Future / Research

Related subsystem/component

notifiers / execution UX

Related artifacts or commands

status notifiers; criticRalphLoop; future execution notifier events