[JasonStys]

Forge2D now has a real Windows scene editor over its existing C++ engine. Users can edit/apply all scene fields, play focused keyboard inputs or recorded replays, save an authored project outside the application folder, recover without resetting invalid saved data, and export matching scene/replay/image/snapshot evidence. Prepared scenes are normal inputs inside the full application.

The portable executable links the static C++ runtime and requires no IDE, Python, Node or network. Native CI tests the actual extracted ZIP and visible window using three synthetic-profile launches; normal PR/push runs retain only bounded receipts/screenshots, while full-package retention requires explicit trusted-main opt-in. A Windows CodeQL build extracts the Win32 host alongside the existing Linux/core analysis. Original coverage, sanitizer/fuzz, SDL, benchmark and container gates remain.

Validation: all three MSVC CTests passed (original ten core groups, four editor groups and real file-boundary cases), all authored C/C++ formatting and repository/index checks passed, original benchmark/demo passed, and actual extracted native acceptance verified custom coordinates, invalid/empty scenes, native Play timer, exported replay equivalence, exclusive profile ownership, no-overwrite exports, durable restart and corrupt-project preservation. Screenshots are actual owned-window captures. Hosted gates remain pending; local results do not imply a public release or installed shortcut.

Limits: unsigned Windows portable candidate; single OS-owner plaintext project; no populated-user upgrade, external OS input automation or clean-machine certification. Collision masks detect overlaps without physical response. Replays require the matching scene. Historical Word publications retain their cited baseline; updated illustrated Word documentation is coordinated separately.

[github-advanced-security]

You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool.

What Enabling Code Scanning Means:

• The 'Security' tab will display more code scanning analysis results (e.g., for the default branch).
• Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results.
• You will be able to see the analysis results for the pull request's branch on this overview once the scans have completed and the checks have passed.

For more information about GitHub Code Scanning, check out the documentation.