Skip to content

Record what the live engine proved #4

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
MasterYoav merged 1 commit into from
Sep 18, 2026
Merged

Record what the live engine proved #4

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions docs/13-launch-checklist.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -191,6 +191,11 @@ From a shell holding no credentials:
- The manifest bundled into the app is byte-identical to the published one, so a first run with the
network blocked still starts from a real pin.
- Every outbound URL the app can show a person answers 200.
- On 18 September, a throwaway engine built from master (with the model hop lifted into
`models/build.ts`) came up healthy on loopback, refused an unauthenticated request with a 401, and
passed all eight live client tests: health, read endpoints, the vault, agent and conversation
round-trip, browser, files, shell, and the asks. Only the conversation store is still unproven,
because that is the hop needing a CopilotKit key.
- The pinned engine is one multi-arch image (linux/amd64 and linux/arm64). On 14 September an Apple
Silicon Mac pulled it anonymously, got arm64, was healthy in about ten seconds on a port other than
3001, and passed the live suite: browser, files, shell, and a help request handed back. Before that
Expand Down
Loading