Clean up module outputFile calculation and move it to the specifications

[alfonso-noriega]

WHY are these changes introduced?

The outputFileName property was previously calculated dynamically using a getter method that relied on the extension's build configuration mode. This approach was inflexible and didn't allow for extension-specific customization of output file names.

WHAT is this pull request doing?

• Converts outputFileName from a computed getter to a direct property on ExtensionInstance
• Adds an optional getOutputFileName method to the ExtensionSpecification interface
• Implements getOutputFileName in all UI extension specifications to return ${extension.handle}.js
• Implements getOutputFileName in function extensions to return index.wasm
• Refactors the BuildConfig type to use a discriminated union for better type safety
• Initializes outputFileName in the constructor using the specification's method or defaults to empty string

How to test your changes?

1. Create extensions of different types (UI extensions, functions, etc.)
2. Verify that the output file names are generated correctly for each extension type
3. Test the build process to ensure extensions are built with the expected output file names
4. Confirm that existing functionality remains unchanged

Measuring impact

How do we know this change was effective? Please choose one:

• n/a - this doesn't need measurement, e.g. a linting rule or a bug-fix

Checklist

• I've considered possible cross-platform impacts (Mac, Linux, Windows)
• I've considered possible documentation changes

[alfonso-noriega]

• Add client steps implementation to support existing functionalities #6966 : 2 dependent PRs (#6867 , #6941 )
• Create abstract client steps infrastracture to externalize the ap modules client configurations #6965
• Clean up module outputFile calculation and move it to the specifications #6967 👈 (View in Graphite)
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

[github-actions]

We detected some changes at packages/*/src and there are no updates in the .changeset.
If the changes are user-facing, run pnpm changeset add to track your changes and include them in the next release CHANGELOG.

Caution

DO NOT create changesets for features which you do not wish to be included in the public changelog of the next CLI release.

[binks-code-reviewer]

🤖 Code Review · #projects-dev-ai for questions
React with 👍/👎 or reply — all feedback helps improve the agent.

✅ Complete - No issues

📋 History

✅ No issues → ✅ 2 findings → ❌ Failed → ✅ No issues

[github-actions]

Coverage report

St.❔	Category	Percentage	Covered / Total
🟡	Statements	77.31%	14594/18878
🟡	Branches	70.84%	7224/10197
🟡	Functions	76.34%	3716/4868
🟡	Lines	78.8%	13798/17511

Test suite run success

3811 tests passing in 1473 suites.

Report generated by 🧪jest coverage report action from 40c8534