fix(install): source the e2e test-mode marker so updater-triggered runs detect CI

[KrasimirKralev]

Problem

The e2e-install CI check fails intermittently with:

[5/18] Detecting WiFi interface...
Error: WiFi interface 'eth0' not found or not wireless.
clawbox-bootstrap.service: Main process exited, code=exited, status=1/FAILURE
install.sh: line N: nvpmodel: command not found
→ install.sh did not finish within 40 min

This is install.sh running the real Jetson/WiFi hardware path inside the non-Jetson CI container — it should be skipped under CLAWBOX_TEST_MODE=1.

Root cause

The e2e-install harness entrypoint seeds /etc/clawbox/test-mode.env (CLAWBOX_TEST_MODE=1 + NETWORK_INTERFACE=eth0) before any install runs, expecting install.sh to read it — its own comment says "so install.sh knows it's in test mode even before it has had a chance to write its own .env."

But install.sh never sourced that file. It read CLAWBOX_TEST_MODE only from its process environment. So:

• The first-boot bootstrap is fine — clawbox-bootstrap.service sets CLAWBOX_TEST_MODE=1 directly.
• But updater-triggered install.sh --step runs via clawbox-root-update@.service inherit only EnvironmentFile=-/etc/clawbox/network.env, which gets the flag late (only after step_network_setup persists it). Those runs execute with CLAWBOX_TEST_MODE=0 → real iw dev eth0 / nvpmodel / jetson_clocks → fail on the CI host.

That's the intermittency: whoever wins/loses the race on when the flag is present.

Fix

Source the seeded marker at install.sh startup (mirrors the existing source "$IFACE_ENV" a few lines below), so every invocation — bootstrap and updater-triggered — detects test mode up front. The file exists only in the CI container, so it's a no-op on real devices.

Validation

• bash -n install.sh clean.
• Simulated: with /etc/clawbox/test-mode.env present → CLAWBOX_TEST_MODE=1, NETWORK_INTERFACE=eth0; absent (real device) → CLAWBOX_TEST_MODE=0.
• The e2e-install check on this PR is the real end-to-end proof — it exercises exactly the updater path that was failing.

Summary by CodeRabbit

• Bug Fixes
  • Improved installer reliability in test environments by ensuring test mode is properly detected and hardware-dependent steps are appropriately skipped during installation.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: 142ac25b-2d88-41c0-81a1-22d8368f807b

📥 Commits

Reviewing files that changed from the base of the PR and between eeb6d37 and 8b8e107.

📒 Files selected for processing (1)

• install.sh

---

📝 Walkthrough

Walkthrough

install.sh gains a 13-line block that sources /etc/clawbox/test-mode.env early in execution, before CLAWBOX_TEST_MODE is set and is_test_mode() is defined, so CI test containers consistently activate test mode for all invocations including updater-triggered --step runs.

Changes

Early test-mode env bootstrap

Layer / File(s)	Summary
Early test-mode.env loader install.sh	Sources /etc/clawbox/test-mode.env when the file exists, injecting test-mode environment variables before any test-mode initialization logic runs in the installer.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

🐇 Hop, hop, before the gate swings wide,
A tiny env file slips inside.
No hardware tricks shall fool the test,
The CI bunny knows what's best!
Source it early, source it right — ✅

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Description check	❓ Inconclusive	The description provides comprehensive problem context, root cause analysis, and validation details, but lacks completion of the required PR description template sections.	Fill out the template sections including Type of change, How was this tested checkboxes, and the Checklist items to match repository standards.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and specifically describes the main change: sourcing the test-mode marker file to fix updater-triggered CI detection.
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 unit tests (beta)

• Create PR with unit tests

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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