[PR #3828] [CLOSED] fix(native): trace UI actions for all receiver kinds #5930

Closed
opened 2026-10-31 01:10:31 +00:00 by bsakaguchi · 0 comments
Owner

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/3828
Author: @dayvison2b
Created: 10/15/2026
Status: ❌ Closed

Base: main ← Head: fix/3343-native-ui-action-handler


📝 Commits (1)

  • 6d29e3e fix(native): trace UI actions for all receiver kinds

📊 Changes

3 files changed (+100 additions, -16 deletions)

View changed files

📝 src/application/native/EnhancedNativeInvestigation.test.ts (+58 -0)
📝 src/domain/native/nativeInvestigationGraph.test.ts (+28 -9)
📝 src/domain/native/nativeInvestigationGraph.ts (+14 -7)

📄 Description

Summary

Known Objective-C handlers are now joined to Interface Builder actions when the receiver is a view, control, or unknown object. The trace no longer silently drops these dispatches.

Fixes #3343

Problem and expected behavior

Before this change, a matching handler was retained for controller receivers but dropped for view, control, and unknown receivers. The trace could then report zero examined dispatches and complete coverage despite the authored action.

Change and scope

The join now matches the declared receiver class for controller, view, control, and unknown receiver kinds. Placeholder and external-object cases keep their existing unresolved/inferred handling. This is a focused fix within the existing static-analysis boundary; no new provider or capability is added.

Contract and boundary impact

  • Semantic owner and earliest changed stage: native investigation graph, Interface Builder to Objective-C dispatch join.
  • Contribution scope fit and linked maintainer decision: ordinary bug fix within existing scope; no new capability decision applies.
  • CLI and MCP/tool-catalog contract: no schema change; the graph now includes known dispatch edges and reports coverage accurately.
  • Provider, bridge, target-format, or platform compatibility: no provider change.
  • Evidence, artifact, provenance, or reconstruction contract: authored action and symbol evidence retain their existing observed/inferred distinctions; unresolved receivers remain visible.
  • Target selection, authority, upstream behavior, and cleanup details: static analysis only; no target execution or mutation.
  • Generated metadata, package, or installation impact: none.

Expected effects:

  • 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: receiver-kind coverage for controller, view, control, and unknown in the graph and shared workflow.

  • Base reproduction or other evidence: simulated metadata reproduces the missing handler for view/control/unknown while the controller case succeeds.

  • User-visible CLI/MCP output: shared workflow tests exercise trace_native_ui_action and verify the dispatch edge and coverage.

  • Remaining proof gaps: no run with Hopper, Ghidra, or a real binary; tests use simulated provider metadata.

  • 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:focused -- src/domain/native/nativeInvestigationGraph.test.ts src/application/native/EnhancedNativeInvestigation.test.ts — 47 tests passed.
  • npm run check:fast — passed.
  • Node 24.17.0 was used; the repository pins 24.18.0, and documents a Node 24.11+ supported floor.

Compatibility, safety, and release

  • Breaking changes or migration steps: none.
  • Real Hopper/Ghidra, browser, or OS coverage: not run; tests use simulated metadata.
  • Package or release metadata impact: none.
  • Security, privacy, process, or containment review: no new process execution or target interaction; this changes a static metadata join.

Author readiness

Human owner:

  • 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/3828 **Author:** [@dayvison2b](https://github.com/dayvison2b) **Created:** 10/15/2026 **Status:** ❌ Closed **Base:** `main` ← **Head:** `fix/3343-native-ui-action-handler` --- ### 📝 Commits (1) - [`6d29e3e`](https://github.com/morluto/rea/commit/6d29e3e3032f8fd90046c6379025c5332eb6c3c2) fix(native): trace UI actions for all receiver kinds ### 📊 Changes **3 files changed** (+100 additions, -16 deletions) <details> <summary>View changed files</summary> 📝 `src/application/native/EnhancedNativeInvestigation.test.ts` (+58 -0) 📝 `src/domain/native/nativeInvestigationGraph.test.ts` (+28 -9) 📝 `src/domain/native/nativeInvestigationGraph.ts` (+14 -7) </details> ### 📄 Description ## Summary Known Objective-C handlers are now joined to Interface Builder actions when the receiver is a view, control, or unknown object. The trace no longer silently drops these dispatches. Fixes #3343 ## Problem and expected behavior Before this change, a matching handler was retained for controller receivers but dropped for view, control, and unknown receivers. The trace could then report zero examined dispatches and complete coverage despite the authored action. ## Change and scope The join now matches the declared receiver class for controller, view, control, and unknown receiver kinds. Placeholder and external-object cases keep their existing unresolved/inferred handling. This is a focused fix within the existing static-analysis boundary; no new provider or capability is added. ## Contract and boundary impact - Semantic owner and earliest changed stage: native investigation graph, Interface Builder to Objective-C dispatch join. - Contribution scope fit and linked maintainer decision: ordinary bug fix within existing scope; no new capability decision applies. - CLI and MCP/tool-catalog contract: no schema change; the graph now includes known dispatch edges and reports coverage accurately. - Provider, bridge, target-format, or platform compatibility: no provider change. - Evidence, artifact, provenance, or reconstruction contract: authored action and symbol evidence retain their existing observed/inferred distinctions; unresolved receivers remain visible. - Target selection, authority, upstream behavior, and cleanup details: static analysis only; no target execution or mutation. - Generated metadata, package, or installation impact: none. Expected effects: - [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: receiver-kind coverage for controller, view, control, and unknown in the graph and shared workflow. - Base reproduction or other evidence: simulated metadata reproduces the missing handler for view/control/unknown while the controller case succeeds. - User-visible CLI/MCP output: shared workflow tests exercise `trace_native_ui_action` and verify the dispatch edge and coverage. - Remaining proof gaps: no run with Hopper, Ghidra, or a real binary; tests use simulated provider metadata. - [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:focused -- src/domain/native/nativeInvestigationGraph.test.ts src/application/native/EnhancedNativeInvestigation.test.ts` — 47 tests passed. - `npm run check:fast` — passed. - Node 24.17.0 was used; the repository pins 24.18.0, and documents a Node 24.11+ supported floor. ## Compatibility, safety, and release - Breaking changes or migration steps: none. - Real Hopper/Ghidra, browser, or OS coverage: not run; tests use simulated metadata. - Package or release metadata impact: none. - Security, privacy, process, or containment review: no new process execution or target interaction; this changes a static metadata join. ## Author readiness Human owner: <!-- @GitHub-handle --> - [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 - [ ] 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. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
bsakaguchi 2026-10-31 01:10:31 +00:00
Sign in to join this conversation.
No milestone
No project
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#5930
No description provided.