Repository navigation
dotSYSTEMX 1.9.0-alpha.5
Pre-releasedotSYSTEMX 1.9.0-alpha.5
Alpha — use at your own risk. This release adds a direct installed CLI for
explicit .SYSTEMXP project routing and updates the complete-system infographic
to make CLI tools and separate child records prominent.
- Use
systemx projects --target OUTER -- SUBCOMMAND ...with the directory
containing.SYSTEMX. Scoped operations require--project NAMEor--root.
The wrapper uses verified managed defaults, preserves output/exit codes, and
defaults offline. Optional--onlinepermits configured startup notices only. tools-guideand local menu option 18 expose a versioned guide to external
management commands, local launchers, project operations, Python API,
Git/gh, and authorized provider tools. The longersystemx run ... -- projects
syntax remains supported.- Reviewed folder-only PowerShell copies now launch their local isolated runner.
Both launchers treat existing malformed/directory/dangling installation markers
as managed state and refuse them without fallback to local unmanaged code. - The current 4K infographic shows the CLI layers, exact
.SYSTEMXPtree,
Project-A/Project-B separation, shared outer defaults, and Agent 0/X/Y/Z.
Its new portable filename is additive for existing projects. The web PNG
stays at its canonical URL. Native imagegen output is 1672 × 941; macOS
sipsexported 3840 × 2160, with JPEG quality 80 under the 2 MiB file limit. - README, setup/project/library guides, and the wiki explain the new commands,
child application working directory, and version migration. Reusable records
remain blank; role and PR authority gates are unchanged.
Verification: 230 tests ran on each of Python 3.14 and Python 3.9, with 225 passed,
five filesystem-case skips, and zero errors in each run. PowerShell launcher
execution tests ran on macOS. Template checks passed for 157 portable files and
98 Markdown documents. ZIP and wheel match all committed portable bytes.
Exact-wheel lifecycle, scoped project commands, backed-up alpha.4-to-alpha.5
upgrade, and a digest-pinned public-tag install passed with user/root/child/host
preservation; an incorrect digest was rejected before installation. See the
review report.
Existing managed projects need a reviewed external alpha.5 tool and an explicit
backed-up bootstrap-refresh for stock manager/launcher changes before updating.
Customized bootstraps remain conflicts for review. Normal updates preserve old
media and user records while adding the new files and selected snapshot.
For --archive-sha256, verify this exact raw codeload tag ZIP digest through a
channel you trust. It differs from the folder-only ZIP and wheel asset hashes:
https://codeload.github.com/WayneTechLab/dotSYSTEMX/zip/refs/tags/v1.9.0-alpha.5
SHA-256 8acbd10d27c21f47bc1dd8dcfef3a83f1b8c5fbb64206487f1ee2681a0806662
GitHub Actions remains disabled. Native Windows/Linux runtime and live provider/PR
integration remain unverified; no new security-plugin scan is claimed. Scope
routing does not isolate external tools from their host account, and --offline
does not block network access by authorized project/provider commands.