The map a program over AndroidApp receives: the base set plus the process
continuation's reference and the process reference. Their identifiers are
never (each is a Context.Reference), so they add no requirement to a
program and are not part of AndroidRuntimeServices; they are picked so the
app layer's own screen actions can run them. CurrentAppProcess is picked the
same way: the transport reads it in every request a program sends, so a
checkpoint error names this process.
The app's own process state is picked beside this list
(androidProcessStateReferences): those keys are internal and are kept out
of the published declarations, so the published surface cannot name their
value types. The map a program receives is this surface, that process state
and the entries' fixture seam (TelemetrySettled) — one equality the
runtime-surface test in android.app.test.ts pins against the layer's own
build context.
The map a program over
AndroidAppreceives: the base set plus the process continuation's reference and the process reference. Their identifiers arenever(each is aContext.Reference), so they add no requirement to a program and are not part ofAndroidRuntimeServices; they are picked so the app layer's own screen actions can run them.CurrentAppProcessis picked the same way: the transport reads it in every request a program sends, so a checkpoint error names this process.The app's own process state is picked beside this list (
androidProcessStateReferences): those keys are internal and are kept out of the published declarations, so the published surface cannot name their value types. The map a program receives is this surface, that process state and the entries' fixture seam (TelemetrySettled) — one equality the runtime-surface test inandroid.app.test.tspins against the layer's own build context.