[zkochan]

Adds a standalone Rust bit CLI, with compatible Node CLI fallback for paths still being ported. Native command execution does not imply independence from Bit's JavaScript runtime: retained host calls and remaining fallbacks are documented and tracked in the completion plan. Yarn is excluded from that plan.

• Implements native workspace and scope inspection, tracking, dependency installation, snapshots, checkout, merge, lane/import/export and recovery paths. The command coverage table records supported modes and remaining boundaries.
• Keeps the diff within native/, Rust documentation/tooling and the two Rust workflows. Upstream master is merged through 3754c4f57 (following Bit 2.2.160).
• Matches upstream's pnpm 12.16 engine, including stale-symlink retry protection and symlinked-lockfile refusal. All engine Git dependencies advance together; native API adapters and lockfiles are updated.
• Handles active-lane object refreshes and cross-scope hidden updates without promoting hidden entries. Workspace merges fetch hidden components' main history and retain histories already received in the same operation. Scope-side fixture production still uses the released CLI.
• Scaffolds CI onboarding in Rust: repository-root workflows, comment-preserving configuration and backups, agent instructions, and GitHub/Enterprise setup guidance. Existing files and hand edits are preserved. Configured startup callbacks, active lanes, bitmap auto-sync and unsupported CI configuration still decline before effects.
• Restores pre-merge main component models when aborting a lane merge, including retained-import proofs so later publication cannot replay the merged heads. The two new upstream assertions run natively; disabling the snapshot makes the regression fail. History traversal now uses indexed lookup while preserving insertion and traversal order.
• Collects bare-scope garbage in Rust, retaining local ancestry, live/trashed lane roots and requested dependency versions. Unix backup/recovery preserves symlinks, overwrite rules, copy ordering and recoverable partial failures. Workspace collection plans before mutation and owns errors afterward. Bare verbose reports, workspace verbose text/JSON output and workspace legacy aliases are also native on the documented inputs. Windows nonempty collection/recovery, workspace verbose text with multiple deletions, complex bare verbose ordering, mixed-type workspace reports, larger batches and unqualified early-failure layouts still delegate before effects.
• Owns configured HTTP export recovery and file pending-directory deletion in Rust. Generic actions, file persistence, runtime/provider replacement, full build/CI orchestration and long-running services remain tracked work.

Validation: formatting, Clippy, Dylint, rustdoc, generated porting/census/asset checks and all 1,809 workspace tests pass. Full E2E: 1,704 passed, two Bit Cloud setup failures and two existing skips. Both failed cases passed unchanged on a serial rerun. All 36 focused collection/recovery/installer cases pass.. The collection tests compare command bytes and complete filesystem effects, with negative controls for alias resolution and repeated lane counts. The main recovery regression proves the restored head and empty export staging. Repository Node lint cannot run locally because tsc is unavailable.

Bit 2.2.160 is not yet downloadable. The new upstream recovery semantics therefore have explicit native regression assertions, while component serialization retains the existing released-qualified projection. Differential qualification against 2.2.160 remains pending that release's availability.

The released Bit reference still bundles pnpm 12.13, so the E2E harness resolves its installer dependency to the integrity-pinned, published @pnpm/napi 12.16 addon. It does not replace Bit implementation code or change its installed files. Comparisons retain the new validation metadata and normalize only qualified clock fields. CI installs this isolated reference on Linux and Windows.

The Windows transfer fixture's setup snapshots use the released CLI explicitly; its native fetch, output and stored-object assertions remain required. The new onboarding cases also run in Windows provisioning CI. Windows provisioning exposed checkout line-ending and filesystem-error differences. The latest commit normalizes the bundled assets and Windows error paths/codes; all 12 onboarding cases also pass locally with CRLF assets. The final nested-workspace discrepancy came from Node preserving DOS short names while Rust expanded them. Path resolution now follows the released Node API, with a direct filesystem oracle and a negative control that fails under canonicalization. Windows provisioning now passes with the path fix. The Linux installer comparison also handles the observed redundant two-package startup redraw, only when the immediately following store banner repeats the same counters. Counter changes, other control sequences, intervening messages, later progress transitions and filesystem assertions remain checked. The recorded CI output fails the former comparison and passes the corrected one. The preceding Rust CI workflow is green on 726e5bc33, including Windows provisioning and all four Linux E2E shards. The collection/recovery commit 673e41df7 failed its generated-inventory check because GitHub merged it with newer upstream tests. This sync preserves that newer master and updates the inventory with both implemented assertions. All platform and E2E jobs on that prior head passed. CI for the new head is pending; Windows merge-history coverage now explicitly includes lane abort.

Latest validation (d88b3f1): the upstream history-merge set optimization is already implemented natively; added 40,000-row ordering/override and empty-input regressions. Fixed the Linux host fixture ETXTBSY race by using a checked-in immutable executable. All 60 CLI unit-suite stress runs at 64 threads pass. Formatting, Clippy, Dylint, rustdoc, generated checks and all 1,811 workspace tests pass. Full E2E: 1,703 passed, three failed, two existing skips. Two failures were Cloud setup requests; one was a dependency-capture freshness failure during environment-policy tagging. All three pass unchanged serially; the intermittent freshness failure remains under investigation. Windows merge-history CI on the preceding head passed, including lane abort. CI for this head is pending.