Keyboard shortcuts

Press ← or → to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

NUIF Editor 0.1.0-alpha.2

This editor research preview makes verified, source-built, user-scoped installation the canonical way to use the reference editor as a persistent development and conformance tool. The application prerelease does not assign a maturity level to the pre-draft specification. It retains all profile-zero editor, adapter, benchmark and release evidence from 0.1.0-alpha.1.

Developer installation

Clone this exact tag and keep the checkout as the lifecycle control plane:

git clone --branch v0.1.0-alpha.2 --depth 1 https://github.com/refpath/nuif.git
cd nuif
git rev-parse HEAD
cargo xtask editor-install --user --channel alpha

The install builds with the checked-in Rust toolchain and Cargo.lock, creates an immutable version directory, activates the host integration, writes a source/build receipt and runs editor-doctor. macOS applies and verifies a local ad-hoc signature. Windows and Linux remain user scoped.

After this release, explicit updates can resolve and install the highest published alpha:

cargo xtask editor-update --user --channel alpha --check
cargo xtask editor-update --user --channel alpha
cargo xtask editor-doctor --user
cargo xtask editor-rollback --user
cargo xtask editor-uninstall --user

The updater verifies the release-manifest attestation against the repository, release workflow, tag, source revision and GitHub-hosted runner before fetching the exact tag with Git hooks disabled. The checkout must match the attested revision and remain clean before it is built. Updates are never silent.

Users of 0.1.0-alpha.1 must perform the exact-tag clone above once because that release did not yet contain the source lifecycle. Subsequent alpha updates use editor-update.

Safety and evidence

  • Installer receipts bind the editor version, commit, deterministic working tree, Cargo.lock, Rust toolchain, platform, architecture and installed binary digest.
  • Active and previous immutable versions are retained for offline rollback.
  • Install, doctor and uninstall run in sandbox roots on Linux x86-64 and Arm64, Windows x86-64, macOS Apple Silicon and macOS Intel release hosts.
  • Existing unrelated paths are rejected. Removal requires a NUIF product marker and never targets a filesystem root.
  • No command disables Gatekeeper, System Integrity Protection, Defender, SmartScreen or Smart App Control, changes a certificate store, or performs a system-wide installation.

The release still includes five native CI archives, five package manifests, SHA-256 checksums, a CycloneDX SBOM, release-manifest.json, and GitHub artifact attestations. These downloads are reproducibility evidence and an expert opt-in path rather than the primary developer installation.

Remaining external boundary

Release archives are not Developer ID-notarized or Windows publisher-signed. A managed machine may require an organization-approved signing identity or device policy. The source lifecycle does not work around administrator-owned controls and does not require Apple or Microsoft marketplace publication.

Canonical source.