#2875 gatorwalk-factory: small driving fixes from the #2711 dogfood

Small driving fixes found in the gatorwalk dogfood run on #2711. Each is minor; together they removed guesswork for the driver.

1. post_attestation logs no id. The attest prompt says "record the id it logs", but the method logs only "posted the attestation for ". The id is only in swamp data get <adapter> attestation-<sha> (.content.id). Log the id, and say that a re-post wrote nothing.
2. The triage packet carries no issue text. The prompt says "Read the issue" but gives no binding or pointer. claim already stores the issue as issue-<n> on the adapter instance, so the triage prompt in swamp-club-swamp-extensions.yaml can name swamp data get <adapter> issue-{{issue}}, with issue bound from item.externalRefs.
3. status repeats itself.
   • Each triage exit prints the same failure twice ("evidence 'classification' has not been recorded"), because two gates read the same evidence. Show it once.
   • Every status call also prints an empty work-item-summary report banner. status is a read, so it should not run the report.
4. Approvals don't say who decided. Evidence takes onBehalfOf and the journal shows "user:skunk-ape for seth". approve, decline, grant_override, manual advance and reset are attributed to the agent's account alone. Accept onBehalfOf on them too, so the journal and summary name the person.
5. The docs don't show a Lab instance as a factory's tracker. Since #2795, the README and driving.md list tracker kinds as builtin | linear and show only the built-in tracker being bound. Add swamp-club and the --global-arg tracker=<lab instance> setup, and say the tracker is created before the factory.
6. init copies no saved scenarios. init --input from=swamp-club-swamp-extensions copied the definition, and validate then ran "0 saved scenario(s)", although the example has 18. Copy the starter's scenarios to scenarios/<factory>/ with their factory key rewritten, never overwriting an existing file.