Run a three-issue legacy migration pilot

User authorized testing a few real old issues through the isolated migration worker. Select three ordinary open General issues from prk/issues, preserve original issue state/body/comments, prepare stable bounded import payloads with attribution/source URLs and historical discussion treated as untrusted source context. Keep attachment URLs as historical links only; no evidence download/upload is implied by the text-only import endpoint. Pilot completed for exactly #3061 gelid eremites at elysium portal not killable (0 comments), #3034 Jon Solare disappears too quickly (2 comments), #3016 Cama Garden Key quests has no description (1 comment; attachment URL and related #2758). Complete original text/comments preserved with attribution; relative attachment URL made absolute, no truncation or attachment downloads. Stable payload checksums/lengths validated; identical second import returned the same reportId with created=false for all three. Durable mappings and verified results: - prk/issues#3061 → report f47ae3b7-41fb-46f7-6597-585044216e6b → intake #105 → known issue #4: https://git.project-rk.com/prk/player-known-issues/issues/4 (Gelid Eremites near the Elysium portal cannot be engaged reliably). - prk/issues#3034 → report 4bc76128-9593-f1a4-a292-4c3b89b1a0c2 → intake #106 → known issue #5: https://git.project-rk.com/prk/player-known-issues/issues/5 (Jon Solare despawns moments after quest combat begins). - prk/issues#3016 → report 064eb0ad-36a3-ce0a-45f1-232e1850169f → intake #107 → known issue #6: https://git.project-rk.com/prk/player-known-issues/issues/6 (Cama Garden Key quest entries lack instructions). All three previewed in migration and returned 204 when targeted via default lane, before any model claim. Ran exactly one controller invocation with isolated temporary config containing only these reportIds/maxBatch=3. Exit0, processed3, all known/proposal-accepted. Analyzer logs show exactly those three IDs and no technical failures. Every intake now has triage:complete and exactly one audit; each known issue has portal:published and exactly one source-correlated publication manifest. Proposals are sanitized structured bug reports with code references and qualified investigation paths, not demonstrated runtime root causes. No duplicate target was safely offered for the historical #2758 mention. Refetched complete source issue JSON after processing and compared exactly with saved originals: all three unchanged (including state, title, body, labels and comments). Normal worker configuration/token/auth hashes remain unchanged and auth/token mounts are isolated. Normal analyzer container changed concurrently because the normal deployment completed merged main 2d6948a; its image matches /var/lib/prk-reporting-deploy/state.json and health passes. This is a verified routine rollout, not a pilot-issued normal-worker restart. Migration timer absent; only analyzer remains running. Artifacts: ignored private local /home/mathias/Projects/engines/.dev-data/reporting-migration-pilot/2026-10-23 (source snapshots, stable payloads/checksums, intake/known issue JSON, outcomes); remote /srv/prk-reporting-migration/pilots/2026-10-23 (same originals/payloads, imports.json, preview snapshots, temporary secret-bearing worker.json mode0600 UID1000, worker.log, worker-exit.json, verification.json, outcomes.json). Do not expose private payload/config contents in repository/PRs. No code changes; git working tree clean. Limitation: publication was verified through the real intake/developer trackers and their owned manifests/labels, not by logging into the portal or directly querying its cached catalogue projection. Logged-in portal rendering was not browser-tested. All analyses used the existing read-only production source snapshot; no new code snapshot was prepared during this pilot. No broader backlog migration or recurring schedule was enabled. Acceptance: import exactly three stable payloads idempotently, target only returned migration report IDs, verify real model outcomes and downstream intake/developer/publication or review states, preserve duplicates/privacy policies and avoid claiming other backlog/player work. Originals remain unchanged, normal worker unchanged, no recurring scheduler. Save private source/payload/result manifests outside committed repository artifacts. On provider/technical failure retain durable IDs/leases and investigate, do not blind-retry imports or rerun model work. Do not expand beyond pilot without user request.