{
  "context": "Evaluates whether the solution uses pynetworktables to configure identity first, start server/client roles, verify connectivity, and reset cleanly. Focuses strictly on built-in connection APIs instead of custom networking logic.",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "Identity set",
      "description": "Calls networktables setNetworkIdentity (on the default or chosen NetworkTablesInstance) before starting any server/client mode and preserves the value for later state reporting.",
      "max_score": 20
    },
    {
      "name": "Server startup",
      "description": "Uses startServer with the provided persist file, listen address, and port to enter server mode instead of custom sockets, and verifies mode via isServer or getNetworkMode.",
      "max_score": 25
    },
    {
      "name": "Client connect",
      "description": "Starts client mode with startClient (or startClientTeam when given a team number) using the provided targets, then relies on isConnected or getConnections to confirm the handshake instead of manual polling.",
      "max_score": 25
    },
    {
      "name": "Connection snapshot",
      "description": "Builds connection_state using package data sources like getConnections and getRemoteAddress together with isConnected to populate remotes, mode, and connected flags (not cached guesses).",
      "max_score": 20
    },
    {
      "name": "Clean reset",
      "description": "Stops activity with stopClient/stopServer and shutdown when resetting, ensuring pending traffic is flushed if needed, rather than leaving threads or sockets running.",
      "max_score": 10
    }
  ]
}