Task Description
Inspect /home/rysweet/src/npurun/README.md and follow its documented setup instructions on the current machine. Diagnose setup, build, runtime, dependency, configuration, repository, and environment failures encountered. Fix issues within the repository or local environment when necessary and appropriate. Preserve all unrelated user changes in the working tree. Continue through complete setup and functional verification rather than stopping after a partial installation or build. Run an end-to-end npurun invocation that exercises the installed or built tool. README.md must be inspected and all applicable setup steps attempted in documented order or with clearly justified equivalent commands; required dependencies must be available; repository must build or install successfully using existing tooling; blocking repository changes must be minimal and conventional; environment changes must be setup-limited and non-destructive; smallest relevant existing tests/checks/build validations must pass; a real npurun command must exit successfully with README-consistent behavior; report meaningful fixes and the exact successful invocation. Do not perform unrelated refactoring, formatting, upgrades, cleanup, publishing, releases, pushes, commits, or PR creation. Do not fix defects unrelated to setup/end-to-end operation or introduce new validation frameworks. Proceed autonomously with safe reversible assumptions and no interactive clarification.
Requirements
Final Unambiguous Requirements
No material ambiguity remains. Proceed with these decisions:
-
Inspect README.md and account for prerequisites and Quick Start steps in documented order.
-
Validate both the Linux/WSL environment and underlying Windows ARM64 host, including hardware, Rust targets, MSVC, Windows SDK, LLVM, QAIRT, and QNN_SDK_ROOT.
-
Attempt Windows- and QAIRT-specific setup only where available; record missing proprietary SDK, tooling, or Snapdragon X-series NPU support as explicit platform limitations.
-
Do not download QAIRT through unofficial means, fabricate SDK artifacts, bypass licensing, or add unsafe runtime stubs.
-
On unsupported NPU hardware, build the repository’s intended no-SDK stub path so non-inference CLI commands remain usable.
-
Use the README-preferred command, cargo install --path crates/npurun-cli --locked, and require it to complete successfully.
-
Limit repository changes to minimal fixes directly required for documented setup or CLI operation. Preserve all unrelated working-tree changes.
-
Run the smallest relevant existing tests and checks. Pre-existing failures outside modified files—such as unrelated formatting differences—must be reported but not fixed.
-
Functionally verify the installed binary with a documented command that exits successfully. The accepted exact invocation is:
NPURUN_MODELS_DIR=/tmp/npurun-empty-models /home/rysweet/.cargo/bin/npurun list
An empty-model result is valid README-consistent behavior.
-
Attempt model inference only when a supported Snapdragon X-series NPU, QAIRT 2.44+, configured SDK, and model assets are all available.
-
Claim NPU acceleration only when Task Manager utilization, qnn_dlc metadata, and qualifying benchmark performance all agree.
-
Do not commit, push, publish, release, open a PR, upgrade unrelated dependencies, refactor unrelated code, or clean unrelated user files.
Decision rationale: The current WSL2 ARM64 environment can support compilation and non-inference CLI verification, but the older Snapdragon platform, absent QAIRT SDK, missing Windows native build tools, and lack of qualifying NPU evidence prevent genuine inference verification. Successful stub-path installation and npurun list execution therefore satisfy setup and end-to-end requirements without overstating hardware acceleration.
Acceptance Criteria
Classification
Generated via default-workflow recipe
Task Description
Inspect /home/rysweet/src/npurun/README.md and follow its documented setup instructions on the current machine. Diagnose setup, build, runtime, dependency, configuration, repository, and environment failures encountered. Fix issues within the repository or local environment when necessary and appropriate. Preserve all unrelated user changes in the working tree. Continue through complete setup and functional verification rather than stopping after a partial installation or build. Run an end-to-end npurun invocation that exercises the installed or built tool. README.md must be inspected and all applicable setup steps attempted in documented order or with clearly justified equivalent commands; required dependencies must be available; repository must build or install successfully using existing tooling; blocking repository changes must be minimal and conventional; environment changes must be setup-limited and non-destructive; smallest relevant existing tests/checks/build validations must pass; a real npurun command must exit successfully with README-consistent behavior; report meaningful fixes and the exact successful invocation. Do not perform unrelated refactoring, formatting, upgrades, cleanup, publishing, releases, pushes, commits, or PR creation. Do not fix defects unrelated to setup/end-to-end operation or introduce new validation frameworks. Proceed autonomously with safe reversible assumptions and no interactive clarification.
Requirements
Final Unambiguous Requirements
No material ambiguity remains. Proceed with these decisions:
Inspect
README.mdand account for prerequisites and Quick Start steps in documented order.Validate both the Linux/WSL environment and underlying Windows ARM64 host, including hardware, Rust targets, MSVC, Windows SDK, LLVM, QAIRT, and
QNN_SDK_ROOT.Attempt Windows- and QAIRT-specific setup only where available; record missing proprietary SDK, tooling, or Snapdragon X-series NPU support as explicit platform limitations.
Do not download QAIRT through unofficial means, fabricate SDK artifacts, bypass licensing, or add unsafe runtime stubs.
On unsupported NPU hardware, build the repository’s intended no-SDK stub path so non-inference CLI commands remain usable.
Use the README-preferred command,
cargo install --path crates/npurun-cli --locked, and require it to complete successfully.Limit repository changes to minimal fixes directly required for documented setup or CLI operation. Preserve all unrelated working-tree changes.
Run the smallest relevant existing tests and checks. Pre-existing failures outside modified files—such as unrelated formatting differences—must be reported but not fixed.
Functionally verify the installed binary with a documented command that exits successfully. The accepted exact invocation is:
An empty-model result is valid README-consistent behavior.
Attempt model inference only when a supported Snapdragon X-series NPU, QAIRT 2.44+, configured SDK, and model assets are all available.
Claim NPU acceleration only when Task Manager utilization,
qnn_dlcmetadata, and qualifying benchmark performance all agree.Do not commit, push, publish, release, open a PR, upgrade unrelated dependencies, refactor unrelated code, or clean unrelated user files.
Decision rationale: The current WSL2 ARM64 environment can support compilation and non-inference CLI verification, but the older Snapdragon platform, absent QAIRT SDK, missing Windows native build tools, and lack of qualifying NPU evidence prevent genuine inference verification. Successful stub-path installation and
npurun listexecution therefore satisfy setup and end-to-end requirements without overstating hardware acceleration.Acceptance Criteria
Classification
Generated via default-workflow recipe