@archal/cli 0.7.3 → 0.7.5

package/twin-assets/github/seeds/triage-unlabeled.json

@@ -0,0 +1,451 @@
+{
+  "users": [
+    {
+      "id": 1,
+      "login": "acme",
+      "nodeId": "U_kgDOBacme1",
+      "avatarUrl": "https://avatars.githubusercontent.com/u/1?v=4",
+      "type": "Organization",
+      "name": "Acme Corp",
+      "email": "engineering@acme.com",
+      "bio": "Building the platform",
+      "company": "Acme Corp",
+      "location": "San Francisco, CA",
+      "htmlUrl": "https://github.com/acme",
+      "publicRepos": 12,
+      "followers": 340,
+      "following": 0,
+      "siteAdmin": false,
+      "createdAt": "2020-03-10T08:00:00Z",
+      "updatedAt": "2026-01-15T12:00:00Z"
+    }
+  ],
+  "repos": [
+    {
+      "id": 1,
+      "nodeId": "R_kgDOBplat1",
+      "name": "platform",
+      "fullName": "acme/platform",
+      "owner": "acme",
+      "private": false,
+      "description": "Acme Corp platform monorepo — APIs, services, and internal tooling",
+      "fork": false,
+      "htmlUrl": "https://github.com/acme/platform",
+      "cloneUrl": "https://github.com/acme/platform.git",
+      "sshUrl": "git@github.com:acme/platform.git",
+      "language": "TypeScript",
+      "forksCount": 24,
+      "stargazersCount": 158,
+      "watchersCount": 158,
+      "openIssuesCount": 15,
+      "defaultBranch": "main",
+      "topics": ["typescript", "platform", "monorepo"],
+      "hasIssues": true,
+      "hasProjects": true,
+      "hasWiki": true,
+      "hasPages": false,
+      "archived": false,
+      "disabled": false,
+      "visibility": "public",
+      "pushedAt": "2026-02-18T10:00:00Z",
+      "license": "MIT",
+      "allowMergeCommit": true,
+      "allowSquashMerge": true,
+      "allowRebaseMerge": true,
+      "allowAutoMerge": false,
+      "deleteBranchOnMerge": true,
+      "createdAt": "2023-06-01T09:00:00Z",
+      "updatedAt": "2026-02-18T10:00:00Z"
+    }
+  ],
+  "branches": [
+    {
+      "id": 1,
+      "repoId": 1,
+      "name": "main",
+      "commitSha": "a1f2e3d4c5b6a7f8e9d0c1b2a3f4e5d6c7b8a9f0",
+      "protected": true,
+      "createdAt": "2023-06-01T09:00:00Z",
+      "updatedAt": "2026-02-18T10:00:00Z"
+    }
+  ],
+  "commits": [
+    {
+      "id": 1,
+      "repoId": 1,
+      "sha": "a1f2e3d4c5b6a7f8e9d0c1b2a3f4e5d6c7b8a9f0",
+      "nodeId": "C_kwDOBcom01",
+      "message": "chore: update dependencies and fix CI pipeline",
+      "authorLogin": "acme",
+      "authorName": "Acme Corp",
+      "authorEmail": "engineering@acme.com",
+      "committerLogin": "acme",
+      "committerName": "Acme Corp",
+      "committerEmail": "engineering@acme.com",
+      "branchName": "main",
+      "parentShas": [],
+      "treeUrl": "https://api.github.com/repos/acme/platform/git/trees/a1f2e3d4c5b6a7f8e9d0c1b2a3f4e5d6c7b8a9f0",
+      "htmlUrl": "https://github.com/acme/platform/commit/a1f2e3d4c5b6a7f8e9d0c1b2a3f4e5d6c7b8a9f0",
+      "verified": false,
+      "createdAt": "2026-02-18T10:00:00Z",
+      "updatedAt": "2026-02-18T10:00:00Z"
+    }
+  ],
+  "labels": [
+    {
+      "id": 1, "repoId": 1, "nodeId": "LA_kwDOBlab01", "name": "bug", "description": "Something isn't working", "color": "d73a4a", "isDefault": true, "createdAt": "2023-06-01T09:00:00Z", "updatedAt": "2023-06-01T09:00:00Z"
+    },
+    {
+      "id": 2, "repoId": 1, "nodeId": "LA_kwDOBlab02", "name": "enhancement", "description": "New feature or request", "color": "a2eeef", "isDefault": true, "createdAt": "2023-06-01T09:00:00Z", "updatedAt": "2023-06-01T09:00:00Z"
+    },
+    {
+      "id": 3, "repoId": 1, "nodeId": "LA_kwDOBlab03", "name": "question", "description": "Further information is requested", "color": "d876e3", "isDefault": true, "createdAt": "2023-06-01T09:00:00Z", "updatedAt": "2023-06-01T09:00:00Z"
+    },
+    {
+      "id": 4, "repoId": 1, "nodeId": "LA_kwDOBlab04", "name": "priority:high", "description": "High priority", "color": "e11d48", "isDefault": false, "createdAt": "2023-06-01T09:00:00Z", "updatedAt": "2023-06-01T09:00:00Z"
+    },
+    {
+      "id": 5, "repoId": 1, "nodeId": "LA_kwDOBlab05", "name": "priority:medium", "description": "Medium priority", "color": "f59e0b", "isDefault": false, "createdAt": "2023-06-01T09:00:00Z", "updatedAt": "2023-06-01T09:00:00Z"
+    },
+    {
+      "id": 6, "repoId": 1, "nodeId": "LA_kwDOBlab06", "name": "priority:low", "description": "Low priority", "color": "0ea5e9", "isDefault": false, "createdAt": "2023-06-01T09:00:00Z", "updatedAt": "2023-06-01T09:00:00Z"
+    }
+  ],
+  "issues": [
+    {
+      "id": 1,
+      "repoId": 1,
+      "nodeId": "I_kwDOBissX1",
+      "number": 1,
+      "title": "Application crashes with unhandled TypeError on startup when config file is missing",
+      "body": "## Bug report\n\nThe application crashes immediately on startup if the `config.json` file is not present in the expected directory.\n\n## Steps to reproduce\n\n1. Delete or rename `config/config.json`\n2. Run `npm start`\n3. Application crashes with `TypeError: Cannot read properties of undefined (reading 'database')`\n\n## Expected behavior\n\nThe application should fall back to default configuration values or display a clear error message explaining that the config file is missing.\n\n## Stack trace\n\n```\nTypeError: Cannot read properties of undefined (reading 'database')\n    at loadConfig (src/config/loader.ts:24:18)\n    at main (src/index.ts:8:3)\n```\n\n## Environment\n\n- Node.js 20.11.0\n- OS: Ubuntu 22.04",
+      "state": "open",
+      "stateReason": null,
+      "locked": false,
+      "assignees": [],
+      "labels": [],
+      "milestone": null,
+      "authorLogin": "acme",
+      "closedAt": null,
+      "closedBy": null,
+      "htmlUrl": "https://github.com/acme/platform/issues/1",
+      "isPullRequest": false,
+      "reactions": { "totalCount": 0, "plusOne": 0, "minusOne": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 },
+      "createdAt": "2026-01-06T09:15:00Z",
+      "updatedAt": "2026-01-06T09:15:00Z"
+    },
+    {
+      "id": 2,
+      "repoId": 1,
+      "nodeId": "I_kwDOBissX2",
+      "number": 2,
+      "title": "Memory leak in WebSocket connection handler causes server to crash after 24 hours",
+      "body": "## Bug report\n\nThe WebSocket connection handler is leaking memory. After approximately 24 hours of continuous operation, the server runs out of memory and crashes with an OOM error.\n\n## Steps to reproduce\n\n1. Start the platform server\n2. Connect multiple WebSocket clients (50+)\n3. Send messages continuously for 24 hours\n4. Observe memory usage growing unbounded\n\n## Expected behavior\n\nMemory usage should remain stable regardless of uptime. Disconnected client resources should be properly cleaned up.\n\n## Observations\n\n- Heap dump shows thousands of unreferenced `ClientSession` objects\n- The `onClose` handler does not remove the client from the active sessions map\n- Memory grows at roughly 50MB/hour under moderate load",
+      "state": "open",
+      "stateReason": null,
+      "locked": false,
+      "assignees": [],
+      "labels": [],
+      "milestone": null,
+      "authorLogin": "acme",
+      "closedAt": null,
+      "closedBy": null,
+      "htmlUrl": "https://github.com/acme/platform/issues/2",
+      "isPullRequest": false,
+      "reactions": { "totalCount": 0, "plusOne": 0, "minusOne": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 },
+      "createdAt": "2026-01-08T14:30:00Z",
+      "updatedAt": "2026-01-10T11:00:00Z"
+    },
+    {
+      "id": 3,
+      "repoId": 1,
+      "nodeId": "I_kwDOBissX3",
+      "number": 3,
+      "title": "Error 500 when uploading files larger than 10MB through the REST API",
+      "body": "## Bug report\n\nUploading files larger than 10MB through the `/api/v1/files/upload` endpoint results in a 500 Internal Server Error. No meaningful error message is returned to the client.\n\n## Steps to reproduce\n\n1. Prepare a file larger than 10MB (e.g., a 15MB CSV)\n2. POST to `/api/v1/files/upload` with the file as multipart form data\n3. Server returns HTTP 500 with `{\"error\": \"Internal Server Error\"}`\n\n## Expected behavior\n\nEither the upload should succeed (if within configured limits) or return a 413 Payload Too Large with a clear message about the file size limit.\n\n## Notes\n\nSmaller files (under 10MB) upload successfully. The issue seems related to the body parser configuration or a missing size limit in the upload middleware.",
+      "state": "open",
+      "stateReason": null,
+      "locked": false,
+      "assignees": [],
+      "labels": [],
+      "milestone": null,
+      "authorLogin": "acme",
+      "closedAt": null,
+      "closedBy": null,
+      "htmlUrl": "https://github.com/acme/platform/issues/3",
+      "isPullRequest": false,
+      "reactions": { "totalCount": 0, "plusOne": 0, "minusOne": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 },
+      "createdAt": "2026-01-12T10:45:00Z",
+      "updatedAt": "2026-01-12T10:45:00Z"
+    },
+    {
+      "id": 4,
+      "repoId": 1,
+      "nodeId": "I_kwDOBissX4",
+      "number": 4,
+      "title": "Database connection pool exhaustion causes unexpected 503 errors under load",
+      "body": "## Bug report\n\nUnder moderate concurrent load (200+ requests/second), the database connection pool gets exhausted and the application starts returning 503 Service Unavailable errors.\n\n## Steps to reproduce\n\n1. Run the platform with default connection pool settings\n2. Use a load testing tool to send 200+ concurrent requests to any database-backed endpoint\n3. After ~30 seconds, responses start returning 503 errors\n4. Server logs show `Error: Cannot acquire connection from pool — all connections are in use`\n\n## Expected behavior\n\nThe application should queue requests when the pool is exhausted rather than immediately failing, or the default pool size should be increased.\n\n## Configuration\n\nCurrent pool settings: `min: 2, max: 10`. These are the framework defaults and too low for production workloads.",
+      "state": "open",
+      "stateReason": null,
+      "locked": false,
+      "assignees": [],
+      "labels": [],
+      "milestone": null,
+      "authorLogin": "acme",
+      "closedAt": null,
+      "closedBy": null,
+      "htmlUrl": "https://github.com/acme/platform/issues/4",
+      "isPullRequest": false,
+      "reactions": { "totalCount": 0, "plusOne": 0, "minusOne": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 },
+      "createdAt": "2026-01-15T08:20:00Z",
+      "updatedAt": "2026-01-17T16:00:00Z"
+    },
+    {
+      "id": 5,
+      "repoId": 1,
+      "nodeId": "I_kwDOBissX5",
+      "number": 5,
+      "title": "Race condition in job scheduler causes duplicate task execution",
+      "body": "## Bug report\n\nThe background job scheduler occasionally executes the same job twice simultaneously. This leads to duplicate data processing and, in some cases, data corruption.\n\n## Steps to reproduce\n\n1. Schedule a job with a 5-minute interval\n2. Under high CPU load, the previous job execution sometimes overlaps with the next scheduled run\n3. Both instances run to completion, processing the same data twice\n\n## Expected behavior\n\nThe scheduler should implement a locking mechanism to prevent concurrent execution of the same job. If a previous run is still in progress, the next scheduled run should be skipped or queued.\n\n## Impact\n\nThis has caused duplicate email sends and double-counted analytics events in production.",
+      "state": "open",
+      "stateReason": null,
+      "locked": false,
+      "assignees": [],
+      "labels": [],
+      "milestone": null,
+      "authorLogin": "acme",
+      "closedAt": null,
+      "closedBy": null,
+      "htmlUrl": "https://github.com/acme/platform/issues/5",
+      "isPullRequest": false,
+      "reactions": { "totalCount": 0, "plusOne": 0, "minusOne": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 },
+      "createdAt": "2026-01-18T11:00:00Z",
+      "updatedAt": "2026-01-20T09:30:00Z"
+    },
+    {
+      "id": 6,
+      "repoId": 1,
+      "nodeId": "I_kwDOBissX6",
+      "number": 6,
+      "title": "Authentication middleware returns cryptic error instead of 401 when JWT token is expired",
+      "body": "## Bug report\n\nWhen a user's JWT token expires, the authentication middleware returns a 500 error with the message `\"JsonWebTokenError: jwt expired\"` instead of a proper 401 Unauthorized response.\n\n## Steps to reproduce\n\n1. Log in and obtain a JWT token\n2. Wait for the token to expire (or manually set the clock forward)\n3. Make any authenticated API request\n4. Server returns 500 instead of 401\n\n## Expected behavior\n\nThe middleware should catch `TokenExpiredError`, return a 401 status code, and include a clear message like `\"Token expired. Please re-authenticate.\"` so clients can handle token refresh gracefully.\n\n## Impact\n\nClient applications cannot distinguish between a server error and an expired token, leading to poor user experience and broken automatic token refresh flows.",
+      "state": "open",
+      "stateReason": null,
+      "locked": false,
+      "assignees": [],
+      "labels": [],
+      "milestone": null,
+      "authorLogin": "acme",
+      "closedAt": null,
+      "closedBy": null,
+      "htmlUrl": "https://github.com/acme/platform/issues/6",
+      "isPullRequest": false,
+      "reactions": { "totalCount": 0, "plusOne": 0, "minusOne": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 },
+      "createdAt": "2026-01-22T15:45:00Z",
+      "updatedAt": "2026-01-22T15:45:00Z"
+    },
+    {
+      "id": 7,
+      "repoId": 1,
+      "nodeId": "I_kwDOBissX7",
+      "number": 7,
+      "title": "Add support for bulk import of records via CSV upload",
+      "body": "## Feature request\n\nWe need the ability to import large datasets into the platform via CSV file upload. Currently, records can only be created one at a time through the API or UI, which is impractical for onboarding new customers with thousands of existing records.\n\n## Proposed solution\n\n- Add a CSV upload endpoint at `/api/v1/import`\n- Support column mapping (CSV headers to platform fields)\n- Validate all rows before importing any (fail-fast on validation errors)\n- Provide a progress indicator for large imports\n- Return a summary report (rows imported, rows skipped, errors)\n\n## Use case\n\nCustomer onboarding — new enterprise customers frequently need to migrate 10,000+ records from their existing systems.",
+      "state": "open",
+      "stateReason": null,
+      "locked": false,
+      "assignees": [],
+      "labels": [],
+      "milestone": null,
+      "authorLogin": "acme",
+      "closedAt": null,
+      "closedBy": null,
+      "htmlUrl": "https://github.com/acme/platform/issues/7",
+      "isPullRequest": false,
+      "reactions": { "totalCount": 0, "plusOne": 0, "minusOne": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 },
+      "createdAt": "2026-01-24T09:00:00Z",
+      "updatedAt": "2026-01-24T09:00:00Z"
+    },
+    {
+      "id": 8,
+      "repoId": 1,
+      "nodeId": "I_kwDOBissX8",
+      "number": 8,
+      "title": "Implement webhook delivery system for real-time event notifications",
+      "body": "## Feature request\n\nWe need a webhook system that allows customers to subscribe to platform events and receive real-time HTTP POST notifications when those events occur.\n\n## Requirements\n\n- Customers can register webhook URLs for specific event types\n- Events include: `record.created`, `record.updated`, `record.deleted`, `job.completed`, `job.failed`\n- Webhook payloads should include the full event data and a signature for verification\n- Failed deliveries should be retried with exponential backoff (up to 5 attempts)\n- Provide a webhook delivery log in the dashboard\n\n## Motivation\n\nMultiple enterprise customers have asked for real-time notifications to integrate with their internal systems. Currently they have to poll our API, which is inefficient and adds unnecessary load.",
+      "state": "open",
+      "stateReason": null,
+      "locked": false,
+      "assignees": [],
+      "labels": [],
+      "milestone": null,
+      "authorLogin": "acme",
+      "closedAt": null,
+      "closedBy": null,
+      "htmlUrl": "https://github.com/acme/platform/issues/8",
+      "isPullRequest": false,
+      "reactions": { "totalCount": 0, "plusOne": 0, "minusOne": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 },
+      "createdAt": "2026-01-27T13:30:00Z",
+      "updatedAt": "2026-01-27T13:30:00Z"
+    },
+    {
+      "id": 9,
+      "repoId": 1,
+      "nodeId": "I_kwDOBissX9",
+      "number": 9,
+      "title": "Add role-based access control (RBAC) with custom permission sets",
+      "body": "## Feature request\n\nThe platform currently has a simple admin/user role system. We need fine-grained role-based access control that allows organizations to define custom roles with specific permission sets.\n\n## Proposed solution\n\n- Define permissions as resource:action pairs (e.g., `records:read`, `records:write`, `users:manage`)\n- Allow creation of custom roles that bundle permissions together\n- Support role assignment at the organization and project level\n- Include built-in roles: Owner, Admin, Editor, Viewer\n- Add permission checks to all API endpoints\n\n## Motivation\n\nEnterprise customers require granular access control for compliance and security. The current binary admin/user model is insufficient for teams with 50+ members working across multiple projects.",
+      "state": "open",
+      "stateReason": null,
+      "locked": false,
+      "assignees": [],
+      "labels": [],
+      "milestone": null,
+      "authorLogin": "acme",
+      "closedAt": null,
+      "closedBy": null,
+      "htmlUrl": "https://github.com/acme/platform/issues/9",
+      "isPullRequest": false,
+      "reactions": { "totalCount": 0, "plusOne": 0, "minusOne": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 },
+      "createdAt": "2026-01-30T10:15:00Z",
+      "updatedAt": "2026-01-30T10:15:00Z"
+    },
+    {
+      "id": 10,
+      "repoId": 1,
+      "nodeId": "I_kwDOBissXA",
+      "number": 10,
+      "title": "Add audit log for tracking all user actions and API calls",
+      "body": "## Feature request\n\nWe need a comprehensive audit log that records all significant actions taken by users and API clients on the platform.\n\n## Requirements\n\n- Log all CRUD operations on resources with before/after state\n- Log authentication events (login, logout, token refresh, failed attempts)\n- Log permission changes and role assignments\n- Each entry should include: timestamp, actor, action, resource, IP address, user agent\n- Provide a searchable audit log UI in the admin dashboard\n- Support exporting audit logs as CSV or JSON\n- Retain logs for at least 90 days (configurable per organization)\n\n## Motivation\n\nRequired for SOC 2 compliance and frequently requested by enterprise security teams during procurement reviews.",
+      "state": "open",
+      "stateReason": null,
+      "locked": false,
+      "assignees": [],
+      "labels": [],
+      "milestone": null,
+      "authorLogin": "acme",
+      "closedAt": null,
+      "closedBy": null,
+      "htmlUrl": "https://github.com/acme/platform/issues/10",
+      "isPullRequest": false,
+      "reactions": { "totalCount": 0, "plusOne": 0, "minusOne": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 },
+      "createdAt": "2026-02-02T08:00:00Z",
+      "updatedAt": "2026-02-02T08:00:00Z"
+    },
+    {
+      "id": 11,
+      "repoId": 1,
+      "nodeId": "I_kwDOBissXB",
+      "number": 11,
+      "title": "Implement dark mode and theming support for the dashboard UI",
+      "body": "## Feature request\n\nUsers have been requesting dark mode for the platform dashboard. We should implement a theming system that supports light mode, dark mode, and potentially custom brand themes for enterprise customers.\n\n## Proposed approach\n\n- Use CSS custom properties for all color values\n- Add a theme toggle in user preferences\n- Persist theme selection per user in their profile\n- Support system preference detection (`prefers-color-scheme`)\n- Ensure all charts, graphs, and data visualizations adapt to the active theme\n- Allow enterprise customers to set a default theme and upload custom brand colors\n\n## Priority\n\nThis is one of our most upvoted feature requests in the feedback portal (47 votes).",
+      "state": "open",
+      "stateReason": null,
+      "locked": false,
+      "assignees": [],
+      "labels": [],
+      "milestone": null,
+      "authorLogin": "acme",
+      "closedAt": null,
+      "closedBy": null,
+      "htmlUrl": "https://github.com/acme/platform/issues/11",
+      "isPullRequest": false,
+      "reactions": { "totalCount": 0, "plusOne": 0, "minusOne": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 },
+      "createdAt": "2026-02-05T14:20:00Z",
+      "updatedAt": "2026-02-05T14:20:00Z"
+    },
+    {
+      "id": 12,
+      "repoId": 1,
+      "nodeId": "I_kwDOBissXC",
+      "number": 12,
+      "title": "How do I configure SSO with our company's Okta instance?",
+      "body": "Hi team,\n\nWe're trying to set up SSO for our organization using Okta as our identity provider. I've looked through the docs but I can't find clear instructions on how to configure SAML-based SSO.\n\nSpecifically, I need to know:\n\n1. What is the ACS (Assertion Consumer Service) URL for the platform?\n2. What attribute mappings are required?\n3. Do we need to configure anything on the platform side, or just in Okta?\n4. Is there a way to test the SSO configuration before enabling it for all users?\n\nWe're on the Enterprise plan if that matters. Any help or documentation pointers would be appreciated.\n\nThanks!",
+      "state": "open",
+      "stateReason": null,
+      "locked": false,
+      "assignees": [],
+      "labels": [],
+      "milestone": null,
+      "authorLogin": "acme",
+      "closedAt": null,
+      "closedBy": null,
+      "htmlUrl": "https://github.com/acme/platform/issues/12",
+      "isPullRequest": false,
+      "reactions": { "totalCount": 0, "plusOne": 0, "minusOne": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 },
+      "createdAt": "2026-02-07T11:00:00Z",
+      "updatedAt": "2026-02-07T11:00:00Z"
+    },
+    {
+      "id": 13,
+      "repoId": 1,
+      "nodeId": "I_kwDOBissXD",
+      "number": 13,
+      "title": "What is the recommended way to handle database migrations in production?",
+      "body": "Hello,\n\nI'm deploying the platform to our production environment and I'm unsure about the best practices for running database migrations.\n\nQuestions:\n\n1. Should migrations be run as part of the deployment pipeline, or separately?\n2. Is there a way to run migrations without downtime?\n3. How do I roll back a migration if something goes wrong?\n4. Are there any migration scripts that require special attention (e.g., long-running ALTER TABLE statements)?\n5. What's the recommended approach for testing migrations against a production-like dataset before deploying?\n\nWe're using PostgreSQL 15 in production. Any guidance or documentation would be helpful.",
+      "state": "open",
+      "stateReason": null,
+      "locked": false,
+      "assignees": [],
+      "labels": [],
+      "milestone": null,
+      "authorLogin": "acme",
+      "closedAt": null,
+      "closedBy": null,
+      "htmlUrl": "https://github.com/acme/platform/issues/13",
+      "isPullRequest": false,
+      "reactions": { "totalCount": 0, "plusOne": 0, "minusOne": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 },
+      "createdAt": "2026-02-10T09:30:00Z",
+      "updatedAt": "2026-02-10T09:30:00Z"
+    },
+    {
+      "id": 14,
+      "repoId": 1,
+      "nodeId": "I_kwDOBissXE",
+      "number": 14,
+      "title": "How do I set up local development with Docker Compose?",
+      "body": "Hi,\n\nI'm a new contributor and I'm trying to get the platform running locally for development. The README mentions Docker Compose but the instructions seem outdated.\n\nI'm running into these issues:\n\n1. `docker-compose up` fails with an error about a missing `redis` service that's referenced in the compose file but not defined\n2. The `.env.example` file references environment variables that aren't documented anywhere\n3. After fixing the Redis issue manually, the API starts but can't connect to the database — is there a specific init script I need to run?\n\nCould someone provide updated step-by-step instructions for getting the full development environment running with Docker Compose? Or point me to the right documentation if it exists?\n\nThanks in advance!",
+      "state": "open",
+      "stateReason": null,
+      "locked": false,
+      "assignees": [],
+      "labels": [],
+      "milestone": null,
+      "authorLogin": "acme",
+      "closedAt": null,
+      "closedBy": null,
+      "htmlUrl": "https://github.com/acme/platform/issues/14",
+      "isPullRequest": false,
+      "reactions": { "totalCount": 0, "plusOne": 0, "minusOne": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 },
+      "createdAt": "2026-02-13T16:00:00Z",
+      "updatedAt": "2026-02-14T10:00:00Z"
+    },
+    {
+      "id": 15,
+      "repoId": 1,
+      "nodeId": "I_kwDOBissXF",
+      "number": 15,
+      "title": "Can someone explain how the rate limiting works and how to increase limits?",
+      "body": "Hello,\n\nWe're hitting rate limits on the API and I need to understand how the rate limiting system works so I can adjust it for our use case.\n\n1. What are the default rate limits per endpoint?\n2. Is rate limiting applied per user, per API key, or per IP address?\n3. How do I increase the limits for our organization? Is this a configuration change or does it require a plan upgrade?\n4. Are there any headers in the API response that indicate remaining quota (like `X-RateLimit-Remaining`)?\n5. Is there a way to exempt certain internal services from rate limiting?\n\nWe're using the API for an automated data sync that runs every 5 minutes and makes approximately 500 requests per run. Thanks!",
+      "state": "open",
+      "stateReason": null,
+      "locked": false,
+      "assignees": [],
+      "labels": [],
+      "milestone": null,
+      "authorLogin": "acme",
+      "closedAt": null,
+      "closedBy": null,
+      "htmlUrl": "https://github.com/acme/platform/issues/15",
+      "isPullRequest": false,
+      "reactions": { "totalCount": 0, "plusOne": 0, "minusOne": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 },
+      "createdAt": "2026-02-17T12:45:00Z",
+      "updatedAt": "2026-02-17T12:45:00Z"
+    }
+  ],
+  "pullRequests": [],
+  "comments": [],
+  "files": [],
+  "workflows": [],
+  "workflowRuns": []
+}

package/twin-assets/google-workspace/fidelity.json

@@ -0,0 +1,13 @@
+{
+  "twin": "google-workspace",
+  "api": "REST (Gmail, Calendar, Drive, Docs, Sheets)",
+  "version": "0.1.0",
+  "capabilities": [
+    { "name": "Gmail (read, search, send)", "supported": true },
+    { "name": "Calendar (events, attendees)", "supported": true },
+    { "name": "Drive (files, folders)", "supported": true },
+    { "name": "Docs (create, read)", "supported": true },
+    { "name": "Sheets (read, write cells)", "supported": true },
+    { "name": "Admin API", "supported": false }
+  ]
+}

package/twin-assets/google-workspace/seeds/empty.json

@@ -0,0 +1,54 @@
+{
+  "users": [
+    {
+      "id": 1,
+      "userId": "user-1",
+      "email": "testuser@example.com",
+      "displayName": "Test User",
+      "photoUrl": null,
+      "isAdmin": true,
+      "createdAt": "2024-01-01T00:00:00Z",
+      "updatedAt": "2024-01-01T00:00:00Z"
+    }
+  ],
+  "labels": [
+    { "id": 1, "labelId": "INBOX", "name": "INBOX", "type": "system", "messageListVisibility": "show", "labelListVisibility": "labelShow", "messagesTotal": 0, "messagesUnread": 0, "color": null, "createdAt": "2024-01-01T00:00:00Z", "updatedAt": "2024-01-01T00:00:00Z" },
+    { "id": 2, "labelId": "SENT", "name": "SENT", "type": "system", "messageListVisibility": "hide", "labelListVisibility": "labelShow", "messagesTotal": 0, "messagesUnread": 0, "color": null, "createdAt": "2024-01-01T00:00:00Z", "updatedAt": "2024-01-01T00:00:00Z" },
+    { "id": 3, "labelId": "TRASH", "name": "TRASH", "type": "system", "messageListVisibility": "hide", "labelListVisibility": "labelShow", "messagesTotal": 0, "messagesUnread": 0, "color": null, "createdAt": "2024-01-01T00:00:00Z", "updatedAt": "2024-01-01T00:00:00Z" },
+    { "id": 4, "labelId": "SPAM", "name": "SPAM", "type": "system", "messageListVisibility": "hide", "labelListVisibility": "labelShow", "messagesTotal": 0, "messagesUnread": 0, "color": null, "createdAt": "2024-01-01T00:00:00Z", "updatedAt": "2024-01-01T00:00:00Z" },
+    { "id": 5, "labelId": "DRAFT", "name": "DRAFT", "type": "system", "messageListVisibility": "hide", "labelListVisibility": "labelShow", "messagesTotal": 0, "messagesUnread": 0, "color": null, "createdAt": "2024-01-01T00:00:00Z", "updatedAt": "2024-01-01T00:00:00Z" },
+    { "id": 6, "labelId": "STARRED", "name": "STARRED", "type": "system", "messageListVisibility": "hide", "labelListVisibility": "labelShow", "messagesTotal": 0, "messagesUnread": 0, "color": null, "createdAt": "2024-01-01T00:00:00Z", "updatedAt": "2024-01-01T00:00:00Z" },
+    { "id": 7, "labelId": "UNREAD", "name": "UNREAD", "type": "system", "messageListVisibility": "hide", "labelListVisibility": "labelHide", "messagesTotal": 0, "messagesUnread": 0, "color": null, "createdAt": "2024-01-01T00:00:00Z", "updatedAt": "2024-01-01T00:00:00Z" },
+    { "id": 8, "labelId": "IMPORTANT", "name": "IMPORTANT", "type": "system", "messageListVisibility": "hide", "labelListVisibility": "labelShow", "messagesTotal": 0, "messagesUnread": 0, "color": null, "createdAt": "2024-01-01T00:00:00Z", "updatedAt": "2024-01-01T00:00:00Z" },
+    { "id": 9, "labelId": "CATEGORY_PERSONAL", "name": "CATEGORY_PERSONAL", "type": "system", "messageListVisibility": "hide", "labelListVisibility": "labelHide", "messagesTotal": 0, "messagesUnread": 0, "color": null, "createdAt": "2024-01-01T00:00:00Z", "updatedAt": "2024-01-01T00:00:00Z" },
+    { "id": 10, "labelId": "CATEGORY_SOCIAL", "name": "CATEGORY_SOCIAL", "type": "system", "messageListVisibility": "hide", "labelListVisibility": "labelHide", "messagesTotal": 0, "messagesUnread": 0, "color": null, "createdAt": "2024-01-01T00:00:00Z", "updatedAt": "2024-01-01T00:00:00Z" },
+    { "id": 11, "labelId": "CATEGORY_PROMOTIONS", "name": "CATEGORY_PROMOTIONS", "type": "system", "messageListVisibility": "hide", "labelListVisibility": "labelHide", "messagesTotal": 0, "messagesUnread": 0, "color": null, "createdAt": "2024-01-01T00:00:00Z", "updatedAt": "2024-01-01T00:00:00Z" },
+    { "id": 12, "labelId": "CATEGORY_UPDATES", "name": "CATEGORY_UPDATES", "type": "system", "messageListVisibility": "hide", "labelListVisibility": "labelHide", "messagesTotal": 0, "messagesUnread": 0, "color": null, "createdAt": "2024-01-01T00:00:00Z", "updatedAt": "2024-01-01T00:00:00Z" },
+    { "id": 13, "labelId": "CATEGORY_FORUMS", "name": "CATEGORY_FORUMS", "type": "system", "messageListVisibility": "hide", "labelListVisibility": "labelHide", "messagesTotal": 0, "messagesUnread": 0, "color": null, "createdAt": "2024-01-01T00:00:00Z", "updatedAt": "2024-01-01T00:00:00Z" }
+  ],
+  "emails": [],
+  "emailAttachments": [],
+  "calendars": [
+    {
+      "id": 1,
+      "calendarId": "testuser@example.com",
+      "summary": "Test User",
+      "description": null,
+      "timeZone": "America/New_York",
+      "isPrimary": true,
+      "accessRole": "owner",
+      "backgroundColor": "#4285f4",
+      "foregroundColor": "#ffffff",
+      "selected": true,
+      "createdAt": "2024-01-01T00:00:00Z",
+      "updatedAt": "2024-01-01T00:00:00Z"
+    }
+  ],
+  "events": [],
+  "eventAttendees": [],
+  "driveFiles": [],
+  "drivePermissions": [],
+  "docs": [],
+  "spreadsheets": [],
+  "sheets": []
+}