@codeam/shared 2.61.29 → 2.61.31

package/dist/index.mjs

@@ -590,6 +590,54 @@ var INTEGRATION_REGISTRY = {
       }
     }
   },
+  github: {
+    id: "github",
+    name: "GitHub",
+    icon: "github",
+    category: "version_control",
+    // LIVE. GitHub is the product's code substrate (codespaces + the PR
+    // Command Center), and it was historically the ONE connection outside this
+    // registry: its credential lives in a `ProviderToken` row rather than the
+    // integrations vault, so it was rendered by a hand-written special-case row
+    // and could not legally appear in a deploy's `integrationIds` (the manifest
+    // resolver rejects unknown ids — a recurring bug class).
+    //
+    // `kind: 'connection'` closes that gap without re-plumbing OAuth: the entry
+    // makes GitHub a first-class, categorised catalog row whose credential the
+    // backend resolves from the SAME `ProviderToken` it always used, while the
+    // connect/disconnect flow stays owned by the codespaces rail (the clients
+    // route those two actions there). ⚠️ It is a REAL connection with a REAL
+    // disconnect — do NOT treat it like `github_issues`, which merely derives
+    // from it and has no actions of its own.
+    enabled: true,
+    auth: { kind: "connection", connection: "github" },
+    // No MCP: a deployed box already has an authenticated `gh` on PATH.
+    delivery: {}
+  },
+  github_issues: {
+    id: "github_issues",
+    name: "GitHub Issues",
+    icon: "github_issues",
+    category: "tracker",
+    // LIVE, and the ONLY integration with NO link flow of its own: the
+    // credential is DERIVED from the GitHub connection the user already made
+    // for codespaces/PRs (`ProviderToken` provider='github-codespaces', which
+    // carries `repo` scope — enough for the whole Issues surface). So there is
+    // no OAuth app, no client id/secret, no Secret Manager entry and nothing
+    // to configuration-gate. The backend auto-provisions the catalog row the
+    // same way `ensureHouseAgentRow` does for the house agent, and resolves
+    // the token live per call rather than vaulting a copy (it can't go stale,
+    // and GitHub token refresh stays owned by exactly one place).
+    enabled: true,
+    auth: { kind: "derived", derivedFrom: "github" },
+    // NO MCP server on purpose. Every other tracker needs one to give the agent
+    // tools, but a deployed box ALREADY has an authenticated `gh` on PATH (the
+    // codespace bootstrap exports GH_TOKEN), so `gh issue list/create/comment`
+    // works with zero delivery. That also means nothing to pre-warm and no
+    // third-party MCP package to pin and keep alive. The Start-from-Work-Item
+    // side is served backend-side by the `TrackerProvider`, not by delivery.
+    delivery: {}
+  },
   slack: {
     id: "slack",
     name: "Slack",
@@ -826,10 +874,10 @@ function getIntegrationsByCategory(category) {
 
 // src/integrations/branding.ts
 var INTEGRATION_BRANDING = {
-  // GitHub — a brand-only entry (NOT an `IntegrationId`; v1 reuses the
-  // codespaces OAuth token rather than exposing GitHub as a linkable toolkit).
-  // Present so the PR/MR Command Center surfaces (the review-launch toast, etc.)
-  // render the official GitHub mark from the ONE shared catalog.
+  // GitHub — now a REAL `IntegrationId` (`version_control`, `kind: 'connection'`).
+  // It started life here as a brand-only entry, back when GitHub was rendered by
+  // a hand-written special-case row; the mark is unchanged, it's just also the
+  // catalog row's logo now. Still used by the PR/MR Command Center surfaces.
   github: {
     id: "github",
     name: "GitHub",
@@ -838,6 +886,18 @@ var INTEGRATION_BRANDING = {
     brandColor: "#FFFFFF",
     logoSvg: '<svg role="img" viewBox="0 0 24 24" xmlns="http://www.w3.org/2000/svg"><title>GitHub</title><path fill="#FFFFFF" d="M12 .297c-6.63 0-12 5.373-12 12 0 5.303 3.438 9.8 8.205 11.385.6.113.82-.258.82-.577 0-.285-.01-1.04-.015-2.04-3.338.724-4.042-1.61-4.042-1.61C4.422 18.07 3.633 17.7 3.633 17.7c-1.087-.744.084-.729.084-.729 1.205.084 1.838 1.236 1.838 1.236 1.07 1.835 2.809 1.305 3.495.998.108-.776.417-1.305.76-1.605-2.665-.3-5.466-1.332-5.466-5.93 0-1.31.465-2.38 1.235-3.22-.135-.303-.54-1.523.105-3.176 0 0 1.005-.322 3.3 1.23.96-.267 1.98-.399 3-.405 1.02.006 2.04.138 3 .405 2.28-1.552 3.285-1.23 3.285-1.23.645 1.653.24 2.873.12 3.176.765.84 1.23 1.91 1.23 3.22 0 4.61-2.805 5.625-5.475 5.92.42.36.81 1.096.81 2.22 0 1.606-.015 2.896-.015 3.286 0 .315.21.69.825.57C20.565 22.092 24 17.592 24 12.297c0-6.627-5.373-12-12-12"/></svg>'
   },
+  // GitHub Issues — the `tracker`-category toolkit integration (a real
+  // `IntegrationId`, unlike the `github` entry above). Same official mark, its
+  // own name/tagline so the catalog row reads as the issue tracker rather than
+  // the code host.
+  github_issues: {
+    id: "github_issues",
+    name: "GitHub Issues",
+    vendor: "GitHub",
+    tagline: "Issues & project tracking",
+    brandColor: "#FFFFFF",
+    logoSvg: '<svg role="img" viewBox="0 0 24 24" xmlns="http://www.w3.org/2000/svg"><title>GitHub</title><path fill="#FFFFFF" d="M12 .297c-6.63 0-12 5.373-12 12 0 5.303 3.438 9.8 8.205 11.385.6.113.82-.258.82-.577 0-.285-.01-1.04-.015-2.04-3.338.724-4.042-1.61-4.042-1.61C4.422 18.07 3.633 17.7 3.633 17.7c-1.087-.744.084-.729.084-.729 1.205.084 1.838 1.236 1.838 1.236 1.07 1.835 2.809 1.305 3.495.998.108-.776.417-1.305.76-1.605-2.665-.3-5.466-1.332-5.466-5.93 0-1.31.465-2.38 1.235-3.22-.135-.303-.54-1.523.105-3.176 0 0 1.005-.322 3.3 1.23.96-.267 1.98-.399 3-.405 1.02.006 2.04.138 3 .405 2.28-1.552 3.285-1.23 3.285-1.23.645 1.653.24 2.873.12 3.176.765.84 1.23 1.91 1.23 3.22 0 4.61-2.805 5.625-5.475 5.92.42.36.81 1.096.81 2.22 0 1.606-.015 2.896-.015 3.286 0 .315.21.69.825.57C20.565 22.092 24 17.592 24 12.297c0-6.627-5.373-12-12-12"/></svg>'
+  },
   // npm — a brand-only entry (NOT an `IntegrationId`): the registry the
   // codeam-cli ships to. Present so surfaces like the Wiki can render the
   // official npm mark from the ONE shared catalog instead of a loose asset.