Run the XPOIS, xFit and XScan device pipeline through Dragon

[tpn]

Run complete XPOIS, xFit, and XScan image-pair jobs in persistent Dragon workers, reusing one device context per worker. Compact launch and result descriptors bind each result to its inputs, configuration, and scientific evidence while preserving Torch-before-CuPy startup.

Live Dragon and GPU execution remain unverified for this revision.

[coderabbitai]

Navigate logical layers of code changes, visualize relationships, and explore their blast radius.

Note

Reviews paused

It looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the reviews.auto_review.auto_pause_after_reviewed_commits setting.

Use the following commands to manage reviews:

• @coderabbitai resume to resume automatic reviews.
• @coderabbitai review to trigger a single review.

Use the checkboxes below for quick actions:

• ▶️ Resume reviews
• 🔍 Trigger review

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Repository: NVIDIA/cuPhoton/.coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: a7a4f2a9-45df-4e90-8616-469ffbc2b85f

📥 Commits

Reviewing files that changed from the base of the PR and between 7439af0 and 6348319.

📒 Files selected for processing (3)

• docs/components/xscan.md
• src/cuphoton/xscan/dragon_pipeline.py
• tests/xscan/test_dragon_pipeline.py

Included review availability: Your plan provides up to 12 included reviews per hour; 6 remain after this review.

---

📝 Walkthrough

Walkthrough

The pull request adds a persistent Dragon-based XScan device pipeline. It validates inputs and results, reuses device contexts across shard items, audits published summaries, and documents direct and Dragon execution.

Changes

XScan device pipeline

Layer / File(s)	Summary
Pipeline contracts and validation src/cuphoton/xscan/dragon_pipeline.py, tests/xscan/test_dragon_pipeline.py	Defines versioned schemas and validates identities, hashes, transfer receipts, results, and scientific evidence. Tests cover malformed results and evidence that conflicts with configuration.
Preflight and persistent worker execution src/cuphoton/xscan/dragon_pipeline.py, tests/xscan/test_dragon_pipeline.py, docs/components/xscan.md	Checks configuration and input files, validates worker options, and builds work items. Each shard initializes one device context and reuses it across items. Tests cover preflight rejection, GPU identity probing, and context reuse or initialization failure. Documentation describes pipeline requirements, input descriptors, and direct execution.
Batch orchestration and terminal auditing src/cuphoton/xscan/dragon_pipeline.py, tests/xscan/test_dragon_pipeline.py, docs/components/xscan.md	Adds run_dragon_device_pipeline with Dragon manifests, timeouts, and record validators. Tests cover coordinator audits of file-backed summaries, runtime records, and device identity. Documentation describes Dragon execution and result handling.

Priority: ⬇️ Low

Merge Risk: ⚪ Minimal · up to 63483

This change adds a validated, persistent Dragon pipeline for XPOIS, xFit and XScan jobs, along with tests and documentation. No concrete defect remains open against the current revision. The author reports that live multi-GPU Dragon runs are still unverified, so owners should confirm a real run, but nothing identified blocks the merge.

🚥 Pre-merge checks | ✅ 2

✅ Passed checks (2 passed)

Check name	Status	Explanation
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

---

_{Comment @coderabbitai help to get the list of available commands.}

[tpn]

@coderabbitai full review

[coderabbitai]

✅ Action performed

Full review finished.

[melo-gonzo]

Approving: the PR tree is byte-identical to the open GitLab branch for every file it touches, and my earlier findings remain as posted. Merge after the internal MR is merged so the histories match.

[tpn]

@coderabbitai full review

[coderabbitai]

✅ Action performed

Full review finished.

[tpn]

@coderabbitai full review

[coderabbitai]

✅ Action performed

Full review finished.