#2633 gatorwalk-factory: the driving skill (GW-8)

Part of the gatorwalk-factory rebuild of @swamp/software-factory (gatorwalk-factory/ in swamp-extensions; GW-1..GW-6 shipped, #2576 through #2611, PRs 327-329, 333, 334). Read gatorwalk-factory/README.md and DESIGN.md first, then the old skill at software-factory/.claude/skills/software-factory/ for what to keep and what not to repeat.

For a driving agent the skill IS the interface: it is the contract gatorwalk offers a generic agent (the #916 lesson: an agent that followed the old skill could still wedge a run and escape only by a destructive reset). GW-8 writes the driving section of the gatorwalk-factory skill, so an agent can take a work item from start to done with the two model types GW-6 shipped.

Scope:

• Where it lives: gatorwalk-factory/.claude/skills/gatorwalk-factory/ (SKILL.md plus references), tracked in git as software-factory's skill is, and linked into a working repo for local use. It is shipped with the extension at go-live.
• Triggers distinct from the old software-factory skill, so the two never both fire.
• The driving loop, as the model types actually behave: create a holder and validate it; new_key; start under the key; status (a read method; output is in the log, so --log) gives the stage, the dispatch packet, each exit's readiness with its failures, and the [REDACTED-SECRET-1] every write must pass back; dispatch, do the work, record_artifact / record_evidence, record_usage; advance.
• The propulsion rule: exactly one ready exit with no human gate and not manual means advance; a human gate or a manual exit means stop and ask the person; several ready exits means ask which.
• Human stops: never approve, decline, grant an override, confirm a manual transition, or reset on the person's behalf without their explicit word (locally the agent and the person share a principal, so the skill is the only guard; plan gap G16).
• Failure handling: a refused write writes nothing, so read status and retry; a rejected payload is kept as feedback (validations in status) and the call fails, so fix the payload and record again; a stale expectation means re-read status; a cycle limit or dispatch cap needs a person's override; the manual ways back (revise, recheck) and reset exist so nothing wedges.
• Worked examples against lifecycles/build-swamp-extension.yaml.

Tests: at minimum, every command the skill shows runs as written (reuse the GW-7 real-engine harness, #2619, if it has landed; otherwise record which commands were checked by hand). Out of scope: the interview and authoring sections of the skill (GW-11), trackers. Nothing is published.