Autoloop: stop double-prefixing program-issue titles and dedupe scheduler discovery

[Copilot]

The create-issue safe-output's title-prefix: "[Autoloop] " was being applied on top of the agent-supplied [Autoloop: name] marker, producing titles like [Autoloop] [Autoloop: tsb-perf-evolve]. The scheduler then slugified that to autoloop-autoloop-tsb-perf-evolve, didn't recognise it as the file-based program, and scheduled the same program twice — two branches, two PRs, two state files, divergent populations.

Changes

• autoloop.md prompt (Fix 1, Option A) — at the two title-construction sites (program-issue creation and unconfigured-program setup-issue), instruct the agent to supply [Autoloop: {program-name}] exactly and not prepend [Autoloop] itself; the safe-output adds it.
• autoloop_scheduler.py (Fix 2) — new extract_program_name_from_issue_title() matches [Autoloop: name] while tolerating any number of leading [Autoloop] prefixes (case-insensitive). First-pass discovery uses it instead of the strict regex, so doubly-prefixed program issues already in the wild merge with their file-based program rather than forking a duplicate.
• autoloop_scheduler.py (Fix 3) — defensive module-level slugify() strips known [Autoloop] / [Autoloop: name] prefixes before slugifying. Used in the second-pass fallback for human-authored issues so even a stray doubly-prefixed title that doesn't match a known file-based program collapses to a clean slug instead of autoloop-autoloop-....
• .gitignore — ignore __pycache__/ and *.pyc.

Behaviour

title:  "[Autoloop] [Autoloop: tsb-perf-evolve]"
before: extract → no match → slugify → "autoloop-autoloop-tsb-perf-evolve"  → second program scheduled
after:  extract → "tsb-perf-evolve" → matches file-based program → selected_issue=189, single program

Out of scope

The repo cleanup called out in the issue (close PR #191, delete branch autoloop/autoloop-autoloop-tsb-perf-evolve, delete the stranded state file on memory/autoloop, rename issue #189) needs a maintainer — an agent can't perform those from a PR. Once these fixes land the next scheduler run merges #189 into the file-based program automatically, so the duplication stops compounding even before that cleanup happens.