[GH-ISSUE #3397] [Bug] Unnamed ELF read-only sections lose embedded Rust compiler-path evidence #1261

New issue

Closed

opened 2026-10-16 21:03:31 +00:00 by bsakaguchi · 1 comment

bsakaguchi commented 2026-10-16 21:03:31 +00:00

Owner

Copy link

Originally created by @coygeek on GitHub (Oct 14, 2026).
Original GitHub issue: https://github.com/morluto/rea/issues/3397

Before submitting

• I searched the open and closed issues for a related report.
• I removed credentials, tokens, private paths, and sensitive target data.

Area

Native analysis or decompilation

Observed behavior

inspect-rust-binary returns rustc_commit: null for a valid ELF whose allocated read-only data section has no name, even though that section contains a complete compiler path. The same bytes in a named section return the hash and its correct file offset. Removing the optional section-name table also returns null. The result says that no compiler path was found in read-only data without exposing the skipped coverage.

All three public CLI commands exit 0. The compiler-path bytes and their offset are identical in all variants. The omission was reproduced through the public CLI with independently constructed inputs.

Reproduction

1. Start from a clean source checkout and build the runtime.

git clone https://github.com/morluto/rea.git rea-repro
cd rea-repro
git checkout --detach 8dde6370d0809ad04cda3342d4e6f290f48aa063
npm ci
npm run build:cached

2. Run the following complete fixture builder and three CLI inspections from the repository root. No Rust compiler or external analysis engine is needed. The builder creates a small ELF64 executable with a read-only load segment and an allocated, file-backed SHT_PROGBITS section. The unnamed variant changes only that section's four-byte name index to zero. The third variant removes the optional section-name table.

work_dir="$(mktemp -d)"
trap 'rm -rf "$work_dir"' EXIT
cat > "$work_dir/create.mjs" <<'EOF'
import { writeFileSync } from 'node:fs';
import { dirname, join } from 'node:path';
import { fileURLToPath } from 'node:url';
const out = process.argv[2] ?? dirname(fileURLToPath(import.meta.url));
const bytes = Buffer.alloc(768);
bytes.set([0x7f, 0x45, 0x4c, 0x46, 2, 1, 1]);
const u16 = (at, value) => bytes.writeUInt16LE(value, at);
const u32 = (at, value) => bytes.writeUInt32LE(value, at);
const u64 = (at, value) => bytes.writeBigUInt64LE(BigInt(value), at);
u16(16, 2); u16(18, 62); u32(20, 1);
u64(32, 64); u64(40, 128);
u16(52, 64); u16(54, 56); u16(56, 1);
u16(58, 64); u16(60, 3); u16(62, 1);
u32(64, 1); u32(68, 4); u64(72, 0); u64(80, 0x400000);
u64(96, bytes.length); u64(104, bytes.length); u64(112, 1);
const names = Buffer.from('\0.shstrtab\0.rodata\0');
names.copy(bytes, 512);
u32(192, 1); u32(196, 3); u64(216, 512); u64(224, names.length); u64(240, 1);
const compilerPath = Buffer.from('/rustc/aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa/library/core');
compilerPath.copy(bytes, 640);
u32(256, 11); u32(260, 1); u64(264, 2); u64(272, 0x400000 + 640);
u64(280, 640); u64(288, compilerPath.length); u64(304, 1);
writeFileSync(join(out, 'readonly-named.elf'), bytes);
const unnamed = Buffer.from(bytes);
unnamed.writeUInt32LE(0, 256);
writeFileSync(join(out, 'readonly-unnamed.elf'), unnamed);
const noNames = Buffer.from(unnamed);
noNames.writeUInt16LE(0, 62); noNames.fill(0, 192, 256);
writeFileSync(join(out, 'readonly-no-names.elf'), noNames);
EOF
node "$work_dir/create.mjs" "$work_dir"
node scripts/rea.mjs inspect-rust-binary "$work_dir/readonly-named.elf" --json
node scripts/rea.mjs inspect-rust-binary "$work_dir/readonly-unnamed.elf" --json
node scripts/rea.mjs inspect-rust-binary "$work_dir/readonly-no-names.elf" --json

3. Compare normalized_result.rustc_commit in the three results. The named control returns the inferred hash at file offset 640. Both other variants return null and the absence limitation quoted below.

Expected behavior

All three inspections should retain the same inferred compiler hash at file offset 640. Empty section names and an absent section-name string table are valid ELF representations. The section's type, allocation flag, file range, read-only permissions, and embedded path remain sufficient to identify its read-only data. The missing dependency section should continue to return auditable_metadata: null.

docs/rust-binaries.md:42 describes compiler-path inference from read-only data. tests/boundary/rust/rustBinaryImage.test.ts:115 explicitly preserves such evidence when a section's name cannot fit the name-decoding window.

Impact and scope

Impact level: P2. Assessment status: supported. A documented static evidence facet silently loses a present compiler path for the reproduced valid ELF representations and reports absence without exposing skipped coverage. No artifact bytes are modified by inspection. Prevalence in compiler-produced binaries was not measured.

Workaround status: unverified. An external ELF reader could inspect the same read-only bytes, but that workflow was not executed. Naming a section in an artifact copy changes its bytes and digest, so the passing named control does not preserve the selected artifact's identity as a workaround.

REA version

6.4.0 (main at 8dde6370d0)

Runtime and platform

Node.js v26.10.0 on macOS 27.0.1. The compiled checkout runtime was used, and REA reports version 6.4.0. The host architecture was not recorded in the reproduction evidence; the fixture architecture is x86-64.

Target and artifact context

Three independently constructed 768-byte ELF64 little-endian x86-64 executables contain /rustc/aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa/library/core at file offset 640. Their data section is allocated, file-backed SHT_PROGBITS, and read-only. The named control has a .rodata name; the unnamed variant sets the name index to zero; the final variant removes the optional section-name table. The compiler-path bytes and file offset remain identical. No .dep-v0 dependency section is present, and no target program or external analysis engine needs to run.

Interface

CLI

Earliest failure stage

Native analysis or reconstruction

Relevant output or evidence

The observed named-control value of normalized_result.rustc_commit, followed by the observed value and limitation for both other variants:

readonly-named.elf:
{"evidence_kind":"inferred","hashes":[{"hash":"aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa","file_offset":640}]}

readonly-unnamed.elf and readonly-no-names.elf:
rustc_commit: null
No /rustc/<40-hex>/ path was found in read-only data, so a rustc commit hash is unknown.

All three commands exit 0.

Evidence provenance: observed. Local verification: reproduced. Reproduction completeness: complete.

Typed outcome or recovery expected

Repeat the three commands. Each must retain the same hash and offset while preserving the selected file's own digest and leaving auditable_metadata null. A control with the data section made writable must still omit the hash, so restoration does not turn compiler inference into an unrestricted byte-string scan. This writable control is a restoration requirement; its result was not recorded in the reproduction evidence.

Analysis or suspected cause

Source-derived reasoning: src/go/GoElfImage.ts:144 skips section recording without a name table, and src/go/GoElfImage.ts:263 omits unnamed sections. src/rust/RustBinaryImage.ts:109 scans only the recorded read-only ranges. These paths explain how unchanged compiler-path bytes in valid read-only sections can disappear from inference when the sections lack names. The CLI outputs above establish the failure; this explanation comes from source inspection.

Additional context

• Related open issue #2536 loses Go build metadata from a later writable segment in a sectionless PIE; this issue loses Rust compiler-path evidence from omitted unnamed read-only section records.
• Related completed issue #1659 concerns Ghidra-defined Rust string-search coverage and missing limitations; this issue concerns the built-in Rust compiler-path inspector without an external analysis engine.

Originally created by @coygeek on GitHub (Oct 14, 2026). Original GitHub issue: https://github.com/morluto/rea/issues/3397 ### Before submitting - [x] I searched the open and closed issues for a related report. - [x] I removed credentials, tokens, private paths, and sensitive target data. ### Area Native analysis or decompilation ### Observed behavior `inspect-rust-binary` returns `rustc_commit: null` for a valid ELF whose allocated read-only data section has no name, even though that section contains a complete compiler path. The same bytes in a named section return the hash and its correct file offset. Removing the optional section-name table also returns null. The result says that no compiler path was found in read-only data without exposing the skipped coverage. All three public CLI commands exit 0. The compiler-path bytes and their offset are identical in all variants. The omission was reproduced through the public CLI with independently constructed inputs. ### Reproduction 1. Start from a clean source checkout and build the runtime. ```sh git clone https://github.com/morluto/rea.git rea-repro cd rea-repro git checkout --detach 8dde6370d0809ad04cda3342d4e6f290f48aa063 npm ci npm run build:cached ``` 2. Run the following complete fixture builder and three CLI inspections from the repository root. No Rust compiler or external analysis engine is needed. The builder creates a small ELF64 executable with a read-only load segment and an allocated, file-backed `SHT_PROGBITS` section. The unnamed variant changes only that section's four-byte name index to zero. The third variant removes the optional section-name table. ```sh work_dir="$(mktemp -d)" trap 'rm -rf "$work_dir"' EXIT cat > "$work_dir/create.mjs" <<'EOF' import { writeFileSync } from 'node:fs'; import { dirname, join } from 'node:path'; import { fileURLToPath } from 'node:url'; const out = process.argv[2] ?? dirname(fileURLToPath(import.meta.url)); const bytes = Buffer.alloc(768); bytes.set([0x7f, 0x45, 0x4c, 0x46, 2, 1, 1]); const u16 = (at, value) => bytes.writeUInt16LE(value, at); const u32 = (at, value) => bytes.writeUInt32LE(value, at); const u64 = (at, value) => bytes.writeBigUInt64LE(BigInt(value), at); u16(16, 2); u16(18, 62); u32(20, 1); u64(32, 64); u64(40, 128); u16(52, 64); u16(54, 56); u16(56, 1); u16(58, 64); u16(60, 3); u16(62, 1); u32(64, 1); u32(68, 4); u64(72, 0); u64(80, 0x400000); u64(96, bytes.length); u64(104, bytes.length); u64(112, 1); const names = Buffer.from('\0.shstrtab\0.rodata\0'); names.copy(bytes, 512); u32(192, 1); u32(196, 3); u64(216, 512); u64(224, names.length); u64(240, 1); const compilerPath = Buffer.from('/rustc/aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa/library/core'); compilerPath.copy(bytes, 640); u32(256, 11); u32(260, 1); u64(264, 2); u64(272, 0x400000 + 640); u64(280, 640); u64(288, compilerPath.length); u64(304, 1); writeFileSync(join(out, 'readonly-named.elf'), bytes); const unnamed = Buffer.from(bytes); unnamed.writeUInt32LE(0, 256); writeFileSync(join(out, 'readonly-unnamed.elf'), unnamed); const noNames = Buffer.from(unnamed); noNames.writeUInt16LE(0, 62); noNames.fill(0, 192, 256); writeFileSync(join(out, 'readonly-no-names.elf'), noNames); EOF node "$work_dir/create.mjs" "$work_dir" node scripts/rea.mjs inspect-rust-binary "$work_dir/readonly-named.elf" --json node scripts/rea.mjs inspect-rust-binary "$work_dir/readonly-unnamed.elf" --json node scripts/rea.mjs inspect-rust-binary "$work_dir/readonly-no-names.elf" --json ``` 3. Compare `normalized_result.rustc_commit` in the three results. The named control returns the inferred hash at file offset 640. Both other variants return null and the absence limitation quoted below. ### Expected behavior All three inspections should retain the same inferred compiler hash at file offset 640. Empty section names and an absent section-name string table are valid ELF representations. The section's type, allocation flag, file range, read-only permissions, and embedded path remain sufficient to identify its read-only data. The missing dependency section should continue to return `auditable_metadata: null`. `docs/rust-binaries.md:42` describes compiler-path inference from read-only data. `tests/boundary/rust/rustBinaryImage.test.ts:115` explicitly preserves such evidence when a section's name cannot fit the name-decoding window. ### Impact and scope Impact level: P2. Assessment status: supported. A documented static evidence facet silently loses a present compiler path for the reproduced valid ELF representations and reports absence without exposing skipped coverage. No artifact bytes are modified by inspection. Prevalence in compiler-produced binaries was not measured. Workaround status: unverified. An external ELF reader could inspect the same read-only bytes, but that workflow was not executed. Naming a section in an artifact copy changes its bytes and digest, so the passing named control does not preserve the selected artifact's identity as a workaround. ### REA version 6.4.0 (main at 8dde6370d0809ad04cda3342d4e6f290f48aa063) ### Runtime and platform Node.js v26.10.0 on macOS 27.0.1. The compiled checkout runtime was used, and REA reports version 6.4.0. The host architecture was not recorded in the reproduction evidence; the fixture architecture is x86-64. ### Target and artifact context Three independently constructed 768-byte ELF64 little-endian x86-64 executables contain `/rustc/aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa/library/core` at file offset 640. Their data section is allocated, file-backed `SHT_PROGBITS`, and read-only. The named control has a `.rodata` name; the unnamed variant sets the name index to zero; the final variant removes the optional section-name table. The compiler-path bytes and file offset remain identical. No `.dep-v0` dependency section is present, and no target program or external analysis engine needs to run. ### Interface CLI ### Earliest failure stage Native analysis or reconstruction ### Relevant output or evidence The observed named-control value of `normalized_result.rustc_commit`, followed by the observed value and limitation for both other variants: ```text readonly-named.elf: {"evidence_kind":"inferred","hashes":[{"hash":"aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa","file_offset":640}]} readonly-unnamed.elf and readonly-no-names.elf: rustc_commit: null No /rustc/<40-hex>/ path was found in read-only data, so a rustc commit hash is unknown. All three commands exit 0. ``` Evidence provenance: observed. Local verification: reproduced. Reproduction completeness: complete. ### Typed outcome or recovery expected Repeat the three commands. Each must retain the same hash and offset while preserving the selected file's own digest and leaving `auditable_metadata` null. A control with the data section made writable must still omit the hash, so restoration does not turn compiler inference into an unrestricted byte-string scan. This writable control is a restoration requirement; its result was not recorded in the reproduction evidence. ### Analysis or suspected cause Source-derived reasoning: `src/go/GoElfImage.ts:144` skips section recording without a name table, and `src/go/GoElfImage.ts:263` omits unnamed sections. `src/rust/RustBinaryImage.ts:109` scans only the recorded read-only ranges. These paths explain how unchanged compiler-path bytes in valid read-only sections can disappear from inference when the sections lack names. The CLI outputs above establish the failure; this explanation comes from source inspection. ### Additional context - Related open issue [#2536](https://github.com/morluto/rea/issues/2536) loses Go build metadata from a later writable segment in a sectionless PIE; this issue loses Rust compiler-path evidence from omitted unnamed read-only section records. - Related completed issue [#1659](https://github.com/morluto/rea/issues/1659) concerns Ghidra-defined Rust string-search coverage and missing limitations; this issue concerns the built-in Rust compiler-path inspector without an external analysis engine.

bsakaguchi referenced this issue 2026-10-17 21:09:57 +00:00

[PR #1277] [MERGED] fix(mcp): deliver tool errors within advertised schema contracts #2762

bsakaguchi closed this issue 2026-10-31 00:30:20 +00:00

bsakaguchi commented 2026-10-31 00:30:21 +00:00

Author

Owner

Copy link

@CassieFox23 commented on GitHub (Oct 21, 2026):

Thanks, coygeek, for the fixture builder. From reading main at 01788bac8, not a run: this still looks valid. The file src/native/metadata/ElfImage.ts:69 drops every section whose name is empty. It also drops every section whose name table is unavailable. That happens before the read-only check at line 80 can keep it. A name index of 0 decodes to an empty name (src/native/metadata/NativeSectionDirectory.ts:181-193). A missing shstrtab sets name_state to unavailable (line 172). So neither unnamed variant reaches the read-only scan in src/rust/RustBinaryImage.ts:122-127. PR #3477 closed on 2026-10-20 without merging. Likely area: native container parsing.

🤖 Written with Claude Code (Fable 5.1, verified by Opus 5.5), posted with my OK 🦊

<!-- gh-comment-id:6321732802 --> @CassieFox23 commented on GitHub (Oct 21, 2026): Thanks, coygeek, for the fixture builder. From reading main at 01788bac8, not a run: this still looks valid. The file `src/native/metadata/ElfImage.ts:69` drops every section whose name is empty. It also drops every section whose name table is unavailable. That happens before the read-only check at line 80 can keep it. A name index of 0 decodes to an empty name (`src/native/metadata/NativeSectionDirectory.ts:181-193`). A missing `shstrtab` sets `name_state` to unavailable (line 172). So neither unnamed variant reaches the read-only scan in `src/rust/RustBinaryImage.ts:122-127`. PR #3477 closed on 2026-10-20 without merging. Likely area: `native container parsing`. 🤖 Written with Claude Code (Fable 5.1, verified by Opus 5.5), posted with my OK 🦊

bsakaguchi referenced this issue 2026-11-01 21:12:35 +00:00

[GH-ISSUE #8425] [Bug] Evidence retention refusal discards a completed direct observation #6600

Sign in to join this conversation.

No Branch/Tag specified

Branches Tags

main

release-please--branches--main--components--rea-agents

release-please--branches--main--components--rea-agents--release-notes

codex/procedure-reference-stacked

codex/kuna-independent-retry

codex/byte-search-overlay-coverage

codex/open-failure-target-receipt

codex/kuna-xref-evidence

codex/ghidra-ambiguous-procedure-recovery

codex/function-source-bundle

codex/trace-function-integration-prototype

codex/snapshot-source-closure

codex/recorded-evidence-array-pages

codex/evidence-recovery-redesign

codex/trace-feature-address-scope

codex/call-discovery-scope

codex/ghidra-literal-candidate-evidence

codex/decompile-directory-independent-retry

codex/retry-provenance-base

codex/value-flow-capability-experiment

codex/ghidra-containing-instruction

cursor/readme-discord-button-ef9f

dependabot/github_actions/actions/setup-node-7.1.0

dependabot/github_actions/actions/upload-artifact-7.0.2

dependabot/npm_and_yarn/npm-minor-and-patch-d8d97ce6df

codex/kuna-1989

fix/8559-native-ui-fixture-ownership

fix/8555-go-verifier-mcp-ownership

codex/provider-capability-recovery

fix/8642-rizin-target-stdin

codex/ghidra-memory-effect-scope

codex/ghidra-annotation-entry-selector

codex/ghidra-readonly-recovery

codex/ghidra-regex-verifier-recovery

codex/evidence-discovery-view-guidance

fix/8545-bulk-append-overflow

fix/8428-navigation-refusal-alternatives

codex/address-context-recovery

codex/matching-member-limitations

codex/unknown-scope-contract

codex/evidence-view-guidance

feat/8373-native-trace-views

codex/ghidra-snapshot-verifier-binding

codex/elf-export-visibility

codex/evidence-view-recovery

codex/native-reference-cli-help

codex/provider-candidate-observation-scope

codex/kuna-session-verification

codex/ghidra-switch-lifetime-guidance

codex/pseudocode-paging-discovery

codex/clarify-evidence-view-support

codex/kuna-xrefs-selector-recovery

codex/context-capacity-recovery

codex/evidence-closure-large-links

codex/same-function-evidence-identity

codex/ghidra-verifier-inspected-jdk

codex/audit-guided-workflows

codex/crash-prompt-retained-dossiers

codex/analysis-view-error-recovery

codex/kuna-verifier-target-selection

codex/ghidra-selected-project-call-coverage

codex/docs-native-analysis-scope

codex/ghidra-java-socket-boundary

codex/ghidra-retained-snapshot-verifier

codex/ghidra-search-inventory-facts

fix/8284-zero-argument-parameter-bindings

fix/8198-ui-action-handler-offset

fix/8257-elf-entry-label-identity

fix/8304-deferred-output-schema-projection

fix/8277-call-path-computed-target-uncertainty

fix/pr-8089-conflicts

fix/ci-static-duplicate-export

dependabot/npm_and_yarn/lint-staged-17.6.0

dependabot/github_actions/actions/download-artifact-8.0.2

dependabot/npm_and_yarn/write-file-atomic-8.0.0

dependabot/npm_and_yarn/canonicalize-5.1.0

dependabot/github_actions/actions/cache/restore-6.1.0

dependabot/npm_and_yarn/toon-format/toon-4.4.0

dependabot/github_actions/actions/deploy-pages-5.0.1

codex/review-fixes-pr-2403

codex/review-fixes-pr-2400

codex/process-terminal-width

codex/test-brittleness-cleanup

verify/7167-browser-connect-macos

fix/7167-browser-connect

feat/native-matching-allowance-setting

feat/browser-scenario-dry-run

test/managed-caller-parameters-20261024

codex/parser-fortythird-boundaries

fix/6926-pinvoke-platform-decorations-20261023

fix/6889-har-body-encoding-20261023

fix/6888-sqlite-schema-budget-20261023

fix/dependency-security-gates-6708

cursor/evidence-overwrite-rebase-b4ac

feat/4057-verify-native-exports

fix/windows-acl-observer-overhead-20261022

cursor/erlang-beam-restack-4476

cursor/pe-certificate-review-bf32

fix/6116-javascript-application-fs-errors

fix/6061-unmapped-runtime-script-unknown

feat/browser-scenario-summary

fix/pe-certificates

codex/verify-3407

cursor/rebase-5699

cursor/rebase-5352

cursor/rebase-5600

cursor/fix-cli-schema-omission-10a8

codex/audit-hopper-shutdown-reasons-20261021

fix/demangle-swift-omitted-record

fix/nib-boolean-value-types

cursor/cancellation-partial-observation-a5ac

fix/ib-object-limit-reasons

fix/electron-fuse-limit-advice

fix/kuna-doctor-dangling-cache

fix/fixed-budget-refusal-advice

fix/js-ipc-listener-dedup

fix/js-return-member-provenance

fix/dmg-integrity-retry-advice

fix/ida-doctor-readiness

fix/kuna-version-probe-output-drain

fix/legacy-swift-runtime-name-matching

fix/dylib-lazy-load-commands

fix/browser-scenario-startup-cancel

fix/swift-nested-punycode-classification

fix/compare-unselected-scopes

fix/objc-method-budget-coverage

fix/dmg-mounted-root-observations

audit/ci-tests-20261019-round2

release/6.7.0

fix/wabt-cleanup-retry-resolution

fix/electron-fuse-elf-pe-architecture

fix/native-plist-descriptor-ownership

fix/kuna-caller-cleanup-ownership

experiment/atomic-codemode-20261016

review/first-contributor-3776

fix/call-resolution-full-read-cycles

fix/member-mutation-selection-repeat

experiment/atomic-re-tools-20261015

perf/member-mutation-lazy-origins

perf/static-network-mutation-index

fix/hopper-startup-lifecycle

audit/3050-windows-proof-20261015

feat/windows-window-capture-2183

audit/3049-windows-proof-20261015

audit/3735-macos-fixtures-20261015

fix/batch-decompile-null-pseudocode

fix/kuna-inventory-honors-jobs

experiment/browser-codemode-tool-design-20261015

fix/hopper-clean-runtime-argv

codex/review-2049-27f1b367

review-fixes/pr-2787-routing

fix/3360-scoped-this-emitters

fix/3367-replaced-global-effects

fix/3838-compact-any-value-items

test/hopper-download-probe-20261015

codex/windows-runtime-creation-red-green-20261015

codex/windows-readonly-root-red-green-20261015

codex/windows-root-share-red-green-20261015

codex/exp-1685-win-mcp-startup

codex/bug-sweep-20261015

investigate/2190-windows-package-phases

investigate/3543-macos-cli-deadline

perf/3281-reverse-tools-feedback-quality

fix/3406-hopper-doctor-fixture

fix/3341-wrapper-require-test-context

fix/3301-owned-uninstall-fixtures

fix/3164-compiler-input-ownership

fix/pcap-cleanup-stdout-newline-20261014

perf/interface-builder-summary

codex/review-fixes-pr-1977

fix/ghidra-effective-jvm-platform

fix/docs-turkish-rust-link-20261013

fix/main-maintenance-ci-20261010

fix/recover-binary-session-process-effects

codex/review-fixes-pr-2457

codex/ci-required-cancellation-gate

fix/main-format-baseline-20261013

fix/setup-preserve-entry-fields

cursor/restore-main-checks-1ffc

fix/ghidra-bridge-hashmap-import

codex/shared-ci-jadx-json-default-20261013

codex/shared-ci-ghidra-test-groups-20261013

codex/shared-ci-java-fixture-format-20261013

codex/fix-intrinsic-invocation-boundaries

test/release-preflight-reusable-jobs

test/js-parameter-provenance-expectation

fix/linux-hopper-verification-current

test/2419-ghidra-elf-probe-size

followup/pr-1544-native-ida

codex/fold-pr-2230-contribution

docs/readme-responsible-use

fix/issue-2064

fix/issue-2050

fix/issue-2053

fix/issue-1968

fix/issue-1945

experiment/codemode-bridge-20261011

fix/tool-effects-negative-wording-1904-20261012

fix/1842-electron-interop-provenance

feat/recover-javascript-multi-input

refactor/website-i18n-prep

fix/nativeaot-pe-virtual-extent

fix/browser-verifier-ci-hang

fix/pe-resources-input-selection

docs/beginner-friendly-guides

docs/beginner-setup-guide

fix/javascript-analysis-worker-1563

fix/1649-ghidra-duplicate-names

fix/javascript-export-keys-integration-1369

test/maintenance-boundary-contracts-20261011

review/javascript-export-keys-1369

review/process-live-progress-1483

test/javascript-1495-growth-ratio

fix/ci-escape-timing

docs/normalized-terminal-geometry-1450

release/6.3.0

archive/release-6.3.0-pr1381

release/6.2.0

fix/electron-preload-dynamic-override

fix/javascript-self-referential-bundler-edges

release/6.1.0

cursor/grok-client-cherry-pick-0b56

feat/signature-posture

feat/dyld-shared-cache

feat/artifact-integrity-policy

feat/pkg-inventory

release/6.0.0

chore/sync-release-5.0.0

release/5.0.0

cursor/cloud-agent-node-787e

fix/javascript-xhr-open-endpoints

review/pr-711-realpath-fallback-wording

cleanup/replay-confinement

codex/test-suite-performance

codex/issue-foundations

codex/address-open-issues-2026-07-20

agent/javascript-vite-rollup-esbuild-adapters

agent/process-cleanup

agent/triage-integration

agent/unknown-commands-registry

feat/mcp-identity-metadata

morlvps/issue_cleanup

codex/installer-redesign

morl/roadmap-investigation-core

morl/roadmap-investigation-docs

release-please--branches--main--components--rea

rea-agents-6.8.0

rea-agents-6.7.0

rea-agents-6.6.0

experiment/atomic-codemode-wait-runtime-20261016

rea-agents-6.5.0

rea-agents-6.4.0

rea-agents-6.3.0

rea-agents-6.2.0

rea-agents-6.1.0

rea-agents-6.0.0

rea-agents-5.0.0

rea-agents-4.1.0

rea-agents-4.0.1

rea-agents-4.0.0

rea-agents-3.2.1

rea-agents-3.2.0

rea-agents-3.1.0

rea-agents-3.0.0

rea-agents-2.7.0

rea-agents-2.6.0

rea-agents-2.5.1

rea-agents-2.5.0

rea-agents-2.4.0

rea-agents-2.3.0

rea-agents-2.2.0

rea-agents-2.1.0

rea-agents-2.0.0

rea-agents-1.7.0

rea-agents-1.6.0

rea-agents-1.5.0

rea-agents-1.4.0

rea-agents-1.3.0

rea-agents-1.2.0

rea-agents-1.1.0

rea-agents-1.0.0

rea-agents-0.5.0

rea-agents-0.4.0

rea-agents-0.3.0

rea-0.2.1

rea-0.2.0

Labels

Clear labels   

area: bridge

  

area: bridge

  

area: build

  

area: build

  

area: build

  

area: cli

  

area: domain

  

area: evidence

  

area: mcp

  

area: native

  

area: providers

  

area: runtime

  

area: server

  

area: setup

  

area: tests

  

bug

  

design

  

documentation

  

enhancement

  

enhancement

  

enhancement

  

experiment

  

help wanted

  

i18n

  

invalid

  

P0: critical

  

P1: high

  

P2: medium

  

P2: medium

  

P2: medium

  

P3: low

  

performance

  

provider-request

  

pull-request

Mirrored from GitHub Pull Request

  

question

  

roadmap

  

triage

No labels

area: bridge

area: bridge

area: build

area: build

area: build

area: cli

area: domain

area: evidence

area: mcp

area: native

area: providers

area: runtime

area: server

area: setup

area: tests

bug

design

documentation

enhancement

enhancement

enhancement

experiment

help wanted

i18n

invalid

P0: critical

P1: high

P2: medium

P2: medium

P2: medium

P3: low

performance

provider-request

pull-request

question

roadmap

triage

Milestone

Clear milestone

No items

No milestone

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

1 participant

Notifications

Subscribe

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

morluto/rea#1261

No description provided.