#MoonJust

Current status

MoonJust is compatible with the pinned just 1.57.0 compatibility inventory on supported Native and wasm1/moonrun hosts. Completion remains excluded. Linux, macOS and Windows Native gates, the shared Ubuntu wasm1 asset, and the official non-completion differential harness pass. Release artifacts remain subject to a strict size baseline gate; publication, tagging and GitHub Release creation are not automatic.

#What is delivered

#Compatibility and support

• Upstream: just 1.57.0, commit e01a6bd7e7a30baf86bc86d2b95b0998ebbdc36f.
• Required targets: native and wasm (wasm1 under moonrun/moonx).
• Differential results are classified as exact, diagnostic-exact, diagnostic-semantic, product identity, excluded completion, upstream ignored, not-applicable, approved-difference, or failed. Product identity, excluded/ignored, not-applicable, and approved-difference cases never enter the compatibility denominator.
• The pinned inventory contains 2,417 rows: 1,792 verified differential cases, 580 verified contract cases, 35 excluded completion cases, and 10 explicit product/upstream-internal not-applicable cases. No compatibility row remains incomplete or unregistered.
• Current platform evidence covers Linux x86_64, macOS arm64, and Windows x86_64 Native candidates plus one Ubuntu-built wasm1 asset downloaded by all three Native jobs. The platform gate and official non-completion harness pass on all six target combinations; the overall CI workflow can still be red for independent coverage, contract, quality, or artifact-size gates.
• Two Linux-only upstream tests for non-UTF-8 working directories are not-applicable for wasm1. The moonrun/MoonX host environment boundary currently panics on the invalid host value before producing a useful MoonJust wasm result. Native passes both tests exactly. This is an accepted host limitation outside MoonJust's platform scope; it is recorded in the pinned exception manifest rather than hidden by normalization.
• Unapproved differences fail by default. Updating the committed oracle requires the explicit audited command documented in tools/upstream/README.md.
• Native signal qualification records async-only policy evidence. Direct-child wait/reap is a hard lifecycle gate; raw signal identity, TERM forwarding, first-signal ordering, SIGINFO and signal-specific diagnostics are not MoonJust guarantees.
• Main and release workflows run report-only benchmarks on Linux x86_64, macOS arm64 and Windows x86_64 with three cold/warm rounds. They gate execution, sample completeness and provenance only; timing values are trend evidence, not absolute performance thresholds. Production coverage keeps Native and Wasm raw reports and gates only the merged overall rate at 80%.
• CI orchestration uses Python 3.11 and native path/file operations. Windows jobs do not require Git Bash; the historical host-async lifecycle probes are isolated and are not a current release gate.
• Browser, arbitrary WASI, wasm-gc process execution and child-process sandboxing are not supported claims.

#Quick start

#Prerequisites

moon, moonc, and moonrun from the latest matching distribution

git config core.hooksPath .githooks

#Build and inspect

moon check --target all --warn-list +73
moon build --target native cmd/just
moon build --target wasm cmd/just
moon run --target native cmd/just -- --help
moon run --target native cmd/just -- --version

moonrun --policy policies/inspect.toml \
  _build/wasm/debug/build/cmd/just/just.wasm --help

#Run the release gate

python3 tools/runner.py run --mode release

#Architecture

argv / stdin / cwd / explicit host facts
        |
        v
CLI composition and validation
        |
        v
loader -> source -> lexer -> parser -> semantic model
                                  |
                                  v
                    evaluator / invocation / query
                                  |
                                  v
              working directory + environment configuration
                                  |
                                  v
                    platform-aware executor boundary

#Repository map

#Security boundary

#Development workflow

moon check --target all --warn-list +73
moon test --target native
moon test --target wasm
moon info
moon fmt
python3 tools/runner.py run --mode verify

#Documentation index

• Project plan: scope, architecture, compatibility tiers and historical delivery sequence.
• Release readiness audit: current consolidated verdict, remediation and remote evidence.
• Historical delivery reports: milestone-local records retained for traceability.
• Public API and release policy: package surface, candidate integrity and maintainer-only publication boundary.
• Architecture: package boundaries and capability flow.
• ADR index: accepted design decisions.
• Security policy: threat model and disclosure boundary.
• Changelog: user-visible project history.

#License and provenance