Fix include-assets-step tests after copy-by-pattern pre-glob check

The new fileExists short-circuit in copyByPattern broke the auto-mocked
pattern tests at the step level (fileExists returns undefined → early
return). Add a beforeEach default for the pattern-entries block, and
switch the pattern-only manifest test from a flat false to an
implementation that returns true for the sourceDir path.

Author: isaacroldan

packages/app/src/cli/services/build/steps/include-assets-step.test.ts

@@ -552,6 +552,11 @@ describe('executeIncludeAssetsStep', () => {
   })
 
   describe('pattern entries', () => {
+    beforeEach(() => {
+      // copyByPattern now short-circuits if sourceDir doesn't exist; default true here.
+      vi.mocked(fs.fileExists).mockResolvedValue(true)
+    })
+
     test('copies files matching include patterns', async () => {
       // Given
       vi.mocked(fs.glob).mockResolvedValue(['/test/extension/public/logo.png', '/test/extension/public/style.css'])
@@ -943,11 +948,13 @@ describe('executeIncludeAssetsStep', () => {
     })
 
     test('writes manifest.json with files array when generatesAssetsManifest is true and only pattern inclusions exist', async () => {
-      // Given — pattern entries contribute output paths to the manifest "files" array
+      // Given — pattern entries contribute output paths to the manifest "files" array.
+      // sourceDir must exist for copyByPattern's pre-glob fileExists check to pass;
+      // everything else can read false (the parent beforeEach default).
       vi.mocked(fs.glob).mockResolvedValue(['/test/extension/public/logo.png'])
       vi.mocked(fs.copyFile).mockResolvedValue()
       vi.mocked(fs.mkdir).mockResolvedValue()
-      vi.mocked(fs.fileExists).mockResolvedValue(false)
+      vi.mocked(fs.fileExists).mockImplementation(async (path) => String(path) === '/test/extension/public')
       vi.mocked(fs.writeFile).mockResolvedValue()
 
       const step: LifecycleStep = {