morluto/rea

Fork

You've already forked rea

mirror of https://github.com/morluto/rea.git synced 2026-11-05 06:45:22 +00:00

Code Issues 1.3k Projects Packages Wiki Activity

[PR #6984] [MERGED] fix(cli): exclude inherited values from Markdown rows #7546

New issue

Closed

opened 2026-11-03 13:38:36 +00:00 by bsakaguchi · 0 comments

bsakaguchi commented

2026-11-03 13:38:36 +00:00

Owner

Copy link

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/6984
Author: @ShuaixinHuang
Created: 10/24/2026
Status: ✅ Merged
Merged: 10/24/2026
Merged by: @morluto

Base: main ← Head: codex/fix-cli-table-owned-fields

📝 Commits (7)

449905b fix(cli): exclude inherited values from Markdown rows
9cf6f3b Merge commit 'dd02d8ff69' into codex/fix-cli-table-owned-fields
cdd41de Merge commit '9895f1870c' into codex/fix-cli-table-owned-fields
d042e4a Merge commit 'be2811e414' into codex/fix-cli-table-owned-fields
4b251c2 test(verifiers): follow shared command output and identity
a4efa3c Merge shared verifier CI test repair
cba2f9f test(ci): synchronize upstream verifier assertion repair

📊 Changes

2 files changed (+44 additions, -3 deletions)

View changed files

📝 src/cli/cliOutputFormatter.ts (+5 -1)
📝 tests/boundary/cli/filteredArrayOutput.test.ts (+39 -2)

📄 Description

Summary

Keep absent fields blank in heterogeneous Markdown object tables instead of printing inherited JavaScript functions or prototype objects.

Problem and expected behavior

For [ {"constructor":"ctor","toString":"text","__proto__":"proto"}, {} ], the column union correctly includes the first record's own keys, but reading the second record with item[key] invents values such as function Object() { [native code] } and {}. A missing own field must remain absent; explicitly supplied values, including 0, false, and null, must remain visible.

Change and scope

Read table cells through an own-property check in the existing formatter, matching the Object.keys rule that creates the columns. Add a regression through registered CLI command dispatch and the production result writer. No separate issue: this PR contains the reproducer and fix.

Follow the contribution scope. This is an ordinary output correctness fix; a separate maintainer scope decision is not applicable.

Contract and boundary impact

Semantic owner and earliest changed stage: cliOutputFormatter.formatObjectTable, when projecting a record into Markdown cells.
Contribution scope fit and linked maintainer decision: existing CLI formatting; not applicable.
CLI and MCP/tool-catalog contract: CLI Markdown missing cells become blank; JSON values and tool schemas are unchanged.
Provider, bridge, target-format, or platform compatibility: JavaScript own-property semantics; no provider protocol change.
Evidence, artifact, provenance, or reconstruction contract: avoid reporting inherited values as supplied analysis facts; preserve source records.
Target selection, authority, upstream behavior, and cleanup details (if applicable): not applicable; formatter only.
Generated metadata (docs/public/product-catalog.json), package, or installation impact (CI generates and validates ignored catalogs and skills/; edit authored instructions in .agents/skills/reverse-engineer-anything/ and never commit build outputs): none; no schema/package change.

Expected effects (check known effects; use documentation-only on its own).
Unchecked items do not establish absence; leave uncertainties visible.

Read existing files or captured data.
Launch or attach to a process.
Inject instrumentation or run scripts/code.
Change process memory, registers, files, or configuration.
Contact network services.
Recover protected code or work around protections.
Documentation or usability only; no target interaction.
Not sure yet; investigation or maintainer guidance needed.

Evidence and regression coverage

Tests added or updated: existing filteredArrayOutput.test.ts now covers heterogeneous records through real command registration, Markdown output, and exact JSON preservation; the input is recursively frozen.
Base reproduction or other evidence: the new test failed on c350343c because the absent row contained inherited Object/toString functions and {}; it passes with the own-property check.
User-visible CLI/MCP output (if applicable): a record with only name: "second" now yields | second | | | | | |, while explicitly supplied 0, false, and null retain those spellings.
Remaining proof gaps: local execution used Windows and Node 24.22.1; Linux/macOS execution and the complete suite remain CI coverage. No external analysis engine was required or exercised.

For evidence-bearing changes:

Observed, derived, and inferred claims remain distinguishable.
Artifact identity, source provenance, and failed attempts remain preserved.
Unsupported, incomplete, unavailable, or uncertain outcomes remain visible.

Validation performed

New selected regression before the fix — 1 failed for inherited values, 27 deselected.
npm run test:focused -- tests/boundary/cli/cliOutput.test.ts tests/boundary/cli/evidenceBundleCommands.test.ts tests/boundary/cli/filteredArrayOutput.test.ts tests/boundary/cli/markdownNestedFacts.test.ts — 4 files, 103 tests passed.
npm run check — 6 tasks passed; resolved module boundaries and architecture guards passed. Lint reported warnings and zero errors.
git diff --check — passed; normal pre-commit formatting/lint passed.

Compatibility, safety, and release

Breaking changes or migration steps: none; only absent cells stop displaying inherited values.
Real Hopper/Ghidra, browser, or OS coverage: Windows CLI boundary tests; no Hopper/Ghidra/browser execution.
Package or release metadata impact: none.
Security, privacy, process, or containment review: no added execution, network request, file mutation, or target access; this is an in-memory output projection.

Author readiness

Human owner: @ShuaixinHuang

I reviewed the final diff and relevant existing code, understand the change and its edge cases, and take responsibility for the complete PR, including AI-assisted work.
I checked the evidence above, confirmed it supports the current change, and recorded meaningful validation gaps.
I declare this PR ready for initial maintainer review.

The human owner instructed the assistant in this session to prepare all three changes and submit them directly for review; this PR is AI-assisted.

Before merge

This PR addresses a concrete problem or an agreed enhancement.
Material scope and authority questions are resolved, and any required maintainer scope decision covers the final diff.
The PR has one focused outcome and the title follows type(scope): outcome.
Related issue is linked, or the reason for not linking one is stated above.
Tests cover changed observable behavior and meaningful failure paths.
Owning docs, contracts, and generated metadata are updated where needed.
User-visible CLI/MCP changes include representative output.
I checked the final diff for secrets, unrelated cleanup, and unsupported claims.

Synchronization validation (2026-10-24)

Synchronized reviewed upstream 347b6e4d95 (#7002), which includes the earlier #6986, #6988 and #6994 repairs. Current head: cba2f9fdab. The complete feature patch is byte-for-byte identical to this PR's pre-repair feature patch and remains 2 files against that upstream revision; no verifier-test changes remain in the PR diff.

The preceding head's shard 6 had 13 failed / 1889 passed / 20 skipped from two shared test-contract mismatches. Those are historical results. A user-authorized local support patch 4b251c25 migrated the error diagnostics and run ID checks, then upstream merged #7002 concurrently. The resulting conflict was resolved by taking both upstream test files exactly. The Python cases now check VerifierCommandExitError, exit code 1 and snapshot.stderr.text. The ownership cases compare leader/descendant identities to the actual launcher-assigned nonce and distinguish the inherited identity. Archive rejection, ambient-import isolation, no extraction, process-exit-before-root-cleanup and cleanup-retry checks remain.

Clean-base comparison before the upstream merge (Windows, pinned Node 24.22.1/npm 11.16.0, Python 3.12.14, native Windows addon present): the exact focused two-file command for packedBridgeVerification.test.ts and packagedWasmVerifierOwnership.test.ts failed 10 / passed 14 / skipped 3 on be2811e414, then passed 24 / skipped 3 after the local migration. A controlled temporary bypass of ast.parse made the existing invalid-Python regression fail as intended (1 failed / 23 deselected); production bytes were restored. These are local repair evidence, not the final upstream-combination result.

On the final integrated ELF branch, npm run test:focused -- tests/boundary/process/packedBridgeVerification.test.ts tests/boundary/process/packagedWasmVerifierOwnership.test.ts tests/boundary/filesystem/verifierCommandOutput.test.ts tests/boundary/process/nativeVerifierPreflightOwnership.test.ts passed 29 / skipped 14 (four files). All 24 packed-Python cases and five command-output cases passed. Existing Windows skips cover three packaged-Wasm lifecycle cases, eight native-client preflight cases and three filesystem failure cases. No new skip was introduced; Linux CI must execute the POSIX coverage. This run does not establish real external-client/provider behavior.

Each final integrated branch passed npm run check (six tasks, module boundaries and architecture guards) and git diff --check; normal commit and push hooks passed. No CI gates, timeouts or skips were weakened. Upstream #7002's own green CI does not establish this PR's new-head result. Latest-head confirmation on 2026-10-24: CI required, Conventional PR title and PR readiness all succeeded for cba2f9fdab. Source tests and all eight test shards succeeded. Optional lanes retain their reported skips; the historical local Windows limits remain disclosed.

Earlier post-sync feature/shared validation passed 222 tests across six CLI and shared-regression files. After the earlier be2811 merge, the two import/type-erasure source files passed all 36 tests on this branch.

Earlier checks also passed all 113 reference-lifetime cases, six property-path regressions, and nine evaluation-gate tests. The former cyclic-path single case passed with the same 512 MiB heap / external 20 s guard (137 ms test time, 3.76 s elapsed); the baseline exhausted the heap. No completed-baseline speedup or process-family RSS claim is made.

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/morluto/rea/pull/6984 **Author:** [@ShuaixinHuang](https://github.com/ShuaixinHuang) **Created:** 10/24/2026 **Status:** ✅ Merged **Merged:** 10/24/2026 **Merged by:** [@morluto](https://github.com/morluto) **Base:** `main` ← **Head:** `codex/fix-cli-table-owned-fields` --- ### 📝 Commits (7) - [`449905b`](https://github.com/morluto/rea/commit/449905b9d4858fd3e79a7a1b6013e0fbffce3a5b) fix(cli): exclude inherited values from Markdown rows - [`9cf6f3b`](https://github.com/morluto/rea/commit/9cf6f3be55d933155bdedceb67b550f990212789) Merge commit 'dd02d8ff696385949b05459f2ab9b6ffda18a52c' into codex/fix-cli-table-owned-fields - [`cdd41de`](https://github.com/morluto/rea/commit/cdd41dea991c41f34322f8b662469723451c0556) Merge commit '9895f1870c5537e64f08e9ff145a0917696b7a50' into codex/fix-cli-table-owned-fields - [`d042e4a`](https://github.com/morluto/rea/commit/d042e4a39624da55eb165badbbc2b6b09226daf0) Merge commit 'be2811e41407f0149b3e8e12cb2bf0ffd5904b2d' into codex/fix-cli-table-owned-fields - [`4b251c2`](https://github.com/morluto/rea/commit/4b251c25d75e1bc400e730ee54d7f4acd2d2504b) test(verifiers): follow shared command output and identity - [`a4efa3c`](https://github.com/morluto/rea/commit/a4efa3ca2ec74a96b10c7f12e1c6455afab4e125) Merge shared verifier CI test repair - [`cba2f9f`](https://github.com/morluto/rea/commit/cba2f9fdabde7786ec1d6c26216b44f7ccddfbf5) test(ci): synchronize upstream verifier assertion repair ### 📊 Changes **2 files changed** (+44 additions, -3 deletions) <details> <summary>View changed files</summary> 📝 `src/cli/cliOutputFormatter.ts` (+5 -1) 📝 `tests/boundary/cli/filteredArrayOutput.test.ts` (+39 -2) </details> ### 📄 Description ## Summary Keep absent fields blank in heterogeneous Markdown object tables instead of printing inherited JavaScript functions or prototype objects. ## Problem and expected behavior For `[ {"constructor":"ctor","toString":"text","__proto__":"proto"}, {} ]`, the column union correctly includes the first record's own keys, but reading the second record with `item[key]` invents values such as `function Object() { [native code] }` and `{}`. A missing own field must remain absent; explicitly supplied values, including `0`, `false`, and `null`, must remain visible. ## Change and scope Read table cells through an own-property check in the existing formatter, matching the `Object.keys` rule that creates the columns. Add a regression through registered CLI command dispatch and the production result writer. No separate issue: this PR contains the reproducer and fix. Follow the [contribution scope](https://github.com/morluto/rea/blob/main/CONTRIBUTING.md#contribution-scope). This is an ordinary output correctness fix; a separate maintainer scope decision is not applicable. ## Contract and boundary impact - Semantic owner and earliest changed stage: `cliOutputFormatter.formatObjectTable`, when projecting a record into Markdown cells. - Contribution scope fit and linked maintainer decision: existing CLI formatting; not applicable. - CLI and MCP/tool-catalog contract: CLI Markdown missing cells become blank; JSON values and tool schemas are unchanged. - Provider, bridge, target-format, or platform compatibility: JavaScript own-property semantics; no provider protocol change. - Evidence, artifact, provenance, or reconstruction contract: avoid reporting inherited values as supplied analysis facts; preserve source records. - Target selection, authority, upstream behavior, and cleanup details (if applicable): not applicable; formatter only. - Generated metadata (`docs/public/product-catalog.json`), package, or installation impact (CI generates and validates ignored catalogs and `skills/`; edit authored instructions in `.agents/skills/reverse-engineer-anything/` and never commit build outputs): none; no schema/package change. Expected effects (check known effects; use documentation-only on its own). Unchecked items do not establish absence; leave uncertainties visible. - [x] Read existing files or captured data. - [ ] Launch or attach to a process. - [ ] Inject instrumentation or run scripts/code. - [ ] Change process memory, registers, files, or configuration. - [ ] Contact network services. - [ ] Recover protected code or work around protections. - [ ] Documentation or usability only; no target interaction. - [ ] Not sure yet; investigation or maintainer guidance needed. ## Evidence and regression coverage - Tests added or updated: existing `filteredArrayOutput.test.ts` now covers heterogeneous records through real command registration, Markdown output, and exact JSON preservation; the input is recursively frozen. - Base reproduction or other evidence: the new test failed on `c350343c` because the absent row contained inherited `Object`/`toString` functions and `{}`; it passes with the own-property check. - User-visible CLI/MCP output (if applicable): a record with only `name: "second"` now yields `| second | | | | | |`, while explicitly supplied `0`, `false`, and `null` retain those spellings. - Remaining proof gaps: local execution used Windows and Node 24.22.1; Linux/macOS execution and the complete suite remain CI coverage. No external analysis engine was required or exercised. For evidence-bearing changes: - [x] Observed, derived, and inferred claims remain distinguishable. - [x] Artifact identity, source provenance, and failed attempts remain preserved. - [x] Unsupported, incomplete, unavailable, or uncertain outcomes remain visible. ## Validation performed - New selected regression before the fix — 1 failed for inherited values, 27 deselected. - `npm run test:focused -- tests/boundary/cli/cliOutput.test.ts tests/boundary/cli/evidenceBundleCommands.test.ts tests/boundary/cli/filteredArrayOutput.test.ts tests/boundary/cli/markdownNestedFacts.test.ts` — 4 files, 103 tests passed. - `npm run check` — 6 tasks passed; resolved module boundaries and architecture guards passed. Lint reported warnings and zero errors. - `git diff --check` — passed; normal pre-commit formatting/lint passed. ## Compatibility, safety, and release - Breaking changes or migration steps: none; only absent cells stop displaying inherited values. - Real Hopper/Ghidra, browser, or OS coverage: Windows CLI boundary tests; no Hopper/Ghidra/browser execution. - Package or release metadata impact: none. - Security, privacy, process, or containment review: no added execution, network request, file mutation, or target access; this is an in-memory output projection. ## Author readiness Human owner: @ShuaixinHuang - [x] I reviewed the final diff and relevant existing code, understand the change and its edge cases, and take responsibility for the complete PR, including AI-assisted work. - [x] I checked the evidence above, confirmed it supports the current change, and recorded meaningful validation gaps. - [x] I declare this PR ready for initial maintainer review. The human owner instructed the assistant in this session to prepare all three changes and submit them directly for review; this PR is AI-assisted. ## Before merge - [x] This PR addresses a concrete problem or an agreed enhancement. - [x] Material scope and authority questions are resolved, and any required maintainer scope decision covers the final diff. - [x] The PR has one focused outcome and the title follows `type(scope): outcome`. - [x] Related issue is linked, or the reason for not linking one is stated above. - [x] Tests cover changed observable behavior and meaningful failure paths. - [x] Owning docs, contracts, and generated metadata are updated where needed. - [x] User-visible CLI/MCP changes include representative output. - [x] I checked the final diff for secrets, unrelated cleanup, and unsupported claims. ## Synchronization validation (2026-10-24) Synchronized reviewed upstream 347b6e4d95 (#7002), which includes the earlier #6986, #6988 and #6994 repairs. Current head: cba2f9fdabde7786ec1d6c26216b44f7ccddfbf5. The complete feature patch is byte-for-byte identical to this PR's pre-repair feature patch and remains 2 files against that upstream revision; no verifier-test changes remain in the PR diff. The preceding head's shard 6 had 13 failed / 1889 passed / 20 skipped from two shared test-contract mismatches. Those are historical results. A user-authorized local support patch 4b251c25 migrated the error diagnostics and run ID checks, then upstream merged #7002 concurrently. The resulting conflict was resolved by taking both upstream test files exactly. The Python cases now check VerifierCommandExitError, exit code 1 and snapshot.stderr.text. The ownership cases compare leader/descendant identities to the actual launcher-assigned nonce and distinguish the inherited identity. Archive rejection, ambient-import isolation, no extraction, process-exit-before-root-cleanup and cleanup-retry checks remain. Clean-base comparison before the upstream merge (Windows, pinned Node 24.22.1/npm 11.16.0, Python 3.12.14, native Windows addon present): the exact focused two-file command for packedBridgeVerification.test.ts and packagedWasmVerifierOwnership.test.ts failed 10 / passed 14 / skipped 3 on be2811e414, then passed 24 / skipped 3 after the local migration. A controlled temporary bypass of ast.parse made the existing invalid-Python regression fail as intended (1 failed / 23 deselected); production bytes were restored. These are local repair evidence, not the final upstream-combination result. On the final integrated ELF branch, npm run test:focused -- tests/boundary/process/packedBridgeVerification.test.ts tests/boundary/process/packagedWasmVerifierOwnership.test.ts tests/boundary/filesystem/verifierCommandOutput.test.ts tests/boundary/process/nativeVerifierPreflightOwnership.test.ts passed 29 / skipped 14 (four files). All 24 packed-Python cases and five command-output cases passed. Existing Windows skips cover three packaged-Wasm lifecycle cases, eight native-client preflight cases and three filesystem failure cases. No new skip was introduced; Linux CI must execute the POSIX coverage. This run does not establish real external-client/provider behavior. Each final integrated branch passed npm run check (six tasks, module boundaries and architecture guards) and git diff --check; normal commit and push hooks passed. No CI gates, timeouts or skips were weakened. Upstream #7002's own green CI does not establish this PR's new-head result. Latest-head confirmation on 2026-10-24: [CI required](https://github.com/morluto/rea/actions/runs/40096655867/job/120883628042), Conventional PR title and PR readiness all succeeded for cba2f9fdabde7786ec1d6c26216b44f7ccddfbf5. Source tests and all eight test shards succeeded. Optional lanes retain their reported skips; the historical local Windows limits remain disclosed. Earlier post-sync feature/shared validation passed 222 tests across six CLI and shared-regression files. After the earlier be2811 merge, the two import/type-erasure source files passed all 36 tests on this branch. Earlier checks also passed all 113 reference-lifetime cases, six property-path regressions, and nine evaluation-gate tests. The former cyclic-path single case passed with the same 512 MiB heap / external 20 s guard (137 ms test time, 3.76 s elapsed); the baseline exhausted the heap. No completed-baseline speedup or process-family RSS claim is made. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

bsakaguchi

2026-11-03 13:38:36 +00:00

closed this issue
added the
pull-request
label

No Branch/Tag specified

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

Mirrored from GitHub Pull Request

No labels

Milestone

Clear milestone

No items

No milestone

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

1 participant

Notifications

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

Reference in a new issue

Repository

morluto/rea

Title

Body

No description provided.

Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?

Rows
Columns