mirror of
https://github.com/Kpa-clawbot/meshcore-analyzer.git
synced 2026-09-27 05:07:53 +00:00
Caught live on stg: after running the script for real, the one genuinely new area it added (SE12) never showed up as scoped via /api/config/areas, while all 14 "enriched" existing areas looked fine. Turned out those 14 already had a correct regionScopes array from earlier manual config work -- the script's regionScope (singular) write was dead data riding along next to it. SE12 had no prior regionScopes, so the script's only write landed on a field cmd/server/routes.go's handleConfigAreas never reads, leaving it silently unlinked. Now appends to regionScopes (preserving any other scopes already on the area) and drops a stray regionScope key if a prior buggy run left one. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>