feat(pm): expand MCP, routines, work items, inbox, and skills - #844
Open
Neonforge98 wants to merge 3 commits into
Open
feat(pm): expand MCP, routines, work items, inbox, and skills#844Neonforge98 wants to merge 3 commits into
Neonforge98 wants to merge 3 commits into
Conversation
Neonforge98
marked this pull request as draft
August 20, 2026 03:15
Neonforge98
changed the title
Neonforge98
marked this pull request as ready for review
August 20, 2026 05:15
Neonforge98
marked this pull request as draft
August 20, 2026 05:15
Neonforge98
marked this pull request as ready for review
August 20, 2026 05:31
Neonforge98
marked this pull request as draft
August 20, 2026 07:27
Neonforge98
marked this pull request as ready for review
August 20, 2026 07:42
Neonforge98
marked this pull request as draft
August 20, 2026 08:34
Neonforge98
marked this pull request as ready for review
August 20, 2026 08:48
Neonforge98
force-pushed
the
feat/pm-expansion-batch
branch
from
August 20, 2026 21:48
437b322 to
a7e9043
Compare
Neonforge98
changed the title
Neonforge98
force-pushed
the
feat/pm-expansion-batch
branch
2 times, most recently
from
August 23, 2026 01:32
ecd8788 to
b15c6ee
Compare
Harry19081
added
enhancement
This was referenced Aug 25, 2026
Neonforge98
force-pushed
the
feat/pm-expansion-batch
branch
2 times, most recently
from
August 27, 2026 16:48
8e9b3b4 to
61ef78b
Compare
Neonforge98
force-pushed
the
feat/pm-expansion-batch
branch
21 times, most recently
from
September 2, 2026 00:11
c0b0f5a to
2b8c2f2
Compare
Add revision-aware work items, custom properties, statuses, saved views, quick actions, routines, work timelines, and their desktop UI/API contracts.
Add MCP isolation, skill provenance, routine execution, follow-up suggestions, worktree safety, runtime error classification, and integration UI wiring used by project collaboration.
Add shared audience routing, Team Inbox coordination, Work Item discussion actions, queued delivery visibility, idempotent retries, and human-versus-Agent message handling.
Neonforge98
force-pushed
the
feat/pm-expansion-batch
branch
from
September 2, 2026 03:33
1eaec91 to
e044511
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
Project-management capabilities were spread across Work Items, MCP, routines, Inbox, Skills, quick actions, and saved views, with duplicated audience and error handling plus incomplete cross-surface workflows.
Solution
Complete the existing PM stack as one coherent feature layer: Work Item properties, statuses and views; routines and quick actions; Team Inbox; shared Skills; MCP injection; CLI timeline support; human audience routing; loopback cloud sign-in; and shared runtime-error classification.
Native cross-provider conversation continuation is intentionally not owned by Work Items. PR #939 is stacked on this PR and supplies that generic session capability.
Potential risks
This is a broad frontend, Rust, and protocol change. The main risks are Work Item sync concurrency, schema drift, audience-routing regressions, and MCP or session policy leakage. The implementation centralizes these paths and adds focused contract and integration coverage.
Verification