#3885 Skill propulsion rule is silent when no transition is satisfied because stage work is outstanding

The driving skill (SKILL.md step 4, references/driving.md 'Propulsion rules') defines what to do once transitions are satisfied: advance if exactly one, stop at a human-approval gate, ask if several. It does not say what to do when NO transition is satisfied because the current stage's own work is outstanding (e.g. a rework re-entry into a dispatch stage whose artifacts are stale: 'recorded in cycle 1, not during the current entry'). An agent can read the silence as a reason to stop and report status, although no human gate or other stop condition applies.

Observed: after design-review sent a run back to design (cycle 2), the agent stopped to give status instead of doing the stage work, record_dispatch and re-recording the artifacts. Nothing in the skill required a stop.

Suggested fix: add to the propulsion rules an explicit statement that entering or re-entering a stage with a work block means do the work (record_dispatch, perform, re-record), and enumerate the only stop conditions: human-approval gate as sole blocker, several satisfied transitions, cycleLimitBlocked, runaway-loop-suspected. Also state when gate-state reporting happens (end of drive vs each cycle). Version: @swamp/software-factory 2026.10.13.1.

Upstream repository: https://github.com/swamp-club/swamp-extensions

Environment

• Extension: @swamp/software-factory@2026.10.13.1
• swamp: 20261021.155838.0-sha.f979f7c1
• OS: linux (x86_64)
• Deno: 2.9.7
• Shell: /bin/bash