Quality Assurance

Quality Assurance

PGX records separate results for structure, source checks, compilation, automation and documentation. A single unversioned total would hide which checks actually ran.

• Static structure: descriptor/module parsing and dependency closure.
• Source boundary: approved paths, license headers and residue/secret scans.
• Compilation: the exported snapshot passed clean Editor and Game rebuilds; focused module builds remain separate evidence.
• Automation: the release run passed 344/344 registered tests across Editor and Game; source presence alone is not a pass result.
• Documentation: link, navigation and claim checks against the release tree.
• Runtime/editor observation: focused walkthroughs and a sample are roadmap items for the first tagged preview.

A passing check establishes only its own boundary. Issue reports should include the exact revision, engine, platform, target, plugin set and reproduction.