0 Fork 0

mirror of https://github.com/Kpa-clawbot/meshcore-analyzer.git synced 2026-11-11 11:57:57 +00:00

Files

T

n30nex 23f938d1d4 docs: consolidate historical release notes (#2313 )

Fixes #2311. Partial follow-up to #1385 (PR-B).

Five historical release notes lived outside `docs/release-notes/`. Move
v2.6.0, v3.0.0, v3.1.0, v3.4.0 and v3.6.0 into that directory using its
existing version naming convention.

Release content is preserved except for concise historical notices and
four relative-link repairs. The v3.0.0 notice identifies its obsolete
Node rollback instructions; current setup links point to README and
DEPLOY. No new documentation hierarchy or index is introduced.

Validation: all five moves are one-to-one; every document matches its
original bytes after only the listed edits; all 14 local Markdown links
resolve; no old-path references remain. Existing external links are
unchanged. All 218 standalone frontend suites pass. The unchanged
backend tree passed full server/ingestor suites, and the unchanged app
passed 12 browser smoke cases.

All five published documents were rendered in Chromium; historical
notices and repaired link targets were verified. Three independent
reviews passed.

TDD exemption: pure documentation; no application, test, CI,
configuration or deployment behavior changed. No settings/customizer
implications. [CI
passed](https://github.com/Kpa-clawbot/CoreScope/actions/runs/40230718673);
its docs-only classification correctly skipped application jobs. The
full-suite results above are local validation.

2026-10-26 15:40:38 +01:00

2.9 KiB

Raw Blame History

CoreScope v3.4 Release Notes

Historical release notes. Features and instructions below describe this release. For current setup and deployment, see the README and deployment guide.

The neighbor affinity release. CoreScope now understands how nodes relate to each other — not just that they exist, but how strongly they're connected. This powers smarter hop resolution, richer node detail pages, and a new graph visualization in analytics.

🎯 Features

Neighbor Affinity System (7 milestones)

A complete neighbor relationship engine, from backend graph building to frontend visualization:

Affinity graph builder — computes neighbor relationships and connection strength from packet traffic (#507)
Affinity API endpoints — REST endpoints to query neighbor data (#508)
Show Neighbors via affinity API — the existing Show Neighbors feature now uses real affinity data instead of raw packet heuristics (#512, fixes #484)
Affinity-aware hop resolution — hop resolver uses neighbor affinity to pick better paths (#511)
Node detail neighbors section — dedicated neighbors panel on the node detail page (#510)
Affinity debugging tools — inspect and troubleshoot affinity calculations (#521)
Neighbor graph visualization — interactive neighbor graph in the analytics tab (#513)

Customizer v2

Event-driven state management replaces the old imperative approach — cleaner, more predictable theme/config updates (#503)

🐛 Bug Fixes

Stale parsed cache on observation packets — observation packets now correctly invalidate the JSON parse cache (#505)
Null-guard rAF callbacks — live page no longer crashes when requestAnimationFrame callbacks fire after cleanup (#506)
Customizer v2 phantom overrides — fixed phantom config entries, missing defaults, and stale dark mode state (#520)
Neighbor affinity empty results — fixed pubKey field name mismatch causing empty affinity graphs (#524)
Home defaults in server theme — server-side theme config now includes home page defaults (#526)
Neighbor UI crash + dark mode — fixed Show Neighbors crash and improved dark mode contrast (#527)
Home page steps + FAQ — both steps AND FAQ now render correctly on the home page (#529)

⚡ Performance

Cached JSON.parse for packet data — packet payloads are parsed once and cached, avoiding redundant JSON.parse calls on repeated access (#400)

Known Limitations

Affinity graph scales with traffic volume — networks with very low packet rates may show weak or missing neighbor relationships until enough data accumulates
Debugging tools are developer-facing — the affinity debug panel (#521) is functional but not polished for end-user consumption
Customizer v2 migration — custom themes saved under v1 may need to be re-applied after upgrade

2.9 KiB Raw Blame History