feat(workflows): bind deterministic workflows to persona snapshots

[BastiHu]

Development workflows previously resolved personas as individual actions launched. Library edits, removal, disabling, or provider changes could therefore alter a workflow after it had already been accepted.

This adds the deterministic development workflow and binds all seven required roles when the workflow starts. The server reads the external YAML library once, validates each role and its workflow-owned authority, resolves its exact model route, and stores immutable definition snapshots and assignments in the workflow execution record. Later phases, corrections, retries, and review restarts reuse those assignments. Legacy tasks without complete snapshots remain readable but require a fresh task to continue, and unavailable pinned providers produce an actionable block instead of silently rerouting.

The change also removes production persona definitions and prompt fallbacks. New environments start with an empty library; Settings continues to support external folders, imports, editing, disabling, removal, and conflict detection. The eleven previous definitions were exported unchanged to the local j5-personas folder and are not part of the repository.

Validation:

• focused server persona, workflow, routing, runtime-policy, launch, persistence, and contract tests: 23 files / 220 tests passed
• focused web workflow and integration tests: 10 files / 80 tests passed
• server, web, mobile, contracts, client-runtime, and workflow-contracts typechecks
• targeted lint for the new server persona/workflow implementation
• workflow source manifest verification and server bundle build
• all eleven external YAML definitions round-trip exactly; production bundles contain no default definitions or synthetic fixtures
• git diff --check

Model: GPT-6 · Harness: Codex

[Jacksondr5]

Heads-up: this PR touches Squadron code that is being removed.

What changed on j5/main (2026-10-08). J5 is retiring Squadrons and folding their behavior into projects (#412, decided 2026-10-05). The client half has merged (#454, #455, #456):

• The Squadron picker, draft chip, sidebar Squadron filter, first-run gate and the Create, Rename and Delete Squadron dialogs are gone. Most of apps/web/src/j5/squadron/ is deleted.
• New threads, drafts, the sidebar filter and Add Project use upstream's project flow again.
• The Fleet page, Inbox and thread cards read the thread's project.

Still to come. The server migration re-keys the ledger from Squadrons to projects, removes list_squadrons and join_squadron, and renames squadron_id / squadronId to project fields across the server, the shared contracts and the peer protocol. After that, a rename pass removes the word from the remaining code.

For this PR. It reads and writes Squadron ids in about 175 changed lines, mostly in apps/web/src/j5/workflow/ (CreateWorkflowDialog.tsx, RunsPage.tsx, WorkflowsPanel.tsx, useCreateWorkflow.ts), apps/server/src/j5/workflow/SidebarRead.ts and apps/server/src/j5/workflow-definitions/Service.ts. It also edits apps/web/src/j5/squadron/SquadronDirectory.ts, which is going away with the migration.

When you next rebase: scope by the thread's or workspace's projectId where this uses a Squadron, and drop any Squadron picker in the create dialog. No Squadron needs to be chosen or sent when a thread is launched; the server derives the home from the project.

Posted by an AI agent on Jackson's behalf.