cmd

cmd is an integrated collection of command-line utilities implemented in MoonBit. It provides executable command modules, a shared runtime, and a test system for preserving GNU/POSIX and command-upstream behavior. Authorization belongs to the caller or host; commands preserve the caller's environment and stream semantics.

0.2.0 is published as cli/core and 47 command modules. Linux, macOS and Windows passed the release source checks, including Linux Native/Wasm pinned oracle comparisons. Exact-version MoonX acceptance is recorded separately in the release evidence. See the support record, and upstream API gaps. This release includes a persistent line-oriented sh -i, real make -j scheduling, JSON input framing, Basic HTTP authentication and cookies. Strict filesystem limits are explicit: default cp and existing-file touch cannot be implemented faithfully with the current public metadata APIs; see ADR-0004.

Releasable commands are available as independent modules under cli/<command>:

MOON_HOME="$HOME/.moon-accounts/cli" moonx cli/base64@0.2.0
MOON_HOME="$HOME/.moon-accounts/cli" moonx cli/grep@0.2.0 -- pattern input.txt
MOON_HOME="$HOME/.moon-accounts/cli" moonx cli/jq@0.2.0 -- -r '.name'

Commands

The repository contains 48 executable commands for local builds. The current Mooncakes registry exposes 47 of them through MoonX. timeout remains local-only because portable process-group cancellation is not available, so moonx cli/timeout is intentionally unavailable.

Text and data

base64 cat cmp comm cut grep head join jq jqlog nl paste printf sha256sum
sort tail tr uniq wc xxd

Files and paths

basename cp dirname find ln ls mkdir mv pwd rm rmdir tee touch

Environment and execution

chmod echo env false make printenv seq sh sleep test timeout true wget curl
xargs

Commands implement their behavior in MoonBit and use explicit runtime APIs for filesystem, streams, processes, networking, and platform capabilities. They do not delegate their implementation to a same-named host command.

Controlled execution

The command set is designed for native and Wasm execution. Under Wasm, commands can run with explicit policies that limit filesystem access, mutations, processes, network access, and permission changes.

The caller configures host authorization. Command capability declarations describe their requirements and do not add a command-level policy. Host-denied operations fail with a nonzero status; the policy suite checks the resulting effects independently of command compatibility.

The repository intentionally does not provide chown or kill, because the required owner-mutation and arbitrary-process-signalling capabilities are not part of the current controlled runtime contract.

Structure

cmd/
|-- core/                 # shared command runtime
|   |-- cli/              # option parsing and command catalog
|   |-- fsops/            # filesystem helpers
|   |-- netops/           # network helpers
|   |-- platform/         # platform capability boundary
|   |-- process/          # child-process specifications
|   |-- shell/            # shell parsing and execution
|   `-- stream/           # byte and line-stream helpers
|-- commands/             # one executable module per command
|-- tests/
|   |-- runner/           # workspace compat, policy, and oracle runner
|   |-- release_runner/   # exact published MoonX versions
|   |-- cases/            # shared active command contracts and oracle fixtures
|   |-- testkit/          # process test utilities
|   `-- fixtures/         # runner manifests and policy profiles
|-- docs/                 # behavior and provenance documentation
`-- moon.work             # MoonBit workspace manifest

The core module provides the shared packages used by command implementations. The tests module remains repository-internal and contains no user-facing command packages.

Test system

The project combines package tests and two runners sharing a Native testkit:

• MoonBit unit and white-box tests for parsers and shared runtime packages.
• compat retains the Native compatibility groups with stable selectable IDs.
• contract runs shared per-command input/output/status contracts against Native or Wasm artifacts; explicit rejection boundaries are counted separately.
• policy executes pre-built Wasm artifacts through moonrun --policy and verifies allowed and denied resource access.
• oracle compares Native and Wasm commands with the pinned upstream image, including declared metadata observations. GNU and stress are independent suites.
• release_runner validates candidate manifests and checks exact published MoonX versions selected by published-0.2.0.json; frozen 0.1.x manifests remain available for historical replay.
• scenarios covers persistent shell input, HTTP auth/cookies, filesystem boundaries and process/make lifecycle on both backends in CI. Former standalone probes are archived with their assertion migration maps.

Generic filesystem snapshots cover paths, kinds and regular-file bytes; explicit observers cover mode, fixed timestamps, symlink targets and fixture link relationships. Missing required observations cannot certify compatibility. See the test entry-point guide for coverage and execution limits.

Run the standard local checks from the repository root, serially:

MOON_HOME="$HOME/.moon-accounts/cli" moon update
MOON_HOME="$HOME/.moon-accounts/cli" moon check --target all --deny-warn
MOON_HOME="$HOME/.moon-accounts/cli" moon test --target all
MOON_HOME="$HOME/.moon-accounts/cli" moon build --target native --release --deny-warn
MOON_HOME="$HOME/.moon-accounts/cli" moon build --target wasm --release --deny-warn
./_build/native/release/build/mooxCLI/cmd-tests/runner/runner.exe --suite compat
./_build/native/release/build/mooxCLI/cmd-tests/runner/runner.exe --suite policy
./_build/native/release/build/mooxCLI/cmd-tests/release_runner/release_runner.exe --manifest tests/release_runner/candidate-0.2.0.json --suite validate
MOON_HOME="$HOME/.moon-accounts/cli" moon info
MOON_HOME="$HOME/.moon-accounts/cli" moon fmt

This sequence excludes the Docker oracle, published-package checks and manual scenario probes; it is not the complete release acceptance suite.

See Compatibility for measured command support and platform behavior, and Provenance for the source of the imported command implementations.

License

Licensed under the Apache License 2.0.