NicandClaude Opus 5 452a428737 Report what ensureConfig actually did, instead of claiming a write ...

The RNS constructor logged "creating config in .reticulum" unconditionally,
immediately before a call that writes only when the config is missing or
reticulumRegenerateConfigOnRestart is set. On every ordinary start the very next
line — the library's own "Config loaded from .reticulum/config.yml" — said the
opposite, and the branch that was actually taken logged "Reticulum config
exists, skipping." at DEBUG, i.e. invisible at the default level.

The claim moves into RNSConfigWriter.ensureConfig, which knows which of its
three branches it took, and all three are INFO — this runs once per start, and
"your edits were left alone" is the case an operator most needs to confirm:

  Reticulum config exists at … — leaving it as-is
  Writing new Reticulum config to …
  Regenerating Reticulum config at … (reticulumRegenerateConfigOnRestart is set)

Registered as §9 item 23. §11.2 check 1 named the old DEBUG string as a thing to
look for on a node run, so it is updated too — it had been asking for a line that
could not appear at INFO.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

2026-08-13 14:02:14 +02:00

..

RNS_analysis.md

Refactoring documents

2026-08-11 17:06:41 +02:00

RNS_implementation.md

Report what ensureConfig actually did, instead of claiming a write

2026-08-13 14:02:14 +02:00