voyager-deploylisted

# Deploy Model Pipeline Compile and deploy a model pipeline for Axelera AI hardware ## Use This Skill When / Not When - Use when: the user explicitly asks to compile, quantize, or calibrate a model with `deploy.py`, especially custom or non-prebuilt models. - Not when: the model is a prebuilt zoo network for a demo -- route to voyager-launch (it uses `axdownloadmodel`). - Not when: they only want to run an already-deployed model -- route to voyager-run. ## Instructions Deploy the specified model/pipeline: **$ARGUMENTS** {{INCLUDE common/voyager-sdk-setup.md}} {{INCLUDE common/voyager-task-integration.md}} ### Step 1: Pre-Deployment Checks - Verify Axelera environment is activated: ```bash echo $AXELERA_FRAMEWORK ``` - If not set, activate with: `source venv/bin/activate` - Read `.voyager-runtime.json`. Verify Axelera hardware only when `execution.mode` is `execute_on_device`: ```bash axdevice ``` In `package_for_linux` mode, prepare the deployment commands and caveat rather than claiming hardware compilation or runtime validation. ### Step 2: Model/Pipeline Identification - Parse model name from arguments - If no model specified, list available models: ```bash ./deploy.py --help ``` - Locate the YAML configuration in `ax_models/` - Verify YAML file exists and is valid ### Step 3: Deployment Mode Selection For prebuilt Voyager SDK model-zoo networks, prefer `axdownloadmodel` and cached payload checks. Use `deploy.py` only when the use