Pass through arguments to json-env-helper command

[tortxof]

Summary by CodeRabbit

• Improvements
  • Development environment setup tool now forwards command arguments to the invoked environment, preserving previous behavior when no arguments are provided.
  • The tool returns the exact exit status from the executed command so callers receive accurate success/failure results.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 53360eaf-59d7-47a1-83ff-69cd504808e4

📥 Commits

Reviewing files that changed from the base of the PR and between efe332f and 3920ded.

📒 Files selected for processing (1)

• dev-shell.sh

🚧 Files skipped from review as they are similar to previous changes (1)

• dev-shell.sh

---

📝 Walkthrough

Walkthrough

The dev-shell script now preserves and forwards CLI arguments: if none are provided it runs json-env-helper -- bash, otherwise it runs json-env-helper -- "$@", then exits with the invoked command's exit code. (50 words)

Changes

Cohort / File(s)	Summary
Command Argument Handling dev-shell.sh	Added conditional to detect presence of CLI arguments; forwards arguments to json-env-helper when present, falls back to launching bash when none are given, and exits with the child process's exit code.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

Poem

🐰 A tiny script hops, polite and spry,
It takes your args or starts a bash by.
Forwards to json-env-helper with care,
Returns the code it got — fair and square! ✨

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'Pass through arguments to json-env-helper command' accurately and clearly describes the main change: enabling the script to forward CLI arguments to the json-env-helper command instead of ignoring them.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch feat/exec-other

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@dev-shell.sh`:
- Around line 45-49: The script currently pipes secret_json into json-env-helper
and then continues running banner/title commands which can mask the invoked
command’s exit status; modify both branches (the no-arg path that runs
json-env-helper -- bash and the arg path that runs json-env-helper -- "$@") to
capture the command’s exit code immediately after it runs (e.g. store "$?" in a
variable like cmd_exit) and then, after any subsequent banner/title output, exit
the script with that captured code (exit $cmd_exit) so failures from
json-env-helper are preserved and returned to the caller.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: dac1878d-ca17-4cc0-acf3-23819b6434d1

📥 Commits

Reviewing files that changed from the base of the PR and between 713b075 and efe332f.

📒 Files selected for processing (1)

• dev-shell.sh