chore: import codebase

[itsjoeoui]

Imports the codebase from the existing private repo as a single squashed commit. This is the initial code drop for the open-source instro repo.

Ticket Alignment

Does the Linear ticket capture the evolution of the development which led to this implementation? If the implementation diverged from the original plan, update the ticket or note the delta below.

• Yes
• No — describe the delta:

Reviewers

• The selected reviewers have the appropriate domain knowledge and/or code ownership for this change

If the right reviewers aren't obvious, explain your selection:

Verification

Provide evidence that verifies you've met the goals of the scope of this ticket/PR. This should provide the reviewer enough information to not have to reproduce your results, but rather evaluate your results against the goals. Use whatever best demonstrates it — e.g. screenshots, a Nominal Core Workbook link, logs, repro steps + result, a staging link. If omitting, explain why.

Regression & Future Safety

Unit tests

Were unit tests added or updated? If existing tests cover this, say so explicitly. If omitting, explain why.

Additional coverage

Did you go further? E.g. end-to-end tests, error reporting, data review coverage, alerting. Document it here — this is how we build better habits over time. If omitting, explain why.

Notes for reviewers

Optional — call out specific files, edge cases, or decisions you'd like eyes on. If you identified out-of-scope risks, consider creating Linear tickets to track them.

[github-actions]

⚠️ PR template incomplete

This check is advisory for now and may become a required gate at some point.

• Ticket Alignment — check at least one option.
• Reviewers — check at least one option.
• Verification — provide content, or explain why it is being omitted.
• Unit tests — provide content, or explain why it is being omitted.

This comment was posted automatically by the PR template check.

[semgrep-code-nominal-io]

Legal Risk

The following dependencies were released under a license that
is currently prohibited by your organization. Merging is blocked until this is resolved.

Recommendation

Reach out to your security team or Semgrep admin to address this issue. In special cases, exceptions may be made for dependencies with violating licenses, however, the general recommendation is to avoid using a dependency under such a license

MPL-2.0

• certifi 2025.8.3

non-standard

• pyvisa 1.15.0
• pyaardvark 0.8.1
• polars 1.35.2
• numpy 2.2.6
• labjack-ljm 1.23.0
• ghp-import 2.1.0