feat(pm): status mapping parity across Linear and JIRA

[zbigniewsobiecki]

Summary

Closes spec 003-linear-status-mapping-parity. Linear PM integration now reaches full parity with Trello + JIRA on CASCADE stage → agent dispatch; JIRA silently-dropped mappings now actually work.

What the operator sees

• Linear wizard Field Mapping step now shows 8 status slots in lifecycle order (backlog, splitting, planning, todo, inProgress, inReview, done, merged), up from 4. Map a Linear workflow state to planning and the planning agent dispatches on issue transitions — previously impossible.
• Existing Linear integrations upgrade in place: the 4 new slots render as "not set" on next wizard visit; no migration, no operator action required to keep existing mappings working.

What changes behind the scenes

• src/pm/lifecycle.ts — ProjectPMConfig.statuses widens from 5 to 9 declared optional keys (adds splitting, planning, todo, debug). The canonical type is now the single source of truth for the CASCADE stage vocabulary.
• src/pm/linear/integration.ts — resolveLifecycleConfig passes splitting/planning/todo/merged through.
• src/pm/jira/integration.ts — silent-drop bug fix. JIRA's wizard already accepted splitting/planning/todo mappings for months, but resolveLifecycleConfig was dropping them — so any agent lifecycle hook (hooks.moveOnPrepare: 'planning') targeting those statuses silently no-op'd. Now passes all 8 through.
• web/src/components/projects/pm-wizard-linear-steps.tsx — LINEAR_STATUS_SLOTS grows from 4 entries to 8.

Not touched

• Trello wizard, JIRA wizard UI, Sentry integration, label mappings, STATUS_TO_AGENT map.
• debug stage: declared on the canonical type for future use, but not surfaced on any wizard UI until a debug trigger handler lands.
• No DB migration. Config is JSONB and the new keys are additive-optional.

Tests

• 9 new unit tests (tests/unit/pm/lifecycle-config-shape.test.ts, linear-integration.test.ts, jira-integration.test.ts, tests/unit/web/linear-field-mapping-step.test.ts).
• Spec ACs fix: use CI environment for deploy workflow secrets #8/fix: improve PostgreSQL startup reliability and agent documentation #9 (agent dispatch for splitting/planning/todo/merged) are covered by the pre-existing tests/unit/triggers/linear-status-changed.test.ts and jira-status-changed.test.ts — discovered during implementation that status-changed handlers read provider-specific config directly (not resolveLifecycleConfig), so dispatch was never blocked at the handler level. The real silent-drop surfaced in downstream PMLifecycleManager and GitHub PR triggers; fixing resolveLifecycleConfig unblocks those.

Totals: 7597 unit + 522 integration — all green. Root + web typecheck + lint clean.

Test plan

• npm test — 7597 passing
• TEST_DATABASE_URL=... npm run test:integration — 522 passing
• npm run lint — clean
• npm run typecheck — clean
• cd web && npx tsc -b — clean
• On dev after deploy: open the Linear wizard on project llmist, confirm 8 status slots render in lifecycle order, map one of the new slots (e.g. planning), save, reload, confirm persistence.
• On dev after deploy: move a Linear issue into the newly-mapped state; confirm the expected agent (e.g. planning) starts in the runs dashboard.
• On dev after deploy: move a JIRA issue into a pre-existing splitting / planning / todo mapping; confirm the agent now dispatches (was silently dropped before).

🤖 Generated with Claude Code

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!