3 Commits

Author SHA1 Message Date
Kpa-clawbot
cdcaa476f2 rename: MeshCore Analyzer → CoreScope (Phase 1 — backend + infra)
Rename product branding, binary names, Docker images, container names,
Go modules, proto go_package, CI, manage.sh, and documentation.

Preserved (backward compat):
- meshcore.db database filename
- meshcore-data / meshcore-staging-data directory paths
- MQTT topics (meshcore/#, meshcore/+/+/packets, etc.)
- proto package namespace (meshcore.v1)
- localStorage keys

Changes by category:
- Go modules: github.com/corescope/{server,ingestor}
- Binaries: corescope-server, corescope-ingestor
- Docker images: corescope:latest, corescope-go:latest
- Containers: corescope-prod, corescope-staging, corescope-staging-go
- Supervisord programs: corescope, corescope-server, corescope-ingestor
- Branding: siteName, heroTitle, startup logs, fallback HTML
- Proto go_package: github.com/corescope/proto/v1
- CI: container refs, deploy path
- Docs: 8 markdown files updated

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
2026-03-28 14:08:15 -07:00
Kpa-clawbot
3c53680e7c fix: resolve 24 proto definition mismatches against Node fixtures
fixes #164

Mismatches fixed:
- analytics-channels: ChannelAnalyticsSummary.hash string -> int32
- analytics-rf: PayloadTypeEntry.type -> optional int32 (can be null)
- bulk-health: flatten BulkHealthEntry (remove .node nesting)
- node-analytics: TimeBucket field label -> bucket (keep both as optional)
- observer-analytics: recentPackets Transmission -> Observation
- packet-detail: ByteRange add string color field
- websocket-message: DecodedResult add transportCodes, raw, routeTypeName;
  flatten payload to DecodedFlatPayload; packet -> Observation
- validate-protos: bare-array wrapping note downgraded to WARNING

Validator now reports 0 errors across all 33 fixtures.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
2026-03-27 14:52:02 -07:00
Kpa-clawbot
0775302c95 Add protobuf definitions for all API responses and WebSocket messages
Define .proto files as single source of truth for the API contract.
10 files covering all 40 endpoints from docs/api-spec.md:

  proto/common.proto     - Pagination, Histogram, RoleCounts, SignalStats
  proto/decoded.proto    - DecodedResult, DecodedPayload oneof (10 payload types)
  proto/packet.proto     - Transmission, Observation, GroupedPacket, traces, audio-lab
  proto/node.proto       - Node, BulkHealth, NodeAnalytics, ResolveHops
  proto/observer.proto   - Observer, ObserverAnalytics
  proto/channel.proto    - Channel, ChannelMessage
  proto/analytics.proto  - RF, Topology, Distance, HashSizes, Subpaths
  proto/websocket.proto  - WSMessage, WSPacketData
  proto/stats.proto      - Stats, Health, Perf
  proto/config.proto     - Theme, Regions, ClientConfig, MapConfig, IataCoords

DRY composition:
- Node defined once (node.proto), reused in 8 response types
- Transmission defined once (packet.proto), reused in 5 response types
- Observation defined once (packet.proto), reused in detail + analytics
- DecodedPayload uses oneof for ADVERT/TXT_MSG/GRP_TXT/ACK/REQ/etc.
- Shared types: Histogram, SignalStats, TimeBucket, RoleCounts
- NodeObserverStats/NodeStats shared across bulk-health, node-health, analytics

All files validated with protoc. proto3 syntax, package meshcore.v1,
go_package github.com/meshcore-analyzer/proto/v1, json_name annotations
where proto3 default camelCase differs from API spec.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
2026-03-27 14:13:59 -07:00