morluto/rea

Fork 0

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

[PR #5511] [MERGED] feat(desktop): suggest managed members for Unity script assemblies #6947

New issue

Closed

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

bsakaguchi commented

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

Owner

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/5511
Author: @8rulerstar
Created: 10/20/2026
Status: ✅ Merged
Merged: 11/4/2026
Merged by: @morluto

Base: main ← Head: feat/unity-script-assembly-probes

📝 Commits (10+)

73f6d95 feat(desktop): suggest managed members for Unity predefined script assemblies
4ba27ac docs(desktop): describe Unity Mono managed member probes
385391e refactor(desktop): read Unity managed directory from the witness fact
6ac7bcf refactor(desktop): reuse the managed directory index for predefined assemblies
b1d0dc3 feat(desktop): point Unity member probes at summary delivery first
2a60361 test(desktop): no member probes without a Unity reference witness
63366a9 docs(desktop): trim Unity member probe note
622aca0 feat(desktop): suggest managed members in Unity IL2CPP backup folders
a5011ba docs(desktop): note IL2CPP backup folder member probes
2e4e51d docs(desktop): list IL2CPP metadata versions 24 and 27 for the metadata probe

📊 Changes

7 files changed (+307 additions, -10 deletions)

View changed files

📝 docs/desktop-applications.md (+9 -0)
📝 src/artifacts/DesktopApplicationReader.ts (+19 -6)
📝 src/domain/desktopApplication.ts (+6 -0)
📝 src/domain/desktopApplicationProjection.test.ts (+5 -0)
📝 src/domain/desktopApplicationProjection.ts (+31 -1)
📝 src/domain/nativeConvention.ts (+43 -3)
📝 tests/boundary/filesystem/desktopApplication.test.ts (+194 -0)

📄 Description

Summary

For a Unity Mono player, inspect_desktop_application suggests inspect_managed_artifact for every managed DLL (90 probes on a Unity 2022.3.62f3 Win64 sample, almost all UnityEngine.*, System.*, Mono.*) and never inspect_managed_members. This adds one inspect_managed_members probe for each Unity predefined script assembly (Assembly-CSharp.dll, Assembly-CSharp-firstpass.dll), listed first, and the same probe for those assemblies in an IL2CPP build's <Product>_BackUpThisFolder_ButDontShipItWithYourGame/Managed/. Related: #3607 (not a fix for it, so not linked with "Fixes").

Problem and expected behavior

Use case: an agent triaging a Unity game wants the game's own code first. Today the probe list is dominated by engine and BCL assemblies, and the member-level operation that answers "what does this game's code contain" is never suggested.

Expected: when a managed directory has a unity-assembly-reference witness, Assembly-CSharp.dll and Assembly-CSharp-firstpass.dll directly in that directory get an inspect_managed_members probe ahead of every inspect_managed_artifact probe. The same applies to those names in Managed/ of an IL2CPP backup folder, with a rationale stating that correspondence to the shipped native code is unknown. All other probes stay identical and in the same order.

Change and scope

desktopPathConventions (src/domain/nativeConvention.ts), which already owns the Unity managed directory rule, also owns the predefined assembly name rule and the backup folder suffix rule (case-folded, non-empty product prefix). The admitted root name is passed in so the root itself can be the backup folder.
The projection adds the Mono probe only when the file has the existing pe-cli-directory fact, sits directly in a managed directory that already has a unity-assembly-reference witness, and has a predefined name. The Mono probe is derived from that existing witness fact plus the path, so it records no new fact; the backup probe has no comparable witness, so it records unity-il2cpp-backup-convention. This asymmetry is deliberate.
New fact unity-il2cpp-backup-convention (offset: null, backup_directory) is a path convention only. No unity-mono label is added from it.
The earlier IL2CPP metadata versions 24 and 27 docs fix is now on main, so this PR no longer carries it.
Not included: assemblies built from asmdef files (project-chosen names that the parsed facts cannot separate from plugin or framework DLLs); roots that are the <Product>_Data or Managed folder itself (an existing limit on main, now documented: point the scan at the game folder); DLLs past the probe byte budget, which get no pe-cli-directory fact, same as the ordinary managed probes.

Follow the contribution scope.
Unresolved scope, authority, side effects, or required verification block
integration. Link the required maintainer scope decision for new providers or
capabilities involving target execution, injection, mutation, or protection
recovery; ordinary fixes within existing boundaries may state "not applicable".
Draft PRs may leave the scope decision pending and the readiness and merge checklists
unchecked. Maintainers can help resolve open questions.

Maintainer scope decision: not applicable (additive probe suggestion within the existing desktop triage boundary; no new provider or capability).

Contract and boundary impact

Semantic owner and earliest changed stage: desktopPathConventions in src/domain/nativeConvention.ts; projection in src/domain/desktopApplicationProjection.ts.
Contribution scope fit and linked maintainer decision: within existing desktop triage; not applicable.
CLI and MCP/tool-catalog contract: next_probes[].operation gains the additive value inspect_managed_members; new additive fact kind unity-il2cpp-backup-convention in files[].facts.
Provider, bridge, target-format, or platform compatibility: none.
Evidence, artifact, provenance, or reconstruction contract: new fact is a path convention with offset: null; probe rationale states IL correspondence to shipped IL2CPP code is unknown.
Target selection, authority, upstream behavior, and cleanup details (if applicable): not applicable.
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.

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: tests/boundary/filesystem/desktopApplication.test.ts covers probe ordering for predefined assemblies in Game_Data/Managed; positive member probe in a macOS bundle Contents/Resources/Data/Managed; no member probe when the root is Game_Data or Game_Data/Managed itself; no member probes without a Unity reference witness; backup folder probes (including the backup folder as root, case folding, and non-matching names). src/domain/desktopApplicationProjection.test.ts adds unity-il2cpp-backup-convention to the fact list that main's probe fan-out test checks against DESKTOP_PROBES_PER_FACT.

Base reproduction or other evidence: executed, on self-built samples at 2e4e51d87, before the main merges. Counts were not re-measured after merging main; the member-probe ordering is covered by committed tests, while "other probes identical" rests on these pre-merge runs only.

Build	Probes before → after	Other probes
Mono 2022.3.62f3 Win64	90 → 91	identical, same order
Mono 2022.3.62f3 macOS	89 → 90	identical, same order
Mono 2020.3.49f1 macOS	93 → 94	identical, same order
IL2CPP 2022.3.62f3 / 2020.3.49f1 macOS	2 → 2	identical
IL2CPP `Build/` with backup folder (2022.3 / 2020.3)	40 → 41 / 39 → 40	member probe first; others identical
Backup folder alone (2022.3 / 2020.3)	37 → 38 / 36 → 37	same

User-visible CLI/MCP output (if applicable): first two next_probes rows for a Game_Data/Managed fixture with Assembly-CSharp.dll (Unity reference) and UnityEngine.CoreModule.dll, captured by running the boundary test's inspect helper on that fixture on Windows 11 (ids shortened with …, local root replaced by <root>, path separators shown as /):

[
  {
    "probe_id": "dsp_aa7219f7…",
    "operation": "inspect_managed_members",
    "path": "<root>/Game_Data/Managed/Assembly-CSharp.dll",
    "file_id": "dsf_22ced2df…",
    "rationale": "Inventory types, members and user strings of this Unity predefined script assembly; its references and contents are unverified. Start with detail \"summary\" and page rows through inspect_analysis_view.",
    "confidence": "inferred"
  },
  {
    "probe_id": "dsp_664cd29a…",
    "operation": "inspect_managed_artifact",
    "path": "<root>/Game_Data/Managed/Assembly-CSharp.dll",
    "file_id": "dsf_22ced2df…",
    "rationale": "Inspect the declared managed metadata and references.",
    "confidence": "inferred"
  }
]

Response size on the Win64 sample: inspect_managed_artifact 12,977 B, inspect_managed_members 104,955 B default, 12,805 B with detail: "summary"; the rationale points to summary first.

Remaining proof gaps: backup folders checked only on macOS builds, not Windows or Linux layouts or a shipped game. No sample contains Assembly-CSharp-firstpass.dll (test only). Not run on Unity 6, Linux players, 32-bit Windows or commercial games. Agent tool selection after the change is unmeasured. How often large games exceed the probe byte budget is unmeasured.

For boundary fixes, identify the applicable boundary regressions
and lifecycle regressions
covered by the evidence above, and explain relevant gaps.

Not applicable: this is a feature, not a boundary fix. The new behavior is covered by the boundary tests listed above.

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

At 5716a2429 (merge of main d48e472fa is 967903f80), Windows 11, Node 24.19.0, below the engines floor 24.22.1 (dependencies installed with --engine-strict=false):

npm run check:fast (typecheck and lint): passed.
node scripts/run-exact-tests.mjs run tests/boundary/filesystem/desktopApplication.test.ts src/domain/desktopApplicationProjection.test.ts: 91 passed, 3 skipped, 1 failed: does not promote filenames, arbitrary pak files or symlink targets into byte facts fails with EPERM creating a symlink (Windows without symlink privilege). That test already exists on main and is not touched by this PR.
npm run test:focused stops before running any test on this machine because its build step needs the Windows native build output (native/windows/build/manifest.json), so the CLI and MCP desktop tests were left to CI. npm run docs:check was not run locally.

CI on 5716a2429: CI required, Build package, Documentation, Portable tests and all eight test shards passed.

Compatibility, safety, and release

Breaking changes or migration steps: none; additive probe operation value and fact kind.
Real Hopper/Ghidra, browser, or OS coverage: macOS and Win64 Unity samples as above; no Hopper/Ghidra involvement.
Package or release metadata impact: none.
Security, privacy, process, or containment review: reads only files already admitted by the scan; no game executed or executable modified.

Author readiness

Human owner: @8rulerstar

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/5511 **Author:** [@8rulerstar](https://github.com/8rulerstar) **Created:** 10/20/2026 **Status:** ✅ Merged **Merged:** 11/4/2026 **Merged by:** [@morluto](https://github.com/morluto) **Base:** `main` ← **Head:** `feat/unity-script-assembly-probes` --- ### 📝 Commits (10+) - [`73f6d95`](https://github.com/morluto/rea/commit/73f6d95b0f25c1ebcce51f6b201019014ed81af5) feat(desktop): suggest managed members for Unity predefined script assemblies - [`4ba27ac`](https://github.com/morluto/rea/commit/4ba27ac1122aa8c7e059d8f54fa85961bf98d346) docs(desktop): describe Unity Mono managed member probes - [`385391e`](https://github.com/morluto/rea/commit/385391eaad212d71b6dc14230b12f932654f4d60) refactor(desktop): read Unity managed directory from the witness fact - [`6ac7bcf`](https://github.com/morluto/rea/commit/6ac7bcfb91cf0ab46af9bfcae72a21ccb8913df5) refactor(desktop): reuse the managed directory index for predefined assemblies - [`b1d0dc3`](https://github.com/morluto/rea/commit/b1d0dc37472b7e911b340888e8eeec7e89123be4) feat(desktop): point Unity member probes at summary delivery first - [`2a60361`](https://github.com/morluto/rea/commit/2a60361b58885d8513689317cc31f0239308fd38) test(desktop): no member probes without a Unity reference witness - [`63366a9`](https://github.com/morluto/rea/commit/63366a9fd551ca899c8425333d3d8a5db412f5d5) docs(desktop): trim Unity member probe note - [`622aca0`](https://github.com/morluto/rea/commit/622aca056ea4d5781d971defd82b4d8f41901da9) feat(desktop): suggest managed members in Unity IL2CPP backup folders - [`a5011ba`](https://github.com/morluto/rea/commit/a5011bad30c4fec96021bab6613232a8d520055e) docs(desktop): note IL2CPP backup folder member probes - [`2e4e51d`](https://github.com/morluto/rea/commit/2e4e51d87b2581b6d8160e7a7bcaf0badf51f842) docs(desktop): list IL2CPP metadata versions 24 and 27 for the metadata probe ### 📊 Changes **7 files changed** (+307 additions, -10 deletions) <details> <summary>View changed files</summary> 📝 `docs/desktop-applications.md` (+9 -0) 📝 `src/artifacts/DesktopApplicationReader.ts` (+19 -6) 📝 `src/domain/desktopApplication.ts` (+6 -0) 📝 `src/domain/desktopApplicationProjection.test.ts` (+5 -0) 📝 `src/domain/desktopApplicationProjection.ts` (+31 -1) 📝 `src/domain/nativeConvention.ts` (+43 -3) 📝 `tests/boundary/filesystem/desktopApplication.test.ts` (+194 -0) </details> ### 📄 Description ## Summary For a Unity Mono player, `inspect_desktop_application` suggests `inspect_managed_artifact` for every managed DLL (90 probes on a Unity 2022.3.62f3 Win64 sample, almost all `UnityEngine.*`, `System.*`, `Mono.*`) and never `inspect_managed_members`. This adds one `inspect_managed_members` probe for each Unity predefined script assembly (`Assembly-CSharp.dll`, `Assembly-CSharp-firstpass.dll`), listed first, and the same probe for those assemblies in an IL2CPP build's `<Product>_BackUpThisFolder_ButDontShipItWithYourGame/Managed/`. Related: #3607 (not a fix for it, so not linked with "Fixes"). ## Problem and expected behavior Use case: an agent triaging a Unity game wants the game's own code first. Today the probe list is dominated by engine and BCL assemblies, and the member-level operation that answers "what does this game's code contain" is never suggested. Expected: when a managed directory has a `unity-assembly-reference` witness, `Assembly-CSharp.dll` and `Assembly-CSharp-firstpass.dll` directly in that directory get an `inspect_managed_members` probe ahead of every `inspect_managed_artifact` probe. The same applies to those names in `Managed/` of an IL2CPP backup folder, with a rationale stating that correspondence to the shipped native code is unknown. All other probes stay identical and in the same order. ## Change and scope - `desktopPathConventions` (`src/domain/nativeConvention.ts`), which already owns the Unity managed directory rule, also owns the predefined assembly name rule and the backup folder suffix rule (case-folded, non-empty product prefix). The admitted root name is passed in so the root itself can be the backup folder. - The projection adds the Mono probe only when the file has the existing `pe-cli-directory` fact, sits directly in a managed directory that already has a `unity-assembly-reference` witness, and has a predefined name. The Mono probe is derived from that existing witness fact plus the path, so it records no new fact; the backup probe has no comparable witness, so it records `unity-il2cpp-backup-convention`. This asymmetry is deliberate. - New fact `unity-il2cpp-backup-convention` (`offset: null`, `backup_directory`) is a path convention only. No `unity-mono` label is added from it. - The earlier IL2CPP metadata versions 24 and 27 docs fix is now on main, so this PR no longer carries it. - Not included: assemblies built from asmdef files (project-chosen names that the parsed facts cannot separate from plugin or framework DLLs); roots that are the `<Product>_Data` or `Managed` folder itself (an existing limit on main, now documented: point the scan at the game folder); DLLs past the probe byte budget, which get no `pe-cli-directory` fact, same as the ordinary managed probes. Follow the [contribution scope](https://github.com/morluto/rea/blob/main/CONTRIBUTING.md#contribution-scope). Unresolved scope, authority, side effects, or required verification block integration. Link the required maintainer scope decision for new providers or capabilities involving target execution, injection, mutation, or protection recovery; ordinary fixes within existing boundaries may state "not applicable". Draft PRs may leave the scope decision pending and the readiness and merge checklists unchecked. Maintainers can help resolve open questions. Maintainer scope decision: not applicable (additive probe suggestion within the existing desktop triage boundary; no new provider or capability). ## Contract and boundary impact - Semantic owner and earliest changed stage: `desktopPathConventions` in `src/domain/nativeConvention.ts`; projection in `src/domain/desktopApplicationProjection.ts`. - Contribution scope fit and linked maintainer decision: within existing desktop triage; not applicable. - CLI and MCP/tool-catalog contract: `next_probes[].operation` gains the additive value `inspect_managed_members`; new additive fact kind `unity-il2cpp-backup-convention` in `files[].facts`. - Provider, bridge, target-format, or platform compatibility: none. - Evidence, artifact, provenance, or reconstruction contract: new fact is a path convention with `offset: null`; probe rationale states IL correspondence to shipped IL2CPP code is unknown. - Target selection, authority, upstream behavior, and cleanup details (if applicable): not applicable. - 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. 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: `tests/boundary/filesystem/desktopApplication.test.ts` covers probe ordering for predefined assemblies in `Game_Data/Managed`; positive member probe in a macOS bundle `Contents/Resources/Data/Managed`; no member probe when the root is `Game_Data` or `Game_Data/Managed` itself; no member probes without a Unity reference witness; backup folder probes (including the backup folder as root, case folding, and non-matching names). `src/domain/desktopApplicationProjection.test.ts` adds `unity-il2cpp-backup-convention` to the fact list that main's probe fan-out test checks against `DESKTOP_PROBES_PER_FACT`. - Base reproduction or other evidence: executed, on self-built samples at `2e4e51d87`, before the main merges. Counts were not re-measured after merging main; the member-probe ordering is covered by committed tests, while "other probes identical" rests on these pre-merge runs only. | Build | Probes before → after | Other probes | |---|---|---| | Mono 2022.3.62f3 Win64 | 90 → 91 | identical, same order | | Mono 2022.3.62f3 macOS | 89 → 90 | identical, same order | | Mono 2020.3.49f1 macOS | 93 → 94 | identical, same order | | IL2CPP 2022.3.62f3 / 2020.3.49f1 macOS | 2 → 2 | identical | | IL2CPP `Build/` with backup folder (2022.3 / 2020.3) | 40 → 41 / 39 → 40 | member probe first; others identical | | Backup folder alone (2022.3 / 2020.3) | 37 → 38 / 36 → 37 | same | - User-visible CLI/MCP output (if applicable): first two `next_probes` rows for a `Game_Data/Managed` fixture with `Assembly-CSharp.dll` (Unity reference) and `UnityEngine.CoreModule.dll`, captured by running the boundary test's `inspect` helper on that fixture on Windows 11 (ids shortened with …, local root replaced by `<root>`, path separators shown as `/`): ```json [ { "probe_id": "dsp_aa7219f7…", "operation": "inspect_managed_members", "path": "<root>/Game_Data/Managed/Assembly-CSharp.dll", "file_id": "dsf_22ced2df…", "rationale": "Inventory types, members and user strings of this Unity predefined script assembly; its references and contents are unverified. Start with detail \"summary\" and page rows through inspect_analysis_view.", "confidence": "inferred" }, { "probe_id": "dsp_664cd29a…", "operation": "inspect_managed_artifact", "path": "<root>/Game_Data/Managed/Assembly-CSharp.dll", "file_id": "dsf_22ced2df…", "rationale": "Inspect the declared managed metadata and references.", "confidence": "inferred" } ] ``` Response size on the Win64 sample: `inspect_managed_artifact` 12,977 B, `inspect_managed_members` 104,955 B default, 12,805 B with `detail: "summary"`; the rationale points to summary first. - Remaining proof gaps: backup folders checked only on macOS builds, not Windows or Linux layouts or a shipped game. No sample contains `Assembly-CSharp-firstpass.dll` (test only). Not run on Unity 6, Linux players, 32-bit Windows or commercial games. Agent tool selection after the change is unmeasured. How often large games exceed the probe byte budget is unmeasured. For boundary fixes, identify the applicable [boundary regressions](https://github.com/morluto/rea/blob/main/docs/testing.md#boundary-regressions) and [lifecycle regressions](https://github.com/morluto/rea/blob/main/docs/testing.md#lifecycle-regressions) covered by the evidence above, and explain relevant gaps. Not applicable: this is a feature, not a boundary fix. The new behavior is covered by the boundary tests listed above. 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 At `5716a2429` (merge of main `d48e472fa` is `967903f80`), Windows 11, Node 24.19.0, below the `engines` floor 24.22.1 (dependencies installed with `--engine-strict=false`): - `npm run check:fast` (typecheck and lint): passed. - `node scripts/run-exact-tests.mjs run tests/boundary/filesystem/desktopApplication.test.ts src/domain/desktopApplicationProjection.test.ts`: 91 passed, 3 skipped, 1 failed: `does not promote filenames, arbitrary pak files or symlink targets into byte facts` fails with `EPERM` creating a symlink (Windows without symlink privilege). That test already exists on main and is not touched by this PR. - `npm run test:focused` stops before running any test on this machine because its build step needs the Windows native build output (`native/windows/build/manifest.json`), so the CLI and MCP desktop tests were left to CI. `npm run docs:check` was not run locally. CI on `5716a2429`: [`CI required`, `Build package`, `Documentation`, `Portable tests` and all eight test shards passed](https://github.com/morluto/rea/actions/runs/41165405212). ## Compatibility, safety, and release - Breaking changes or migration steps: none; additive probe operation value and fact kind. - Real Hopper/Ghidra, browser, or OS coverage: macOS and Win64 Unity samples as above; no Hopper/Ghidra involvement. - Package or release metadata impact: none. - Security, privacy, process, or containment review: reads only files already admitted by the scan; no game executed or executable modified. ## Author readiness Human owner: @8rulerstar - [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. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

bsakaguchi added the

pull-request

label

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

bsakaguchi referenced this issue

2026-11-01 21:48:05 +00:00

[PR #6950] [MERGED] perf(entropy): separate physical reads from report resolution #7472

bsakaguchi changed title from ~~[PR #5511] feat(desktop): suggest managed members for Unity script assemblies~~ to [PR #5511] [MERGED] feat(desktop): suggest managed members for Unity script assemblies

2026-11-04 12:17:27 +00:00

bsakaguchi closed this issue

2026-11-04 12:17:27 +00:00

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

No description provided.

Rows
Columns