What exact Pi runtime image and configuration contract does the proof of concept support? Settle pinned Pi and MCP-adapter versions, Node/toolchain contents, rootfs build and distribution for both daemon topologies, project trust, ancestor instruction files, ambient extensions/skills/packages, custom models, user MCP servers, offline catalog behavior, and whether provider/catalog/adapter probes must use the same sandbox profile as live sessions.
Part of #1
Blocked by: #8
## Question
What exact Pi runtime image and configuration contract does the proof of concept support? Settle pinned Pi and MCP-adapter versions, Node/toolchain contents, rootfs build and distribution for both daemon topologies, project trust, ancestor instruction files, ambient extensions/skills/packages, custom models, user MCP servers, offline catalog behavior, and whether provider/catalog/adapter probes must use the same sandbox profile as live sessions.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Part of #1
Blocked by: #8
Question
What exact Pi runtime image and configuration contract does the proof of concept support? Settle pinned Pi and MCP-adapter versions, Node/toolchain contents, rootfs build and distribution for both daemon topologies, project trust, ancestor instruction files, ambient extensions/skills/packages, custom models, user MCP servers, offline catalog behavior, and whether provider/catalog/adapter probes must use the same sandbox profile as live sessions.