Add a shipwright ping command that prints pong to stdout and exits 0#195
Add a shipwright ping command that prints pong to stdout and exits 0#195
Conversation
- Adds scripts/sw-ping.sh: prints "pong" to stdout, exits 0 - Adds scripts/sw-ping-test.sh: 6 tests covering output, exit codes, --help/-h, --version/-v, and unknown option handling - Registers ping command in scripts/sw router after hello command Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
📝 WalkthroughWalkthroughThe PR adds a new Changes
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~20 minutes Poem
🚥 Pre-merge checks | ✅ 2 | ❌ 1❌ Failed checks (1 inconclusive)
✅ Passed checks (2 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches
🧪 Generate unit tests (beta)
Tip Try Coding Plans. Let us write the prompt for your AI agent so you can ship faster (with fewer bugs). Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 7
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In @.claude/loop-state.md:
- Around line 73-74: The discovery entry contains an unclosed quote in the
string 'Resolution: "' which breaks parsers; edit the entry in the loop-state
content to close or remove the stray double quote so the value becomes a valid
string (e.g., change 'Resolution: "' to 'Resolution: ""', 'Resolution: "some
value"', or 'Resolution: ' with no trailing quote) so the malformed discovery
entry is corrected.
- Around line 33-37: The header-style lines for the "sw-ping.sh — public
interface" block are written with leading '#' which renders as Markdown headings
and triggers lint MD019; change that block so it is not a heading—convert the
lines starting with "# sw-ping.sh — public interface", "# Inputs: ...", "#
Outputs: ...", and "# Exit: ..." into either a bullet list or a fenced
code/quote block (e.g., remove the '#' prefixes and prefix with '-' for bullets
or wrap the whole block in triple backticks) so the interface notes are plain
text and no longer treated as headings.
- Around line 17-25: The Markdown table in .claude/loop-state.md is missing a
blank line terminator and has inconsistent pipe usage that causes the following
line to be parsed as a malformed row; fix by ensuring every table row uses
consistent leading and trailing pipes (e.g., "| 1 | ... |") and add a single
blank line immediately after the final table row so the parser recognizes the
table end (update the table block shown in the diff and ensure subsequent text
is separated by a blank line).
In @.claude/platform-hygiene.json:
- Line 3: The JSON key "repository" in .claude/platform-hygiene.json is set to
"compound-e2e" but should reflect this repo's Shipwright identifier; update the
"repository" value to the correct Shipwright repo name used by your automation
(replace "compound-e2e" with the appropriate Shipwright repo identifier) so
hygiene findings and automation outputs are attributed correctly.
In `@docs/plans/2026-03-02-add-ping-command.md`:
- Around line 362-370: Add language identifiers to the two fenced code blocks
that currently contain the inline shell commands and insert the ping test
command after the first hello test; specifically, update the fence opening for
the block containing "bash scripts/sw-hello-test.sh &&" to use a language tag
(e.g., ```text or ```bash) and replace the following block so it reads the
two-command line "bash scripts/sw-hello-test.sh && bash scripts/sw-ping-test.sh
&&" inside a fenced block that also starts with the same language tag, ensuring
both fenced blocks include the language identifier.
In `@scripts/sw-ping-test.sh`:
- Around line 92-93: The test captures the exit code incorrectly so it can mask
a succeeding command as failure; replace the current one-liner that uses "||
local exit_code=$?" with a two-step capture: run "$SCRIPT_DIR/sw-ping.sh"
--invalid > /dev/null 2>&1 and immediately set local exit_code=$? (so exit_code
is always assigned), then call assert_exit_code 1 "${exit_code}" "ping with
invalid option exits with code 1"; update the usage of the exit_code variable
and keep the assert_exit_code call as-is.
- Around line 15-18: Replace all uses of the post-increment arithmetic form that
can return zero under set -e (e.g. ((PASS++)) and ((FAIL++))) with a form that
performs the increment without producing a zero exit status; for example change
each ((PASS++)) to PASS=$((PASS+1)) and each ((FAIL++)) to FAIL=$((FAIL+1)).
Update every occurrence of the PASS and FAIL increments in the script so the
counters increment reliably under set -euo pipefail.
ℹ️ Review info
Configuration used: defaults
Review profile: CHILL
Plan: Pro
⛔ Files ignored due to path filters (6)
.claude/loop-logs/audit-iter-1.logis excluded by!**/*.log.claude/loop-logs/audit-iter-2.logis excluded by!**/*.log.claude/loop-logs/iteration-1.logis excluded by!**/*.log.claude/loop-logs/iteration-2.logis excluded by!**/*.log.claude/loop-logs/tests-iter-1.logis excluded by!**/*.log.claude/loop-logs/tests-iter-2.logis excluded by!**/*.log
📒 Files selected for processing (9)
.claude/daemon-config.json.claude/intelligence-cache.json.claude/loop-state.md.claude/platform-hygiene.jsondocs/plans/2026-03-02-add-ping-command.mdpackage.jsonscripts/swscripts/sw-ping-test.shscripts/sw-ping.sh
| | # | Task | Files | | ||
| |---|------|-------| | ||
| | 1 | Create `sw-ping.sh` (prints `pong`, exits 0) | `scripts/sw-ping.sh` (new) | | ||
| | 2 | Make it executable + verify output | — | | ||
| | 3 | Create `sw-ping-test.sh` (6 tests) | `scripts/sw-ping-test.sh` (new) | | ||
| | 4 | Run tests, confirm `PASS: 6 FAIL: 0` | — | | ||
| | 5 | Add `ping)` case to router after `hello)` | `scripts/sw` | | ||
| | 6 | Verify `bash scripts/sw ping` → `pong` | — | | ||
| [... full plan in .claude/pipeline-artifacts/plan.md] |
There was a problem hiding this comment.
Clean up table termination to satisfy markdown table rules.
The table rows are fine, but the next line is interpreted as a malformed row. Add a blank line after the table and use consistent leading/trailing pipes.
Proposed fix
-| # | Task | Files |
-|---|------|-------|
-| 1 | Create `sw-ping.sh` (prints `pong`, exits 0) | `scripts/sw-ping.sh` (new) |
-| 2 | Make it executable + verify output | — |
-| 3 | Create `sw-ping-test.sh` (6 tests) | `scripts/sw-ping-test.sh` (new) |
-| 4 | Run tests, confirm `PASS: 6 FAIL: 0` | — |
-| 5 | Add `ping)` case to router after `hello)` | `scripts/sw` |
-| 6 | Verify `bash scripts/sw ping` → `pong` | — |
+| # | Task | Files |
+| --- | --- | --- |
+| 1 | Create `sw-ping.sh` (prints `pong`, exits 0) | `scripts/sw-ping.sh` (new) |
+| 2 | Make it executable + verify output | — |
+| 3 | Create `sw-ping-test.sh` (6 tests) | `scripts/sw-ping-test.sh` (new) |
+| 4 | Run tests, confirm `PASS: 6 FAIL: 0` | — |
+| 5 | Add `ping)` case to router after `hello)` | `scripts/sw` |
+| 6 | Verify `bash scripts/sw ping` → `pong` | — |
+
[... full plan in .claude/pipeline-artifacts/plan.md]📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| | # | Task | Files | | |
| |---|------|-------| | |
| | 1 | Create `sw-ping.sh` (prints `pong`, exits 0) | `scripts/sw-ping.sh` (new) | | |
| | 2 | Make it executable + verify output | — | | |
| | 3 | Create `sw-ping-test.sh` (6 tests) | `scripts/sw-ping-test.sh` (new) | | |
| | 4 | Run tests, confirm `PASS: 6 FAIL: 0` | — | | |
| | 5 | Add `ping)` case to router after `hello)` | `scripts/sw` | | |
| | 6 | Verify `bash scripts/sw ping` → `pong` | — | | |
| [... full plan in .claude/pipeline-artifacts/plan.md] | |
| | # | Task | Files | | |
| | --- | --- | --- | | |
| | 1 | Create `sw-ping.sh` (prints `pong`, exits 0) | `scripts/sw-ping.sh` (new) | | |
| | 2 | Make it executable + verify output | — | | |
| | 3 | Create `sw-ping-test.sh` (6 tests) | `scripts/sw-ping-test.sh` (new) | | |
| | 4 | Run tests, confirm `PASS: 6 FAIL: 0` | — | | |
| | 5 | Add `ping)` case to router after `hello)` | `scripts/sw` | | |
| | 6 | Verify `bash scripts/sw ping` → `pong` | — | | |
| [... full plan in .claude/pipeline-artifacts/plan.md] |
🧰 Tools
🪛 markdownlint-cli2 (0.21.0)
[warning] 25-25: Table pipe style
Expected: leading_and_trailing; Actual: no_leading_or_trailing; Missing leading pipe
(MD055, table-pipe-style)
[warning] 25-25: Table pipe style
Expected: leading_and_trailing; Actual: no_leading_or_trailing; Missing trailing pipe
(MD055, table-pipe-style)
[warning] 25-25: Table column count
Expected: 3; Actual: 1; Too few cells, row will be missing data
(MD056, table-column-count)
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In @.claude/loop-state.md around lines 17 - 25, The Markdown table in
.claude/loop-state.md is missing a blank line terminator and has inconsistent
pipe usage that causes the following line to be parsed as a malformed row; fix
by ensuring every table row uses consistent leading and trailing pipes (e.g., "|
1 | ... |") and add a single blank line immediately after the final table row so
the parser recognizes the table end (update the table block shown in the diff
and ensure subsequent text is separated by a blank line).
| # sw-ping.sh — public interface | ||
| # Inputs: $1 (optional) — one of: "", "--help", "-h", "--version", "-v", <unknown> | ||
| # Outputs: stdout — one of: "pong\n", help text, VERSION string, error message | ||
| # Exit: 0 on success (no args, --help, --version) | ||
| # 1 on unknown arg |
There was a problem hiding this comment.
Don’t use # prefixes for interface “comments” in markdown.
These render as headings (and trigger lint issues like MD019). Use bullets or a fenced block instead.
Proposed fix
-# sw-ping.sh — public interface
-# Inputs: $1 (optional) — one of: "", "--help", "-h", "--version", "-v", <unknown>
-# Outputs: stdout — one of: "pong\n", help text, VERSION string, error message
-# Exit: 0 on success (no args, --help, --version)
-# 1 on unknown arg
+**sw-ping.sh — public interface**
+- Inputs: `$1` (optional) — one of: `""`, `--help`, `-h`, `--version`, `-v`, `<unknown>`
+- Outputs: stdout — one of: `pong\n`, help text, VERSION string, error message
+- Exit: `0` on success (no args, `--help`, `--version`); `1` on unknown arg📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| # sw-ping.sh — public interface | |
| # Inputs: $1 (optional) — one of: "", "--help", "-h", "--version", "-v", <unknown> | |
| # Outputs: stdout — one of: "pong\n", help text, VERSION string, error message | |
| # Exit: 0 on success (no args, --help, --version) | |
| # 1 on unknown arg | |
| **sw-ping.sh — public interface** | |
| - Inputs: `$1` (optional) — one of: `""`, `--help`, `-h`, `--version`, `-v`, `<unknown>` | |
| - Outputs: stdout — one of: `pong\n`, help text, VERSION string, error message | |
| - Exit: `0` on success (no args, `--help`, `--version`); `1` on unknown arg |
🧰 Tools
🪛 markdownlint-cli2 (0.21.0)
[warning] 37-37: Multiple spaces after hash on atx style heading
(MD019, no-multiple-space-atx)
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In @.claude/loop-state.md around lines 33 - 37, The header-style lines for the
"sw-ping.sh — public interface" block are written with leading '#' which renders
as Markdown headings and triggers lint MD019; change that block so it is not a
heading—convert the lines starting with "# sw-ping.sh — public interface", "#
Inputs: ...", "# Outputs: ...", and "# Exit: ..." into either a bullet list or a
fenced code/quote block (e.g., remove the '#' prefixes and prefix with '-' for
bullets or wrap the whole block in triple backticks) so the interface notes are
plain text and no longer treated as headings.
| [design] Design completed for Add a shipwright ping command that prints pong to stdout and exits 0 — Resolution: " | ||
| iteration: 2 |
There was a problem hiding this comment.
Fix malformed discovery entry (Resolution: " has an unclosed quote).
The value starts with a quote and never closes, which can break parsers that read this state file.
Proposed fix
-[design] Design completed for Add a shipwright ping command that prints pong to stdout and exits 0 — Resolution: "
+[design] Design completed for Add a shipwright ping command that prints pong to stdout and exits 0 — Resolution: complete
iteration: 2📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| [design] Design completed for Add a shipwright ping command that prints pong to stdout and exits 0 — Resolution: " | |
| iteration: 2 | |
| [design] Design completed for Add a shipwright ping command that prints pong to stdout and exits 0 — Resolution: complete | |
| iteration: 2 |
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In @.claude/loop-state.md around lines 73 - 74, The discovery entry contains an
unclosed quote in the string 'Resolution: "' which breaks parsers; edit the
entry in the loop-state content to close or remove the stray double quote so the
value becomes a valid string (e.g., change 'Resolution: "' to 'Resolution: ""',
'Resolution: "some value"', or 'Resolution: ' with no trailing quote) so the
malformed discovery entry is corrected.
| "timestamp": "2026-03-02T07:15:33Z", | ||
| "repository": "shipwright", | ||
| "timestamp": "2026-03-02T13:18:32Z", | ||
| "repository": "compound-e2e", |
There was a problem hiding this comment.
Repository identifier appears incorrect for this repo.
Line 3 changes repository to compound-e2e, which does not match the Shipwright repository context in this PR. This can misattribute hygiene findings and automation outputs.
🔧 Proposed fix
- "repository": "compound-e2e",
+ "repository": "shipwright",📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| "repository": "compound-e2e", | |
| "repository": "shipwright", |
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In @.claude/platform-hygiene.json at line 3, The JSON key "repository" in
.claude/platform-hygiene.json is set to "compound-e2e" but should reflect this
repo's Shipwright identifier; update the "repository" value to the correct
Shipwright repo name used by your automation (replace "compound-e2e" with the
appropriate Shipwright repo identifier) so hygiene findings and automation
outputs are attributed correctly.
| ``` | ||
| bash scripts/sw-hello-test.sh && | ||
| ``` | ||
|
|
||
| Insert immediately after it: | ||
|
|
||
| ``` | ||
| bash scripts/sw-hello-test.sh && bash scripts/sw-ping-test.sh && | ||
| ``` |
There was a problem hiding this comment.
Add language identifiers to fenced code blocks to satisfy markdown lint.
The blocks at Line 362 and Line 368 should specify a language (e.g., text or bash).
📝 Proposed fix
-```
+```text
bash scripts/sw-hello-test.sh &&
-```
+```
-```
+```text
bash scripts/sw-hello-test.sh && bash scripts/sw-ping-test.sh &&
-```
+```🧰 Tools
🪛 markdownlint-cli2 (0.21.0)
[warning] 362-362: Fenced code blocks should have a language specified
(MD040, fenced-code-language)
[warning] 368-368: Fenced code blocks should have a language specified
(MD040, fenced-code-language)
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@docs/plans/2026-03-02-add-ping-command.md` around lines 362 - 370, Add
language identifiers to the two fenced code blocks that currently contain the
inline shell commands and insert the ping test command after the first hello
test; specifically, update the fence opening for the block containing "bash
scripts/sw-hello-test.sh &&" to use a language tag (e.g., ```text or ```bash)
and replace the following block so it reads the two-command line "bash
scripts/sw-hello-test.sh && bash scripts/sw-ping-test.sh &&" inside a fenced
block that also starts with the same language tag, ensuring both fenced blocks
include the language identifier.
| ((PASS++)) | ||
| echo -e " \033[38;2;74;222;128m\033[1m✓\033[0m $description" | ||
| else | ||
| ((FAIL++)) |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
# Check if the file exists and inspect the flagged lines
git ls-files | grep -E "scripts/sw-ping-test.sh"Repository: sethdford/shipwright
Length of output: 87
🏁 Script executed:
# Look at the actual script content around the flagged lines
if [ -f scripts/sw-ping-test.sh ]; then
cat -n scripts/sw-ping-test.sh | head -100
fiRepository: sethdford/shipwright
Length of output: 4190
🏁 Script executed:
# Test the claimed behavior about ((var++)) under set -e
bash -c 'set -e; n=0; ((n++)); echo "reached echo"' && echo "Script succeeded" || echo "Script failed with status $?"Repository: sethdford/shipwright
Length of output: 91
🏁 Script executed:
# Additional test: verify post-increment semantics
bash -c 'n=0; result=$((n++)); echo "n=$n result=$result"; exit $result' && echo "Exit 0" || echo "Exit non-zero"Repository: sethdford/shipwright
Length of output: 83
set -e with post-increment operators causes script to abort on first passing test.
Lines 15, 18 (and 28, 31, 56, 59, 69, 72, 82, 85) use ((PASS++)) and ((FAIL++)) with set -euo pipefail enabled. In Bash arithmetic, post-increment ((var++)) when var=0 evaluates to 0, returning exit status 1. This immediately terminates the script under set -e before any test result is recorded.
Since PASS and FAIL initialize to 0 at the top of the script, the first passing assertion will trigger the abort, preventing the test suite from running.
🔧 Proposed fix
- ((PASS++))
+ PASS=$((PASS + 1))- ((FAIL++))
+ FAIL=$((FAIL + 1))📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| ((PASS++)) | |
| echo -e " \033[38;2;74;222;128m\033[1m✓\033[0m $description" | |
| else | |
| ((FAIL++)) | |
| PASS=$((PASS + 1)) | |
| echo -e " \033[38;2;74;222;128m\033[1m✓\033[0m $description" | |
| else | |
| FAIL=$((FAIL + 1)) |
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@scripts/sw-ping-test.sh` around lines 15 - 18, Replace all uses of the
post-increment arithmetic form that can return zero under set -e (e.g.
((PASS++)) and ((FAIL++))) with a form that performs the increment without
producing a zero exit status; for example change each ((PASS++)) to
PASS=$((PASS+1)) and each ((FAIL++)) to FAIL=$((FAIL+1)). Update every
occurrence of the PASS and FAIL increments in the script so the counters
increment reliably under set -euo pipefail.
| "$SCRIPT_DIR/sw-ping.sh" --invalid > /dev/null 2>&1 || local exit_code=$? | ||
| assert_exit_code 1 "${exit_code:-1}" "ping with invalid option exits with code 1" |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
cd scripts && head -100 sw-ping-test.sh | tail -15Repository: sethdford/shipwright
Length of output: 592
🏁 Script executed:
# Verify the exact bash behavior with the || local pattern
cat > /tmp/test_local_or.sh << 'EOF'
#!/bin/bash
# Test 1: Command exits 0 with || local var=$?
echo "Test 1: Command exits 0"
true || local exit_code=$?
echo "exit_code is: ${exit_code:-UNSET}"
# Test 2: Command exits non-zero with || local var=$?
echo -e "\nTest 2: Command exits 1"
false || local exit_code2=$?
echo "exit_code2 is: ${exit_code2:-UNSET}"
# Test 3: Proper pattern without local in compound
echo -e "\nTest 3: Proper pattern"
local exit_code3=0
false || exit_code3=$?
echo "exit_code3 is: $exit_code3"
EOF
bash /tmp/test_local_or.shRepository: sethdford/shipwright
Length of output: 351
🏁 Script executed:
# Read the exact lines from the file
sed -n '85,100p' scripts/sw-ping-test.sh | cat -nRepository: sethdford/shipwright
Length of output: 723
🏁 Script executed:
# More accurate test in function context
bash << 'EOF'
test_function() {
# Simulate command exiting 0
echo "Scenario 1: Command exits 0"
true || local exit_code=$?
echo " exit_code value: ${exit_code:-UNSET}"
echo " Would assert_exit_code compare: 1 vs ${exit_code:-1}"
# Simulate command exiting 1
echo ""
echo "Scenario 2: Command exits 1"
(exit 1) || local exit_code=$?
echo " exit_code value: ${exit_code:-UNSET}"
echo " Would assert_exit_code compare: 1 vs ${exit_code:-1}"
}
test_function
EOFRepository: sethdford/shipwright
Length of output: 248
Test can incorrectly pass when command returns 0.
When sw-ping.sh --invalid succeeds (exit code 0), the || local exit_code=$? clause doesn't execute, leaving exit_code unset. The default ${exit_code:-1} then masks this as 1, causing the assertion to pass when it should fail.
Initialize exit_code before the command and assign directly in the || clause:
Suggested fix
test_ping_invalid_option() {
- "$SCRIPT_DIR/sw-ping.sh" --invalid > /dev/null 2>&1 || local exit_code=$?
- assert_exit_code 1 "${exit_code:-1}" "ping with invalid option exits with code 1"
+ local exit_code=0
+ "$SCRIPT_DIR/sw-ping.sh" --invalid > /dev/null 2>&1 || exit_code=$?
+ assert_exit_code 1 "$exit_code" "ping with invalid option exits with code 1"
}📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| "$SCRIPT_DIR/sw-ping.sh" --invalid > /dev/null 2>&1 || local exit_code=$? | |
| assert_exit_code 1 "${exit_code:-1}" "ping with invalid option exits with code 1" | |
| test_ping_invalid_option() { | |
| local exit_code=0 | |
| "$SCRIPT_DIR/sw-ping.sh" --invalid > /dev/null 2>&1 || exit_code=$? | |
| assert_exit_code 1 "$exit_code" "ping with invalid option exits with code 1" | |
| } |
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@scripts/sw-ping-test.sh` around lines 92 - 93, The test captures the exit
code incorrectly so it can mask a succeeding command as failure; replace the
current one-liner that uses "|| local exit_code=$?" with a two-step capture: run
"$SCRIPT_DIR/sw-ping.sh" --invalid > /dev/null 2>&1 and immediately set local
exit_code=$? (so exit_code is always assigned), then call assert_exit_code 1
"${exit_code}" "ping with invalid option exits with code 1"; update the usage of
the exit_code variable and keep the assert_exit_code call as-is.
1 participant
Summary
Plan: Add
shipwright pingcommandWhat the plan covers
4 files touched, 10 tasks total:
sw-ping.sh(printspong, exits 0)scripts/sw-ping.sh(new)sw-ping-test.sh(6 tests)scripts/sw-ping-test.sh(new)PASS: 6 FAIL: 0ping)case to router afterhello)scripts/swbash scripts/sw ping→pongChanges
16 files changed, 16057 insertions(+), 1071 deletions(-)
8 commit(s) via
shipwright pipeline(standard)Test Results
Code review: 4 issues found
Developer simulation: 0 reviewer concerns pre-addressed
Architecture validation: 0 violations
standardGenerated by
shipwright pipelineSummary by CodeRabbit
New Features
pingcommand to the CLI that outputs "pong" and supports--helpand--versionflags.Tests