mirror of
https://github.com/morluto/rea.git
synced 2026-11-22 06:25:44 +00:00
* 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>
Documentation directory
Find an installation step, investigation guide, or contributor reference by task. The REA website has worked examples and product pages.
Getting started
- Installation and setup
- Supported targets and requirements
- Client configuration and troubleshooting
- CLI and Evidence
- Guided MCP prompts and completion
Desktop applications
- Desktop installation directories
- Desktop application capture
- Desktop application state
- Desktop application tasks
- Desktop application export
- Desktop build computer
- Desktop build witness
Agent environments
Native binaries
- Native binary investigation
- Go binary build metadata
- DWARF compile units
- Offline binary diagnostics
- ELF separate debug files
- ELF and Mach-O initializer functions
- ELF unwind function ranges
- Linux kernel build config
- Recorded crash evidence
- Windows Shell Link shortcuts
- Acquired NTFS metadata
- Binary hardening
- ELF note tables
- ELF dependency tables
- Linux kernel modules
- PE Authenticode certificate tables
- PE import and delay-load tables
- PE TLS callbacks and load configuration
- Match native functions across builds
- Rust binary dependency metadata
- Static CUDA and HIP code objects
JavaScript and Electron
- JavaScript Application Graph
- Cross-layer JavaScript application workflows
- JavaScript artifact reconstruction
- JavaScript source recovery
- Passive Node and Electron runtime observation
- JavaScript static/runtime reconciliation
- Electron file-page observation
- V8 code cache inspection
- Electron fuse state
- Static JavaScript route inventory
- Bun standalone executables
- Deno compile executables
- Node.js single executable applications
Browser and captured websites
- Website observation with CDP
- Browser scenario contract
- Website runtime source attribution
- Historical web network captures
- HTTP/3 capture lab
- Captured website source locations
- Captured website module relationships
- Captured website scripts and static JavaScript analysis
- Offline Playwright traces
Android applications
- Static Android APK analysis
- Apktool resource decoding
- ADB device inspection and acquisition
- Flutter build identification
- Android boot and vendor_boot images
- APK signature schemes
Apple applications
.NET assemblies
Firmware
- Firmware analysis
- Android OTA update payloads
- Flattened devicetree inspection
- ESP flash images
- ESP images
- U-Boot FIT images
- Intel HEX and S-record images
- UF2 and DfuSe images
- U-Boot legacy uImage containers
HarmonyOS packages
Packages and metadata
- Offline API contract inventory
- CycloneDX dependencies
- Maven POM and Gradle module metadata
- Release exposure
- Model file declarations
- Python packaged applications
- CPython pyc inspection
- Erlang BEAM files
- Godot PCK archives
- UnityFS AssetBundle archives
- iNES containers
- WeChat mini-program wxapkg archives
WebAssembly
EVM contracts
Databases and recorded packets
Process capture and instrumentation
Provider setup and formats
- Ghidra provider semantics
- DOS MZ and COM analysis with Ghidra
- Optional NativeAOT metadata recovery
- MIPS ELF analysis through Ghidra
- PSP static ELF analysis through Ghidra
- RISC-V ELF analysis through Ghidra
- Windows Ghidra P0
- Headerless raw-binary analysis with Ghidra
- IDA provider
- JEB instrumentation and analysis
- GameCube DOL analysis through Ghidra
- PowerPC ELF analysis through Ghidra
- Kuna provider
- Reverse-engineering tool integrations
Contracts and evidence
Development and verification
- Documentation ownership and authoring
- Settings and recovery
- REA limit inventory
- MCP tool design
- Testing REA
- Client and agent verification
- Reconstruction readiness conformance
- Releasing REA
- Testing lanes and provider verification
- Measure MCP catalog costs in Codex
- Static analysis in GitHub Actions
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/.