Add "A primitive's groups list as an array of Group instances not names" bullet to the Alternatives Considered section

Author: cliffhall

seps/2084-primitive-groups.md

@@ -206,7 +206,7 @@ This specification proposal was selected for its ease of understanding since it
   Since this proposal spans all primitives, such a compatibility failure would be catastrophic.
 
 
-- **A primitive's groups list as an array of Group instances not names:** A variation of the proposed specification, but the schema would reference the Groups definition instead of being a string (group name). This means that full Group instances would appear in the primitive's group list, significantly increasing the token count when passed to an LLM without modification. Also, beacuse groups can be hierarchical, every child of a given group would carry a duplicate of the parent instance. There was discussion of mitigating the duplication on the line using libraries that perform a marshalling on send/receive, replacing the parent with a pointer to a single copy of the parent instance. This appeared to be unnecessary effort for no clear benefit, when a client can easily look up a group by name in the `groups/list` result.
+- **A primitive's groups list as an array of Group instances not names:** A variation of the proposed specification, but the schema would reference the Groups definition instead of declaring a string (group name). This means that full Group instances would appear in the primitive's group list, significantly increasing the token count when passed to an LLM without modification. Also, beacuse groups can be hierarchical, every child of a given group would carry a duplicate of the parent instance. There was discussion of mitigating the duplication on the line using libraries that perform a marshalling on send/receive, replacing the parent with a pointer to a single copy of the parent instance. This appeared to be unnecessary effort for no clear benefit, when a client can easily look up a group by name in the `groups/list` result.
 
 
 - **Groups as MCP Resources instead of new primitive:** A completely separate proposal where the group metadata is declared in MCP resources with a specific schema and mimeType, referenced by their URIs, e.g., `mcp://groups/{groupId}`. Servers MAY publish the group index at a URI which MUST be defined in the capabilities object during the server initialization. This proposal could reduce spec changes and implementation effort significantly, but it was not considered as intuitive.