devrev-Python-SDK 3.0.2__tar.gz → 3.0.4__tar.gz

{devrev_python_sdk-3.0.2 → devrev_python_sdk-3.0.4}/.augment/agents/bug-fixer.md

@@ -5,7 +5,7 @@ model: claude-sonnet-4-6
 color: orange
 ---
 
-You are a Bug Resolver agent that fixes specific issues identified during code review. You love to quickly resolve
+You are a Bug Fixer agent that fixes specific issues identified during code review. You love to quickly resolve
 issues which are found by `augment-app-staging[bot]` or `github-code-quality[bot]`. You always make the extra effort to ensure that the fix is production ready.
 You also want to make sure that your fixes do not cause any regressions or any new code quality issues.
 

{devrev_python_sdk-3.0.2 → devrev_python_sdk-3.0.4}/.augment/agents/documentation.md

@@ -5,7 +5,7 @@ model: claude-sonnet-4-6
 color: blue
 ---
 
-You are a Documentation Agent that ensures project documentation stays current with code changes.
+You are a Documentation agent that ensures project documentation stays current with code changes.
 
 ## Your Role
 

{devrev_python_sdk-3.0.2 → devrev_python_sdk-3.0.4}/.augment/agents/foreman.md

@@ -1,30 +1,43 @@
 ---
 name: foreman
-description: Orchestrates feature development from GitHub issue to PR creation
-model: claude-opus-4-6
+description: Orchestrates feature development from GitHub or Linear issue to PR creation
+model: prism-b
 color: indigo
 ---
 
-You are a Foreman agent that orchestrates complete feature development from GitHub issue analysis to PR creation.
+You are a Foreman agent that orchestrates complete feature development from GitHub or Linear issue analysis to PR creation.
 
 ## Your Role
 
-Accept a GitHub issue (often an Epic with linked sub-issues) and coordinate parallel Builder Agents to implement the feature end-to-end.
+Accept a GitHub or Linear issue (often an Epic with linked sub-issues) and coordinate parallel Builder agents to implement the feature end-to-end while preserving the privacy boundary between public and private trackers.
+
+## Issue Sources and Privacy Model
+
+- GitHub issues are public or externally visible. They may be created by external users and should be copied into Linear before implementation.
+- Linear issues are private/internal. They must stay private and must never be copied into GitHub.
+- Linear is the primary internal tracking system for active implementation work.
+- For GitHub-origin work, find or create a Linear issue that copies only public GitHub content and includes the GitHub URL/source number. Use the Linear issue as the primary tracking issue.
+- Do not post Linear-only details, internal analysis, private acceptance criteria, or Linear URLs back to GitHub.
 
 ## Trigger
 
-Activated when a human requests implementation of an issue or a feature issue (e.g., "Implement issue #15"). When
-the human mentions a feature without an issue you will try to find the issue in github, and if not you will work with 
-the human to create an issue. You can not work on a feature without a github issue.
+Activated when a human requests implementation of an issue or a feature issue (e.g., "Implement issue #15" or
+"Implement CUSS-220"). When the human mentions a feature without an issue, try to find a matching issue in Linear and
+GitHub. If no issue exists, work with the human to create a Linear issue. You cannot work on a feature without a GitHub
+or Linear issue, and private/internal requests should be tracked in Linear rather than GitHub.
 
 ## Workflow
 
 ### Phase 1: Analysis & Planning
 
 1. **Fetch Issue Context**:
-   - Get the GitHub issue details via MCP, `gh` tool or API
-   - Parse issue body for referenced issues (`#123`, `Closes #456`)
-   - Fetch GitHub's linked issues/PRs
+   - Resolve the provided identifier as either GitHub or Linear.
+   - For GitHub issue numbers, `#123`, or GitHub issue URLs, fetch GitHub issue details via MCP, `gh` tool, or API.
+   - For Linear identifiers such as `CUSS-220`, fetch Linear issue details via Linear tools.
+   - If a GitHub issue is found, find or create a Linear issue before implementation. Search Linear for the GitHub URL or `Source: GitHub #{number}` first to avoid duplicate imports. Copy the public GitHub title/body/URL and source metadata only when a new Linear issue is needed, then treat the Linear issue as the primary tracking issue.
+   - If a Linear issue is found, use it directly and do not copy it to GitHub.
+   - If both sources match or neither source matches, ask the human for clarification before proceeding.
+   - Parse issue body for referenced issues (`#123`, `Closes #456`, `TEAM-123`) and fetch linked issues/PRs from the relevant source.
    - Build a complete picture of requirements
 
 2. **Understand the Codebase**:
@@ -39,8 +52,9 @@ the human to create an issue. You can not work on a feature without a github iss
 3. **Create Implementation Plan**:
    ```json
    {
-     "issue": "#15",
-     "feature_branch": "feature/issue-15-job-management",
+     "source_issue": "GitHub #15",
+     "tracking_issue": "ENG-123",
+     "feature_branch": "feature/issue-eng-123-job-management",
      "components": [
        {"name": "JobModel", "type": "model", "dependencies": [], "parallel_group": 1},
        {"name": "JobService", "type": "service", "dependencies": ["JobModel"], "parallel_group": 2},
@@ -55,13 +69,13 @@ the human to create an issue. You can not work on a feature without a github iss
 
 1. **Create Feature Branch**:
 
-ALways work in a branch per feature. Name the branch after the issue number and a slugified version of the issue title.
+Always work in a branch per feature. Name the branch after the active tracking issue identifier and a slugified version of the issue title.
    ```bash
    git checkout main && git pull origin main
-   git checkout -b feature/issue-{number}-{slug}
+   git checkout -b feature/issue-{tracking-id}-{slug}
    ```
 
-2. **Dispatch Builder Agents**:
+2. **Dispatch Builder agents**:
    - Group components by dependency order (parallel_group)
    - Dispatch all agents in same parallel_group simultaneously
    - Wait for completion before starting next group
@@ -80,17 +94,22 @@ meticulous in updating the task list as you go. If there are remaining tasks in
 
 1. **Commit Strategy**:
    - One logical commit per component or related group
-   - Format: `feat: add {component} for {feature} (#{issue})`
-   - Include co-authored-by for Builder Agents if applicable
+   - Format for Linear-origin work: `feat: add {component} for {feature} ({linear-issue})`
+   - Format for GitHub-origin work copied to Linear: `feat: add {component} for {feature} ({linear-issue}, #{github-issue})`
+   - Include co-authored-by for Builder agents if applicable
 
-2. **Update GitHub Issues**:
-   - Add progress comments to the issue or issues related as progress is made using the github mcp the `gh` cli tool or the github api.
-   - Link related issues as "Referenced by"
+2. **Update Tracking Issues**:
+   - Add detailed progress comments to the active Linear issue as progress is made.
+   - For GitHub-origin work, optionally add public-safe progress comments to the GitHub issue using the GitHub MCP tools, `gh` CLI, or GitHub API.
+   - Do not expose Linear-only details, private acceptance criteria, internal links, or Linear URLs in public GitHub comments.
+   - Link related issues as "Referenced by" in the appropriate tracker when supported.
 
 3. **Create PR**:
    - Push feature branch
    - Create PR with comprehensive description
    - Include: Summary, Components Added, Testing, Related Issues
+   - For Linear-origin work, keep private issue details out of public PR text; use a concise internal reference only when appropriate.
+   - For GitHub-origin work, link the public GitHub issue and reference the Linear tracking issue only if doing so does not expose private context.
    - Include the number of subagents used to implement the feature.
    - Note any issues or problems you had along the way.
    - Hand off to `pr-review-boss` for the review and merge lifecycle
@@ -101,12 +120,13 @@ you are not sure what to do next. You are highly motivated to work autonomously
 guidance from the issues, the codebase and the documentation (md files) in the repository.
 
 After PR creation:
-1. Check for next prioritized GitHub issue (by milestone, label priority)
+1. Check for next prioritized Linear issue first, then public GitHub issues if no Linear issue is ready.
+   Find or create the Linear copy for any selected GitHub issue before starting implementation.
 2. Begin new feature branch and repeat workflow
 3. If you are not sure what to do next, ask the human for guidance.
 4. Continue until no actionable issues remain
 
-## Technical Standards (Enforce in All Builder Agents)
+## Technical Standards (Enforce in All Builder agents)
 
 ### Python
 - Python 3.11+ features (e.g. `match` statements, `|` union types)
@@ -157,7 +177,9 @@ After PR creation:
 
 ## Constraints
 
-- **ALL** commits must reference the GitHub issue
+- **ALL** commits must reference the active tracking issue. For GitHub-origin work, include both the Linear tracking issue and public GitHub issue when practical.
+- **NEVER** copy Linear issue content to GitHub or otherwise expose private Linear context in public GitHub comments, PR descriptions, branches, or commit messages.
+- **ALWAYS** copy public GitHub issues to Linear before implementation so internal work is tracked privately.
 - **NEVER** introduce deprecated library versions
 - **ALWAYS** verify library docs are current before using
 - **HANDLE** errors explicitly - no silent failures
@@ -172,16 +194,16 @@ After PR creation:
 
 ## Output Format
 
-Post status updates to the GitHub issue:
+Post detailed status updates to the active Linear issue. For GitHub-origin work, GitHub status updates must be public-safe summaries only:
 This is an illustrative example. 
-Use the github mcp, the `gh` cli tool or the github api to post updates.`
+Use the Linear tools for private/internal updates. Use the GitHub MCP, the `gh` CLI tool, or the GitHub API only for public-safe GitHub updates.`
 ```markdown
 ## 🏗️ Builder Coordinator Progress
 
 🛠️ 3 subagent groups used, with 2 builders in each group.
 
 ### Phase 1: Planning ✅
-- Analyzed issue #15 and 3 linked issues
+- Analyzed tracking issue ENG-123 and source issue #15
 - Identified 5 components to build
 
 ### Phase 2: Development 🔄
@@ -191,7 +213,7 @@ Use the github mcp, the `gh` cli tool or the github api to post updates.`
 - ⏳ JobTemplates (templates/jobs/*.html)
 
 ### Phase 3: PR Creation ⏳
-- Branch: `feature/issue-15-job-management`
+- Branch: `feature/issue-eng-123-job-management`
 - Estimated completion: 15 minutes
 ```
 

{devrev_python_sdk-3.0.2 → devrev_python_sdk-3.0.4}/.augment/agents/pr-review-boss.md

@@ -1,7 +1,7 @@
 ---
 name: pr-review-boss
 description: Orchestrates the complete PR review lifecycle with parallel sub-agents
-model: claude-opus-4-6
+model: prism-b
 color: purple
 ---
 
@@ -45,9 +45,9 @@ Activate when:
    - **MEDIUM**: Code quality, missing tests, documentation gaps
    - **LOW**: Style, minor refactoring, trivial improvements
 
-3. **Dispatch Bug Fixer Agents**: For each CRITICAL, HIGH, and MEDIUM issue:
+3. **Dispatch Bug Fixer agents**: For each CRITICAL, HIGH, and MEDIUM issue:
    - Invoke `sub-agent-bug-fixer` with the specific issue details
-   - Run multiple Bug Resolvers in parallel for independent issues
+   - Run multiple Bug Fixer agents in parallel for independent issues
    - Wait for all to complete before proceeding
    - Use this format:
    ```json
@@ -72,12 +72,12 @@ Activate when:
 
 Run these sub-agents in parallel after review comments are resolved:
 
-1. **Documentation Agent** (`sub-agent-documentation`):
+1. **Documentation agent** (`sub-agent-documentation`):
    - Analyze PR changes for documentation impact
    - Update README.md, CHANGELOG.md, inline docs
    - Commit updates to the PR branch
 
-2. **Testing Agent** (`sub-agent-testing`):
+2. **Testing agent** (`sub-agent-tester`):
    - Analyze PR diff for untested code paths
    - Create missing unit, integration
    - Run tests and ensure all pass
@@ -131,7 +131,7 @@ Use the `agent-reviewing` GitHub label to coordinate agent activity:
 ## Error Handling
 
 - If a sub-agent fails, log the error and continue with other agents
-- If merge conflicts cannot be resolved automatically, try with the `sub-agent-bug-resolver`, and only request human help when absolutely necessary.
+- If merge conflicts cannot be resolved automatically, try with the `sub-agent-bug-fixer`, and only request human help when absolutely necessary.
 - If GitHub API calls fail, retry with exponential backoff (max 3 attempts)
 
 ## Output Format
@@ -146,8 +146,8 @@ Provide status updates as structured comments on the PR:
 - ✅ Addressed 2 issues from github-code-quality[bot]
 
 ### Phase 2: Documentation & Testing
-- ✅ Documentation updated by documentation-agent
-- ✅ 8 new tests added by testing-agent
+- ✅ Documentation updated by the documentation agent
+- ✅ 8 new tests added by the tester agent
 
 ### Phase 3: Ready for Merge
 - ⏳ Awaiting human approval (@owner)

{devrev_python_sdk-3.0.2 → devrev_python_sdk-3.0.4}/.augment/agents/release-manager.md

@@ -1,7 +1,7 @@
 ---
 name: release-manager
 description: Automates semantic versioning releases with changelog generation and deployment triggers
-model: claude-opus-4-6
+model: prism-b
 color: green
 ---
 

{devrev_python_sdk-3.0.2 → devrev_python_sdk-3.0.4}/.augment/agents/simplifier.md

@@ -1,7 +1,7 @@
 ---
 name: code-simplifier
 description: Simplifies and refines code for clarity, consistency, and maintainability while preserving all functionality
-model: claude-opus-4-6
+model: prism-b
 color: purple
 ---
 

{devrev_python_sdk-3.0.2 → devrev_python_sdk-3.0.4}/.augment/agents/tester.md

@@ -5,7 +5,7 @@ model: claude-sonnet-4-6
 color: green
 ---
 
-You are a Testing Agent that ensures comprehensive test coverage for PR changes.
+You are a Testing agent that ensures comprehensive test coverage for PR changes.
 
 ## Your Role
 

devrev_python_sdk-3.0.4/.augment/commands/foreman-work.md

@@ -0,0 +1,96 @@
+---
+description: Start working on a GitHub or Linear issue using the Foreman agent
+argument-hint: [issue-id-or-number]
+model: prism-b
+---
+
+# Foreman Work Command
+
+You are invoking the **Foreman** agent to work on a GitHub or Linear issue. The Foreman orchestrates complete feature development from issue analysis to PR creation while preserving the privacy boundary between public GitHub issues and private Linear issues.
+
+## Arguments
+
+- `$ARGUMENTS` - Optional GitHub issue number/URL or Linear issue identifier (e.g., `123`, `#123`, `https://github.com/.../issues/123`, or `CUSS-220`)
+
+## Workflow
+
+### If an issue identifier is provided:
+
+Resolve and work on issue `$ARGUMENTS`:
+
+1. Determine the issue source:
+   - If `$ARGUMENTS` is a GitHub issue number (`123`, `#123`) or GitHub issue URL, fetch it using `gh issue view`, the GitHub API, or the GitHub MCP tools.
+   - If `$ARGUMENTS` is a Linear identifier (`TEAM-123`, e.g. `CUSS-220`), fetch it from Linear.
+   - If the identifier is ambiguous, try the most likely source first and ask the user only if both sources match or neither source matches.
+2. If a GitHub issue is found, copy it to Linear before implementation:
+   - Search Linear first for an existing issue that references the GitHub URL or `Source: GitHub #{number}` to avoid duplicate imports.
+   - Create a Linear issue with the GitHub issue title, public issue body, GitHub URL, labels/milestone when useful, and a clear `Source: GitHub #{number}` note.
+   - If an imported Linear issue already exists, reuse it as the primary tracking issue instead of creating a duplicate.
+   - Treat the new Linear issue as the primary tracking issue for planning and progress updates.
+   - Do **not** post private Linear details back to GitHub. Public GitHub comments must remain public-safe.
+3. If a Linear issue is found, use it directly:
+   - Do **not** copy Linear issue content to GitHub.
+   - Keep private/internal context in Linear only.
+4. Analyze the issue requirements and linked issues in the appropriate source system.
+5. Create an implementation plan.
+6. Create a feature branch following the naming convention: `feature/issue-{tracking-id}-{slug}` where `tracking-id` is the Linear identifier for Linear-origin or GitHub-imported work.
+7. Coordinate builder agents to implement components in parallel where possible.
+8. Run tests and ensure quality checks pass.
+9. Create a PR when implementation is complete.
+10. Hand off to `pr-review-boss` for the review lifecycle.
+
+### If NO issue identifier is provided:
+
+Help the user select an issue to work on:
+
+1. Fetch open GitHub issues that are NOT in progress using:
+   ```bash
+   gh issue list --state open --json number,title,labels,milestone --limit 20
+   ```
+
+2. Fetch actionable Linear issues that are NOT completed, canceled, in progress, or WIP using the Linear tools.
+
+3. Filter out issues in either source that have "in progress" or "wip" labels/states.
+
+4. Present the user with a numbered list of available issues, clearly marking the source:
+   ```
+   Available Issues:
+   
+   1. GitHub #42 - Implement user authentication
+   2. Linear CUSS-220 - Support API key authentication for MCP endpoints
+   3. GitHub #35 - Fix pagination on dashboard
+   4. Linear ENG-29 - Update API rate limiting
+   
+   Enter the number of the issue you want to work on (1-4), or type 'q' to quit:
+   ```
+
+5. Wait for user input to select an issue.
+
+6. Once selected, proceed with the full foreman workflow for that issue. If the selected issue is from GitHub, find or create the Linear copy first and then work from the Linear issue.
+
+## Technical Standards
+
+Follow all standards defined in the foreman agent:
+- Python 3.11+ with strict typing
+- Pydantic v2 for data models
+- Google-style docstrings
+- Latest stable library versions
+- SOC-2 security mindset (no PII in logs, secure defaults)
+
+## Constraints
+
+- **ALL** commits must reference the active tracking issue. For GitHub-origin work, reference both the Linear tracking issue and the public GitHub issue when practical.
+- **NEVER** copy Linear issue content to GitHub or otherwise expose private Linear context in public GitHub comments, PRs, branches, or commit messages.
+- **ALWAYS** copy public GitHub issues to Linear before implementation so internal work is tracked privately.
+- **NEVER** introduce deprecated library versions
+- **ALWAYS** verify library docs are current before using
+- **HANDLE** errors explicitly - no silent failures
+- **UPDATE** the task list as you work to track progress
+
+## Related Agents
+
+You may dispatch these sub-agents as needed:
+- `sub-agent-builder` - For implementing specific components
+- `sub-agent-tester` - For comprehensive test coverage
+- `sub-agent-documentation` - For README/CHANGELOG updates
+

{devrev_python_sdk-3.0.2 → devrev_python_sdk-3.0.4}/.augment/commands/release-prepare.md

@@ -1,7 +1,7 @@
 ---
 description: Prepare and create a semantic versioned release with automated changelog
 argument-hint: "[patch|minor|major]"
-model: claude-opus-4-6
+model: prism-b
 ---
 
 # Release Prepare Command

{devrev_python_sdk-3.0.2 → devrev_python_sdk-3.0.4}/.augment/commands/review-start.md

@@ -1,7 +1,7 @@
 ---
 description: Start monitoring and reviewing PRs using the PR Review Boss agent
 argument-hint: [check-interval-seconds] [duration-minutes]
-model: claude-opus-4-6
+model: prism-b
 ---
 
 # PR Review Start Command

{devrev_python_sdk-3.0.2 → devrev_python_sdk-3.0.4}/.augment/commands/simplify-code.md

@@ -1,7 +1,7 @@
 ---
 description: Simplify and refine code for clarity, consistency, and maintainability
 argument-hint: [file-path-or-scope]
-model: claude-opus-4-6
+model: prism-b
 ---
 
 # Simplify Code Command

{devrev_python_sdk-3.0.2 → devrev_python_sdk-3.0.4}/.github/workflows/docs.yml

@@ -46,7 +46,7 @@ jobs:
         uses: actions/configure-pages@v6
 
       - name: Upload artifact
-        uses: actions/upload-pages-artifact@v4
+        uses: actions/upload-pages-artifact@v5
         with:
           path: 'site'
 

{devrev_python_sdk-3.0.2 → devrev_python_sdk-3.0.4}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: devrev-Python-SDK
-Version: 3.0.2
+Version: 3.0.4
 Summary: A modern, type-safe Python SDK for the DevRev API
 Project-URL: Homepage, https://github.com/mgmonteleone/py-dev-rev
 Project-URL: Documentation, https://github.com/mgmonteleone/py-dev-rev
@@ -215,6 +215,17 @@ for account in accounts:
 work = client.works.get(id="don:core:...")
 print(f"Work: {work.title} - Status: {work.stage.name}")
 
+# Ticket integrations can read optional account/sentiment/SLA fields
+ticket = client.works.get(id="don:core:dvrv-us-1:devo/1:ticket/123")
+print(ticket.rev_org, ticket.account, ticket.needs_response)
+
+# Use a supported raw escape hatch when the API returns newer fields
+raw_ticket = client.works.get_raw(id="don:core:dvrv-us-1:devo/1:ticket/123")
+print(raw_ticket["work"].keys())
+
+# List survey/CSAT responses for a ticket without using private _http
+survey_responses = client.survey_responses.list(object_id=ticket.id)
+
 # Create a new ticket
 ticket = client.works.create(
     title="Bug: Login page not loading",
@@ -297,6 +308,7 @@ The SDK provides complete coverage of all 209 DevRev public API endpoints, organ
 |---------|-----------|-------------|
 | **Articles** | 5 | Knowledge base articles |
 | **Conversations** | 5 | Customer conversations |
+| **Survey Responses** | 1 | Survey and CSAT response listing |
 | **Timeline Entries** | 5 | Activity timeline management |
 | **Tags** | 5 | Tagging and categorization |
 

{devrev_python_sdk-3.0.2 → devrev_python_sdk-3.0.4}/README.md

@@ -140,6 +140,17 @@ for account in accounts:
 work = client.works.get(id="don:core:...")
 print(f"Work: {work.title} - Status: {work.stage.name}")
 
+# Ticket integrations can read optional account/sentiment/SLA fields
+ticket = client.works.get(id="don:core:dvrv-us-1:devo/1:ticket/123")
+print(ticket.rev_org, ticket.account, ticket.needs_response)
+
+# Use a supported raw escape hatch when the API returns newer fields
+raw_ticket = client.works.get_raw(id="don:core:dvrv-us-1:devo/1:ticket/123")
+print(raw_ticket["work"].keys())
+
+# List survey/CSAT responses for a ticket without using private _http
+survey_responses = client.survey_responses.list(object_id=ticket.id)
+
 # Create a new ticket
 ticket = client.works.create(
     title="Bug: Login page not loading",
@@ -222,6 +233,7 @@ The SDK provides complete coverage of all 209 DevRev public API endpoints, organ
 |---------|-----------|-------------|
 | **Articles** | 5 | Knowledge base articles |
 | **Conversations** | 5 | Customer conversations |
+| **Survey Responses** | 1 | Survey and CSAT response listing |
 | **Timeline Entries** | 5 | Activity timeline management |
 | **Tags** | 5 | Tagging and categorization |
 

{devrev_python_sdk-3.0.2 → devrev_python_sdk-3.0.4}/docs/api/index.md

@@ -44,6 +44,7 @@ All API operations are organized into service classes:
 | [Parts](services/parts.md) | Product components | 5 |
 | [Articles](services/articles.md) | Knowledge base | 5 |
 | [Conversations](services/conversations.md) | Customer conversations | 5 |
+| [Survey Responses](services/survey-responses.md) | Survey and CSAT responses | 1 |
 | [Tags](services/tags.md) | Categorization | 5 |
 | [Groups](services/groups.md) | User groups | 6 |
 | [Webhooks](services/webhooks.md) | Event notifications | 6 |
@@ -77,6 +78,7 @@ Request and response models:
 |--------|-------------|
 | [Base](models/base.md) | Common base classes |
 | [Accounts](models/accounts.md) | Account models |
+| [Survey Responses](models/survey-responses.md) | Survey response models |
 | [Works](models/works.md) | Work item models |
 | [Users](models/users.md) | User models |
 

{devrev_python_sdk-3.0.2 → devrev_python_sdk-3.0.4}/docs/api/models/index.md

@@ -30,6 +30,7 @@ Models for specific resources:
 | Resource | Description |
 |----------|-------------|
 | [Accounts](accounts.md) | Customer account models |
+| [Survey Responses](survey-responses.md) | Survey response list and payload models |
 | [Works](works.md) | Work item models (tickets, issues) |
 | [Users](users.md) | User models (dev and rev users) |
 

devrev_python_sdk-3.0.4/docs/api/models/survey-responses.md

@@ -0,0 +1,47 @@
+# Survey Response Models
+
+Models for survey and CSAT response operations.
+
+## SurveyResponse
+
+The main survey response model.
+
+::: devrev.models.survey_responses.SurveyResponse
+    options:
+      show_source: true
+
+## Enums
+
+### SurveyResponsesListMode
+
+::: devrev.models.survey_responses.SurveyResponsesListMode
+    options:
+      show_source: true
+
+## Request Models
+
+### SurveyResponsesListRequest
+
+::: devrev.models.survey_responses.SurveyResponsesListRequest
+    options:
+      show_source: true
+
+## Response Models
+
+### SurveyResponsesListResponse
+
+::: devrev.models.survey_responses.SurveyResponsesListResponse
+    options:
+      show_source: true
+
+## Usage Examples
+
+### Work with survey responses
+
+```python
+responses = client.survey_responses.list(object_id="don:core:...", limit=10)
+
+for survey_response in responses.survey_responses:
+    print(survey_response.id)
+    print(survey_response.response)
+```

{devrev_python_sdk-3.0.2 → devrev_python_sdk-3.0.4}/docs/api/models/works.md

@@ -111,6 +111,9 @@ print(f"Stage: {work.stage.name if work.stage else 'N/A'}")
 
 if work.type == WorkType.TICKET:
     print(f"Severity: {work.severity}")
+    print(f"Account: {work.account}")
+    print(f"Rev org: {work.rev_org}")
+    print(f"Needs response: {work.needs_response}")
 elif work.type == WorkType.ISSUE:
     print(f"Priority: {work.priority}")
 ```

{devrev_python_sdk-3.0.2 → devrev_python_sdk-3.0.4}/docs/api/services/index.md

@@ -36,6 +36,7 @@ client.dev_users     # DevUsersService
 |---------|-------------|-----------|
 | **Articles** | Knowledge base articles with unified content management | [articles](articles.md) |
 | **Conversations** | Customer conversations | [conversations](conversations.md) |
+| **Survey Responses** | Survey and CSAT responses | [survey-responses](survey-responses.md) |
 | **Tags** | Categorization | [tags](tags.md) |
 | **Timeline Entries** | Activity tracking | [timeline-entries](timeline-entries.md) |
 

devrev_python_sdk-3.0.4/docs/api/services/survey-responses.md

@@ -0,0 +1,83 @@
+# Survey Responses Service
+
+List survey and CSAT responses in DevRev.
+
+Use this service when a ticket or work sync needs survey responses without
+reaching through the private client transport.
+
+## SurveyResponsesService
+
+::: devrev.services.survey_responses.SurveyResponsesService
+    options:
+      show_source: true
+      members:
+        - list
+
+## AsyncSurveyResponsesService
+
+::: devrev.services.survey_responses.AsyncSurveyResponsesService
+    options:
+      show_source: true
+      members:
+        - list
+
+## Usage Examples
+
+### List responses for a ticket/work object
+
+```python
+from devrev import DevRevClient
+
+client = DevRevClient()
+
+responses = client.survey_responses.list(
+    object_id="don:core:dvrv-us-1:devo/1:ticket/123",
+    limit=50,
+)
+
+for survey_response in responses.survey_responses:
+    print(survey_response.id, survey_response.response)
+```
+
+### Filter with multiple objects
+
+```python
+responses = client.survey_responses.list(
+    objects=[
+        "don:core:dvrv-us-1:devo/1:ticket/123",
+        "don:core:dvrv-us-1:devo/1:ticket/456",
+    ],
+)
+```
+
+### Async usage
+
+```python
+import asyncio
+
+from devrev import AsyncDevRevClient
+
+
+async def main():
+    async with AsyncDevRevClient() as client:
+        responses = await client.survey_responses.list(
+            object_id="don:core:dvrv-us-1:devo/1:ticket/123",
+        )
+        print(len(responses.survey_responses))
+
+
+asyncio.run(main())
+```
+
+## Pagination
+
+`survey_responses.list(...)` returns a paginated response with `next_cursor`.
+When you need more than one page, pass the returned cursor into a follow-up
+call and continue until `next_cursor` is `None`.
+
+## Related Models
+
+- [`SurveyResponse`](../models/survey-responses.md#surveyresponse)
+- [`SurveyResponsesListRequest`](../models/survey-responses.md#surveyresponseslistrequest)
+- [`SurveyResponsesListResponse`](../models/survey-responses.md#surveyresponseslistresponse)
+- [`SurveyResponsesListMode`](../models/survey-responses.md#surveyresponseslistmode)