morluto/rea

Fork 0

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

[PR #4908] [CLOSED] fix(plist): keep CFPropertyList non-finite real spellings as observed values #6672

New issue

Closed

opened 2026-11-01 21:42:12 +00:00 by bsakaguchi · 0 comments

bsakaguchi commented

2026-11-01 21:42:12 +00:00

Owner

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/4908
Author: @mertkayacs
Created: 10/17/2026
Status: ❌ Closed

Base: main ← Head: fix/plist-non-finite-real-spellings

📝 Commits (4)

4223e90 test(plist): cover CFPropertyList non-finite real spellings
1946b69 fix(plist): keep CFPropertyList non-finite real spellings as observed values
09f070a test(plist): cover conversion-spelled reals and the spelled keyed-archive case
f780cde fix(plist): keep conversion-spelled non-finite reals unknown for binary sources

📊 Changes

14 files changed (+327 additions, -35 deletions)

View changed files

📝 docs/native-investigation.md (+12 -1)
📝 src/artifacts/apple/KeyedArchiveReader.ts (+7 -3)
📝 src/domain/apple/keyedArchive.ts (+1 -0)
📝 src/domain/apple/plistNumbers.ts (+29 -0)
📝 src/domain/apple/plistValue.test.ts (+28 -1)
📝 src/domain/apple/plistValue.ts (+40 -5)
📝 src/domain/propertyListKeys.ts (+3 -2)
📝 src/domain/propertyListXml.test.ts (+48 -0)
📝 src/domain/propertyListXml.ts (+7 -1)
📝 src/native/NativeMacOSProvider.ts (+17 -14)
📝 src/native/parsers/plist.test.ts (+34 -0)
📝 src/native/parsers/plist.ts (+20 -4)
📝 tests/acceptance/applications/keyedArchiveScalarKinds.test.ts (+77 -1)
📝 tests/boundary/filesystem/keyedArchiveSelection.test.ts (+4 -3)

📄 Description

Summary

inspect-keyed-archive, inspect_keyed_archive and the XML fallback of inspect_plist report every <real> that CFPropertyList writes as +infinity, -infinity or nan as an unknown real, { "$plist_type": "real", "value": null }, with a limitation saying the decoder cannot distinguish NaN from infinity. The sign and the identity of the value are lost although the source text states both. This change reads CFPropertyList's spellings at the XML decoder and reports them as { "$plist_type": "real", "value": "+infinity" | "-infinity" | "nan" } with status observed. Non-finite numbers that carry no spelling, such as a binary plist double or XML text the decoder could not read as a number, keep today's value: null representation with a reworded limitation. Fixes #4906.

Problem and expected behavior

Trigger: an XML keyed archive whose $objects holds <real>+infinity</real>, <real>-infinity</real> and <real>nan</real>. On 2fb5e204a all three objects are reported as { "kind": "scalar", "status": "observed", "value": { "$plist_type": "real", "value": null } } and the limitation reads 3 non-finite real value(s) are reported as { "$plist_type": "real", "value": null } because JSON evidence cannot preserve NaN vs infinity.

Violated invariant: the decoder replaces an exact source value with an unknown while the source text is unambiguous. Number.parseFloat only recognises the JavaScript spelling Infinity, case-sensitively, so each of Apple's spellings parses to NaN before the projection sees it. CFPropertyList's XML writer emits exactly nan, +infinity and -infinity for non-finite doubles (__CFNumberCreateFormattingDescriptionAsFloat64 in CFNumber.c, used by _CFAppendXML0 in CFPropertyList.c), and its XML parser compares the whole <real> text case-insensitively against nan, +infinity, -infinity, infinity, -inf, inf and +inf (parseRealTag in CFPropertyList.c, swift-corelibs-foundation main). AGENTS.md asks for exact source values and explicit unknowns to be preserved across boundaries; here a known value was reported as unknown.

Change and scope

parsePlistNonFiniteRealLiteral (src/domain/apple/plistNumbers.ts) reads a whole <real> text as one of CFPropertyList's spellings, case-insensitively and without trimming, matching parseRealTag. Any other text keeps the existing parseFloat path untouched.
The XML decoder returns a PlistNonFiniteReal scalar for a spelled value, the same way it returns Date, Uint8Array and bigint for values JSON cannot carry. Incomplete markup inside the element still marks the number metadata incomplete.
projectPlistValue projects that scalar as { "$plist_type": "real", "value": "<spelling>" } through the existing wrapper hook, so keyed-archive classification keeps treating it as a scalar, and counts it separately (nonFiniteRealCount). A raw non-finite number still becomes value: null and is counted as before (unknownRealCount).
omitPrototypeKeys passes the new scalar through like Date and Uint8Array.
The two limitation strings now live in plistValue.ts next to the negative-zero one and are used by both KeyedArchiveReader and the native parsePlistXml path; the old wording claimed the decoder cannot distinguish NaN from infinity, which is no longer true.
docs/native-investigation.md documents the representation next to the negative-zero paragraph.

Not included: binary plist doubles. A binary +inf or -inf still reports value: null; the sign is knowable there and a follow-up could spell it, but that is a different producer (plist's parseBinary) and I kept this PR to the XML text boundary. That holds for the macOS inspect_plist path too: when plutil converts a binary plist to XML, the spelling in that XML is the converter's, so parsePlistXml takes the source format (plistSourceFormat, classified before decoding) and keeps a conversion-spelled real an explicit unknown; only XML source text reports the spelling as observed. Also not included: the strict literal grammar for malformed <real> text discussed in #4852; this change only recognises text CFPropertyList accepts, and leaves everything else exactly as it was.

Contribution scope: ordinary fix within existing boundaries, not applicable.

Contract and boundary impact

Semantic owner and earliest changed stage: decodeXmlPropertyList (src/domain/propertyListXml.ts), result projection.
Contribution scope fit and linked maintainer decision: not applicable, read-only decoding of caller-selected files.
CLI and MCP/tool-catalog contract: the $plist_type: "real" wrapper already allowed "-0"; "+infinity", "-infinity" and "nan" are new string values of the same shape. value: null keeps its meaning for unspelled non-finite numbers. Two limitation texts change wording. No schema change.
Provider, bridge, target-format, or platform compatibility: XML plists only; binary and OpenStep paths unchanged. plist@5 writes JavaScript's Infinity, which CFPropertyList reads as +infinity, so one existing acceptance expectation changed for the XML format.
Evidence, artifact, provenance, or reconstruction contract: observed values gain their sign and spelling; unknowns stay explicit and counted.
Target selection, authority, upstream behavior, and cleanup details: not applicable.
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:
- src/domain/propertyListXml.test.ts: every CFPropertyList spelling, in both cases and through CDATA, decodes to the spelled scalar; 1e999, -1e999, nan, -nan and infinite stay plain numbers; unsupported markup inside a spelled real marks the metadata incomplete.
- src/domain/apple/plistValue.test.ts: spelled scalars project to typed wrappers reported through the wrapper hook, raw non-finite numbers stay value: null, a lookalike dictionary is left alone, and the two counts are separate.
- src/native/parsers/plist.test.ts: parsePlistXml output and both limitation texts, and the same XML read with sourceFormat: "binary", which keeps value: null with the unknown-real limitation.
- tests/boundary/filesystem/keyedArchiveSelection.test.ts: the existing non-finite case (plist writes NaN as <real>nan</real>) now expects the spelled value and the new limitation.
- tests/acceptance/applications/keyedArchiveScalarKinds.test.ts: a new public CLI and MCP case with +infinity, -INFINITY and nan objects, and the existing scalar-kinds case now expects "+infinity" for the XML format.
Base reproduction or other evidence: executed. With only the test commit (7b332bcc0) checked out, npm run test:local on the three unit files reports 15 failed / 32 passed, and npm run test:focused -- tests/acceptance/applications/keyedArchiveScalarKinds.test.ts reports 2 failed / 4 passed (the new case and the XML scalar-kinds case). With the fix (e875e11e6) the same commands report 47 passed and 6 passed.
User-visible CLI/MCP output: inspect-keyed-archive non_finite.plist --json on the fix, objects 1 to 3 of the fixture above:
```
{"id":1,"kind":"scalar","status":"observed","value":{"$plist_type":"real","value":"+infinity"}}
{"id":2,"kind":"scalar","status":"observed","value":{"$plist_type":"real","value":"-infinity"}}
{"id":3,"kind":"scalar","status":"observed","value":{"$plist_type":"real","value":"nan"}}
```
Limitation: 3 non-finite real value(s) are reported as { "$plist_type": "real", "value": "<spelling>" } with the CFPropertyList spelling nan, +infinity or -infinity because a JSON number cannot carry them.
Remaining proof gaps: no macOS run; the CFPropertyList behavior is taken from the swift-corelibs-foundation sources named above, not from plutil on a Mac. Binary plist non-finite doubles are not covered by this change.

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

npm run test:local -- src/domain/propertyListXml.test.ts src/domain/apple/plistValue.test.ts src/native/parsers/plist.test.ts at 7b332bcc0 (tests only) — 15 failed, 32 passed.
npm run test:focused -- tests/acceptance/applications/keyedArchiveScalarKinds.test.ts at 7b332bcc0 — 2 failed, 4 passed.
npm run test:local on the 20 test files under src/domain/apple, src/artifacts/apple, src/native/parsers plus src/domain/propertyListXml.test.ts, src/domain/propertyListKeys.test.ts and src/application/AppBundleExecutable.test.ts at e875e11e6 — 372 passed.
npm run test:focused -- tests/acceptance/applications/keyedArchiveScalarKinds.test.ts at e875e11e6 — 6 passed.
npm run check:fast at e875e11e6 — typecheck and lint passed.
npm run docs:check — 5 passed.
After the review follow-ups (source format threaded through the conversion path, stale boundary case updated): npm run test:local on src/native/parsers/plist.test.ts, src/domain/apple/plistValue.test.ts, src/domain/propertyListXml.test.ts — 48 passed; npm run test:focused on tests/boundary/filesystem/keyedArchiveSelection.test.ts and tests/boundary/providers/native/plistSourceFormat.test.ts — 35 passed; npm run check:fast — passed; npm run docs:check — passed. tests/boundary/cli/nativePlistCli.test.ts is macOS-only and skipped here (17 skipped); its binary arm keeps value: null by construction of the source-format branch.
Node 24.18.0, Linux x64. Rebased on d0253c99d; the three unit files pass there (47 passed).

Compatibility, safety, and release

Breaking changes or migration steps: none. Consumers that matched "value": null for every non-finite real will now see "+infinity", "-infinity" or "nan" for spelled XML values; the wrapper shape is unchanged.
Real Hopper/Ghidra, browser, or OS coverage: not applicable; no provider involved.
Package or release metadata impact: none.
Security, privacy, process, or containment review: read-only decoding of the selected file; no new inputs are executed.

Author readiness

Human owner: @mertkayacs

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/4908 **Author:** [@mertkayacs](https://github.com/mertkayacs) **Created:** 10/17/2026 **Status:** ❌ Closed **Base:** `main` ← **Head:** `fix/plist-non-finite-real-spellings` --- ### 📝 Commits (4) - [`4223e90`](https://github.com/morluto/rea/commit/4223e902072d784a430f5d96a20bb361150959f1) test(plist): cover CFPropertyList non-finite real spellings - [`1946b69`](https://github.com/morluto/rea/commit/1946b6954968a649b18fb395842821c3c35bf4fb) fix(plist): keep CFPropertyList non-finite real spellings as observed values - [`09f070a`](https://github.com/morluto/rea/commit/09f070a6239d591569041f0bec59424ff65597f2) test(plist): cover conversion-spelled reals and the spelled keyed-archive case - [`f780cde`](https://github.com/morluto/rea/commit/f780cde749d025dc5b9cfef85549279e3783ed6a) fix(plist): keep conversion-spelled non-finite reals unknown for binary sources ### 📊 Changes **14 files changed** (+327 additions, -35 deletions) <details> <summary>View changed files</summary> 📝 `docs/native-investigation.md` (+12 -1) 📝 `src/artifacts/apple/KeyedArchiveReader.ts` (+7 -3) 📝 `src/domain/apple/keyedArchive.ts` (+1 -0) 📝 `src/domain/apple/plistNumbers.ts` (+29 -0) 📝 `src/domain/apple/plistValue.test.ts` (+28 -1) 📝 `src/domain/apple/plistValue.ts` (+40 -5) 📝 `src/domain/propertyListKeys.ts` (+3 -2) 📝 `src/domain/propertyListXml.test.ts` (+48 -0) 📝 `src/domain/propertyListXml.ts` (+7 -1) 📝 `src/native/NativeMacOSProvider.ts` (+17 -14) 📝 `src/native/parsers/plist.test.ts` (+34 -0) 📝 `src/native/parsers/plist.ts` (+20 -4) 📝 `tests/acceptance/applications/keyedArchiveScalarKinds.test.ts` (+77 -1) 📝 `tests/boundary/filesystem/keyedArchiveSelection.test.ts` (+4 -3) </details> ### 📄 Description ## Summary `inspect-keyed-archive`, `inspect_keyed_archive` and the XML fallback of `inspect_plist` report every `<real>` that CFPropertyList writes as `+infinity`, `-infinity` or `nan` as an unknown real, `{ "$plist_type": "real", "value": null }`, with a limitation saying the decoder cannot distinguish NaN from infinity. The sign and the identity of the value are lost although the source text states both. This change reads CFPropertyList's spellings at the XML decoder and reports them as `{ "$plist_type": "real", "value": "+infinity" | "-infinity" | "nan" }` with status `observed`. Non-finite numbers that carry no spelling, such as a binary plist double or XML text the decoder could not read as a number, keep today's `value: null` representation with a reworded limitation. Fixes #4906. ## Problem and expected behavior Trigger: an XML keyed archive whose `$objects` holds `<real>+infinity</real>`, `<real>-infinity</real>` and `<real>nan</real>`. On `2fb5e204a` all three objects are reported as `{ "kind": "scalar", "status": "observed", "value": { "$plist_type": "real", "value": null } }` and the limitation reads `3 non-finite real value(s) are reported as { "$plist_type": "real", "value": null } because JSON evidence cannot preserve NaN vs infinity.` Violated invariant: the decoder replaces an exact source value with an unknown while the source text is unambiguous. `Number.parseFloat` only recognises the JavaScript spelling `Infinity`, case-sensitively, so each of Apple's spellings parses to NaN before the projection sees it. CFPropertyList's XML writer emits exactly `nan`, `+infinity` and `-infinity` for non-finite doubles (`__CFNumberCreateFormattingDescriptionAsFloat64` in CFNumber.c, used by `_CFAppendXML0` in CFPropertyList.c), and its XML parser compares the whole `<real>` text case-insensitively against `nan`, `+infinity`, `-infinity`, `infinity`, `-inf`, `inf` and `+inf` (`parseRealTag` in CFPropertyList.c, swift-corelibs-foundation main). AGENTS.md asks for exact source values and explicit unknowns to be preserved across boundaries; here a known value was reported as unknown. ## Change and scope - `parsePlistNonFiniteRealLiteral` (src/domain/apple/plistNumbers.ts) reads a whole `<real>` text as one of CFPropertyList's spellings, case-insensitively and without trimming, matching `parseRealTag`. Any other text keeps the existing `parseFloat` path untouched. - The XML decoder returns a `PlistNonFiniteReal` scalar for a spelled value, the same way it returns `Date`, `Uint8Array` and `bigint` for values JSON cannot carry. Incomplete markup inside the element still marks the number metadata incomplete. - `projectPlistValue` projects that scalar as `{ "$plist_type": "real", "value": "<spelling>" }` through the existing wrapper hook, so keyed-archive classification keeps treating it as a scalar, and counts it separately (`nonFiniteRealCount`). A raw non-finite number still becomes `value: null` and is counted as before (`unknownRealCount`). - `omitPrototypeKeys` passes the new scalar through like `Date` and `Uint8Array`. - The two limitation strings now live in `plistValue.ts` next to the negative-zero one and are used by both `KeyedArchiveReader` and the native `parsePlistXml` path; the old wording claimed the decoder cannot distinguish NaN from infinity, which is no longer true. - docs/native-investigation.md documents the representation next to the negative-zero paragraph. Not included: binary plist doubles. A binary `+inf` or `-inf` still reports `value: null`; the sign is knowable there and a follow-up could spell it, but that is a different producer (`plist`'s `parseBinary`) and I kept this PR to the XML text boundary. That holds for the macOS `inspect_plist` path too: when plutil converts a binary plist to XML, the spelling in that XML is the converter's, so `parsePlistXml` takes the source format (`plistSourceFormat`, classified before decoding) and keeps a conversion-spelled real an explicit unknown; only XML source text reports the spelling as observed. Also not included: the strict literal grammar for malformed `<real>` text discussed in #4852; this change only recognises text CFPropertyList accepts, and leaves everything else exactly as it was. Contribution scope: ordinary fix within existing boundaries, not applicable. ## Contract and boundary impact - Semantic owner and earliest changed stage: `decodeXmlPropertyList` (src/domain/propertyListXml.ts), result projection. - Contribution scope fit and linked maintainer decision: not applicable, read-only decoding of caller-selected files. - CLI and MCP/tool-catalog contract: the `$plist_type: "real"` wrapper already allowed `"-0"`; `"+infinity"`, `"-infinity"` and `"nan"` are new string values of the same shape. `value: null` keeps its meaning for unspelled non-finite numbers. Two limitation texts change wording. No schema change. - Provider, bridge, target-format, or platform compatibility: XML plists only; binary and OpenStep paths unchanged. plist@5 writes JavaScript's `Infinity`, which CFPropertyList reads as `+infinity`, so one existing acceptance expectation changed for the XML format. - Evidence, artifact, provenance, or reconstruction contract: observed values gain their sign and spelling; unknowns stay explicit and counted. - Target selection, authority, upstream behavior, and cleanup details: not applicable. - 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: - src/domain/propertyListXml.test.ts: every CFPropertyList spelling, in both cases and through CDATA, decodes to the spelled scalar; `1e999`, `-1e999`, ` nan `, `-nan` and `infinite` stay plain numbers; unsupported markup inside a spelled real marks the metadata incomplete. - src/domain/apple/plistValue.test.ts: spelled scalars project to typed wrappers reported through the wrapper hook, raw non-finite numbers stay `value: null`, a lookalike dictionary is left alone, and the two counts are separate. - src/native/parsers/plist.test.ts: `parsePlistXml` output and both limitation texts, and the same XML read with `sourceFormat: "binary"`, which keeps `value: null` with the unknown-real limitation. - tests/boundary/filesystem/keyedArchiveSelection.test.ts: the existing non-finite case (plist writes `NaN` as `<real>nan</real>`) now expects the spelled value and the new limitation. - tests/acceptance/applications/keyedArchiveScalarKinds.test.ts: a new public CLI and MCP case with `+infinity`, `-INFINITY` and `nan` objects, and the existing scalar-kinds case now expects `"+infinity"` for the XML format. - Base reproduction or other evidence: executed. With only the test commit (`7b332bcc0`) checked out, `npm run test:local` on the three unit files reports 15 failed / 32 passed, and `npm run test:focused -- tests/acceptance/applications/keyedArchiveScalarKinds.test.ts` reports 2 failed / 4 passed (the new case and the XML scalar-kinds case). With the fix (`e875e11e6`) the same commands report 47 passed and 6 passed. - User-visible CLI/MCP output: `inspect-keyed-archive non_finite.plist --json` on the fix, objects 1 to 3 of the fixture above: ```json {"id":1,"kind":"scalar","status":"observed","value":{"$plist_type":"real","value":"+infinity"}} {"id":2,"kind":"scalar","status":"observed","value":{"$plist_type":"real","value":"-infinity"}} {"id":3,"kind":"scalar","status":"observed","value":{"$plist_type":"real","value":"nan"}} ``` Limitation: `3 non-finite real value(s) are reported as { "$plist_type": "real", "value": "<spelling>" } with the CFPropertyList spelling nan, +infinity or -infinity because a JSON number cannot carry them.` - Remaining proof gaps: no macOS run; the CFPropertyList behavior is taken from the swift-corelibs-foundation sources named above, not from plutil on a Mac. Binary plist non-finite doubles are not covered by this change. 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 - `npm run test:local -- src/domain/propertyListXml.test.ts src/domain/apple/plistValue.test.ts src/native/parsers/plist.test.ts` at `7b332bcc0` (tests only) — 15 failed, 32 passed. - `npm run test:focused -- tests/acceptance/applications/keyedArchiveScalarKinds.test.ts` at `7b332bcc0` — 2 failed, 4 passed. - `npm run test:local` on the 20 test files under src/domain/apple, src/artifacts/apple, src/native/parsers plus src/domain/propertyListXml.test.ts, src/domain/propertyListKeys.test.ts and src/application/AppBundleExecutable.test.ts at `e875e11e6` — 372 passed. - `npm run test:focused -- tests/acceptance/applications/keyedArchiveScalarKinds.test.ts` at `e875e11e6` — 6 passed. - `npm run check:fast` at `e875e11e6` — typecheck and lint passed. - `npm run docs:check` — 5 passed. - After the review follow-ups (source format threaded through the conversion path, stale boundary case updated): `npm run test:local` on `src/native/parsers/plist.test.ts`, `src/domain/apple/plistValue.test.ts`, `src/domain/propertyListXml.test.ts` — 48 passed; `npm run test:focused` on `tests/boundary/filesystem/keyedArchiveSelection.test.ts` and `tests/boundary/providers/native/plistSourceFormat.test.ts` — 35 passed; `npm run check:fast` — passed; `npm run docs:check` — passed. `tests/boundary/cli/nativePlistCli.test.ts` is macOS-only and skipped here (17 skipped); its binary arm keeps `value: null` by construction of the source-format branch. - Node 24.18.0, Linux x64. Rebased on `d0253c99d`; the three unit files pass there (47 passed). ## Compatibility, safety, and release - Breaking changes or migration steps: none. Consumers that matched `"value": null` for every non-finite real will now see `"+infinity"`, `"-infinity"` or `"nan"` for spelled XML values; the wrapper shape is unchanged. - Real Hopper/Ghidra, browser, or OS coverage: not applicable; no provider involved. - Package or release metadata impact: none. - Security, privacy, process, or containment review: read-only decoding of the selected file; no new inputs are executed. ## Author readiness Human owner: @mertkayacs - [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

2026-11-01 21:42:12 +00:00

closed this issue
added the
pull-request
label

bsakaguchi referenced this issue

2026-11-01 21:47:42 +00:00

[PR #6794] [CLOSED] docs(desktop): list all supported IL2CPP metadata versions #7415

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

No description provided.

Rows
Columns