chore: archive add-graphql-tools change

Archive completed change proposal to openspec/changes/archive/.
Updated specs with new GraphQL introspection and MCP tool requirements:

- graphql-api: Added GraphQL Introspection Support requirement
- mcp-integration: Added 3 requirements for GraphQL tools
  - Get GraphQL Schema Tool
  - Execute GraphQL Query Tool
  - Tool Input Schema for GraphQL Execution

All requirements include comprehensive scenarios and are now part
of the active specification.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>

openspec/specs/graphql-api/spec.md

@@ -303,3 +303,26 @@ The system MUST provide clear, actionable error messages for validation failures
 **And** client receives generic "Internal server error" message
 **And** HTTP status code is 500
 
+### Requirement: GraphQL Introspection Support
+The GraphQL API SHALL support introspection queries that enable clients to discover the complete schema dynamically.
+
+#### Scenario: Introspection query returns schema types
+- **GIVEN** the GraphQL API is running
+- **WHEN** a client executes an introspection query for `__schema`
+- **THEN** the response SHALL include all types defined in the schema
+- **AND** include queries, mutations, and object types
+- **AND** include field names, types, and descriptions
+
+#### Scenario: Introspection query returns type details
+- **GIVEN** the GraphQL API is running
+- **WHEN** a client executes an introspection query for `__type(name: "Member")`
+- **THEN** the response SHALL include complete Member type details
+- **AND** include all fields with their types
+- **AND** include field descriptions where defined
+
+#### Scenario: Introspection is enabled by default
+- **GIVEN** the Strawberry GraphQL schema is configured
+- **WHEN** the schema is created
+- **THEN** introspection SHALL be enabled
+- **AND** the `__schema` and `__type` queries SHALL be available
+