Files
reverse-engineering-anything/docs
abba1f43bb fix(setup): register aube's bin shim instead of its versioned store path (#5311)
* fix(setup): register aube's bin shim instead of its versioned store path

mise's npm backend installs with aube, whose bin is a shell shim that runs
the script inside one version's store directory. Setup registered that
versioned script, which the next upgrade removes from under the agents.
Setup now registers the shim when it proves, from the shim's own header,
that it runs this exact entrypoint, and registration identity accepts that
shim as REA's own.

Refs #4847

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* fix(setup): move aube store registrations to the shim and follow links to it

Status now reports a direct registration as stale when the running
entrypoint has an aube bin shim and the registration is not that shim, so
doctor and setup move registrations written before this fix. A link to a
shim resolves the target from the shim's real directory, as the shim does.
The shim check runs only when the exact-path check does not already own the
command, applies on every platform (the header alone decides), and a failed
close no longer escapes classification. The test now lays out versions the
way mise does, with `latest` as a symlink.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* fix(setup): launch managed shims without client PATH dependencies

* fix(setup): bind Node for installed Aube shims without a sidecar

* fix(setup): keep an independent Node fallback for Aube shims

* fix(setup): preserve independent Node aliases across upgrades

* fix(setup): reuse verified Node for host-bound Aube shims

* fix(setup): keep Aube registrations across shim format changes

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: morluto <76467478+morluto@users.noreply.github.com>
2026-11-21 16:34:38 -05:00
..

Documentation directory

Find an installation step, investigation guide, or contributor reference by task. The REA website has worked examples and product pages.

Getting started

Desktop applications

Agent environments

Native binaries

JavaScript and Electron

Browser and captured websites

Android applications

Apple applications

.NET assemblies

Firmware

HarmonyOS packages

Packages and metadata

WebAssembly

EVM contracts

Databases and recorded packets

Process capture and instrumentation

Provider setup and formats

Contracts and evidence

Development and verification

Release migrations

Signal recordings

Generated files and release records

Path Owner and update command
public/product-catalog.json Ignored contract projection; npm run docs:generate
verification/managed-conformance-*.json Ignored managed conformance projections; npm run evidence:generate
error-contract.schema.json Tracked schema from contracts; npm run docs:error-schema
user-visible-errors.csv Generated error code and category per domain and provider-owned error case; npm run docs:error-schema
releases/<version>.contributions.json Durable release contribution record; follow the release guide

Regenerate catalogs and Evidence projections from their canonical source. Release records preserve the exact commit messages and references for each release. Guides share authored images in assets/.