i4h-workflow-setup

i4h Workflow Setup

Purpose

Prepare the complete runtime, then prove dependency-light workflow discovery works.

Instructions

Resolve the base checkout.
Run every host preflight check.
Run default full setup.
Verify discovery and lint --all.

Resolve the checkout

export I4H_WORKFLOWS_REPO_URL="${I4H_WORKFLOWS_REPO_URL:-https://github.com

Treat this resolver as part of the skill contract: a hosted copy may run outside the base repository, so never assume the current checkout contains workflows/i4h_workflows. I4H_WORKFLOWS_REPO_URL selects the clone source. When I4H_WORKFLOWS is unset, derive the fallback directory from that URL; set I4H_WORKFLOWS only to reuse or choose a specific destination. Never replace an existing checkout.

Preflight

Require supported Linux on x86_64 or aarch64, uv, Git, network access for missing packages/assets, sufficient disk and model-cache space, and an NVIDIA driver compatible with the repository's Isaac Sim version. Read the exact current requirements from ./README.md; do not rely on remembered version numbers. Require Docker only when the requested local VLM or Cosmos service needs it.

Sync

Run the default full setup:

The explicit equivalent is:

Use ./setup.sh clean only when the user explicitly requests a full rebuild or cleanup because it deletes generated caches, component environments, and third-party checkouts. Setup is idempotent; do not clean as a generic repair. The setup script restores pinned third-party sources and the upstream Isaac Sim skill catalog; do not copy that catalog into skills/.

Verify

Use run.sh show <workflow> --mode <mode> when the user named a workflow. These checks prove discovery and contracts without importing Isaac Sim. Use i4h-workflow-validate for an actual rollout.

Troubleshooting

On failure, report the first host, network, checkout, or uv-sync error and rerun full setup only after correcting that cause.

Prerequisites

Require supported Linux, network access, uv, Git, disk space, and a compatible NVIDIA GPU/driver for simulator use.

Limitations

Setup does not download every optional checkpoint or prove any rollout succeeds. clean is destructive to generated environments and third-party checkouts.

Examples

Set up the i4h workflow on this machine and tell me if any host requirements are missing. → preflight, run default full setup, then run discovery and lint --all.

Completion gate

Report every host check, synced target, first failing component if any, discovery/lint results, and the smallest next smoke command. Do not claim simulator or policy success from setup alone.