Fork builds ship without the orcad deployment template #39

After the 2026-10-22 sync (#38), fork desktop builds ship without the orcad deployment template. Managed SSH hosts then can't be deployed from a fork build.

Why. Upstream stablyai#24155 bundles out/orcad-template as an extraResources entry. Without it:

• orcad-artifact-materializer.ts throws OrcadArtifactsUnavailableError('The packaged orcad deployment template is missing'), which is the path that deploys orcad to managed SSH hosts;
• orca serve falls back to Electron (orcad-local-serve-selection-entry.ts), so orca serve hosts keep working, but not on orcad.

Upstream's release builds the template through the reusable .github/workflows/qualified-orcad-template.yml, downloads the orcad-template artifact into out/orcad-template before packaging (release-mac-build.yml), and sets ORCA_REQUIRE_ORCAD_TEMPLATE=1, so packaging fails rather than ship without it. .github/workflows/swaplabs-build.yml does none of this.

To do

• Build or download the qualified template in swaplabs-build.yml for every leg, and set ORCA_REQUIRE_ORCAD_TEMPLATE=1.
• Check the first post-sync macOS build. afterPack now builds and signs orca_shipit_scheduling.node with the CSC_NAME identity, which is untried with the fork's self-signed identity. On Linux, beforePack now builds the Wayland clipboard helper.
• Confirm on a managed SSH host that a fork desktop build deploys orcad.