smart-orchestrator preflight fails: resolve-bundle-asset rejects 'helper-path' asset name (binary 0.9.39)

[rysweet]

Symptom

amplihack recipe run amplifier-bundle/recipes/smart-orchestrator.yaml fails at the preflight-validation step with:

=== SMART-ORCHESTRATOR PRE-FLIGHT FAILED ===
  ✗ Cannot find orch_helper.py — set AMPLIHACK_HOME to a valid amplihack root

Root cause

The recipe YAML invokes amplihack resolve-bundle-asset helper-path in 4 steps (lines 58, 206, 257, 493 of amplifier-bundle/recipes/smart-orchestrator.yaml), but the installed Rust binary amplihack 0.9.39 only accepts asset name multitask-orchestrator (or relative paths starting with amplifier-bundle/):

$ amplihack resolve-bundle-asset helper-path
ERROR: Unknown asset name "helper-path". Expected one of: multitask-orchestrator

The file actually exists at /home/azureuser/.amplihack/amplifier-bundle/tools/orch_helper.py, and the relative-path form works:

$ amplihack resolve-bundle-asset amplifier-bundle/tools/orch_helper.py
/home/azureuser/.amplihack/amplifier-bundle/tools/orch_helper.py

So the recipe and the binary are out of sync: either the binary needs to add helper-path as a recognised alias, or the recipe needs to be updated to use the relative path.

Reproduction

amplihack --version  # 0.9.39
AMPLIHACK_HOME=/home/azureuser/.amplihack \
  amplihack recipe run /home/azureuser/.amplihack/amplifier-bundle/recipes/smart-orchestrator.yaml \
    -c task_description=test -c repo_path=.

Environment

• amplihack 0.9.39
• AMPLIHACK_RUST_RUNTIME=1
• AMPLIHACK_HOME=/home/azureuser/.amplihack

Workaround

Invoke default-workflow / investigation-workflow directly — they do not depend on helper-path.

Suggested fix

Add helper-path (and any other names referenced from recipe YAML — likely hooks-dir, see line 60) to the asset name allow-list in amplihack resolve-bundle-asset, mapping to the corresponding amplifier-bundle/ paths.