Deploy workspace affinity without schema changes

[michaelmwu]

Purpose

Promote the reviewed workspace-affinity feature to the branch used by the personal Paseo Hub deployment while preserving its existing GitHub team-filter and Linear-trigger customizations.

This applies only the Hub feature delta from getpaseo#86 and pins cross-repository CI to the exact companion daemon commit from getpaseo/paseo#3994.

The current pin is ef9202c3d222ae78adb4f73587176e3503548647.

Deployment safety

• No drizzle/, database schema, lockfile, package, or runtime configuration files change.
• This intentionally avoids rebasing the deployment onto current upstream main, whose 0035–0040 migration lineage diverges from the already-deployed private Linear migration.
• Existing daemons remain compatible and continue creating fresh workspaces when they omit the optional acknowledgement.
• Exact workspace reuse/restoration begins only on daemons that support the companion affinity lease.

QA

Verified locally on Linux against the existing 0.4.0 deployment branch:

• 142 affected config, workflow, provider, protocol, dispatcher, and daemon-registry tests passed
• npm run typecheck passed
• npm run lint passed
• npm run format:check passed
• pre-commit formatting, lint, and typecheck passed
• after final review feedback, 90 config, workflow-engine, and Hub-protocol tests passed again; typecheck, lint, and format checks also passed
• after the final provider/compiler feedback, 89 config and workflow-engine tests passed on the deployment branch; its pre-commit typecheck, lint, and formatting checks also passed
• the production-shaped migration regression passed after correcting its stale expected journal count from 35 to the deployment branch's existing 36 entries; no migration or schema changed
• after the final recovery and event-gating review, 91 config and workflow-engine tests passed on the deployment branch, along with the full typecheck
• after the unstable-worktree review, all 46 deployment-branch compiler tests passed, along with the full typecheck, full lint, and formatting checks
• corrected the private Linear branch's stale browser harness registration and three-provider assertion after the clean browser job exposed the mismatch; the focused provider-readiness browser E2E, production build, full typecheck, full lint, and formatting checks pass
• pinned the companion daemon's persisted-resume lookup/unarchive lease fix after its focused race tests and full pre-commit checks passed
• propagated affinity authority validation through transitive named values; all 109 deployment-branch config tests plus full typecheck, lint, and formatting checks passed
• pinned the daemon's final terminal-creation and stored-relationship archive fences after its complete affected suites passed 287 tests with 4 skipped; the deployment pin commit passed pre-commit formatting and all Hub typechecks
• applied the final transitive named-value runtime fix and shared daemon terminal-manager pin; all 94 deployment-branch compiler and workflow-engine tests passed through workflow completion, along with full typecheck, lint, and formatting checks
• pinned the daemon's final unarchive/archive exclusion fix after both concurrency regressions, all 209 affected archive/affinity tests, and all 289 affected session-workspace/agent-manager tests passed
• pinned the daemon's final affinity restore/create lease fix after all 7 affinity-manager tests, all 16 daemon-execution tests, all 21 bootstrap smoke tests, and full daemon pre-commit checks passed
• pinned the daemon's final stored-agent loading fence after all 190 agent-loading/agent-manager/affinity tests, all 22 workspace-archive tests, all 61 schedule tests, and full daemon pre-commit checks passed
• pinned the daemon's final provider-import fence after both import/archive race orderings, all 220 import/agent-manager/workspace-archive tests, and full daemon pre-commit checks passed
• pinned the daemon's final workspace-recovery/expiry fence after both race orderings, in-exclusion target resolution, all 325 affected tests with 4 skipped, and full daemon pre-commit checks passed
• pinned the daemon's final open-project/expiry fence after both request/archive orderings, all 326 affected tests with 4 skipped, and full daemon pre-commit checks passed
• pinned the daemon's final standalone-provisioning, rename, and duplicate-affinity request fences after all four race regressions, 246 passing tests with 4 skipped across the complete affected files, and full daemon pre-commit checks
• pinned the daemon's final scheduled-provisioning and late-terminal-worker fences after both focused regressions, all 327 affected schedule, terminal-manager, agent-manager, and workspace-archive tests, and full daemon pre-commit checks
• pinned the daemon's residual-worktree cleanup fix after the zero-record retry regression, all 65 affected archive, affinity, bootstrap, and auto-archive tests, and full daemon pre-commit checks

The loopback daemon-registry suite was run outside the filesystem/network sandbox. No UI or database migration changed.

Upstream PR: getpaseo#86

Companion daemon PR: getpaseo/paseo#3994

[michaelmwu]

@codex review

[michaelmwu]

@codex review

[michaelmwu]

@codex review

[michaelmwu]

@codex review

[michaelmwu]

@codex review

[michaelmwu]

@codex review

[michaelmwu]

@codex review

[michaelmwu]

@codex review

[michaelmwu]

@codex review

[michaelmwu]

@codex review

[michaelmwu]

@codex review

[michaelmwu]

@codex review

[michaelmwu]

@codex review

[michaelmwu]

@codex review

[michaelmwu]

@codex review

[michaelmwu]

@codex review

[michaelmwu]

@codex review

[michaelmwu]

@codex review

[michaelmwu]

@codex review

[michaelmwu]

@codex review