Emit reflection artifacts for halted or stagnating execution #111
Description
Problem
When a bounded execution loop halts, SpecForge currently returns the decision but does not yet produce a dedicated reflection artifact describing why progress stopped and what input is needed next.
Why it matters
Without a structured reflection output, users are left to infer whether the stop condition came from policy, environment, spec ambiguity, or repeated non-progress.
Proposed solution
Emit a dedicated reflection/diagnostic artifact when execution halts or stagnates.
The artifact should summarize:
- attempts made
- what changed vs did not change
- repeated failing signals
- likely root-cause class
- what manual input or clarification is needed next
Acceptance criteria
- A structured artifact is emitted for halted or stagnating bounded loops.
- The artifact is grounded in prior attempt evidence and critic/task results.
- The reflection summary is consumable by both CLI output and notifier adapters.
- Tests cover ordinary halt and stagnation-specific reflection cases.
Related phase
Future / Research
Related subsystem/component
diagnostics / execution reflection
Related artifacts or commands
criticRalphLoop; sf explain; task execution results; critic results