docs(praxis-onboarding): use --stream when reading release logs (#17)

- raptor `logs release` now gates the stdout stream behind --stream (default
  off; raptor#155). Without the flag, callers — including the praxis mcp
  wrapper — see only "Logs: /tmp/..." and "Release logs fetched"; log
  content lives on disk only, which the model can't read back.
- The flow's failure-recovery example (`flows/first-deployment.md`, Stop 6)
  is the one place the skill shells out to raptor for logs; add --stream so
  the model receives the content via stdout. Tempfile is unchanged
  (authoritative, written file-first per the raptor change).
- Depends on the Praxis backend bundling a raptor build with --stream;
  until then the server-side wrapper will return "unknown flag: --stream".

Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>

Author: samarthya-gupta1

internal/skillinstall/embedded/praxis-onboarding/flows/first-deployment.md

@@ -404,7 +404,9 @@ until rel=$(raptor get releases -p <project> -e <env> 2>&1) && \
 ```
 
 On failure, hand off to `praxis-release-debugging` / `troubleshoot` and read the
-logs together: `raptor logs release -p <project> -e <env> <release-id>`.
+logs together: `raptor logs release -p <project> -e <env> <release-id> --stream`.
+The `--stream` flag is what tees the log lines into stdout — without it you only
+get the tempfile path, which the model can't read back through the MCP wrapper.
 
 ---