conductor code: can't pass task name non-interactively, fails with EOF when piped

[nthmost-orkes]

Problem

`conductor code` prompts interactively for a task name. If the command is run non-interactively (piped, in CI, or with output redirected), it fails immediately:

```
Error: failed to build template context: failed to read input for taskname: EOF
```

The command accepts `-l`, `-t`, and `-n` flags for language, template, and project name — but there is no flag for the task name. It must be typed interactively.

This makes the command impossible to script, use in CI, or include in automated onboarding flows.

Fix

Add a `--task-name` (or `--task`) flag so all inputs can be provided non-interactively:

```bash
conductor code -l python -t basic-worker -n my-project --task-name my_task
```

Affects

• `conductor-oss/conductor-cli`

[nthmost-orkes]

Fixed in conductor-oss/conductor-cli#77 (merged). The README now documents that conductor code is interactive-only and cannot be used in scripts or piped environments.