Skip to content

chore(submod): bump mcps/internal -> 47bd0638 (#2409 W1/W2/W3 follow-ups)#2436

Merged
jsboige merged 1 commit into
mainfrom
wt/submod-bump-562
May 30, 2026
Merged

chore(submod): bump mcps/internal -> 47bd0638 (#2409 W1/W2/W3 follow-ups)#2436
jsboige merged 1 commit into
mainfrom
wt/submod-bump-562

Conversation

@myia-ai-01
Copy link
Copy Markdown
Collaborator

Pointer bump

Advances mcps/internal (roo-state-manager) from 58a81584 to 47bd0638 — the squash SHA of jsboige-mcp-servers#562.

What #562 delivered (ServicesConfigService, VibeSync Epic #2406 / #2409)

  • W1stopProcess PID-filtered kill (collected PID → CIM Win32_Process name+startCommand filter → named fallback), avoids killing unrelated same-name processes.
  • W2startArgs rendered as a PowerShell -ArgumentList @(...) array with single-quote escaping.
  • W3 — bidirectional applyTargets(desiredStatuses) with per-target reconciliation + stop-rollback.
  • +14 unit tests (ServicesConfigService.test.ts).

Anti-#1799 compliance

check-submodule-pointer should go green.

🤖 Generated with Claude Code

…3 follow-ups)

Advances the roo-state-manager submodule pointer to the squash SHA of
jsboige-mcp-servers#562 (W1 PID filter, W2 startArgs array, W3 bidirectional
apply for ServicesConfigService). Anti-#1799: parent bump created AFTER the
submod PR merged; target SHA is the squash commit, verified cat-file -e +
merge-base --is-ancestor origin/main.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Copy link
Copy Markdown
Owner

@jsboige jsboige left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pointer-bump to #562 squash SHA 47bd0638. Anti-#1799 verified: submod PR merged 04:52:56Z, target SHA is reachable on mcps/internal origin/main (cat-file -e + merge-base --is-ancestor). Approving as codeowner (author=myia-ai-01).

@jsboige jsboige merged commit ec55e33 into main May 30, 2026
4 checks passed
@jsboige jsboige deleted the wt/submod-bump-562 branch May 30, 2026 05:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants