@otto-code/protocol 0.8.3 → 0.8.4

package/dist/forge-manifest.js

@@ -22,6 +22,17 @@ export const FORGE_DEFINITIONS = [
         signIn: { cli: "gh", command: "gh auth login" },
         cloudHosts: ["github.com", "ssh.github.com"],
     },
+    {
+        id: "bitbucket-cloud",
+        displayName: "Bitbucket Cloud",
+        changeRequestAbbrev: "PR",
+        changeRequestNoun: "pull request",
+        changeRequestNumberPrefix: "#",
+        issueNumberPrefix: "#",
+        iconKind: "bitbucket-cloud",
+        signIn: null,
+        cloudHosts: ["bitbucket.org"],
+    },
     {
         id: "gitlab",
         displayName: "GitLab",

package/dist/messages.js

@@ -8398,13 +8398,9 @@ export const CheckoutPrStatusSchema = z.object({
     // Provider-neutral per-PR hosting facts. Absent from old daemons; for
     // GitHub projects both this and the legacy `github` field are populated.
     //
-    // NOT a shim, and deliberately untagged: this does not collapse into `forge`.
-    // Otto registers every hosting provider into the forge registry under the
-    // forge id `github`, which is the provider-routing facade rather than the gh
-    // CLI (bootstrap.ts, `createGitHostingResolver`). So `forge` reads "github"
-    // for a Bitbucket workspace and only `hosting.provider` carries the truth.
-    // The two disagree by design; a reader wanting the real provider must use
-    // this field.
+    // NOT a shim, and deliberately untagged: this carries provider capabilities
+    // alongside the Forge identity. They match for built-in hosts today, but the
+    // provider remains the source of truth for hosting-specific capabilities.
     hosting: z
         .object({
         provider: GitHostingProviderIdWireSchema,
@@ -8430,9 +8426,8 @@ const CheckoutPrStatusPayloadSchema = z.object({
     githubFeaturesEnabled: z.boolean(),
     // Provider-neutral enablement. Present even when status is null so clients
     // can drive search/create-PR affordances for the workspace's provider.
-    // Permanent for the same reason as the `hosting` block on the PR status
-    // schema above: `forge` is a routing-facade id and cannot answer "which
-    // provider is this really".
+    // Permanent so provider-specific capability decisions do not need to infer
+    // behavior from the Forge presentation identity.
     hosting: z
         .object({
         provider: GitHostingProviderIdWireSchema,

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@otto-code/protocol",
-  "version": "0.8.3",
+  "version": "0.8.4",
   "description": "Otto shared protocol schemas and wire types",
   "license": "AGPL-3.0-or-later",
   "files": [
@@ -37,7 +37,7 @@
   "devDependencies": {
     "@types/node": "^20.9.0",
     "typescript": "^5.2.2",
-    "vitest": "^4.1.6",
+    "vitest": "^4.1.10",
     "zod-aot": "0.20.4"
   }
 }