workflow-e2e-fixlisted

# workflow-e2e-fix Counterpart of `workflow-e2e-author` for the fix lane. Address the coverage gate's findings on a slice's authored E2E specs. Scope is read from the most recent coverage-gate review comment on the slice (newer than the slice branch's last `Refs #<slice#>` commit). No label drives this — the calling workflow holds the slice lock and re-gates after the fix. ## When to activate Activate this skill whenever: - The dispatch prompt opens with `Fix E2E coverage feedback on slice #<n>`. - The user types `/workflow-e2e-fix`, or phrases like "address the E2E coverage findings on slice #<n>". Do NOT activate to author fresh E2E specs (use `workflow-e2e-author`), or to fix production code (engineer's lane via `workflow-engineer-fix-slice`). ## Input contract Read the slice issue #<n> body. Locate the task block(s) in the `## Tasks` checklist (each entry is a header `[ ] \`<id>\` · **<type>** · blocked-by <ids|—>`, the delivery on the next line, a `covers:` + `contract:`/`entry-source:`/`done:` pointer line, then `scenario:` and a fenced ```gherkin block of named Scenarios). The checklist is the durable task ledger — a box already checked `[x]` means that task is DONE. Read the slice's Acceptance criteria (EARS) and each e2e task's own `scenario:` Gherkin for the behavior the specs must cover; follow each e2e task's `scenario:` Gherkin for the unit spec. ## Workflow ### 1. Read the slice body Fetch the slice issue (number, title, body, labels, url) via `bash sk