Opcore 0.2.1

Opcore 0.2.1 is an urgent macOS stability hotfix for Rust validation.

Rust Cargo and native-tool checks previously created a fresh recursive copy of the target repository for every
selected check. On large repositories and concurrent agent runs, that produced a high-volume create/delete event
storm, left large temporary trees behind when processes were interrupted, and could drive macOS fseventsd memory
growth.

This release:

• materializes one Rust workspace per validation file-view state and materialization environment;
• shares that exact staged, tree, or hypothetical after-state across selected Rust checks;
• disposes run-scoped workspaces on normal, fail-fast, streaming, and failed exits;
• retains separate snapshots when Git/tool environments differ; and
• adds regression coverage for bounded materialization, cleanup, resource factory failures, and reverse-order
  disposal.

Install:

npm install --global opcore@0.2.1

Or run without installing:

npx opcore@0.2.1 --version

Full comparison: v0.2.0...v0.2.1

Opcore 0.2.0

Opcore 0.2.0 makes the default robustness loop lighter on large repositories and strengthens validation correctness. This release reduces several major sources of unnecessary in-memory data while keeping coverage and degraded checks explicit.

Highlights

• Bounds product scan validation output to summaries, counts, failed check IDs, and diagnostic samples instead of retaining and serializing an unrestricted result payload.
• Makes validation file views lazy so path-specific checks do not enumerate every visible file unless they need the complete file universe.
• Sends committed clone-analysis inputs as path references and reserves content-bearing overlays for changed or hypothetical files.
• Replaces the Python syntax heuristic with parser-backed ast.parse validation, including structured locations and an honest unsupported result when no Python interpreter is available.
• Adds native validation-policy parity and tightens the package guardrails around it.

Memory scope

These changes materially reduce memory pressure in scan and validation paths, but they do not complete the broader large-monorepo memory program. Graph build/query working sets, inspect/edit language-service isolation, bounded history and sidecar payloads, and regression harness work remain tracked separately.

Upgrade

npm install --global opcore@0.2.0

Or run it without a global install:

npx opcore@0.2.0 --version

Full comparison: v0.1.0...v0.2.0

Opcore 0.1.0

Initial Opcore alpha release.