chore(deps): adopt muxcore v0.28.0

[thebtf]

Summary

• bump github.com/thebtf/mcp-mux/muxcore from v0.27.1 to released v0.28.0
• retain Aimux's persistent in-process SessionHandler daemon and existing update/reconnect topology unchanged
• add no consumer-local materialization, dormancy, spawn/retry, PID cleanup, request replay, or updater machinery

Provider module tag muxcore/v0.28.0 resolves to commit 1b91f54c1d517db352136c7d16949a2662c52b0e.

Applicability

Aimux uses engine.Config{Persistent: true, SessionHandler: ...} without an upstream Command. Tagged v0.28.0 keeps zero-value materialization eager and forces persistent owners to MaterializationPersistent; cache-only discovery, first-demand materialization, and environment-template bypass are therefore structurally N/A to this consumer topology. Retained-host-stdio dormancy remains disabled and provider-gated by Engram #373.

Verification

• go mod download github.com/thebtf/mcp-mux/muxcore@v0.28.0
• go list -m -f ... matched version/ref/hash/sums
• go build ./...
• go vet ./...
• go test ./... -count=1 (57 packages passed; 4 packages had no tests)
• focused lifecycle E2E package passed
• customer-mode 29-tool health/resource smoke passed against a separately named engine
• independent checker: ACCEPT
• independent code review: APPROVE, no >80% findings
• context-blind judge: BLIND_ACCEPT, confidence 0.85

go mod verify is blocked only by pre-existing external github.com/mark3labs/mcp-go@v0.47.0 module-cache contamination; clean repo-local GOMODCACHE verification returns all modules verified.

Rollback

Revert this commit to restore muxcore v0.27.1. If provider behavior requires operational rollback beyond this consumer patch, the provider issue names v0.27.2; that would be a separate reviewed dependency update rather than local lifecycle workarounds.

Tracking: Engram #399 (adoption), Engram #373 (retained-stdio provider boundary).

[gemini-code-assist]

Code Review

This pull request updates the dependency github.com/thebtf/mcp-mux/muxcore from version v0.27.1 to v0.28.0 in go.mod and go.sum. There are no review comments, and I have no feedback to provide.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

[coderabbitai]

Walkthrough

Версия зависимости github.com/thebtf/mcp-mux/muxcore в go.mod обновлена с v0.27.1 до v0.28.0.

Changes

Обновление зависимости

Layer / File(s)	Summary
Версия muxcore go.mod	Требуемая версия github.com/thebtf/mcp-mux/muxcore изменена с v0.27.1 на v0.28.0.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Possibly related PRs

• thebtf/aimux#197: затрагивает ту же зависимость github.com/thebtf/mcp-mux/muxcore.

Poem

Прыг-скок — muxcore стал новей,
В go.mod порядок средь полей.
Версия вверх — морковка ввысь,
Пусть сборки бодро понеслись! 🐇

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	Заголовок точно отражает основное изменение: обновление зависимости muxcore до v0.28.0.

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch work/aimux-muxcore-v0280-adoption

---

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