Prompt 4: Spark support chat should use concrete command-not-found checks before reinstall guidance

[Aeyod7]

Problem

For Spark Compete prompt 4, Spark correctly avoided telling the user to reinstall immediately, but the diagnostic steps were still too vague at the point where a new user needs exact checks.

It also suggested spark --version, but in this local Spark CLI shape that command did not return a version. It printed usage because a subcommand is required:

spark: error: the following arguments are required: command

Evidence

User prompt tested:

I just installed Spark and my terminal says `spark: command not found`. Do I need to reinstall, or is there a smaller safe fix first?

Observed Spark response:

No need to reinstall yet. This is usually a PATH or shell session issue.

Try this:

1. Close your terminal and open a new one, then run `spark --version`.
2. If that fails, check where Spark was installed (look for a local install path or a setup script in your Spark folder) and add it to your PATH.
3. If you used a setup script, re-run it and make sure it completed without errors.

If none of that works, run `/diagnose` here and I can help you inspect the install.

What worked:

• Spark did not jump straight to reinstall.
• Spark identified PATH/stale shell session as likely.
• Spark escalated to diagnostics only after smaller checks.

Gap:

• “Look for a local install path” is vague.
• spark --version may not be reliable for the current CLI behavior.
• The answer should include exact shell checks for Linux/WSL and Windows.

Sanitized local capture used for this report:

/tmp/spark-qa-user-prompts-3-4-49.raw.txt

No secrets, tokens, cookies, wallet material, or private logs are included.

Fix

Use concrete command-not-found checks before suggesting setup reruns or reinstall.

Cross-platform checks:

command -v spark
spark status
spark verify --onboarding

For WSL/Linux installs:

export PATH="$HOME/.spark/bin:$PATH"
command -v spark
spark status

For Windows PowerShell installs:

Get-Command spark
$env:Path -split ';' | Select-String -Pattern 'spark'

Support guidance should make the safe order explicit:

1. Open a fresh terminal.
2. Check whether spark is discoverable.
3. Check the likely install path.
4. Add the correct install bin directory to the correct shell PATH.
5. Only rerun setup/reinstall if the binary is actually missing or setup failed.

Verification

Reviewer can verify with this prompt replay:

I just installed Spark and my terminal says `spark: command not found`. Do I need to reinstall, or is there a smaller safe fix first?

Expected passing behavior:

• Response says not to reinstall first.
• Response gives exact command -v spark / Get-Command spark style checks.
• Response uses spark status or spark verify --onboarding for verification.
• Response avoids relying only on spark --version.
• Response separates Windows PATH from WSL/Linux PATH.