Athena KaminskyandClaude Opus 5
9104c724c4
The CLI shipped from `management/`, which also holds desktop-only pieces (the Tk control panel, the XFCE panel wiring, the shell wrappers). Packaging that directory meant the wheel either dragged in tkinter or shipped a broken import. Split it: `nexusos_cli/` is what the wheel ships and what `nexus`/`ncp`/ `nexusos` dispatch to, `management/` keeps the desktop half. Alongside the move: * hatch_build.py decides the interface/web/dist include at build time. dist/ is gitignored, so a static force-include aborts `pip install -e .` on a fresh clone - before the reader reaches the `npm run build` step. Editable installs now skip a missing dist; wheels and sdists hard-error naming the command to run. * synapse/proc_util.py gives frontend_manager and ncp process inspection and termination without psutil, which became an optional extra when the wheel landed. It routes around Windows having no signals, where os.kill(pid, 15) is an unblockable TerminateProcess rather than a polite request. * nexusos_cli/monitor.py adds `ncp monitor`, an ASCII dashboard with no curses or rich dependency so it works in Termux, plain SSH and Windows Terminal. Collector and renderer are separate so tests feed fixtures, no stack needed. * tests/test_packaging_deps.py fails the gate when synapse or nexusos_cli import a distribution pyproject does not declare, and when an optional dependency is imported at module scope instead of lazily. * bin/check.sh now builds the wheel, twine-checks it, and asserts the compiled UI and seed playbooks are actually inside it. A wheel that builds but ships no dist/ serves a blank page, which only shows up after release. tests/test_nexus_api.py moves to tests/ with the module it covers. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
32 lines
1.6 KiB
Batchfile
32 lines
1.6 KiB
Batchfile
@echo off
|
|
REM ncp - PATH entry point on Windows. A .cmd, not a .ps1, on purpose: PowerShell's
|
|
REM execution policy governs .ps1 only, so this keeps working under the default
|
|
REM Restricted policy and from cmd, Win+R, Task Scheduler and .lnk targets - none
|
|
REM of which load a PowerShell profile. install-windows.ps1 puts this directory on
|
|
REM the machine PATH.
|
|
REM
|
|
REM This file must NOT be accompanied by an ncp.ps1 in the same directory:
|
|
REM PowerShell resolves ExternalScript (.ps1) ahead of Application (.cmd), so a
|
|
REM sibling ncp.ps1 wins in PowerShell and drags the execution policy back in -
|
|
REM exactly what this file exists to avoid.
|
|
REM
|
|
REM ASCII only, same rule as the .ps1 files - a test in tests/test_smoke.py enforces it.
|
|
setlocal
|
|
REM The CLI pins its stdout to UTF-8 (it prints check marks and em-dashes, and a
|
|
REM redirected stdout would otherwise raise UnicodeEncodeError). A console still
|
|
REM on codepage 437 renders those bytes as mojibake, so switch it to UTF-8 here.
|
|
REM ponytail: chcp changes the calling console's codepage and does not restore
|
|
REM it on exit. Harmless in practice; if that ever matters, set the console CP
|
|
REM from inside the CLI with ctypes SetConsoleOutputCP instead.
|
|
chcp 65001 >nul 2>&1
|
|
set "ROOT=%~dp0.."
|
|
REM System Python fallback so backup/restore work before the venv exists; those
|
|
REM delegate to the stdlib-only bin/sync.py. Mirrors the same fallback in ncp.ps1.
|
|
set "PY=%ROOT%\Promethean\Scripts\python.exe"
|
|
if not exist "%PY%" set "PY=python"
|
|
pushd "%ROOT%"
|
|
"%PY%" -m nexusos_cli.cli %*
|
|
set "NEXUS_EXIT=%ERRORLEVEL%"
|
|
popd
|
|
exit /b %NEXUS_EXIT%
|
GitNexus · part of the Nexus stack