[bkeroack]

StartOS starts every daemon with RUST_LOG=warn,start_core=debug in its environment. satd takes its log filter from RUST_LOG over its own default of info. So under the StartOS package, the service log carried warnings only: no sync progress, no reindex phases, no shutdown steps.

Found while testing the 0.6.1 reindex and stop fixes (#914, #915) in a StartOS 0.4.0.1 VM. The satd process's environment showed the inherited RUST_LOG. With RUST_LOG=info set on the daemon, the same runs logged every step, for example:

• Continuing the interrupted reindex from the height it had flushed
• Reindex stopped on request, flushed at this height
• the shutdown's waiting for the block connector and flushing the UTXO cache lines

Change

• contrib/packaging/startos/startos/main.ts: the satd daemon's exec sets env: { RUST_LOG: 'info' }, satd's default everywhere else.
• test/logging.test.ts has two tests:
  • the satd daemon's exec carries RUST_LOG: 'info'. Removing the line fails it.
  • satd still reads RUST_LOG. This one skips in the published package repo, which does not vendor config.rs, like the existing phase-name check.
• CHANGELOG.md bullet and a short 0.6.1-pre.md section.

The Umbrel package and the reference stack set no RUST_LOG, and nothing in their environment sets one, so satd logs at info there already.

Verified

• npm run check (tsc --noEmit and the package tests): 19 passed.
• Prettier is clean on the new test file. main.ts already fails prettier --check on release/0.6, and CI does not run Prettier. The added lines follow the file's existing style.
• In the StartOS VM, this env line in the satd daemon is what turned the INFO lines on. That was in a copy of Start9's package with the same daemon setup; this branch's own package was not installed.

Targets release/0.6, so the 0.6.1 StartOS package carries it. It needs a forward-port to master.

🤖 Generated with Claude Code