fix(init): flash init show usage menu when called without arguments

[deanq]

Summary

• flash init with no arguments now shows a usage panel with examples and exits instead of silently initializing in the current directory
• flash init . continues to initialize in the current directory (unchanged)
• flash init <name> continues to create a new project folder (unchanged)

Before: flash init and flash init . had identical behavior -- both initialized in cwd.
After: flash init shows usage menu; flash init . is the explicit way to initialize in cwd.

Test plan

• Added 3 new tests for no-args behavior (exits with code 0, does not create skeleton, prints usage panel)
• Updated existing test that asserted None creates skeleton (removed -- behavior changed)
• All 18 init tests pass
• Full make quality-check passes (1261 tests, 73.75% coverage)
• Manual verification of all three modes: flash init, flash init ., flash init <name>

[Copilot]

Pull request overview

Updates the flash init CLI behavior so invoking it without a project argument shows a usage/help panel and exits, making “initialize in current directory” an explicit flash init ..

Changes:

• Added an early-exit usage panel for flash init when called with no positional argument.
• Updated init logic so only flash init . initializes the current directory (no longer the default when omitted).
• Added/updated unit tests to cover the new no-args behavior (exit code, no skeleton creation, usage output).

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.

File	Description
src/runpod_flash/cli/commands/init.py	Adds no-args usage panel + exit and adjusts current-directory branching to require ..
tests/unit/cli/commands/test_init.py	Adds tests validating no-args exit behavior, output, and that no skeleton is created.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[runpod-Henrik]

Code Review — PR #235: flash init usage menu

The init.py change is clean — showing usage panel when no args instead of silently initializing in cwd is good UX.

Note: This PR shares a large diff overlap with PRs #221 and #237 (aiohttp session consolidation, api_key_context.py removal, DEFAULT_WORKERS_MIN change, get_api_key() migration). The bugs found in those shared components apply here too:

1. HIGH — Authorization header sent to presigned S3 URLs in app.py (see PR #221 review)
2. HIGH — Per-request API key propagation from LB to workers silently removed (see PR #221 review)
3. HIGH — uv pip install fails without active venv in update.py (see PR #237 review, if update.py is included)

The init.py change itself has no issues. Tests cover all three modes (flash init, flash init ., flash init name).