fix(automations): keep nested workspace jobs visible

[jcllobet]

Summary

• keep scheduler-backed automations visible when the selected OpenWork workspace is nested under the job's stored workdir by falling back from exact matches to related parent/child workspace roots
• apply the same workdir matching behavior in both the desktop Tauri scheduler commands and the OpenWork server scheduler API so local and remote listings stay aligned
• add focused coverage for the new fallback matching logic in apps/server/src/scheduler.test.ts and Rust unit tests in apps/desktop/src-tauri/src/commands/scheduler.rs

Current vs expected behavior

• Current: local automations only appear when the selected workspace root exactly equals the job's stored workdir; if a job was created at /Users/jan/Programming/the-cloud-factory, opening /Users/jan/Programming/the-cloud-factory/_repos/openwork hides it completely
• Expected: when no exact workspace-root match exists, OpenWork should still surface related automations from a nested parent/child workspace root instead of making a working automation look missing

Before and after

These screenshots use the real local scheduler jobs on this machine with a nested selected workspace root of /Users/jan/Programming/the-cloud-factory/_repos/openwork.

Before

After

Validation

• pnpm --filter openwork-server test -- ./src/scheduler.test.ts
• pnpm --filter openwork-server build:bin
• cargo test scheduler::tests --lib in apps/desktop/src-tauri
• cargo check --lib in apps/desktop/src-tauri
• bun -e '...' against real local scheduler job JSONs to confirm the existing automations stay visible for /Users/jan/Programming/the-cloud-factory, /Users/jan/Programming/the-cloud-factory/_repos/openwork, and /Users/jan/Programming/the-cloud-factory/_repos/openwork/apps/app

UI verification blocker

• I attempted the required Docker + Chrome MCP flow with packaging/docker/dev-up.sh, but the dev stack failed before the web UI became available
• First failure: share exited during dependency setup with ENOTEMPTY: directory not empty, rmdir '/app/node_modules/.pnpm'
• After clearing the stale dev volumes and retrying, orchestrator failed with ERR_PNPM_ENOTEMPTY: ENOTEMPTY: directory not empty, rmdir '/app/node_modules/.pnpm/[email protected]/node_modules/dayjs'
• Because the UI stack never reached a healthy state, these before/after screenshots are repo-backed reproduction artifacts derived from the same local scheduler data rather than live Chrome MCP captures of the full app

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
openwork-app	Ready	Preview, Comment	Apr 8, 2026 2:11am
openwork-den	Ready	Preview, Comment	Apr 8, 2026 2:11am
openwork-den-worker-proxy	Ready	Preview, Comment	Apr 8, 2026 2:11am
openwork-landing	Ready	Preview, Comment, Open in v0	Apr 8, 2026 2:11am
openwork-share	Ready	Preview, Comment	Apr 8, 2026 2:11am

[github-actions]

The following comment was made by an LLM, it may be inaccurate: