{
  "context": "Evaluates how the solution leverages @fluidframework/container-loader audience presence APIs to build the presence tracker described in the spec. Emphasis is on sourcing membership from the container audience, reacting to join/leave events, and surfacing client metadata from the Fluid audience model.",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "Audience source",
      "description": "Obtains a real Fluid audience from the container (e.g., `container.audience`) rather than a custom store, passing that object into tracker setup.",
      "max_score": 15
    },
    {
      "name": "Initial snapshot",
      "description": "Seeds tracker state from `audience.getMembers()` so preexisting participants appear in `getActiveMembers` before new events arrive.",
      "max_score": 25
    },
    {
      "name": "Join/leave events",
      "description": "Subscribes to `audience.on('addMember')` and `audience.on('removeMember')` (and unsubscribes via `off`/`removeListener`) to emit ordered join/leave events that keep tracker state in sync.",
      "max_score": 30
    },
    {
      "name": "Member lookup",
      "description": "Uses audience lookups (`audience.getMember(clientId)` or `getMembers()[clientId]`) to resolve the latest metadata when serving `getMember` calls instead of duplicating stale copies.",
      "max_score": 15
    },
    {
      "name": "Metadata fidelity",
      "description": "Propagates Fluid audience member metadata (e.g., `mode`, `capabilities`, `client.details`) into emitted events and snapshots so consumers can distinguish agent vs. human clients.",
      "max_score": 15
    }
  ]
}