6 Commits

Include renames

Author	SHA1	Message	Date
swung0x48	0b96a3efbf	MOBILEGL_FRAMES_IN_FLIGHT drives both backends and derives the split present credit (default 3 keeps credit 1; the Magma name stays as an alias).	2026-10-08 19:49:05 -04:00
swung0x48	1987bdff5c	[Feat] (Android): the render server screen and binary ship in the plugin APK too, not just trace	2026-09-28 22:10:56 -04:00
swung0x48	2fa58940e4	[Fix] (ci): the trace APK is a launchable app; assert exactly one launcher activity ... The "Trace APK must not expose a launcher activity" check predates the render-server screen: 1f72597dd gave the trace APK a launcher on purpose and 884f6aac9 moved the entry icon back to PostActivity with a bottom navigation bar between the two screens, so the apk.yml build job has been red ever since - taking the whole retrace matrix down with it (skipped, not failed), which hid the distinction. What is left of the old isolation contract is the count: exactly one android.intent.action.MAIN in the merged manifest (a second one means a screen grew a launcher entry by accident), and it belongs to PostActivity. The fclPlugin metadata ban is unchanged.	2026-09-28 21:54:16 -04:00
swung0x48	5d51372c44	[Chore] (Config): triage backend-scoped env toggles under MOBILEGL_ESPRYT_ and MOBILEGL_MAGMA_ prefixes	2026-08-28 00:38:17 -04:00
swung0x48	3e4ce5caa7	[Refactor] (MG_Impl/GLImpl): replace Flywheel dispatch sync hack with MOBILEGL_COHERENT_AS_FLUSH	2026-07-15 21:51:20 -04:00
swung0x48	7ebaf43282	[Refactor] (Android plugin): unify renderer APK with Plugin V2 DSL	2026-07-14 23:37:21 -04:00