How can a Windows Store Codex package be mapped to its bundled CLI/app-server version and source commit?

[turun574]

I need an authoritative mapping for this Windows Store Codex package:

PackageFullName:
OpenAI.Codex_26.803.10989.0_x64__2p2nqsd0c76g0

Package version:
26.803.10989.0

Bundled executable:
app\resources\codex.exe

Executable size:
293412656 bytes

Executable SHA-256:
592958896CBFFA154709618476FC9C9BF7FE73957E9A4FC12094C5051B6C69B3

Direct execution of the packaged executable with --version could not be
established, so I do not want to infer its CLI version from the Store package
version or select a nearby public release.

Could an OpenAI maintainer clarify:

1. What exact Codex CLI/app-server version is bundled in this package?
2. What exact openai/codex release tag and full commit SHA produced it?
3. Is there an official manifest, API, or deterministic mapping from the
   Windows Store package version to the bundled CLI version and source commit?
4. Is the Store package version independently versioned from the bundled CLI?
5. Is there an official way to obtain the generated TypeScript or JSON Schema
   bundle for this exact packaged version without copying or directly executing
   the WindowsApps binary?

The App Server documentation states that generated schemas are specific to the
Codex version that generated them:
https://learn.chatgpt.com/docs/app-server#message-schema

I am looking for an authoritative mapping, not an inferred or approximate one.

[sylvesterkaczmarek]

From what is publicly exposed today, I don't think there is an authoritative Store-package → CLI tag/SHA mapping you can derive yourself.

The Store version should be treated as the app/package version, not assumed to equal the Codex CLI release number. The documented deterministic route is the binary itself: codex app-server generate-ts or generate-json-schema, whose output is guaranteed to match that Codex version.

So unless OpenAI publishes a manifest for 26.803.10989.0, I don't think the exact release tag/commit can be proven from the Store package number or executable SHA alone. A maintainer-provided mapping would be needed for that.