pythinker-code 0.48.0__tar.gz → 0.50.0__tar.gz

{pythinker_code-0.48.0 → pythinker_code-0.50.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: pythinker-code
-Version: 0.48.0
+Version: 0.50.0
 Summary: Pythinker — an agentic CLI developed by Pythoughts-labs.
 Keywords: cli,agent,ai,coding-assistant,llm,claude,openai,terminal
 Author: Pythoughts-labs
@@ -115,13 +115,12 @@ It speaks the [**Agent Client Protocol (ACP)**](https://github.com/agentclientpr
 
 ---
 
-## 🆕 What's New in 0.48.0
+## 🆕 What's New in 0.50.0
 
-- **LSP code intelligence.** New `LSP` tool (go-to-definition, references, hover, symbols, call hierarchy) with plugin-backed language servers, session-scoped lifecycle, passive diagnostics after edits, and structured errors when a server lacks `implementationProvider`.
-- **TUI theme and streaming overhaul.** Centralized theme system (`/theme`), 25 Hz paced streaming, syntax-highlighted diff cards, report panel polish, and smoother interactive/non-interactive live views — no preamble ghosting, mid-stream scrollback flicker, or fossilized spinners during tool transitions.
-- **Proxy and tool-call hardening.** Tool results flatten for Anthropic-compatible proxies (fixes invisible GLM/z.ai outputs); `ToolSearch` is hidden from providers that cannot use deferred discovery; diff cards strip ANSI escapes; collapsed ReadFile cards show line counts and previews.
+- **Safer silent updates.** The downloaded build is now staged beside the running executable and promoted at exit, instead of overwriting the live onefile bundle in place — eliminating mid-session `zlib: incorrect header check` crashes after a background update.
+- **Cleaner update notice.** The "Updated → vX. Restart to apply." line renders below the prompt's bottom border, not inside the input area.
 
-Upgrade with `pythinker update`, `pip install --upgrade pythinker-code==0.48.0`, or use the native installer for your platform from the [Releases page](https://github.com/Pythoughts-labs/pythinker-code/releases/latest).
+Upgrade with `pythinker update`, `pip install --upgrade pythinker-code==0.50.0`, or use the native installer for your platform from the [Releases page](https://github.com/Pythoughts-labs/pythinker-code/releases/latest).
 
 
 ---
@@ -211,7 +210,7 @@ matches your OS — no Python, Node, or `uv` prerequisite.
 
 | Platform | Recommended install | Artifact source |
 |---|---|---|
-| **🪟 Windows** | `irm https://pythinker.com/install.ps1 \| iex` | `PythinkerSetup-0.48.0.exe` from [Releases](https://github.com/Pythoughts-labs/pythinker-code/releases/latest) |
+| **🪟 Windows** | `irm https://pythinker.com/install.ps1 \| iex` | `PythinkerSetup-0.50.0.exe` from [Releases](https://github.com/Pythoughts-labs/pythinker-code/releases/latest) |
 | **<img src="https://img.shields.io/badge/-macOS-000000?style=flat-square&logo=apple&logoColor=white" alt="macOS"> / <img src="https://img.shields.io/badge/-Linux-FCC624?style=flat-square&logo=linux&logoColor=black" alt="Linux">** | `curl -fsSL https://pythinker.com/install.sh \| bash` | native tarball from [Releases](https://github.com/Pythoughts-labs/pythinker-code/releases/latest) |
 | **<img src="https://img.shields.io/badge/-macOS-000000?style=flat-square&logo=apple&logoColor=white" alt="macOS"> — Homebrew** | `brew install Pythoughts-labs/pythinker/pythinker-code` | auto-published Homebrew tap |
 | **🐳 Docker** | `docker run --rm -it ghcr.io/pythoughts-labs/pythinker-code` | GHCR multi-arch image |
@@ -239,7 +238,7 @@ pythinker                      # start the interactive TUI
 
 ### 🪟 Windows — native installer
 
-`PythinkerSetup-0.48.0.exe` is a signed* Inno Setup wizard. Installs per-user
+`PythinkerSetup-0.50.0.exe` is a signed* Inno Setup wizard. Installs per-user
 into `%LOCALAPPDATA%\Programs\Pythinker`, registers `pythinker` on your user
 PATH (`HKCU\Environment`), broadcasts `WM_SETTINGCHANGE` so new shells see
 the change. **No UAC prompt.**
@@ -250,13 +249,13 @@ irm https://pythinker.com/install.ps1 | iex
 
 # Or manually download the installer + checksum from the Releases page,
 # verify with Get-FileHash, then run:
-.\PythinkerSetup-0.48.0.exe
+.\PythinkerSetup-0.50.0.exe
 
 # Open a fresh PowerShell
 pythinker --version
 ```
 
-**Per-machine install** (IT-managed boxes): `.\PythinkerSetup-0.48.0.exe /ALLUSERS`
+**Per-machine install** (IT-managed boxes): `.\PythinkerSetup-0.50.0.exe /ALLUSERS`
 installs to `%ProgramFiles%\Pythinker` and writes PATH to HKLM (requires admin).
 
 **Upgrade:** `pythinker update` from inside the running app — it downloads
@@ -314,26 +313,26 @@ attached to every GitHub Release.
 
 ```sh
 # Debian / Ubuntu (x86_64)
-sudo dpkg -i pythinker-code_0.48.0_amd64.deb
+sudo dpkg -i pythinker-code_0.50.0_amd64.deb
 sudo apt-get install -f       # only if dpkg reports missing deps
 
 # Debian / Ubuntu (ARM64)
-sudo dpkg -i pythinker-code_0.48.0_arm64.deb
+sudo dpkg -i pythinker-code_0.50.0_arm64.deb
 
 # Fedora / RHEL / openSUSE (x86_64)
-curl -LO https://github.com/Pythoughts-labs/pythinker-code/releases/download/v0.48.0/pythinker-code-0.48.0.x86_64.rpm
-curl -LO https://github.com/Pythoughts-labs/pythinker-code/releases/download/v0.48.0/pythinker-code-0.48.0.x86_64.rpm.sha256
-sha256sum -c pythinker-code-0.48.0.x86_64.rpm.sha256
+curl -LO https://github.com/Pythoughts-labs/pythinker-code/releases/download/v0.50.0/pythinker-code-0.50.0.x86_64.rpm
+curl -LO https://github.com/Pythoughts-labs/pythinker-code/releases/download/v0.50.0/pythinker-code-0.50.0.x86_64.rpm.sha256
+sha256sum -c pythinker-code-0.50.0.x86_64.rpm.sha256
 # Fedora / RHEL:
-sudo dnf install ./pythinker-code-0.48.0.x86_64.rpm
+sudo dnf install ./pythinker-code-0.50.0.x86_64.rpm
 # openSUSE:
-sudo zypper install ./pythinker-code-0.48.0.x86_64.rpm
+sudo zypper install ./pythinker-code-0.50.0.x86_64.rpm
 
 # Fedora / RHEL (aarch64)
-curl -LO https://github.com/Pythoughts-labs/pythinker-code/releases/download/v0.48.0/pythinker-code-0.48.0.aarch64.rpm
-curl -LO https://github.com/Pythoughts-labs/pythinker-code/releases/download/v0.48.0/pythinker-code-0.48.0.aarch64.rpm.sha256
-sha256sum -c pythinker-code-0.48.0.aarch64.rpm.sha256
-sudo dnf install ./pythinker-code-0.48.0.aarch64.rpm
+curl -LO https://github.com/Pythoughts-labs/pythinker-code/releases/download/v0.50.0/pythinker-code-0.50.0.aarch64.rpm
+curl -LO https://github.com/Pythoughts-labs/pythinker-code/releases/download/v0.50.0/pythinker-code-0.50.0.aarch64.rpm.sha256
+sha256sum -c pythinker-code-0.50.0.aarch64.rpm.sha256
+sudo dnf install ./pythinker-code-0.50.0.aarch64.rpm
 ```
 
 Both packages drop a small `/usr/bin/pythinker` launcher that execs the real
@@ -342,8 +341,8 @@ binary under `/usr/lib/pythinker/`, so your `$PATH` stays tidy.
 **Verify before install:**
 
 ```sh
-sha256sum -c pythinker-code_0.48.0_amd64.deb.sha256        # Debian/Ubuntu
-sha256sum -c pythinker-code-0.48.0.x86_64.rpm.sha256       # Fedora/RHEL
+sha256sum -c pythinker-code_0.50.0_amd64.deb.sha256        # Debian/Ubuntu
+sha256sum -c pythinker-code-0.50.0.x86_64.rpm.sha256       # Fedora/RHEL
 ```
 
 **Upgrade:** download the new `.deb`/`.rpm` from Releases and `dpkg -i` /

{pythinker_code-0.48.0 → pythinker_code-0.50.0}/README.md

@@ -50,13 +50,12 @@ It speaks the [**Agent Client Protocol (ACP)**](https://github.com/agentclientpr
 
 ---
 
-## 🆕 What's New in 0.48.0
+## 🆕 What's New in 0.50.0
 
-- **LSP code intelligence.** New `LSP` tool (go-to-definition, references, hover, symbols, call hierarchy) with plugin-backed language servers, session-scoped lifecycle, passive diagnostics after edits, and structured errors when a server lacks `implementationProvider`.
-- **TUI theme and streaming overhaul.** Centralized theme system (`/theme`), 25 Hz paced streaming, syntax-highlighted diff cards, report panel polish, and smoother interactive/non-interactive live views — no preamble ghosting, mid-stream scrollback flicker, or fossilized spinners during tool transitions.
-- **Proxy and tool-call hardening.** Tool results flatten for Anthropic-compatible proxies (fixes invisible GLM/z.ai outputs); `ToolSearch` is hidden from providers that cannot use deferred discovery; diff cards strip ANSI escapes; collapsed ReadFile cards show line counts and previews.
+- **Safer silent updates.** The downloaded build is now staged beside the running executable and promoted at exit, instead of overwriting the live onefile bundle in place — eliminating mid-session `zlib: incorrect header check` crashes after a background update.
+- **Cleaner update notice.** The "Updated → vX. Restart to apply." line renders below the prompt's bottom border, not inside the input area.
 
-Upgrade with `pythinker update`, `pip install --upgrade pythinker-code==0.48.0`, or use the native installer for your platform from the [Releases page](https://github.com/Pythoughts-labs/pythinker-code/releases/latest).
+Upgrade with `pythinker update`, `pip install --upgrade pythinker-code==0.50.0`, or use the native installer for your platform from the [Releases page](https://github.com/Pythoughts-labs/pythinker-code/releases/latest).
 
 
 ---
@@ -146,7 +145,7 @@ matches your OS — no Python, Node, or `uv` prerequisite.
 
 | Platform | Recommended install | Artifact source |
 |---|---|---|
-| **🪟 Windows** | `irm https://pythinker.com/install.ps1 \| iex` | `PythinkerSetup-0.48.0.exe` from [Releases](https://github.com/Pythoughts-labs/pythinker-code/releases/latest) |
+| **🪟 Windows** | `irm https://pythinker.com/install.ps1 \| iex` | `PythinkerSetup-0.50.0.exe` from [Releases](https://github.com/Pythoughts-labs/pythinker-code/releases/latest) |
 | **<img src="https://img.shields.io/badge/-macOS-000000?style=flat-square&logo=apple&logoColor=white" alt="macOS"> / <img src="https://img.shields.io/badge/-Linux-FCC624?style=flat-square&logo=linux&logoColor=black" alt="Linux">** | `curl -fsSL https://pythinker.com/install.sh \| bash` | native tarball from [Releases](https://github.com/Pythoughts-labs/pythinker-code/releases/latest) |
 | **<img src="https://img.shields.io/badge/-macOS-000000?style=flat-square&logo=apple&logoColor=white" alt="macOS"> — Homebrew** | `brew install Pythoughts-labs/pythinker/pythinker-code` | auto-published Homebrew tap |
 | **🐳 Docker** | `docker run --rm -it ghcr.io/pythoughts-labs/pythinker-code` | GHCR multi-arch image |
@@ -174,7 +173,7 @@ pythinker                      # start the interactive TUI
 
 ### 🪟 Windows — native installer
 
-`PythinkerSetup-0.48.0.exe` is a signed* Inno Setup wizard. Installs per-user
+`PythinkerSetup-0.50.0.exe` is a signed* Inno Setup wizard. Installs per-user
 into `%LOCALAPPDATA%\Programs\Pythinker`, registers `pythinker` on your user
 PATH (`HKCU\Environment`), broadcasts `WM_SETTINGCHANGE` so new shells see
 the change. **No UAC prompt.**
@@ -185,13 +184,13 @@ irm https://pythinker.com/install.ps1 | iex
 
 # Or manually download the installer + checksum from the Releases page,
 # verify with Get-FileHash, then run:
-.\PythinkerSetup-0.48.0.exe
+.\PythinkerSetup-0.50.0.exe
 
 # Open a fresh PowerShell
 pythinker --version
 ```
 
-**Per-machine install** (IT-managed boxes): `.\PythinkerSetup-0.48.0.exe /ALLUSERS`
+**Per-machine install** (IT-managed boxes): `.\PythinkerSetup-0.50.0.exe /ALLUSERS`
 installs to `%ProgramFiles%\Pythinker` and writes PATH to HKLM (requires admin).
 
 **Upgrade:** `pythinker update` from inside the running app — it downloads
@@ -249,26 +248,26 @@ attached to every GitHub Release.
 
 ```sh
 # Debian / Ubuntu (x86_64)
-sudo dpkg -i pythinker-code_0.48.0_amd64.deb
+sudo dpkg -i pythinker-code_0.50.0_amd64.deb
 sudo apt-get install -f       # only if dpkg reports missing deps
 
 # Debian / Ubuntu (ARM64)
-sudo dpkg -i pythinker-code_0.48.0_arm64.deb
+sudo dpkg -i pythinker-code_0.50.0_arm64.deb
 
 # Fedora / RHEL / openSUSE (x86_64)
-curl -LO https://github.com/Pythoughts-labs/pythinker-code/releases/download/v0.48.0/pythinker-code-0.48.0.x86_64.rpm
-curl -LO https://github.com/Pythoughts-labs/pythinker-code/releases/download/v0.48.0/pythinker-code-0.48.0.x86_64.rpm.sha256
-sha256sum -c pythinker-code-0.48.0.x86_64.rpm.sha256
+curl -LO https://github.com/Pythoughts-labs/pythinker-code/releases/download/v0.50.0/pythinker-code-0.50.0.x86_64.rpm
+curl -LO https://github.com/Pythoughts-labs/pythinker-code/releases/download/v0.50.0/pythinker-code-0.50.0.x86_64.rpm.sha256
+sha256sum -c pythinker-code-0.50.0.x86_64.rpm.sha256
 # Fedora / RHEL:
-sudo dnf install ./pythinker-code-0.48.0.x86_64.rpm
+sudo dnf install ./pythinker-code-0.50.0.x86_64.rpm
 # openSUSE:
-sudo zypper install ./pythinker-code-0.48.0.x86_64.rpm
+sudo zypper install ./pythinker-code-0.50.0.x86_64.rpm
 
 # Fedora / RHEL (aarch64)
-curl -LO https://github.com/Pythoughts-labs/pythinker-code/releases/download/v0.48.0/pythinker-code-0.48.0.aarch64.rpm
-curl -LO https://github.com/Pythoughts-labs/pythinker-code/releases/download/v0.48.0/pythinker-code-0.48.0.aarch64.rpm.sha256
-sha256sum -c pythinker-code-0.48.0.aarch64.rpm.sha256
-sudo dnf install ./pythinker-code-0.48.0.aarch64.rpm
+curl -LO https://github.com/Pythoughts-labs/pythinker-code/releases/download/v0.50.0/pythinker-code-0.50.0.aarch64.rpm
+curl -LO https://github.com/Pythoughts-labs/pythinker-code/releases/download/v0.50.0/pythinker-code-0.50.0.aarch64.rpm.sha256
+sha256sum -c pythinker-code-0.50.0.aarch64.rpm.sha256
+sudo dnf install ./pythinker-code-0.50.0.aarch64.rpm
 ```
 
 Both packages drop a small `/usr/bin/pythinker` launcher that execs the real
@@ -277,8 +276,8 @@ binary under `/usr/lib/pythinker/`, so your `$PATH` stays tidy.
 **Verify before install:**
 
 ```sh
-sha256sum -c pythinker-code_0.48.0_amd64.deb.sha256        # Debian/Ubuntu
-sha256sum -c pythinker-code-0.48.0.x86_64.rpm.sha256       # Fedora/RHEL
+sha256sum -c pythinker-code_0.50.0_amd64.deb.sha256        # Debian/Ubuntu
+sha256sum -c pythinker-code-0.50.0.x86_64.rpm.sha256       # Fedora/RHEL
 ```
 
 **Upgrade:** download the new `.deb`/`.rpm` from Releases and `dpkg -i` /

{pythinker_code-0.48.0 → pythinker_code-0.50.0}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "pythinker-code"
-version = "0.48.0"
+version = "0.50.0"
 description = "Pythinker — an agentic CLI developed by Pythoughts-labs."
 readme = "README.md"
 requires-python = ">=3.12"

{pythinker_code-0.48.0 → pythinker_code-0.50.0}/src/pythinker_code/CHANGELOG.md

@@ -15,6 +15,37 @@ GitHub Releases page; `0.8.0` is the new starting line.
 
 ## Unreleased
 
+## 0.50.0 (2026-06-20)
+
+- **Silent native updates no longer crash a running session.** The downloaded
+  build is now staged beside the running executable and swapped in at exit (it goes
+  live on the next launch), instead of overwriting the live onefile bundle in place.
+  Overwriting it mid-session corrupted later lazy imports with a
+  `zlib.error: incorrect header check`. A boundary guard also converts any residual
+  post-update archive-corruption crash into a clear "restart to apply" message.
+- **Update notice renders below the input box.** The "Updated → vX. Restart to
+  apply." line now appears underneath the prompt's bottom border instead of inside
+  the input area.
+
+## 0.49.0 (2026-06-20)
+
+- **Reduction ladder in the default agent prompt.** The agent now walks an explicit,
+  ordered ladder before writing code — does this need to exist at all, then the standard
+  library, a native platform or framework feature, an already-installed dependency, one
+  line, and only then the minimum custom code — so it reaches for the simplest working
+  solution by default. The same guidance is mirrored into the `/best-practices` profile,
+  and deliberate shortcuts with a known ceiling are flagged with a comment naming the
+  ceiling and the upgrade path. Input validation, error handling, security, and
+  accessibility are never traded away for fewer lines.
+- **New `cleanup-audit` skill.** A read-only, whole-repo pass that ranks over-engineering
+  — what to delete, simplify, or replace with standard-library/platform equivalents — as
+  the repo-wide complement to the diff-scoped `pythinker review diff --mode deslopify`. It
+  applies no fixes and never proposes cutting validation, error handling, security, or
+  accessibility.
+- **Fix: duplicate update notices at startup.** When a background install finishes
+  or a cached update is detected, the hint now renders only on the persistent
+  under-input line instead of also flashing as a footer toast.
+
 ## 0.48.0 (2026-06-17)
 
 - **Fix: tool outputs invisible on Anthropic-compatible proxies (GLM-5.2 via z.ai).**

{pythinker_code-0.48.0 → pythinker_code-0.50.0}/src/pythinker_code/agents/default/system.md

@@ -149,7 +149,9 @@ ${PYTHINKER_SCRATCHPAD_SECTION}
 
 **Simplicity first — minimum code that solves the problem, nothing speculative.** No features beyond what was asked; no abstractions for single-use code; no unrequested configurability; no error handling for impossible scenarios — validate at boundaries only. If a 200-line draft could be 50 lines, rewrite it before showing it. Over-fragmentation is overcomplication too: don't scatter logic across tiny files or extra layers to satisfy a pattern — match the codebase's existing granularity. Self-check: *would a senior engineer call this over-engineered?* If yes, simplify.
 
-**Quality defaults** (unless project or domain rules override): focused, shallow, scannable functions with early exits over deep nesting; meaningful identifiers, no shadowing, the context's casing convention; avoid duplicate logic within a change without inventing broad abstractions for one-off repetition; comment only non-obvious algorithms, workarounds, business rules, and edge cases (`TODO:` for real debt; no self-evident comments; never add copyright or license headers unless requested); cohesive, testable modules; efficient data structures where they aid clarity or scale; wrap error-prone I/O, API, network, and resource operations with handling, timeouts/fallbacks, and cleanup; adopt stricter domain standards (e.g. MISRA-style C/C++) when relevant. Once correct, run the repo's formatter (up to 3 attempts); never add one where none exists.
+**The reduction ladder — walk it before writing code; stop at the first rung that holds.** (1) *Does this need to exist at all?* A speculative need is skipped, said so in one line. (2) *Does the standard library do it?* Use it. (3) *Does a native platform or framework feature cover it?* A database constraint over an app-level check, a built-in form control over a picker library, the language's own construct over a hand-rolled one — use it. (4) *Does a dependency already in the manifest solve it?* Use it; never add a new dependency for what a few lines cover. (5) *Can it be one line?* Make it one line. (6) *Only then* write the minimum code that works. When two rungs both hold, take the higher one and move on — the ladder is a reflex, not a research project. None of this overrides the guards in this section: trust-boundary validation, error handling that prevents data loss, security, and accessibility stay in even at rung 5.
+
+**Quality defaults** (unless project or domain rules override): focused, shallow, scannable functions with early exits over deep nesting; meaningful identifiers, no shadowing, the context's casing convention; avoid duplicate logic within a change without inventing broad abstractions for one-off repetition; comment only non-obvious algorithms, workarounds, business rules, edge cases, and deliberate simplifications whose ceiling matters — a coarse lock, an O(n²) scan, a naive heuristic — naming the ceiling and the upgrade path (`TODO:` for real debt; no self-evident comments; never add copyright or license headers unless requested); cohesive, testable modules; efficient data structures where they aid clarity or scale; wrap error-prone I/O, API, network, and resource operations with handling, timeouts/fallbacks, and cleanup; adopt stricter domain standards (e.g. MISRA-style C/C++) when relevant. Once correct, run the repo's formatter (up to 3 attempts); never add one where none exists.
 
 **Honest testing.** Verification per Rule 3, from the narrowest scope outward. Never game it: no weakened or deleted assertions, skipped tests, widened tolerances, overfitting to test cases, or mocking away the behavior under test. Keep tests deterministic — control time, randomness, and the network through the repo's existing patterns; never synchronize with sleeps.
 

{pythinker_code-0.48.0 → pythinker_code-0.50.0}/src/pythinker_code/cli/__init__.py

@@ -333,6 +333,43 @@ def _version_callback(value: bool) -> None:
         raise typer.Exit()
 
 
+def _is_post_update_bundle_corruption(exc: BaseException) -> bool:
+    """True when a frozen build's archive read failed mid-session.
+
+    This is the signature of a silent self-update having replaced the running
+    bundle on disk (see ``_install_native_archive``): the old process keeps
+    running, and the next not-yet-loaded lazy import reads from the now-stale
+    on-disk archive and raises ``zlib.error: incorrect header check``.
+
+    Gated on the PyInstaller ``sys.frozen`` marker so source / pip installs (which
+    never self-replace this way) are unaffected, and narrowed to the documented
+    corruption message (``incorrect header check``) so an unrelated decompression
+    failure elsewhere on a frozen build is *not* misclassified as a stale bundle and
+    masked behind a restart-only message. The zlib error class is matched by
+    ``__module__``/``__name__`` rather than ``isinstance`` so the handler never
+    imports ``zlib`` from a possibly-corrupted archive — ``sys`` is a C built-in and
+    is always safe to import. The cause/context chain is walked with a cycle guard so
+    a self-referential chain can't spin.
+    """
+    import sys
+
+    if not getattr(sys, "frozen", False):
+        return False
+    seen: set[int] = set()
+    current: BaseException | None = exc
+    while current is not None and id(current) not in seen:
+        seen.add(id(current))
+        cls = type(current)
+        if (
+            cls.__module__ == "zlib"
+            and cls.__name__ == "error"
+            and "incorrect header check" in str(current).lower()
+        ):
+            return True
+        current = current.__cause__ or current.__context__
+    return False
+
+
 @cli.callback(invoke_without_command=True)
 def pythinker(
     ctx: typer.Context,
@@ -1310,6 +1347,17 @@ def pythinker(
             # ClickException includes the errors Typer knows how to render; don't
             # wrap them, or we'd lose the standard error UI and exit codes.
             raise
+        if _is_post_update_bundle_corruption(exc):
+            # A silent self-update replaced this running build on disk; lazy imports
+            # from the stale archive now fail. This only resolves with a restart —
+            # surface a clear, actionable message instead of a fatal traceback.
+            logger.warning("Post-update bundle corruption detected; prompting restart")
+            _emit_fatal_error(
+                "A Pythinker update was installed during this session and the "
+                "running build was replaced on disk.\n"
+                "Please restart Pythinker to finish applying the update."
+            )
+            raise typer.Exit(code=1) from exc
         logger.exception("Fatal error when running CLI")
         if debug:
             import traceback

{pythinker_code-0.48.0 → pythinker_code-0.50.0}/src/pythinker_code/prompts/best_practices.md

@@ -30,6 +30,7 @@ The user ran `/best-practices`. Engineering best practices are now in effect: ap
 - Never invent APIs. Verify every external symbol — function signatures, config keys, CLI flags, library methods — against the actual source, installed package, or type definitions before using it. If you cannot verify it, look it up; if you still cannot, say so instead of guessing.
 - Prefer the standard library and dependencies already in the manifest. A new dependency is a design decision: justify it (maintenance, license, size, transitive risk), verify the exact package name exists in the registry (hallucinated names are a typosquatting vector), pin it per repo convention, and modify lockfiles only through the package manager — never by hand.
 - Apply YAGNI: no speculative abstractions, flags, generality, or extension points the request does not need.
+- Before writing code, walk the reduction ladder and stop at the first rung that holds: (1) does this need to exist at all (YAGNI) — skip it and say so; (2) does the standard library do it; (3) does a native platform or framework feature cover it (a database constraint over app code, a built-in control over a library); (4) does a dependency already in the manifest solve it — never add a new one for what a few lines cover; (5) can it be one line; (6) only then the minimum code that works. When two rungs both hold, take the higher one and move on. The guards in this profile — trust-boundary validation, data-loss handling, security, accessibility — are never traded away for fewer lines.
 - No placeholders in completed work: no TODO stubs, commented-out blocks, empty handler bodies, or mock data presented as a real integration.
 - Fail loudly per the codebase's conventions. Never swallow exceptions, downgrade errors to warnings, or return fabricated defaults to make a failure disappear.
 - Preserve backward compatibility by default. Search the integration surfaces your change touches — public APIs, CLI parameters, configuration loading, persisted state, session and wire formats, database schemas — and if a break is unavoidable, call it out and migrate or gate it.

pythinker_code-0.50.0/src/pythinker_code/skills/cleanup-audit/SKILL.md

@@ -0,0 +1,50 @@
+---
+name: cleanup-audit
+description: Whole-repo audit for over-engineering and accidental complexity. Scans the entire codebase (not just a diff) and returns a ranked, read-only list of what to delete, simplify, or replace with standard-library or platform equivalents. Use when the user asks to "audit the codebase", "find bloat", "what can I delete", or wants a repo-wide simplification pass. For a diff-scoped pass use `pythinker review diff --mode deslopify` instead. One-shot report; applies no fixes.
+---
+
+# Cleanup Audit
+
+A read-only, whole-repo pass that hunts accidental complexity and over-engineering. The diff-scoped
+version of this job already ships as `pythinker review diff --mode deslopify`; this skill is its
+repo-wide complement — scan the whole tree, rank the biggest cut first.
+
+Scope is complexity only. Correctness bugs, security holes, and performance belong to a normal
+review or security pass — note them in one line if you trip over them, but do not chase them here.
+
+## What to hunt
+
+- Dead code, unused flexibility, and speculative features no caller needs.
+- Hand-rolled logic the standard library already ships — name the function that replaces it.
+- A dependency (or hand-written code) doing what the language, runtime, or framework already does.
+- Single-implementation interfaces, one-product factories, wrappers that only delegate, a module
+  that exports one trivial thing, dead flags and config nobody sets.
+- The same logic spelled out long-hand where a shorter, equally clear form exists.
+
+## How to work
+
+1. Map before judging: read the tree, the manifest/lockfile, and entry points; use `Grep`/`Glob`
+   (or `LSP` for references and call hierarchy) to confirm a thing is actually unused before
+   proposing its deletion. A deletion proposed without checking callers is a guess.
+2. Rank findings biggest cut first.
+3. Apply nothing. This is a report.
+
+## Output
+
+One line per finding, ranked, each tagged and citing a path:
+
+- `delete:` — dead code / speculative feature. Replacement: nothing.
+- `stdlib:` — hand-rolled thing the standard library ships. Name the function.
+- `native:` — dependency or code doing what the platform/framework already does. Name the feature.
+- `yagni:` — abstraction with one implementation, config nobody sets, layer with one caller.
+- `shrink:` — same logic, fewer lines. Show the shorter form.
+
+Format: `<tag> <what to cut>. <replacement>. [path:line]`
+End with an estimate: `net: ~-<N> lines, -<M> deps possible.` Nothing to cut: `Lean already.`
+
+## Guardrails
+
+Never propose cutting trust-boundary validation, error handling that prevents data loss, security
+measures, or accessibility — minimal is not the same as unsafe. When a "simplification" would touch
+one of those, leave it and say why. Verify each deletion candidate is truly unreferenced before
+listing it; an audit that proposes deleting live code is worse than no audit.

{pythinker_code-0.48.0 → pythinker_code-0.50.0}/src/pythinker_code/ui/shell/__init__.py

@@ -2095,22 +2095,10 @@ class Shell:
     async def _auto_update(self) -> None:
         # Background-refresh the cached latest version (throttled); never blocks startup.
         await refresh_update_cache_if_due()
-        # Non-blocking shell notice based on the cached value.
-        notice = pending_update_notice()
-        if notice:
-            # Make version notices easy to see on macOS/Linux terminals too:
-            # put them at the front of the toast queue, keep them around long
-            # enough to survive startup redraws, and force a repaint if the
-            # prompt is already active.
-            toast(
-                notice,
-                topic="update",
-                duration=30.0,
-                immediate=True,
-                style="fg:ansibrightyellow bold",
-            )
-            if self._prompt_session is not None:
-                self._prompt_session.invalidate()
+        # The persistent under-input line renders the cached update hint; refresh
+        # it when the cache changes instead of duplicating the text as a toast.
+        if pending_update_notice():
+            self._refresh_update_notice_line()
 
     async def _silent_auto_update(self) -> None:
         """Install a newer release silently in the background at startup."""
@@ -2147,10 +2135,15 @@ class Shell:
                 style="fg:ansiyellow",
             )
             return
-        self._update_toast(
-            self._installed_update_restart_notice(),
-            style="fg:ansibrightyellow bold",
-        )
+        # The persistent under-input line (_append_update_notice) already renders
+        # the restart message; a toast duplicates it on the footer's second row.
+        self._refresh_update_notice_line()
+
+    def _refresh_update_notice_line(self) -> None:
+        """Drop the update-notice memo and repaint so the footer picks up new text."""
+        self._update_notice_cache = (0.0, None)
+        if self._prompt_session is not None:
+            self._prompt_session.invalidate()
 
     def _installed_update_smoke_check_failed(self) -> bool:
         status = read_update_status()
@@ -2210,8 +2203,8 @@ class Shell:
         if not target:
             return None
         # A release already installed this session needs a restart, not /update —
-        # keep this line in agreement with the install toast instead of telling
-        # the user to re-run an update that has already landed.
+        # surface that here instead of telling the user to re-run an update that
+        # has already landed.
         status = read_update_status()
         installed = (
             status is not None
@@ -2230,12 +2223,12 @@ class Shell:
         """Pick the startup update behavior and schedule it (non-blocking).
 
         - env kill-switch set → nothing (cache filters already suppress the
-          toast, matching today's hard-disable behavior).
+          notice, matching today's hard-disable behavior).
         - enabled → silent background install.
-        - config-disabled OR source checkout → informational toast only
-          (`_auto_update`); self-suppresses for source checkouts because
+        - config-disabled OR source checkout → refresh the persistent notice
+          only (`_auto_update`); self-suppresses for source checkouts because
           `pending_update_notice()` returns None in that path.
-        - non-PythinkerSoul → same toast-only path (no runtime config to
+        - non-PythinkerSoul → same notice-refresh path (no runtime config to
           consult), matching the prior unconditional `_auto_update` behavior.
         """
         if get_env_bool("PYTHINKER_CLI_NO_AUTO_UPDATE"):

{pythinker_code-0.48.0 → pythinker_code-0.50.0}/src/pythinker_code/ui/shell/prompt.py

@@ -3915,10 +3915,11 @@ class CustomPromptSession:
                 error=exc,
             )
 
-    def _prepend_update_notice(self, fragments: list[tuple[str, str]], columns: int) -> None:
-        """Prepend a persistent yellow 'update available' line above the footer
-        separator, so it renders directly under the prompt input. No-op when no
-        update is pending; style-agnostic across both toolbar layouts."""
+    def _append_update_notice(self, fragments: list[tuple[str, str]], columns: int) -> None:
+        """Append a persistent yellow 'update available' line *below* the footer
+        separator, so it renders underneath the prompt input box rather than
+        inside it. Call this right after the separator rule. No-op when no update
+        is pending; style-agnostic across both toolbar layouts."""
         provider = getattr(self, "_update_notice_provider", None)
         if provider is None:
             return
@@ -3930,7 +3931,7 @@ class CustomPromptSession:
             return
         tokens = _get_tui_tokens()
         style = f"fg:{tokens.warning or 'ansiyellow'} bold"
-        fragments[:0] = [(style, line), ("", "\n")]
+        fragments.extend([(style, line), ("", "\n")])
 
     def _render_bottom_toolbar(self) -> FormattedText:
         if (
@@ -3954,9 +3955,9 @@ class CustomPromptSession:
         fragments: list[tuple[str, str]] = []
         tc = get_toolbar_colors()
 
-        self._prepend_update_notice(fragments, columns)
         fragments.append((self._prompt_separator_style(tc.separator), _prompt_rule(columns)))
         fragments.append(("", "\n"))
+        self._append_update_notice(fragments, columns)
 
         remaining = columns
 
@@ -4185,9 +4186,9 @@ class CustomPromptSession:
         secondary_style = f"fg:{tokens.muted}"
 
         fragments: list[tuple[str, str]] = []
-        self._prepend_update_notice(fragments, columns)
         fragments.append((self._prompt_separator_style(tc.separator), _prompt_rule(columns)))
         fragments.append(("", "\n"))
+        self._append_update_notice(fragments, columns)
 
         try:
             ctx = self._build_statusline_context(columns)

{pythinker_code-0.48.0 → pythinker_code-0.50.0}/src/pythinker_code/ui/shell/update.py

@@ -1,6 +1,7 @@
 from __future__ import annotations
 
 import asyncio
+import atexit
 import contextlib
 import os
 import platform
@@ -1075,6 +1076,57 @@ def _install_linux_package(asset: Path, package_kind: str) -> UpdateResult:
     return UpdateResult.UPDATED if result.returncode == 0 else UpdateResult.FAILED
 
 
+def staged_native_path() -> Path:
+    """Side path next to the running executable where a downloaded native update is
+    held until it is promoted into place. Deterministic so the orchestrator's smoke
+    check and the exit-time promotion agree on the same file."""
+    target = Path(sys.executable).resolve()
+    return target.with_name(f".{target.name}.staged")
+
+
+def register_staged_native_promotion() -> None:
+    """Arrange for the staged native binary to replace the running executable at
+    process exit.
+
+    Swapping at exit — rather than in place mid-session — is the whole point: the
+    running onefile build reads its Python archive lazily from ``sys.executable``,
+    so overwriting that path while the process is alive corrupts later imports
+    (``zlib.error: incorrect header check``). At exit no further imports happen, so
+    the swap is safe, and the new binary goes live on the next launch — exactly what
+    the "Updated → vX. Restart to apply." notice promises.
+
+    Registering more than once (e.g. a silent update plus a manual ``/update`` in the
+    same session) is harmless: the handler no-ops once the staged file has been
+    promoted, so any duplicate registration just runs a second no-op.
+    """
+    atexit.register(_promote_staged_native_update)
+
+
+def discard_staged_native_update() -> None:
+    """Remove a staged binary that must not be promoted (e.g. it failed its smoke
+    check). Fail-open: a leftover staged file is only ever promoted deliberately."""
+    with contextlib.suppress(OSError):
+        staged_native_path().unlink()
+
+
+def _promote_staged_native_update() -> None:
+    # ponytail: known residual windows, both far smaller than the mid-session login
+    # crash this replaces — (1) a hard kill (SIGKILL) skips atexit, so promotion
+    # defers to the next clean exit (self-healing); (2) a first-time lazy import
+    # during the rest of interpreter shutdown, after the swap below, could read
+    # stale bytes. Closing both needs a detached post-exit swapper (the deferred
+    # seamless-relaunch design); not built here.
+    staged = staged_native_path()
+    if not staged.is_file():
+        return
+    target = Path(sys.executable).resolve()
+    try:
+        os.replace(staged, target)
+    except OSError:
+        # Leave the staged binary in place; a later clean exit retries the swap.
+        logger.exception("Failed to promote staged native update on exit:")
+
+
 def _install_native_archive(archive: Path) -> UpdateResult:
     target = Path(sys.executable).resolve()
     extract_dir = archive.parent / "extract"
@@ -1091,18 +1143,23 @@ def _install_native_archive(archive: Path) -> UpdateResult:
         logger.error("Native archive did not contain a pythinker executable")
         return UpdateResult.FAILED
 
-    replacement = target.with_name(f".{target.name}.new-{os.getpid()}")
+    # Stage the new binary beside the running executable instead of overwriting it
+    # in place. Promotion into `target` happens at process exit (see
+    # register_staged_native_promotion), keeping the live build's on-disk archive
+    # intact so mid-session lazy imports never read stale bytes.
+    staged = staged_native_path()
+    staging_tmp = target.with_name(f".{target.name}.new-{os.getpid()}")
     try:
-        shutil.copyfile(extracted, replacement)
-        replacement.chmod(target.stat().st_mode | 0o755)
-        os.replace(replacement, target)
+        shutil.copyfile(extracted, staging_tmp)
+        staging_tmp.chmod(target.stat().st_mode | 0o755)
+        os.replace(staging_tmp, staged)
         (target.parent / ".pythinker-native").write_text(
             "pythinker-native-build\n", encoding="utf-8"
         )
     except OSError:
-        logger.exception("Failed to replace native executable:")
+        logger.exception("Failed to stage native executable:")
         with contextlib.suppress(OSError):
-            replacement.unlink()
+            staging_tmp.unlink()
         return UpdateResult.FAILED
     return UpdateResult.UPDATED