feat(fls): a project's own applications through the editor model

The model carries the captured beans of a project's own applications
(ownApplicationsByNodeId); the export writes them again on the system
software of their node, and their classes go with the archive's other
entries. Checked by Java: from the exported files FILIUS loads
Accumulator and Broadcast as from the original; the export test no longer
leaves own applications out, and a probe that drops them is caught.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

packages/fls/test/exportProject.test.ts

@@ -39,7 +39,6 @@ import {
   type ProjectToExport,
 } from '../src/index.js';
 import { writeTopologyXml } from '../src/topologyWriter.js';
-import { withoutOwnApplications } from './ownApplications.js';
 
 const here = dirname(fileURLToPath(import.meta.url));
 const corpusRoot = join(here, '../../../corpus');
@@ -350,8 +349,7 @@ describe('the editor model exported, as Java loads it', () => {
           return nic.mac === derived ? derived : undefined;
         }),
       );
-      // The model does not install own applications yet (B2).
-      const source = withoutOwnApplications(original[name]!);
+      const source = original[name]!;
       const nodeIds = project.graph.nodes.map((node) => node.id);
       const pairs = nodeIds.map((id) => project.remoteLinkConfigurations.get(id)?.pairIdentifier);
       // The account files of each host the export writes anew, by path, as the file has them.