Build wisp ReleaseSafe for diagnosable crash traces

[wksantiago]

Closes #8

Summary by CodeRabbit

• Chores
  • Updated application build configuration to prioritize safety and stability over maximum performance during compilation.

[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: c3cc19f0-2fe9-4415-972b-2785de06cd6e

📥 Commits

Reviewing files that changed from the base of the PR and between 68cb256 and 9f8eedc.

📒 Files selected for processing (1)

• Dockerfile

---

Walkthrough

The Dockerfile's builder stage zig build command is changed from -Doptimize=ReleaseFast to -Doptimize=ReleaseSafe on line 41. All other build arguments and Dockerfile instructions remain unchanged.

Changes

Zig Build Optimization Mode

Layer / File(s)	Summary
Zig build flag: ReleaseFast → ReleaseSafe Dockerfile	The -Doptimize flag in the builder stage zig build invocation is changed from ReleaseFast to ReleaseSafe, enabling Zig runtime safety checks and panic traces in the produced binary.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐇 A single flag flipped, one word swapped in place,
From Fast to Safe, a more cautious race.
Now when a fault hides deep in the night,
A panic trace shines a diagnostic light.
Hop hop, little build — reveal your SIGSEGV's face! 🔍

🚥 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 accurately and concisely describes the main change: switching Zig build optimization from ReleaseFast to ReleaseSafe to enable crash diagnostics.
Linked Issues check	✅ Passed	The code change directly addresses issue #8's primary objective by modifying the Dockerfile to build wisp with ReleaseSafe optimization for diagnosable crash traces.
Out of Scope Changes check	✅ Passed	The pull request contains only the single, focused change to the build optimization flag as specified in issue #8, with no unrelated modifications.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

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

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix/wisp-releasesafe

---

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.}