Undocumented behavior: Aliasified packages fail to deploy to Production when there is no "prod" folder

[thraco]

Describe the bug
When an aliasified package is deployed to Prod, it fails if it does not contain a prod-specific folder. The Prod deployment does not use the default package.

To Reproduce
Steps to reproduce the behavior:

• Create an aliasified package without a "prod" folder, but with a "default" folder
• Attempt to deploy the aliasified package to a Production environment

Per the logs, the default folder is selected, but the deployment fails. The error message received is Error: Aliasfied package 'redhatcrm-loyalty-mgmt-env-specific' does not have an alias with 'prod' or 'default' directory, which is inaccurate, as this package does have a default directory, as shown in the screenshot below.

On reviewing the documentation, I can find no mention of this behavior, but it's clearly specified in the code (

sfp/src/core/package/packageInstallers/InstallPackage.ts

Lines 145 to 159 in 5082c88

	if (orgDetails.isSandbox) {
	// If the target org is a sandbox, find a 'default' directory to use as package directory
	aliasDir = files.find(
	(file) =>
	path.basename(file) === 'default' &&
	fs.lstatSync(path.join(searchDirectory, file)).isDirectory()
	);
	}
	}
	if (!aliasDir) {
	throw new Error(
	`Aliasfied package '${this.sfpPackage.packageName}' does not have an alias with '${alias}' or 'default' directory`
	);
	}

).

Expected behavior

• Documentation and error messaging match the behavior of the application.

Screenshots

Platform Details (please complete the following information):

• OS: Ubuntu 22.04.4 LTS
• Version: 39.1.0
• Salesforce CLI(sfdx cli) Version: 2.49.7
• CI Platform: GitHub Actions