RuvNet Brain 4.6.0 — coordinated installed-tool updates

RuvNet Brain 4.6.0 — coordinated installed-tool updates

Manual and overnight updates use one coordinator, saved policy and shared owner lock. The
installed ruvnet-brain-update --check and --apply commands expose that coordinator. Configured
automatic lifecycle paths join its immutable registered closure; unconfigured legacy/proof paths
retain their compatibility setting. RNBC
presents Keep all tools updated with Latest (recommended) or Alpha, and reports the
saved choice, native scheduler state and actual run evidence separately. The scheduled run is
03:30 in the user's local time. The public default covers installed RuvNet-suite tools; broader
developer-tool maintenance is an explicit choice.

Latest/Alpha policy remains explicit in runtime receipts. Native updates use the existing
command owner; private caches and signed applications retain their existing owner and path.

The coordinator discovers the existing package prefix, commands and plugin scopes before
applying updates. It preserves their owner and path, refuses downgrades and records targets,
before/after snapshots and exclusions. Enabled maintenance stages use existing managers rather
than installing absent tools. Legitimate project dependencies, active leased generations,
signed apps' embedded runtimes, pinned toolchains, local builds and local Python wheels remain
owned by their existing lifecycle. Cleanup has a separate opt-in and preserves active or
unclassified sources.

Activity uses the source-bound run receipt. A check remains a check, a failed stage stays
visible, and an excluded or unverified tool is not reported as current. Hosted MCP software
updates remain the provider's responsibility; checking a connection does not prove software
currency. The Brain's signed corpus update still preserves private and local-ingest stores.

Dependency and plugin identity checks

The knowledge runtime advances Sharp from 0.35.4 to 0.35.5, with a supported dependency floor
of >=0.35.5. npm audits of the root and knowledge-runtime lockfiles on October 10 reported
zero vulnerabilities. Dependency-audit results describe the audited lockfiles at their check time;
they do not prove native image-processing behavior or all future registry state.

Plugin currency uses published semantic versions for versioned unpinned plugins and exact
commit identity for pinned or otherwise opaque targets. A versioned unpinned plugin does not
need to match a newer repository HEAD when its published version is unchanged. Updates preserve
installed user/project/local scopes and disabled state. Unresolved targets remain visible rather
than being reported as current. A catalogue refresh is distinct from an installed plugin update.
The inspected Codex CLI has no installed-plugin update command: Git catalogues can refresh while
installed generations remain preserved. These limits stay visible in the run receipt.

Evidence and limits

This document describes the 4.6.0 source. Publication and public installation require the
protected release transaction's install-verified receipt on its exact candidate; a version
stamp, passing unit tests or scheduler registration does not establish that outcome. Native
scheduled execution and every enabled maintenance stage require their actual run receipts.
The operating contract and developer-checkout commands live in CONTRIBUTING.md under
"Coordinated developer updates (4.6.0)".

Agentic Kit's upstream updater ownership integration remains separate work, tracked as issue
469 in pacphi/agentic-kit. A private patched installation is not evidence of an upstream Kit
release. Local RuOS OAuth scope and editor command preferences are machine repairs, not
features shipped by this Brain release.

Provider ownership and unattended limits

Scheduled runs preserve managed, project and local plugin scopes without opening their project files; those scopes remain explicitly unverified. Pinned Claude artifacts may use exact immutable resource-byte proof when provider Git metadata is stale, with computed references, other hosts and whole-repository equality excluded.

Claude commands disable the independent background updater while the coordinator owns the run. If the canonical entry is the exact recognized stock placeholder, the coordinator may select an already-installed, version- and platform-matched native executable inside the same original owner. It performs no new install or download for that fallback.

Exact release evidence

Source: db36152f274043d423eb61ef1cf0a85fb9ff49a7.

Public npm and GitHub package SHA-256: 8c5cfc8ce0c7c518dc559c44a44e3853dba799b776d06341c6ed3a040805a6e0.

Protected preflight: run 38052630620, all 22 jobs passed. Protected publication and public installation: run 38054210706; terminal verification requires its signed install-verified receipt.