Add email_verified field to user response and update shared repo docs (#68)

## Summary

This PR introduces the `email_verified` field to the `UserResponse`
model and updates documentation for shared repository endpoints across
the graphs and service offerings APIs.

## Key Accomplishments

- **User Response Model Enhancement**: Extended `UserResponse` model
with a new `email_verified` attribute, providing visibility into whether
a user's email address has been verified. This adds an important field
for downstream consumers that need to make authorization or display
decisions based on email verification status.

- **Documentation Updates for Shared Repositories**: Updated docstrings
and parameter documentation in both `get_graphs` and
`get_service_offerings` API modules to clarify behavior related to
shared repositories, ensuring consistency and accuracy across the client
library.

## Changes Breakdown

| Area | Change |
|------|--------|
| `models/user_response.py` | Added `email_verified` field (+13/-2
lines), including type annotation and serialization support |
| `api/graphs/get_graphs.py` | Updated documentation for shared
repository parameters (+4/-4 lines) |
| `api/service_offerings/get_service_offerings.py` | Updated
documentation for shared repository parameters (+4/-4 lines) |

## Breaking Changes

- **Potential minor impact**: Consumers that perform strict schema
validation on `UserResponse` may need to account for the new
`email_verified` field. However, since this is an additive change, most
clients should handle it gracefully.

## Testing Notes

- Verify that the `UserResponse` model correctly deserializes API
responses that include the `email_verified` field
- Confirm backward compatibility when the field is absent from older API
responses (ensure proper default/optional handling)
- Validate that the graphs and service offerings endpoints continue to
function correctly with the updated parameter documentation

## Infrastructure Considerations

- No infrastructure changes required
- API consumers should be aware of the new field availability for any
email verification workflows
- Client library version should be bumped appropriately to signal the
model enhancement to downstream users

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

**Branch Info:**
- Source: `feature/user-email-verified`
- Target: `main`
- Type: feature

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

Author: jfrench9

robosystems_client/api/graphs/get_graphs.py

@@ -72,7 +72,7 @@ def sync_detailed(
   - Graphs you create or have been invited to
 
   **Shared Repositories (isRepository: true):**
-  - Read-only data repositories like SEC filings, industry benchmarks
+  - Read-only data repositories (e.g., SEC filings)
   - Access levels: `read`, `write` (for data contributions), `admin`
   - Cannot be selected (each has separate subscription)
   - Require separate subscriptions (personal, cannot be shared)
@@ -137,7 +137,7 @@ def sync(
   - Graphs you create or have been invited to
 
   **Shared Repositories (isRepository: true):**
-  - Read-only data repositories like SEC filings, industry benchmarks
+  - Read-only data repositories (e.g., SEC filings)
   - Access levels: `read`, `write` (for data contributions), `admin`
   - Cannot be selected (each has separate subscription)
   - Require separate subscriptions (personal, cannot be shared)
@@ -198,7 +198,7 @@ async def asyncio_detailed(
   - Graphs you create or have been invited to
 
   **Shared Repositories (isRepository: true):**
-  - Read-only data repositories like SEC filings, industry benchmarks
+  - Read-only data repositories (e.g., SEC filings)
   - Access levels: `read`, `write` (for data contributions), `admin`
   - Cannot be selected (each has separate subscription)
   - Require separate subscriptions (personal, cannot be shared)
@@ -261,7 +261,7 @@ async def asyncio(
   - Graphs you create or have been invited to
 
   **Shared Repositories (isRepository: true):**
-  - Read-only data repositories like SEC filings, industry benchmarks
+  - Read-only data repositories (e.g., SEC filings)
   - Access levels: `read`, `write` (for data contributions), `admin`
   - Cannot be selected (each has separate subscription)
   - Require separate subscriptions (personal, cannot be shared)

robosystems_client/api/service_offerings/get_service_offerings.py

@@ -69,7 +69,7 @@ def sync_detailed(
 
   Includes:
   - Graph infrastructure tiers (ladybug-standard, ladybug-large, ladybug-xlarge) - per-graph pricing
-  - Shared repository subscriptions (SEC, industry, economic data) - org-level
+  - Shared repository subscriptions - org-level
   - Operation costs and credit information
   - Features and capabilities for each tier
   - Enabled/disabled status for repositories
@@ -115,7 +115,7 @@ def sync(
 
   Includes:
   - Graph infrastructure tiers (ladybug-standard, ladybug-large, ladybug-xlarge) - per-graph pricing
-  - Shared repository subscriptions (SEC, industry, economic data) - org-level
+  - Shared repository subscriptions - org-level
   - Operation costs and credit information
   - Features and capabilities for each tier
   - Enabled/disabled status for repositories
@@ -157,7 +157,7 @@ async def asyncio_detailed(
 
   Includes:
   - Graph infrastructure tiers (ladybug-standard, ladybug-large, ladybug-xlarge) - per-graph pricing
-  - Shared repository subscriptions (SEC, industry, economic data) - org-level
+  - Shared repository subscriptions - org-level
   - Operation costs and credit information
   - Features and capabilities for each tier
   - Enabled/disabled status for repositories
@@ -201,7 +201,7 @@ async def asyncio(
 
   Includes:
   - Graph infrastructure tiers (ladybug-standard, ladybug-large, ladybug-xlarge) - per-graph pricing
-  - Shared repository subscriptions (SEC, industry, economic data) - org-level
+  - Shared repository subscriptions - org-level
   - Operation costs and credit information
   - Features and capabilities for each tier
   - Enabled/disabled status for repositories

robosystems_client/models/user_response.py

@@ -21,19 +21,21 @@ class UserResponse:
 
   Example:
       {'accounts': [{'provider': 'github', 'provider_account_id': '12345', 'provider_type': 'oauth'}, {'provider':
-          'google', 'provider_account_id': '67890', 'provider_type': 'oauth'}], 'email': 'john@example.com', 'id':
-          'user-123', 'name': 'johndoe'}
+          'google', 'provider_account_id': '67890', 'provider_type': 'oauth'}], 'email': 'john@example.com',
+          'email_verified': True, 'id': 'user-123', 'name': 'johndoe'}
 
   Attributes:
       id (str): Unique identifier for the user
       name (None | str | Unset): User's display name
       email (None | str | Unset): User's email address
+      email_verified (bool | Unset): Whether user's email is verified Default: False.
       accounts (list[AccountInfo] | Unset): User's authentication accounts
   """
 
   id: str
   name: None | str | Unset = UNSET
   email: None | str | Unset = UNSET
+  email_verified: bool | Unset = False
   accounts: list[AccountInfo] | Unset = UNSET
   additional_properties: dict[str, Any] = _attrs_field(init=False, factory=dict)
 
@@ -52,6 +54,8 @@ def to_dict(self) -> dict[str, Any]:
     else:
       email = self.email
 
+    email_verified = self.email_verified
+
     accounts: list[dict[str, Any]] | Unset = UNSET
     if not isinstance(self.accounts, Unset):
       accounts = []
@@ -70,6 +74,8 @@ def to_dict(self) -> dict[str, Any]:
       field_dict["name"] = name
     if email is not UNSET:
       field_dict["email"] = email
+    if email_verified is not UNSET:
+      field_dict["email_verified"] = email_verified
     if accounts is not UNSET:
       field_dict["accounts"] = accounts
 
@@ -100,6 +106,8 @@ def _parse_email(data: object) -> None | str | Unset:
 
     email = _parse_email(d.pop("email", UNSET))
 
+    email_verified = d.pop("email_verified", UNSET)
+
     _accounts = d.pop("accounts", UNSET)
     accounts: list[AccountInfo] | Unset = UNSET
     if _accounts is not UNSET:
@@ -113,6 +121,7 @@ def _parse_email(data: object) -> None | str | Unset:
       id=id,
       name=name,
       email=email,
+      email_verified=email_verified,
       accounts=accounts,
     )