fix: default to cwd instead of interactive directory prompt

[parshvadaftari]

Summary

• Remove the interactive Repository path prompt that blocks the CLI when run without --dir or --prompt
• gitclaw now defaults to process.cwd() immediately, matching modern CLI conventions
• Remove the now-unused askQuestion helper function

Closes #13

Motivation

Running gitclaw with no flags would block on an interactive prompt asking for the repository path. This was unnecessary since parseArgs() already defaults dir to
process.cwd(), and ensureRepo() handles scaffolding agent.yaml if missing.

Changes

src/index.ts

• Removed askQuestion() helper (only used by the interactive prompt)
• Removed the else if branch that triggered the directory prompt when no --dir or --prompt was provided

Test plan

• gitclaw with no flags — starts immediately without prompting
• gitclaw --dir /some/path — works as before
• gitclaw -p "some prompt" — works as before
• gitclaw --repo <url> — works as before