run-kilin-workflowlisted

# Run a Kilin workflow Run one existing workflow from an exact physical working directory. Keep the Kilin run and Viewer as separate attached processes: the run owns provider execution, while the Viewer only presents the compiled graph and local history. ## Resolve the invocation 1. Resolve the physical working directory and the requested workflow ID. Do not substitute a similarly named directory or workflow. 2. Resolve this skill's physical directory from the `SKILL.md` path supplied by the skill loader. The Kilin package root is exactly two directories above it, and the matching built CLI is `dist/cli/main.js` beneath that root. Stop and report an invalid or incomplete installation if either path cannot be resolved. 3. Run `node <resolved-kilin-cli> workflow validate <id> --cwd <absolute-cwd> --json`. Do not pass `--scope`: validation must select the same project-over-user package that `kilin run` will use. 4. Run `node <resolved-kilin-cli> workflow list --cwd <absolute-cwd> --json`, locate the visible package, and read its sibling `WORKFLOW.yaml` only to identify declared run parameters. Ask for every missing required value; do not invent values. Warn that `--param` values can appear in shell history and process lists, and never request a secret through that flag. 5. Preserve caller-supplied timeout, output, concurrency, and parameter choices. Otherwise use the CLI defaults. Do not add retries, continuations, or approvals that the user did