chore: set dev profile debug to 1

[jdx]

Summary

Reduces target/ disk usage by setting [profile.dev] debug = 1, while keeping backtrace file:line info intact.

The default debug = 2 writes full DWARF — including variable/type info that's only needed when stepping through code in a debugger (lldb/gdb). With debug = 1, panics, RUST_BACKTRACE=1, and error chains still resolve to file:line; only debugger variable inspection is reduced.

In practice this typically shrinks target/ by a meaningful percentage, which adds up across worktrees.

Test plan

• cargo build still succeeds
• CI is green

---

This PR was generated by an AI coding assistant.

---

Note

Low Risk
Low risk build configuration tweak that only affects local dev compilation artifacts and debug symbol detail; no runtime logic changes.

Overview
Updates Cargo.toml to set [profile.dev] debug = 1, reducing debug info emitted in dev builds (smaller target/ output) while keeping basic file/line backtraces available.

^{Reviewed by Cursor Bugbot for commit b9e17c3. Bugbot is set up for automated code reviews on this repo. Configure here.}

[greptile-apps]

Greptile Summary

Sets [profile.dev] debug = 1 in Cargo.toml to reduce target/ directory size by omitting DWARF variable/type info while preserving file:line data for backtraces and panics. This is a well-understood Rust workspace optimization with no functional impact on test or release builds.

Confidence Score: 5/5

Safe to merge — minimal, correct config change with no runtime impact.

Single-line Cargo profile setting with well-documented semantics; no logic, no dependencies, no security surface. File:line backtrace info is preserved; only interactive debugger variable inspection is reduced.

No files require special attention.

Important Files Changed

Filename	Overview
Cargo.toml	Adds [profile.dev] debug = 1 to reduce DWARF output size; correct and non-breaking change.

_{Reviews (1): Last reviewed commit: "chore: set dev profile debug to 1" | Re-trigger Greptile}