Import all open legacy issues and run continuous migration

Closure: user confirmed production deployment and accepted closure. Historical progress and validation notes below are retained; no fresh queue-drain measurement or independently rerun checks are claimed. User explicitly authorizes importing all currently open issues from prk/issues and continuously processing the migration lane, waiting10 minutes on provider failures. Leave closed issues and legacy originals unchanged. Do not add CD or mix normal worker credentials/queue. Fixed snapshot scope must be recorded, with complete private source archive and stable per-source payload/result manifests. Historical comments are untrusted context, not staff authority; attachment URLs retained as source links, not copied/validated files. Reuse current isolated prk-reporting-migration worker and coordinator capability. Continuous service already prepared/inactive at merged worker b3aa84c, coordinator workflow_v0.1.4. Existing pilot sources3061/3034/3016 already imported and completed; reuse their exact stored payloads to avoid409 and never retriage automatically. Fixed snapshot enumerated at2026-10-23T18:46:05Z contains628 open issues (IDs355–3589), with full raw issue/comment JSON archived. Final preparation covers all628 with no unresolved exceptions; source discussion and751 attachment source URLs retained, no files downloaded. Eight reports (355,524,614,1705,1864,2471,3187,3278) use explicitly labelled historical continuation blocks across fields, verified to preserve the complete text without loss. #2383 NT feedback thread is about40KB, larger than all report fields combined: prepared a clearly labelled faithful summary of the invitation and all16 attributed comments; full verbatim source, equipment export, tables and attachment metadata remain in the unchanged source and private archive. Summary covers competing opinions and unverified comparisons, not confirmed defects. Three pilot payloads reused byte-for-byte to avoid conflict/retriage. Every final payload/source SHA256, UTF16 field length, request size/control/reference syntax checked. No silent truncation or overwriting conflict payloads. Import retries must be idempotent with exact bytes, and any already-imported changed-content409 needs local investigation rather than overwrite. Bound import rate and use normal coordinator delivery scheduling; no per-row ticks. Private local snapshot/helpers: /home/mathias/Projects/engines/.dev-data/reporting-migration-bulk/2026-10-23; transferred checksum-verified archive to git-prk-server under /srv/prk-reporting-migration/imports/2026-10-23. Final manifest prepared.json records per-source payload/source SHA256, summary/continuation methods and pilot identity. All originals remain outside committed artifacts; no repository edits. Import is running via prk-legacy-issue-import.service, a finite fixed-snapshot job, one POST per second, per-row atomic import-state.json checkpoints and deterministic source-to-Guid validation. Exact-byte retries on HTTP429/5xx/connection trouble wait600seconds, survive service restart;400/409/413 are explicit per-source exceptions, not overwrites. Readiness/capabilities checked before importing and periodically. Service restart-on-failure600s and boot enable support interrupted jobs; disable finite import unit after completion. No per-row ticks or CD added. Continuous migration worker started and boot-enabled through prk-reporting-migration.service after capability preflight. Preserved main b3aa84c, lane=migration, maxBatch4, isolated auth/token/project and600s provider cooldown. Type=simple/TimeoutStartSec0; added restart-on-failure600s (no timer/CD). Service backup at /srv/prk-reporting-migration/service-before-bulk-import. Queue initially idle; imported rows are delivered and analyzed through normal shared-stage bounds (ten default first, at most two migration per pass). Import phase completed at2026-10-23T19:12:10Z:628/628 imported,625 new plus3 existing pilot IDs, zero exceptions; durable full source/report mapping preserved in import-state.json. Finite importer boot-start disabled after completion. Processing is now deliberately stopped/disabled following user report of stock-client legacy bugs misclassified as Spiritech. Normal pipeline untouched. Follow-up tsk_sycuafuq3m owns containment/preventive fix/repair:10 misplaced Spiritech canonicals withdrawn/closed,11 imported reports restored toGeneral,5 already-General wrong-client citations queued for retriage. All corrections preserve originals/audits. A persistent pause marker prevents manual migration starts; no migration containers running. Saved provider cooldown belongs to source1305 and must be retained. Authoritative legacy-client routing guards are now deployed and live-verified; continuous isolated migration resumed on worker5c0a8d4/coordinator workflow_v0.1.6 with v6 stock context. Source509 and source524 are verified completed General canaries; source524 now owns published General known#56 while retired Spiritech#84 remains closed/hidden. No open Spiritech canonical is owned by any bulk import at resumption check. Stale pre-repair provider retry for source1305 was archived only after repeated v6 eligibility and exact old-token409 proof; it remains queued for fresh processing. Service active+enabled; no timer/CD. Task returns to in_progress for ongoing model processing. Do not claim all628 analyzed; import completion and model processing are separate. Continue monitoring controller/provider-paused events, General publications and any blocked technical failures until migration lane drains. On remote SSH/auth/connectivity/timeout trouble stop and ask rather than switching credentials or rerunning unknown remote work. Acceptance: fixed open-source scope archived, stable bounded payloads and complete source-to-report map or explicit exceptions recorded, source issues unmodified, continuous migration worker enabled only for its lane with existing600s retry policy, default worker unaffected, no unintended scheduler/CD changes. Report counts, progress and limitations honestly; do not claim whole backlog processed while it is still queued or model-limited.