[GH-ISSUE #5150] [Feature] Expose Constant-table default values for literal fields and parameters in inspect_managed_members #3171

New issue

Open

opened 2026-10-31 00:37:27 +00:00 by bsakaguchi · 6 comments

bsakaguchi commented 2026-10-31 00:37:27 +00:00

Owner

Copy link

Originally created by @elricfd on GitHub (Oct 19, 2026).
Original GitHub issue: https://github.com/morluto/rea/issues/5150

Before submitting

• I searched the open and closed issues and pull requests for a related proposal.
• I understand the contribution scope must be reviewed before integration; open questions are welcome here.
• This request does not include credentials, private samples, or sensitive target data.

Area

Native analysis or decompilation

Current limitation

The ECMA-335 Constant table (default values of literal fields, enum members and parameters) is not exposed. Mixed In Key 11's MixedInKey.exe has 957 Constant rows (inspect-managed-artifact table_row_counts). In inspect-managed-members --type MixedInKey.Audio.AudioAnalyser the 26 field records only have name, declaring_type_token, flags, declaring_type, signature, row_offset, token. Four have flags & 0x8000 (HasDefault), for example WMGraphNotify (0x04000f43, flags 32849 = 0x8051, field_type: "i4"); the value is nowhere in the result, and I found no constant/default key in output or schema.

Source-derived: Constant appears only in src/dotnet/ManagedMetadataLayout.ts:23 and ManagedMetadataRowSizes.ts:28 (row sizing); grep -ri constant src/dotnet src/domain/managed finds no row reader or schema field, only the CIL operand kind "constant".

Observed on rea 6.7.0, SHA-256 b014a00e6f6b80ed9313f68ad3da8f42c2de38f9111582e62145cec63c7da843 (rea inspect-managed-members <exe> --type MixedInKey.Audio.AudioAnalyser --json, ran twice).

Use cases

Enum members, version numbers and algorithm selectors are literal fields. Without values an analyst cannot name the 4 in ldloc.s 4; ldc.i4.4; bne.un or map an enum to its members.

Desired outcome and success criteria

For fields and parameters with HasDefault, return the decoded constant (element type and value), with an explicit unknown when the blob is malformed or the type is unsupported, inside the existing representation budget. Success: WMGraphNotify reports its value.

Expected interaction with targets

Read existing files or captured data

Target and scope details (optional)

Read-only metadata; no execution. Adjacent but distinct: open PR #3835 (FieldRVA initial data).

Verification available so far

I have a prototype or observed results

Verification details (optional)

Observed absence on one type. Not checked: parameters (Param flags HasDefault), property constants.

Alternatives considered

An external metadata reader for the Constant table, which is what I would have to use today.

Possible direction

A nullable constant on field (and later parameter) records, parsed by the owner that already reads the row. Proposal only.

References

ECMA-335 II.22.9 (Constant), II.23.1.5 (FieldAttributes.HasDefault).

Originally created by @elricfd on GitHub (Oct 19, 2026). Original GitHub issue: https://github.com/morluto/rea/issues/5150 ### Before submitting - [x] I searched the open and closed issues and pull requests for a related proposal. - [x] I understand the [contribution scope](https://github.com/morluto/rea/blob/main/CONTRIBUTING.md#contribution-scope) must be reviewed before integration; open questions are welcome here. - [x] This request does not include credentials, private samples, or sensitive target data. ### Area Native analysis or decompilation ### Current limitation The ECMA-335 `Constant` table (default values of literal fields, enum members and parameters) is not exposed. Mixed In Key 11's `MixedInKey.exe` has 957 `Constant` rows (`inspect-managed-artifact` `table_row_counts`). In `inspect-managed-members --type MixedInKey.Audio.AudioAnalyser` the 26 field records only have `name, declaring_type_token, flags, declaring_type, signature, row_offset, token`. Four have `flags & 0x8000` (`HasDefault`), for example `WMGraphNotify` (`0x04000f43`, flags 32849 = `0x8051`, `field_type: "i4"`); the value is nowhere in the result, and I found no `constant`/`default` key in output or schema. Source-derived: `Constant` appears only in `src/dotnet/ManagedMetadataLayout.ts:23` and `ManagedMetadataRowSizes.ts:28` (row sizing); `grep -ri constant src/dotnet src/domain/managed` finds no row reader or schema field, only the CIL operand kind "constant". Observed on rea 6.7.0, SHA-256 `b014a00e6f6b80ed9313f68ad3da8f42c2de38f9111582e62145cec63c7da843` (`rea inspect-managed-members <exe> --type MixedInKey.Audio.AudioAnalyser --json`, ran twice). ### Use cases Enum members, version numbers and algorithm selectors are literal fields. Without values an analyst cannot name the `4` in `ldloc.s 4; ldc.i4.4; bne.un` or map an enum to its members. ### Desired outcome and success criteria For fields and parameters with `HasDefault`, return the decoded constant (element type and value), with an explicit unknown when the blob is malformed or the type is unsupported, inside the existing representation budget. Success: `WMGraphNotify` reports its value. ### Expected interaction with targets Read existing files or captured data ### Target and scope details (optional) Read-only metadata; no execution. Adjacent but distinct: open PR #3835 (FieldRVA initial data). ### Verification available so far I have a prototype or observed results ### Verification details (optional) Observed absence on one type. Not checked: parameters (`Param` flags `HasDefault`), property constants. ### Alternatives considered An external metadata reader for the `Constant` table, which is what I would have to use today. ### Possible direction A nullable `constant` on field (and later parameter) records, parsed by the owner that already reads the row. Proposal only. ### References ECMA-335 II.22.9 (Constant), II.23.1.5 (FieldAttributes.HasDefault).

bsakaguchi commented 2026-10-31 00:37:28 +00:00

Author

Owner

Copy link

@XinwangTao commented on GitHub (Oct 19, 2026):

Exposing the Constant table in inspect-managed-members is genuinely useful: literal field defaults, enum values and parameter default values are frequently the quickest signal for what a managed API expects, and right now they are invisible even though the rows are already counted. A couple of design suggestions for the shape of the output: (1) print the default alongside its owner (field/parameter) with the ECMA-335 element type so a 0x0b (boolean) vs 0x08 (string) default is unambiguous; (2) for enum members the Constant is the underlying integral value, so annotate whether the raw value maps to a named member of the declaring enum when one exists; (3) consider a flag to suppress defaults for parameters that simply mirror C# optional-parameter nulls, since those dominate the table in real assemblies and add noise. This would fit the existing row_offset/token reporting style without changing the summary contract.

<!-- gh-comment-id:6257730822 --> @XinwangTao commented on GitHub (Oct 19, 2026): Exposing the Constant table in inspect-managed-members is genuinely useful: literal field defaults, enum values and parameter default values are frequently the quickest signal for what a managed API expects, and right now they are invisible even though the rows are already counted. A couple of design suggestions for the shape of the output: (1) print the default alongside its owner (field/parameter) with the ECMA-335 element type so a 0x0b (boolean) vs 0x08 (string) default is unambiguous; (2) for enum members the Constant is the underlying integral value, so annotate whether the raw value maps to a named member of the declaring enum when one exists; (3) consider a flag to suppress defaults for parameters that simply mirror C# optional-parameter nulls, since those dominate the table in real assemblies and add noise. This would fit the existing row_offset/token reporting style without changing the summary contract.

bsakaguchi commented 2026-10-31 00:37:28 +00:00

Author

Owner

Copy link

@ShaheryarKhan728 commented on GitHub (Oct 20, 2026):

I’d like to work on this, opening a PR shortly.

<!-- gh-comment-id:6298791573 --> @ShaheryarKhan728 commented on GitHub (Oct 20, 2026): I’d like to work on this, opening a PR shortly.

bsakaguchi commented 2026-10-31 00:37:28 +00:00

Author

Owner

Copy link

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

Good to see someone picking this up. When the PR lands, the acceptance case is WMGraphNotify (0x04000f43) reporting its decoded i4 default, so a test fixture that asserts both the element type (ECMA-335) and the value for a HasDefault field would anchor it. It would also be worth covering the two edges the issue calls out: a malformed blob should produce an explicit unknown rather than a hard failure, and enum members should show whether the underlying value maps to a named member of the declaring enum.

<!-- gh-comment-id:6305621512 --> @XinwangTao commented on GitHub (Oct 21, 2026): Good to see someone picking this up. When the PR lands, the acceptance case is WMGraphNotify (0x04000f43) reporting its decoded i4 default, so a test fixture that asserts both the element type (ECMA-335) and the value for a HasDefault field would anchor it. It would also be worth covering the two edges the issue calls out: a malformed blob should produce an explicit unknown rather than a hard failure, and enum members should show whether the underlying value maps to a named member of the declaring enum.

bsakaguchi commented 2026-10-31 00:37:28 +00:00

Author

Owner

Copy link

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

Good to see someone picking this up. When the PR lands, the acceptance case is WMGraphNotify (0x04000f43) reporting its decoded i4 default, so a test fixture that asserts both the element type (ECMA-335) and the value for a HasDefault field would anchor it. It would also be worth covering the two edges the issue calls out: a malformed blob should produce an explicit unknown rather than a hard failure, and enum members should show whether the underlying value maps to a named member of the declaring enum.

<!-- gh-comment-id:6305657663 --> @XinwangTao commented on GitHub (Oct 21, 2026): Good to see someone picking this up. When the PR lands, the acceptance case is WMGraphNotify (0x04000f43) reporting its decoded i4 default, so a test fixture that asserts both the element type (ECMA-335) and the value for a HasDefault field would anchor it. It would also be worth covering the two edges the issue calls out: a malformed blob should produce an explicit unknown rather than a hard failure, and enum members should show whether the underlying value maps to a named member of the declaring enum.

bsakaguchi commented 2026-10-31 00:37:29 +00:00

Author

Owner

Copy link

@xu91102 commented on GitHub (Oct 29, 2026):

Independent public-CLI reproduction on current main f25d1e3e9fbda7971c312caa3da757dc525a73f6 (Node 24.22.1, npm 11.16.0, macOS arm64), before implementing anything:

• A source-owned inert PE/CLI fixture declares WMGraphNotify, Field 0x04000001, HasDefault, and one Constant row. An independent ECMA-335 byte reader confirms element type 0x08 (i4), raw bytes 865d0000, value 23942.
• inspect-managed-artifact counts the Constant row. Actual inspect-managed-members … --json exits 0 and retains the field/name/type/flags, but exposes no constant value. The ordinary field control still succeeds; a missing-target control still returns target_unavailable. Input bytes are retained unchanged. This is an existing feature gap, not a claim of a regression or runtime behavior.

I plan one bounded contribution for field-owned constants, through the existing shared reader, CLI/MCP and retained field pages. It will retain source row coordinates and encoded bytes, decode supported primitive defaults losslessly, and leave missing/duplicate/malformed/unsupported declarations explicitly unavailable with coverage diagnostics. Parameter/property constants, enum-name inference, assembly loading/execution and FieldRVA data are outside this slice.

I found the earlier intent-to-work comment. Current open/closed PR searches for this issue, HasDefault and managed constant readers found no public implementation; that does not establish the absence of unpublished work. I read the related FieldRVA (#3835) and nominal CIL identity (#4516) production changes: those own different facts and will not be duplicated.

No private MixedInKey sample, CLR execution, external provider, other host runtime or performance validation has been performed. New PR author declarations will remain for human confirmation.

Current delivered revision (2026-10-30)

#8015 remains open and ready at normal fork head 008e3455e9e9ddaf7abba3f6446da92e713f2877, after integrating main 317bf3fe235e655b2d752d3be261cc0da7d00f2b for an actual conflict. The field-focused scope above is unchanged; this does not close the broader parameter/property request.

The latest CI-source reproduction had two inherited diagnostic-prose failures (2 FAIL / 17 PASS). Main's canonical typed CLI/Flutter assertions are retained, alongside both-invalid-field and no-Evidence MCP checks; corrected controls pass 28 cases on that exact CI source. Main's independently reproduced unused internal exports/constant aliases were minimally cleaned up with the original Node timer maximum and fixed debugger control allowance unchanged, without gate suppression.

Current integrated source validation: 18 focused files / 616 PASS, fresh README 9 PASS = 19 distinct files / 625 PASS / 0 skip. Full check, docs, discovery (2869 files exactly once), package verifier and pack dry-run pass. Actual compiled CLI 7 cases + installed CLI 7 cases + installed stdio MCP 1 session/6 calls verify complete/partial values, retained fields and negative controls. All 2663 product files match current/archive/install; 233 tools and 6 prompts are observed, with awaited transport/package cleanup.

Independent frozen Standards and Spec reviews both pass. A normal hook's five unrelated rewrites were blocked before push; ordinary revert and exact replay restored all reviewed source/product bytes without rewriting history. The source tested above is byte-identical to the final delivered source; those tests were not counted as another fresh run after replay.

Earlier cleanup uncertainty and external harness failures remain recorded, not relabeled as product failures or erased by later success. Current-head CI/Codex and the human author declarations are separate from local validation. Parameter/property constants, enum-name inference, private MixedInKey input, CLR execution, real external engines/agents, other host runtimes and performance remain unverified/outside this slice.

<!-- gh-comment-id:6490787903 --> @xu91102 commented on GitHub (Oct 29, 2026): Independent public-CLI reproduction on current main `f25d1e3e9fbda7971c312caa3da757dc525a73f6` (Node 24.22.1, npm 11.16.0, macOS arm64), before implementing anything: - A source-owned inert PE/CLI fixture declares `WMGraphNotify`, Field `0x04000001`, `HasDefault`, and one `Constant` row. An independent ECMA-335 byte reader confirms element type `0x08` (`i4`), raw bytes `865d0000`, value **23942**. - `inspect-managed-artifact` counts the Constant row. Actual `inspect-managed-members … --json` exits 0 and retains the field/name/type/flags, but exposes no constant value. The ordinary field control still succeeds; a missing-target control still returns `target_unavailable`. Input bytes are retained unchanged. This is an existing feature gap, not a claim of a regression or runtime behavior. I plan one bounded contribution for **field-owned constants**, through the existing shared reader, CLI/MCP and retained field pages. It will retain source row coordinates and encoded bytes, decode supported primitive defaults losslessly, and leave missing/duplicate/malformed/unsupported declarations explicitly unavailable with coverage diagnostics. Parameter/property constants, enum-name inference, assembly loading/execution and FieldRVA data are outside this slice. I found the earlier intent-to-work comment. Current open/closed PR searches for this issue, HasDefault and managed constant readers found no public implementation; that does not establish the absence of unpublished work. I read the related FieldRVA (#3835) and nominal CIL identity (#4516) production changes: those own different facts and will not be duplicated. No private MixedInKey sample, CLR execution, external provider, other host runtime or performance validation has been performed. New PR author declarations will remain for human confirmation. ### Current delivered revision (2026-10-30) [#8015](https://github.com/morluto/rea/pull/8015) remains open and ready at normal fork head `008e3455e9e9ddaf7abba3f6446da92e713f2877`, after integrating main `317bf3fe235e655b2d752d3be261cc0da7d00f2b` for an actual conflict. The field-focused scope above is unchanged; this does not close the broader parameter/property request. The latest CI-source reproduction had two inherited diagnostic-prose failures (2 FAIL / 17 PASS). Main's canonical typed CLI/Flutter assertions are retained, alongside both-invalid-field and no-Evidence MCP checks; corrected controls pass 28 cases on that exact CI source. Main's independently reproduced unused internal exports/constant aliases were minimally cleaned up with the original Node timer maximum and fixed debugger control allowance unchanged, without gate suppression. Current integrated source validation: 18 focused files / 616 PASS, fresh README 9 PASS = 19 distinct files / 625 PASS / 0 skip. Full check, docs, discovery (2869 files exactly once), package verifier and pack dry-run pass. Actual compiled CLI 7 cases + installed CLI 7 cases + installed stdio MCP 1 session/6 calls verify complete/partial values, retained fields and negative controls. All 2663 product files match current/archive/install; 233 tools and 6 prompts are observed, with awaited transport/package cleanup. Independent frozen Standards and Spec reviews both pass. A normal hook's five unrelated rewrites were blocked before push; ordinary revert and exact replay restored all reviewed source/product bytes without rewriting history. The source tested above is byte-identical to the final delivered source; those tests were not counted as another fresh run after replay. Earlier cleanup uncertainty and external harness failures remain recorded, not relabeled as product failures or erased by later success. Current-head CI/Codex and the human author declarations are separate from local validation. Parameter/property constants, enum-name inference, private MixedInKey input, CLR execution, real external engines/agents, other host runtimes and performance remain unverified/outside this slice.

bsakaguchi commented 2026-10-31 00:37:29 +00:00

Author

Owner

Copy link

@XinwangTao commented on GitHub (Oct 29, 2026):

Thanks for the independent reproduction and for keeping the contribution bounded. The "retain row coordinates/raw bytes, decode supported primitives losslessly, explicitly unavailable for malformed/duplicate/unsupported" split matches the acceptance criteria in the issue. One suggestion: in the coverage diagnostics, distinguish "no Constant row for this parent" from "row present but decode failed" — that keeps the malformed-blob edge testable instead of collapsing both into a single unavailable state. Agreed that parameter/property constants and enum-name inference can wait for a follow-up.

<!-- gh-comment-id:6491340812 --> @XinwangTao commented on GitHub (Oct 29, 2026): Thanks for the independent reproduction and for keeping the contribution bounded. The "retain row coordinates/raw bytes, decode supported primitives losslessly, explicitly unavailable for malformed/duplicate/unsupported" split matches the acceptance criteria in the issue. One suggestion: in the coverage diagnostics, distinguish "no Constant row for this parent" from "row present but decode failed" — that keeps the malformed-blob edge testable instead of collapsing both into a single unavailable state. Agreed that parameter/property constants and enum-name inference can wait for a follow-up.

bsakaguchi referenced this issue 2026-10-31 00:44:58 +00:00

[GH-ISSUE #6484] [Bug] stop counting changed PyInstaller member types as unchanged #3890

Sign in to join this conversation.

No Branch/Tag specified

Branches Tags

main

codex/procedure-reference-stacked

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

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

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#3171

No description provided.