fix(config): correct DefaultMode semantics and default to real weights

[Copilot]

The DefaultMode configuration field had an inverted comment ("false = test mode") and both environments defaulted to test mode with simulated weights instead of reading from actual hardware.

Configuration Changes:

• Fixed DefaultMode comment to reflect actual semantics: true = test mode (simulated weights), false = real weights
• Changed both local and remote environments to DefaultMode: false for real scale readings by default

// Before
DefaultMode bool // false = test mode (simulated weights)
// ...
"remote": {
    DefaultMode: true,  // Defaults to test mode
},

// After  
DefaultMode bool // true = test mode (simulated weights), false = real weights
// ...
"remote": {
    DefaultMode: false,  // Defaults to real weights
},

Both deployment environments now read from actual scale hardware by default, with test mode available via runtime configuration updates when needed.

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[Copilot]

Pull request overview

Corrects the meaning of the DefaultMode configuration flag and updates environment defaults so the daemon starts in real hardware mode rather than simulated/test mode.

Changes:

• Fix Environment.DefaultMode comment to match actual behavior (true = test/simulated, false = real hardware).
• Change both remote and local environment defaults to DefaultMode: false (real weights by default).

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[adcondev]

nice