Emdash — lessons for Forge

Sources:

• https://github.com/generalaction/emdash
• https://github.com/generalaction/emdash/blob/main/agents/workflows/worktrees.md
• https://github.com/generalaction/emdash/blob/main/CONTRIBUTING.md

Observed source lessons

Emdash treats one task worktree as a real provisioning pipeline rather than only git worktree add: inspect, resolve base, add, verify, plus lifecycle scripts/settings around the environment.

It supports local and remote machines and multiple CLI providers, demonstrating the long-term value of keeping provider integration and runtime/workspace concerns organized behind explicit boundaries.

Contributor guidance calls out process/PTY and database/migration areas as sensitive infrastructure.

Forge decisions influenced

• worktree creation is a lifecycle/Operation;
• project setup scripts belong to a trust boundary;
• process launch/environment handling should be centralized;
• Execution Environment should be a first-class abstraction independent from agent strategy;
• migrations deserve dedicated tests and upgrade discipline.