Imported from wtthornton/agentforge-workflow-plugin (
.tapps-mcp/backups/2026-08-03-213426/.claude/skills/tapps-upgrade/SKILL.md). Install upstream withnpx skills add wtthornton/agentforge-workflow-plugin --skill tapps-upgrade. Copyright stays with the author.
Upgrade tapps-mcp / docs-mcp end-to-end. The user's request to upgrade is standing authorization for the full pipeline — do NOT pause mid-flow.
Pick an install source from the prompt:
- Local checkout (
--from-checkout <path>or user mentions a local clone):uv tool install --reinstall --from <path>/packages/tapps-mcp tapps-mcpand the same fordocs-mcp. - Git tag (
--from-tag vX.Y.Z):uv tool install --reinstall "git+https://github.com/wtthornton/tapps-mcp.git@vX.Y.Z#subdirectory=packages/tapps-mcp" tapps-mcpand the same fordocs-mcp. - If neither is specified, ASK once which to use.
Steps:
- Reinstall global CLIs. Run both
uv tool install --reinstall ...commands. Verify:uv tool list | grep -E '(tapps-mcp|docs-mcp)'— both must show the same version. - Restart MCP servers. The running processes still hold old code. Tell the user to exit/reopen (or
/mcpreconnect), then re-invoke this skill. Stop here on the first invocation. - Verify new version is live. Call
mcp__nlt-build__tapps_session_start(force=true). Confirmserver.versionmatches target anddiagnostics.install_drift.drift_detected == false. If drift persists, the server wasn't restarted — go back to step 2. - Dry-run the scaffolding refresh. Run
tapps-mcp upgrade --dry-run. Review the diff for AGENTS.md, CLAUDE.md, .claude/hooks/, .claude/rules/, .claude/agents/, .claude/skills/, .mcp.json. Notemcp_bundle/mcp_bundle_notein the result — custom trimmed Cursor sets are preserved; explicit yaml wins. The smart-merge preserves customizations in non-canonical sections; canonical sections are replaced wholesale. Pause if a customized canonical section will be overwritten. - Apply the upgrade. Run
tapps-mcp upgrade(writes timestamped backup to.tapps-mcp/backups/<ts>/). - Verify. Run
tapps-mcp doctorANDmcp__nlt-build__tapps_checklist(task_type="upgrade"). Surface any problems — do not declare done on a failure. Doctor NLT row shows eager (Claude) vs listed (Cursor). - Report. One-line summary:
Upgraded: tapps-mcp X.Y.Z, docs-mcp X.Y.Z. Scaffolding: N files. Bundle: <mcp_bundle>. Doctor: OK. Checklist: complete. Backup: .tapps-mcp/backups/<ts>/.
Bundle opt-down after upgrade: tapps-mcp mcp-bundle set developer|minimal|… then reload MCP (do not hand-edit mcp.json and expect upgrade to keep a yaml=full mismatch).
Rollback (only if step 5/6 broke something): tapps-mcp rollback restores from the most recent backup. Do NOT roll back "to be safe" after a clean run.
Do NOT:
- Publish to PyPI / npm — tapps-mcp is local-install only.
- Bump versions in the tapps-mcp dev repo itself — separate workflow.
- Touch tapps-brain — separate Docker service with its own release flow.
- Add
tapps-brainas a top-level.mcp.jsonentry — it's bridge-only via tapps-mcp's BrainBridge.
