fix(install): resolve '+' version in env.jsonc for env capsules

When generating .bit_roots package.json for env capsules, the '+' version
placeholder from env.jsonc was passed directly to pnpm, causing
"isn't supported by any available resolver" errors.

The fix resolves '+' by looking up the already-resolved version from
the env component's dependencies (via getDependencies), leveraging
the existing resolution infrastructure in apply-overrides.

Author: davidfirst

e2e/harmony/lanes/lane-import.e2e.ts

@@ -312,6 +312,56 @@ describe('bit lane import operations', function () {
     });
   });
 
+  describe('lane import with env using "+" version for component peer dependency (snaps)', () => {
+    before(() => {
+      helper.scopeHelper.setWorkspaceWithRemoteScope();
+      // Create comp1 which will be used as a peer dependency in the env
+      helper.fs.outputFile('comp1/index.js', 'module.exports = function() { return "comp1"; };');
+      helper.command.addComponent('comp1');
+      // Create an env with "+" version for comp1 in the peers
+      helper.env.setEmptyEnv();
+      const comp1PkgName = helper.general.getPackageNameByCompName('comp1', false);
+      helper.fs.outputFile(
+        'empty-env/env.jsonc',
+        `{
+  "policy": {
+    "peers": [
+      {
+        "name": "${comp1PkgName}",
+        "version": "+",
+        "supportedRange": "^0.0.1"
+      }
+    ]
+  }
+}
+`
+      );
+      // Create comp2 (independent) that uses the env
+      helper.fs.outputFile('comp2/index.js', 'module.exports = function() { return "comp2"; };');
+      helper.command.addComponent('comp2');
+      helper.command.setEnv('comp2', 'empty-env');
+      // Create a lane and snap (not tag) - this creates hash-based versions
+      helper.command.createLane('dev');
+      helper.command.snapAllComponentsWithoutBuild();
+      helper.command.export();
+    });
+    // This test verifies the fix for the bug where "+" version resolution
+    // was not properly resolving to the actual version from workspace/bitmap,
+    // causing pnpm to receive "+" as a version which it cannot handle
+    it('should resolve "+" version and not pass it directly to pnpm', () => {
+      helper.scopeHelper.reInitWorkspace();
+      helper.scopeHelper.addRemoteScope();
+      // Import the component using the env - this triggers installation
+      // where the "+" version must be resolved to actual version
+      const output = helper.command.importLane('dev', `--pattern ${helper.scopes.remote}/comp2`);
+      // The "+" should be resolved to actual version, not passed to pnpm directly
+      // The specific error we're fixing is "isn't supported by any available resolver"
+      // which happens when "+" is passed as a version to pnpm
+      expect(output).to.not.have.string("isn't supported by any available resolver");
+      expect(output).to.not.have.string('@+'); // No "@+" should appear in error messages
+    });
+  });
+
   describe('getting new components from the lane', () => {
     let firstWorkspaceAfterExport: string;
     let secondWorkspace: string;

scopes/dependencies/dependency-resolver/manifest/workspace-manifest-factory.ts

@@ -258,7 +258,8 @@ export class WorkspaceManifestFactory {
       const currentDeps = this.dependencyResolver.getDependencies(component);
       const found = currentDeps.findByPkgNameOrCompId(name);
       // If not found, use '*' as fallback
-      return [name, found?.version || '*'];
+      // Use snapToSemver to convert raw hash versions to valid semver format (0.0.0-{hash})
+      return [name, found?.version ? snapToSemver(found.version) : '*'];
     });
     return fromPairs(resolved);
   }

scopes/workspace/install/install.main.runtime.ts

@@ -951,10 +951,27 @@ export class InstallMain {
   private async _getEnvDependencies(envId: ComponentID): Promise<Record<string, string>> {
     const policy = await this.dependencyResolver.getEnvPolicyFromEnvId(envId);
     if (!policy) return {};
+
+    // Get the env component to access its resolved dependencies
+    // The "+" versions are resolved during dependency detection in apply-overrides.resolveEnvPeerDepVersion
+    const envComponent = await this.envs.getEnvComponentByEnvId(envId.toString(), envId.toString());
+    const envDeps = envComponent ? this.dependencyResolver.getDependencies(envComponent) : undefined;
+
     return Object.fromEntries(
       policy.selfPolicy.entries
         .filter(({ force, value }) => force && value.version !== '-')
-        .map(({ dependencyId, value }) => [dependencyId, value.version])
+        .map(({ dependencyId, value }) => {
+          let version = value.version;
+          // Resolve "+" version placeholders by looking up the already resolved version
+          // from the env component's dependencies (resolved in apply-overrides.resolveEnvPeerDepVersion)
+          if (version === '+' && envDeps) {
+            const found = envDeps.findByPkgNameOrCompId(dependencyId);
+            version = found?.version ? snapToSemver(found.version) : '*';
+          } else if (version === '+') {
+            version = '*';
+          }
+          return [dependencyId, version];
+        })
     );
   }