stack-not-at-head-remediationlisted

# Stack-Not-At-Head Remediation ## When to use Invoke this skill when `/health` (or any health-check run) returns: HEALTHCHECK: fail (1) -- stack-not-at-head The healthcheck output includes exact fix commands. Run the commands it prints — but on **this** repo there is one repo-specific side effect that makes the bare `uv sync` non-trivial (see the caution under step 1). Don't re-litigate *which* packages to upgrade; do handle the pysqlite3 regression and MCP restart that follow. ## Key insight (from session 2026-05-20) > "Fair. These aren't risky or ambiguous — the healthcheck gave exact fix commands and the gaps are clear. I should have just run them." When healthcheck provides an exact fix command, execute it — the *package selection* is decided. The one thing that IS repo-specific and must be handled, not skipped, is the post-sync pysqlite3 re-patch + MCP-server restart below. ## Steps ### 1. Run the upgrade command from healthcheck output Upgrade only the packages the healthcheck names (often just `jcodemunch-mcp`). mempalace is decommissioned — do NOT add `--upgrade-package mempalace`. Typical command: cd /opt/proj/Uncle-J-s-Refinery && uv lock --upgrade-package jcodemunch-mcp --upgrade-package jdatamunch-mcp --upgrade-package jdocmunch-mcp && uv sync --inexact (Use the exact command the healthcheck printed — it may differ by session.) > ⚠ **Repo-specific landmine — do not skip.** `uv sync` reverts the pysqlite3 SQLite source > build (3.51.3) back to the 3.5