Repository navigation
Conversation
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The portable area now has a standalone workspace with retained Linux terminals and a bounded Pi SDK worker lifecycle. A local scripted provider drives real SDK tools while the new UI handles reloads, cancellation, uncertain requests and terminal switching. ARM64 QEMU/kiosk recipes and runtime packaging support rehearsal before Raspberry Pi USB testing.
Validation: independent backend checks passed 26/26, packaging checks passed 29/29, and browser checks covered retained shells, delayed request races and 1024×768 layout. Actual ARM64 QEMU verification exercised SDK imports, the native binding, QuickJS, exact SDK file output and terminal readback. Documentation links and whitespace checks pass.
The full offline integration gate completed on this revision after correcting Python user-site and temporary-path prerequisites: 50 suites passed and four failed (session, notebook, TUI, browser). The failing runtime/test paths are byte-identical to the hosted parent; the gate remains red and this PR must remain draft. A separate scoped portable run passed 27/27 with the actual SDK and a synthetic model. No legacy behavior repairs were added. Tor startup, provider inference, live funding, encrypted persistence and physical USB boot remain milestones under #76. The current rehearsal account and Node deployment do not establish the final agent authority boundary.
Refs #76.