`ucm run.pipe` doesn't appear to work anymore

[jcwilk]

Reproduce:

echo -e 'helloWorld : '\''{IO, Exception} ()\nhelloWorld _ = printLine "Hello World!"' | ./ucm -Ctemp --exit run.pipe helloWorld

Expected behavior: I was expecting it to output "Hello World!"

Actual behavior:

# echo -e 'helloWorld : '\''{IO, Exception} ()\nhelloWorld _ = printLine "Hello World!"' | ./ucm -Ctemp --exit run.pipe helloWorld

   _____     _             
  |  |  |___|_|___ ___ ___ 
  |  |  |   | |_ -| . |   |
  |_____|_|_|_|___|___|_|_|
  
  👋 Welcome to Unison!
  
  You are running version: release/0.5.12

  📚 Read the official docs at https://www.unison-lang.org/docs/
  
  Type 'project.create' to get started.

  
    ❓
    
    I couldn't resolve any of these symbols:
    
        1 | helloWorld : '{IO, Exception} ()
    
    
    Symbol      Suggestions
                
    Exception   No matches
                
    IO          No matches
  

  😶
  
  I looked for a function `helloWorld` in the most recently typechecked file and codebase but
  couldn't find one. It has to have the type:
  
    helloWorld : '{##IO, #4n0fgs00hp} result

From a thread in slack, @aryairani suggested it may be due to the semi-recent introduction of Projects and a lack of ability to specify which project run.pipe should use.

Certainly would be nice if it didn't output all that intro text as well, or if there was a flag to disable it, or if there was some clear divider pattern to make it easier to parse out whatever the actual output is.

[aryairani]

The current UX deficiency affects run, and run.file as well as run.pipe.

What if we make -p / --path accept a project/branch argument too? We could even add --project as a synonym.

[jcwilk]

I thought that's what -p / --path did at first skim so it seems to check the box for intuitive