feat(pm): PM skill pack fast-follows — single /pm command, portfolio roll-up, real health bottlenecks

[getappz]

Rebased/integrated version of #469 onto current master.

#469 predates two subsequent master changes that conflicted with it:

• crates/agentflare-backend/src/item.rs was independently split into item/{claim,crud,relations,search}.rs submodules on master (item feat(pm): PM skill pack fast-follows — single /pm command, portfolio roll-up, real health bottlenecks #469's own scope also included this exact split — now superseded, kept master's structure).
• The assignment_events recording call (the actual new feature — wires item::update's assignee-change detection into the health bottleneck signal) has been re-applied on top of master's crud.rs.
• Migration 0011_item_assignment_events.sql is byte-identical on both sides (already picked up by fix: recover schema-ahead DB migration + worktree branch-resolution collision #471's DB-recovery fix) — no real conflict there.
• Removed one now-stale test (item_health_reports_velocity_wip_and_bottleneck_placeholder) whose "no handoff history" placeholder assertion is superseded by the real bottleneck detection this PR enables; the identical scenario is already covered by item_health_reports_velocity_wip_and_empty_bottlenecks.
• Applied CodeRabbit's one nitpick from the sibling PR fix(agent_launch): headless work-item dispatch flashes a visible console window on Windows #473 pattern proactively where relevant.

Full local verification: cargo build, cargo fmt --check, cargo clippy --workspace -- -A unsafe_code -A clippy::pedantic -D warnings, cargo test --workspace --bins (1286 passed, 0 failed).

Supersedes #469 — closing that one in favor of this rebased version.

[coderabbitai]

Warning

Review limit reached

You’ve reached a temporary PR review limit under our Fair Usage Limits Policy.

Your recent review volume is higher than typical usage, so adaptive limits are currently applied.

Next review available in: 24 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: a9bc4b9e-89a6-4c4e-8d02-d994cf508a3b

📥 Commits

Reviewing files that changed from the base of the PR and between 0fe2b65 and 28ed541.

📒 Files selected for processing (11)

• .claude/commands/pm.md
• .claude/skills/pm/SKILL.md
• crates/agentflare-backend/src/assignment_events.rs
• crates/agentflare-backend/src/item/crud.rs
• crates/agentflare-backend/src/lib.rs
• src/mcp_server.rs
• src/mcp_server/item.rs
• src/mcp_server/tests/item_tests.rs
• src/mcp_server/tests/item_tests_reporting.rs
• src/mcp_server/tests/mod.rs
• src/mcp_server/types.rs

---

_{Comment @coderabbitai help to get the list of available commands.}