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 #5647] [MERGED] fix(doctor): reject unusable Kuna caches and invalid native settings #7010

New issue

Closed

opened 2026-11-01 21:44:41 +00:00 by bsakaguchi · 0 comments

bsakaguchi commented

2026-11-01 21:44:41 +00:00

Owner

Copy link

📋 Pull Request Information

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

Base: main ← Head: cursor/doctor-readiness-4f30

📝 Commits (8)

8129597 fix(kuna): reject dangling cache roots in doctor
0ca5bc2 fix(doctor): admit the same settings native analysis rejects
40e7f8c fix(doctor): report an invalid log level from doctor
3e4c2b2 fix(doctor): require log-level failures in every scope
e7a2434 fix(kuna): strip only the platform cache separator
f2b3cd3 fix(doctor): fail every provider on an invalid Hopper timeout
2ed26ac style(doctor): format the Hopper timeout regression
504ccbb fix(doctor): fail client scopes on MCP startup errors

📊 Changes

15 files changed (+719 additions, -38 deletions)

View changed files

📝 docs/installation.md (+7 -0)
📝 scripts/rea.mjs (+24 -1)
📝 src/application/Doctor.test.ts (+268 -1)
📝 src/application/Doctor.ts (+12 -0)
📝 src/application/DoctorDiagnostics.ts (+39 -0)
📝 src/application/DoctorScope.ts (+27 -0)
📝 src/cli.ts (+6 -2)
📝 src/config.test.ts (+23 -0)
📝 src/config/parseConfig.ts (+25 -6)
📝 src/kuna/KunaDoctor.ts (+57 -14)
📝 src/logger.ts (+12 -0)
📝 tests/boundary/cli/cliLogLevelConfiguration.test.ts (+50 -11)
📝 tests/boundary/cli/doctorHopperDiscovery.test.ts (+69 -0)
📝 tests/boundary/providers/kuna/kunaDoctor.test.ts (+95 -2)
📝 tests/boundary/providers/kuna/kunaSetupReadiness.test.ts (+5 -1)

📄 Description

Summary

Fixes #5454, #5554, and #5105.

Scoped rea doctor could report a selected engine healthy when shared native configuration was invalid, and Kuna doctor could report a dangling cache root as creatable and available. Readiness now uses the same environment admission as native commands, and a cache path is creatable only when no directory entry occupies its name.

Problem and expected behavior

rea doctor --provider hopper stayed successful for REA_ANALYSIS_PROVIDER=Hopper and REA_GHIDRA_STARTUP_TIMEOUT_MS=abc, while analyze and search-bytes failed with configuration_invalid. rea doctor --provider ghidra could likewise succeed with REA_HOPPER_STARTUP_TIMEOUT_MS=abc, because that setting had its own check and the check was required only for Hopper. A Kuna cache root that is a dangling symlink, including one written with a trailing separator, was reported ready because stat follows the link and ENOENT was treated as absence. Setup's ready-provider list already required passing checks, but the inspection still published available: true.

An invalid REA_LOG_LEVEL was rejected in the executable dispatcher before doctor ran, so the readiness check never reached rea doctor --json. After that path reached doctor, a client-only or skill scope could still report healthy because the failure was included only when a provider was selected. That client cannot start REA: the dispatcher rejects every other command, and MCP startup rejects the same setting.

Doctor should fail the selected engine and name the rejected setting. An invalid REA_LOG_LEVEL should also fail client and skill scopes. Every other parseConfig failure, including REA_GHIDRA_STARTUP_TIMEOUT_MS and REA_HOPPER_STARTUP_TIMEOUT_MS, should fail a selected client because MCP startup rejects it. A skill-only scope leaves those other settings informational. An invalid REA_HOPPER_STARTUP_TIMEOUT_MS should fail every selected provider. A dangling cache link should fail the cache check, clear availability, and leave the installation check and caller-selected registration settings in place. A resolving link and a missing path under a writable parent stay ready. On Darwin and Linux, a trailing \ is part of the configured cache path. REA_JEB_MCP_TIMEOUT_MS remains outside native admission. Commands other than doctor still stop before execution when the log level is invalid.

Change and scope

parseConfig and doctor share nativeAnalysisConfigurationError. Rejected settings become runtime-configuration:<setting> checks. They fail the full audit. An explicit provider scope includes every rejected native setting. REA_LOG_LEVEL also fails client and skill scopes. A selected client includes every other native admission failure, because MCP startup rejects it. A skill-only scope leaves those other settings informational. REA_HOPPER_STARTUP_TIMEOUT_MS keeps its existing hopper-startup-timeout check, and that check is required for every selected provider.

The dispatcher lets doctor continue after an invalid REA_LOG_LEVEL so that check is in the public JSON report. Every other command keeps the existing stderr rejection.

Kuna cache inspection strips the selected platform's terminal separator before lstat, so a dangling link is not mistaken for a missing path. On Darwin and Linux that separator is /. available follows the cache check.

Contribution scope: ordinary readiness fixes inside existing doctor and Kuna cache diagnosis. No new provider, target execution, injection, mutation, or protection recovery. Maintainer scope decision: not applicable.

Already fixed on main and not included: #5561, #5559, and #5604 (dd0015aaf); #5568 (7b2087e44).

Contract and boundary impact

Semantic owner and earliest changed stage: parseConfig owns native environment admission; PROCESS_START_CONFIGURATION_SETTINGS owns which of those settings block process start; the executable dispatcher owns the log-level exception for doctor; KunaDoctor owns cache-root classification. Earliest stage is setup or provider admission, before a provider session.
Contribution scope fit and linked maintainer decision: bugfix within existing doctor and Kuna readiness. Not applicable.
CLI and MCP/tool-catalog contract: rea doctor JSON gains runtime-configuration:<setting> checks when native admission fails, including an invalid REA_LOG_LEVEL. That log-level check is required in every explicit scope. A selected client also requires every other native admission failure and hopper-startup-timeout. hopper-startup-timeout remains required for every selected provider. Exit status follows healthy. Other commands keep the plain stderr rejection for an invalid log level. No new command or tool.
Provider, bridge, target-format, or platform compatibility: Kuna cache diagnosis changes for dangling links, trailing platform separators, and POSIX paths that end in \. Other providers are unchanged. No engine protocol change.
Evidence, artifact, provenance, or reconstruction contract: none.
Target selection, authority, upstream behavior, and cleanup details: doctor remains read-only. It does not create the cache or repair the link.
Generated metadata (docs/public/product-catalog.json), package, or installation impact: docs/installation.md states that an invalid REA_LOG_LEVEL fails every doctor scope, and that other MCP startup failures fail a selected client and every selected provider. CI generates and validates ignored catalogs and skills/.

Expected effects (check known effects; use documentation-only on its own).

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: src/application/Doctor.test.ts, src/config.test.ts, tests/boundary/cli/doctorHopperDiscovery.test.ts, tests/boundary/cli/cliLogLevelConfiguration.test.ts, tests/boundary/providers/kuna/kunaDoctor.test.ts, tests/boundary/providers/kuna/kunaSetupReadiness.test.ts.
Base reproduction or other evidence: source inspection of stat/ENOENT, of doctor versus parseConfig, of scripts/rea.mjs exiting before doctor when REA_LOG_LEVEL is invalid, of the scope partition that omitted process-start failures when no provider was selected, and of hopper-startup-timeout being required only when Hopper itself was selected. The historical CLI timings in #5454 and #5554 were not re-run on a real Hopper or Kuna engine.
User-visible CLI/MCP output: focused CLI doctor with REA_ANALYSIS_PROVIDER=Hopper and REA_GHIDRA_STARTUP_TIMEOUT_MS=abc exited 1 and included both runtime-configuration checks in scope_checks. REA_JEB_MCP_TIMEOUT_MS=abc added no such check. rea --json doctor --provider hopper and rea --json doctor --client codex with REA_LOG_LEVEL=loud and INFO exited 1 with an empty stderr and runtime-configuration:REA_LOG_LEVEL in scope_checks. rea --json doctor --client codex with REA_GHIDRA_STARTUP_TIMEOUT_MS=abc exited 1 and included that check in scope_checks with providers: []. rea --help with an invalid log level still prints the stderr configuration error and no stdout.
Remaining proof gaps: no real Hopper, Ghidra, IDA, or Kuna engine. Windows cache links were not run (kunaDoctor tests skip win32). The non-Hopper timeout regression uses a scripted Ghidra inspection.
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

npm run test:local -- src/application/Doctor.test.ts src/config.test.ts src/application/Doctor.lifecycle.test.ts — 129 passed.
npm run test:focused -- tests/boundary/providers/kuna/kunaDoctor.test.ts tests/boundary/providers/kuna/kunaSetupReadiness.test.ts tests/boundary/cli/doctorHopperDiscovery.test.ts — 16 passed.
npm run test:focused -- tests/boundary/cli/cliLogLevelConfiguration.test.ts tests/boundary/cli/dispatcher.test.ts tests/boundary/cli/doctorHopperDiscovery.test.ts — 8 passed.
npm run test:focused -- src/application/Doctor.test.ts tests/boundary/cli/cliLogLevelConfiguration.test.ts tests/boundary/providers/kuna/kunaDoctor.test.ts — 72 passed.
npm run test:focused -- src/application/Doctor.test.ts tests/boundary/cli/doctorHopperDiscovery.test.ts — 64 passed on df9a78014.
npm run test:local -- src/ida/IdaOperationFailures.test.ts — 33 passed on 91dc38c64.
npm run check:fast — passed on df9a78014.
npx oxfmt --check . — passed on df9a78014.
npx tsc --noEmit — passed on an earlier revision; check:fast typechecked this revision.

Compatibility, safety, and release

Breaking changes or migration steps: rea doctor with an invalid REA_LOG_LEVEL now returns the doctor report instead of the dispatcher's stderr line, and that failure makes client and skill scopes unhealthy. A selected client is also unhealthy for every other setting MCP startup rejects. An invalid REA_HOPPER_STARTUP_TIMEOUT_MS fails every selected provider and a selected client. Other commands are unchanged. Callers who treated a dangling Kuna cache, a POSIX cache path ending in \, or an invalid native setting as healthy now get a failing doctor result.
Real Hopper/Ghidra, browser, or OS coverage: not run. Linux scripted CLI and filesystem fixtures only.
Package or release metadata impact: none.
Security, privacy, process, or containment review: read-only diagnosis. No new process launch. Rejected setting values are not copied into the check detail; the parser constraint is.

Author readiness

Human owner: @morluto

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.

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.

_{🔄 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/5647 **Author:** [@morluto](https://github.com/morluto) **Created:** 10/20/2026 **Status:** ✅ Merged **Merged:** 10/20/2026 **Merged by:** [@morluto](https://github.com/morluto) **Base:** `main` ← **Head:** `cursor/doctor-readiness-4f30` --- ### 📝 Commits (8) - [`8129597`](https://github.com/morluto/rea/commit/8129597b9f92d0b84579373071abc4771e60d398) fix(kuna): reject dangling cache roots in doctor - [`0ca5bc2`](https://github.com/morluto/rea/commit/0ca5bc29d4813a7f471c49925b3cc2cb46f1739c) fix(doctor): admit the same settings native analysis rejects - [`40e7f8c`](https://github.com/morluto/rea/commit/40e7f8c2a8f24e7df25fc8698862bfe62d2d3060) fix(doctor): report an invalid log level from doctor - [`3e4c2b2`](https://github.com/morluto/rea/commit/3e4c2b2321ba1171aefc39fa873c982635eb2e5a) fix(doctor): require log-level failures in every scope - [`e7a2434`](https://github.com/morluto/rea/commit/e7a2434c27dda1673130dcd151036e7a2a8f74da) fix(kuna): strip only the platform cache separator - [`f2b3cd3`](https://github.com/morluto/rea/commit/f2b3cd3bc0cda57ef108af425000333ce2ef20e6) fix(doctor): fail every provider on an invalid Hopper timeout - [`2ed26ac`](https://github.com/morluto/rea/commit/2ed26ac4a881519ff664af3c2e8102b4855e56a7) style(doctor): format the Hopper timeout regression - [`504ccbb`](https://github.com/morluto/rea/commit/504ccbb13d317b516f071ac837ade98034fbb9f3) fix(doctor): fail client scopes on MCP startup errors ### 📊 Changes **15 files changed** (+719 additions, -38 deletions) <details> <summary>View changed files</summary> 📝 `docs/installation.md` (+7 -0) 📝 `scripts/rea.mjs` (+24 -1) 📝 `src/application/Doctor.test.ts` (+268 -1) 📝 `src/application/Doctor.ts` (+12 -0) 📝 `src/application/DoctorDiagnostics.ts` (+39 -0) 📝 `src/application/DoctorScope.ts` (+27 -0) 📝 `src/cli.ts` (+6 -2) 📝 `src/config.test.ts` (+23 -0) 📝 `src/config/parseConfig.ts` (+25 -6) 📝 `src/kuna/KunaDoctor.ts` (+57 -14) 📝 `src/logger.ts` (+12 -0) 📝 `tests/boundary/cli/cliLogLevelConfiguration.test.ts` (+50 -11) 📝 `tests/boundary/cli/doctorHopperDiscovery.test.ts` (+69 -0) 📝 `tests/boundary/providers/kuna/kunaDoctor.test.ts` (+95 -2) 📝 `tests/boundary/providers/kuna/kunaSetupReadiness.test.ts` (+5 -1) </details> ### 📄 Description  ## Summary Fixes #5454, #5554, and #5105. Scoped `rea doctor` could report a selected engine healthy when shared native configuration was invalid, and Kuna doctor could report a dangling cache root as creatable and available. Readiness now uses the same environment admission as native commands, and a cache path is creatable only when no directory entry occupies its name. ## Problem and expected behavior `rea doctor --provider hopper` stayed successful for `REA_ANALYSIS_PROVIDER=Hopper` and `REA_GHIDRA_STARTUP_TIMEOUT_MS=abc`, while `analyze` and `search-bytes` failed with `configuration_invalid`. `rea doctor --provider ghidra` could likewise succeed with `REA_HOPPER_STARTUP_TIMEOUT_MS=abc`, because that setting had its own check and the check was required only for Hopper. A Kuna cache root that is a dangling symlink, including one written with a trailing separator, was reported ready because `stat` follows the link and `ENOENT` was treated as absence. Setup's ready-provider list already required passing checks, but the inspection still published `available: true`. An invalid `REA_LOG_LEVEL` was rejected in the executable dispatcher before doctor ran, so the readiness check never reached `rea doctor --json`. After that path reached doctor, a client-only or skill scope could still report healthy because the failure was included only when a provider was selected. That client cannot start REA: the dispatcher rejects every other command, and MCP startup rejects the same setting. Doctor should fail the selected engine and name the rejected setting. An invalid `REA_LOG_LEVEL` should also fail client and skill scopes. Every other `parseConfig` failure, including `REA_GHIDRA_STARTUP_TIMEOUT_MS` and `REA_HOPPER_STARTUP_TIMEOUT_MS`, should fail a selected client because MCP startup rejects it. A skill-only scope leaves those other settings informational. An invalid `REA_HOPPER_STARTUP_TIMEOUT_MS` should fail every selected provider. A dangling cache link should fail the cache check, clear availability, and leave the installation check and caller-selected registration settings in place. A resolving link and a missing path under a writable parent stay ready. On Darwin and Linux, a trailing `\` is part of the configured cache path. `REA_JEB_MCP_TIMEOUT_MS` remains outside native admission. Commands other than doctor still stop before execution when the log level is invalid. ## Change and scope `parseConfig` and doctor share `nativeAnalysisConfigurationError`. Rejected settings become `runtime-configuration:<setting>` checks. They fail the full audit. An explicit provider scope includes every rejected native setting. `REA_LOG_LEVEL` also fails client and skill scopes. A selected client includes every other native admission failure, because MCP startup rejects it. A skill-only scope leaves those other settings informational. `REA_HOPPER_STARTUP_TIMEOUT_MS` keeps its existing `hopper-startup-timeout` check, and that check is required for every selected provider. The dispatcher lets `doctor` continue after an invalid `REA_LOG_LEVEL` so that check is in the public JSON report. Every other command keeps the existing stderr rejection. Kuna cache inspection strips the selected platform's terminal separator before `lstat`, so a dangling link is not mistaken for a missing path. On Darwin and Linux that separator is `/`. `available` follows the cache check. Contribution scope: ordinary readiness fixes inside existing doctor and Kuna cache diagnosis. No new provider, target execution, injection, mutation, or protection recovery. Maintainer scope decision: not applicable. Already fixed on main and not included: #5561, #5559, and #5604 (`dd0015aaf`); #5568 (`7b2087e44`). ## Contract and boundary impact - Semantic owner and earliest changed stage: `parseConfig` owns native environment admission; `PROCESS_START_CONFIGURATION_SETTINGS` owns which of those settings block process start; the executable dispatcher owns the log-level exception for doctor; `KunaDoctor` owns cache-root classification. Earliest stage is setup or provider admission, before a provider session. - Contribution scope fit and linked maintainer decision: bugfix within existing doctor and Kuna readiness. Not applicable. - CLI and MCP/tool-catalog contract: `rea doctor` JSON gains `runtime-configuration:<setting>` checks when native admission fails, including an invalid `REA_LOG_LEVEL`. That log-level check is required in every explicit scope. A selected client also requires every other native admission failure and `hopper-startup-timeout`. `hopper-startup-timeout` remains required for every selected provider. Exit status follows `healthy`. Other commands keep the plain stderr rejection for an invalid log level. No new command or tool. - Provider, bridge, target-format, or platform compatibility: Kuna cache diagnosis changes for dangling links, trailing platform separators, and POSIX paths that end in `\`. Other providers are unchanged. No engine protocol change. - Evidence, artifact, provenance, or reconstruction contract: none. - Target selection, authority, upstream behavior, and cleanup details: doctor remains read-only. It does not create the cache or repair the link. - Generated metadata (`docs/public/product-catalog.json`), package, or installation impact: `docs/installation.md` states that an invalid `REA_LOG_LEVEL` fails every doctor scope, and that other MCP startup failures fail a selected client and every selected provider. CI generates and validates ignored catalogs and `skills/`. Expected effects (check known effects; use documentation-only on its own). - [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: `src/application/Doctor.test.ts`, `src/config.test.ts`, `tests/boundary/cli/doctorHopperDiscovery.test.ts`, `tests/boundary/cli/cliLogLevelConfiguration.test.ts`, `tests/boundary/providers/kuna/kunaDoctor.test.ts`, `tests/boundary/providers/kuna/kunaSetupReadiness.test.ts`. - Base reproduction or other evidence: source inspection of `stat`/`ENOENT`, of doctor versus `parseConfig`, of `scripts/rea.mjs` exiting before doctor when `REA_LOG_LEVEL` is invalid, of the scope partition that omitted process-start failures when no provider was selected, and of `hopper-startup-timeout` being required only when Hopper itself was selected. The historical CLI timings in #5454 and #5554 were not re-run on a real Hopper or Kuna engine. - User-visible CLI/MCP output: focused CLI doctor with `REA_ANALYSIS_PROVIDER=Hopper` and `REA_GHIDRA_STARTUP_TIMEOUT_MS=abc` exited 1 and included both `runtime-configuration` checks in `scope_checks`. `REA_JEB_MCP_TIMEOUT_MS=abc` added no such check. `rea --json doctor --provider hopper` and `rea --json doctor --client codex` with `REA_LOG_LEVEL=loud` and `INFO` exited 1 with an empty stderr and `runtime-configuration:REA_LOG_LEVEL` in `scope_checks`. `rea --json doctor --client codex` with `REA_GHIDRA_STARTUP_TIMEOUT_MS=abc` exited 1 and included that check in `scope_checks` with `providers: []`. `rea --help` with an invalid log level still prints the stderr configuration error and no stdout. - Remaining proof gaps: no real Hopper, Ghidra, IDA, or Kuna engine. Windows cache links were not run (`kunaDoctor` tests skip win32). The non-Hopper timeout regression uses a scripted Ghidra inspection. - [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 - `npm run test:local -- src/application/Doctor.test.ts src/config.test.ts src/application/Doctor.lifecycle.test.ts` — 129 passed. - `npm run test:focused -- tests/boundary/providers/kuna/kunaDoctor.test.ts tests/boundary/providers/kuna/kunaSetupReadiness.test.ts tests/boundary/cli/doctorHopperDiscovery.test.ts` — 16 passed. - `npm run test:focused -- tests/boundary/cli/cliLogLevelConfiguration.test.ts tests/boundary/cli/dispatcher.test.ts tests/boundary/cli/doctorHopperDiscovery.test.ts` — 8 passed. - `npm run test:focused -- src/application/Doctor.test.ts tests/boundary/cli/cliLogLevelConfiguration.test.ts tests/boundary/providers/kuna/kunaDoctor.test.ts` — 72 passed. - `npm run test:focused -- src/application/Doctor.test.ts tests/boundary/cli/doctorHopperDiscovery.test.ts` — 64 passed on `df9a78014`. - `npm run test:local -- src/ida/IdaOperationFailures.test.ts` — 33 passed on `91dc38c64`. - `npm run check:fast` — passed on `df9a78014`. - `npx oxfmt --check .` — passed on `df9a78014`. - `npx tsc --noEmit` — passed on an earlier revision; `check:fast` typechecked this revision. ## Compatibility, safety, and release - Breaking changes or migration steps: `rea doctor` with an invalid `REA_LOG_LEVEL` now returns the doctor report instead of the dispatcher's stderr line, and that failure makes client and skill scopes unhealthy. A selected client is also unhealthy for every other setting MCP startup rejects. An invalid `REA_HOPPER_STARTUP_TIMEOUT_MS` fails every selected provider and a selected client. Other commands are unchanged. Callers who treated a dangling Kuna cache, a POSIX cache path ending in `\`, or an invalid native setting as healthy now get a failing doctor result. - Real Hopper/Ghidra, browser, or OS coverage: not run. Linux scripted CLI and filesystem fixtures only. - Package or release metadata impact: none. - Security, privacy, process, or containment review: read-only diagnosis. No new process launch. Rejected setting values are not copied into the check detail; the parser constraint is. ## Author readiness Human owner: @morluto - [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. ## 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.  <div><a href="https://cursor.com/agents/bc-f78dfee1-da7e-510b-b638-e11cad194f30?cursor_ref=pr_footer&cursor_cta=open_in_web"><picture><source media="(prefers-color-scheme: dark)" srcset="https://cursor.com/assets/images/open-in-web-dark.png"><source media="(prefers-color-scheme: light)" srcset="https://cursor.com/assets/images/open-in-web-light.png"><img alt="Open in Web" width="114" height="28" src="https://cursor.com/assets/images/open-in-web-dark.png"></picture></a> <a href="https://cursor.com/background-agent?bcId=bc-f78dfee1-da7e-510b-b638-e11cad194f30&cursor_ref=pr_footer&cursor_cta=open_in_cursor"><picture><source media="(prefers-color-scheme: dark)" srcset="https://cursor.com/assets/images/open-in-cursor-dark.png"><source media="(prefers-color-scheme: light)" srcset="https://cursor.com/assets/images/open-in-cursor-light.png"><img alt="Open in Cursor" width="131" height="28" src="https://cursor.com/assets/images/open-in-cursor-dark.png"></picture></a> </div> --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

bsakaguchi

2026-11-01 21:44:41 +00:00

closed this issue
added the
pull-request
label

bsakaguchi referenced this issue

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

[PR #7010] [MERGED] feat(elf): inspect Linux kernel module metadata #7572

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

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