docs: add cloud dev environment instructions - #553
Open
RonenMars wants to merge 2 commits into
Open
Conversation
RonenMars
marked this pull request as ready for review
August 4, 2026 15:25
RonenMars
force-pushed
the
docs/cloud-dev-environment-18a1
branch
4 times, most recently
from
August 4, 2026 15:34
24b55ed to
fba0e10
Compare
The advisory `E2E jest` job has flaked twice on cold CI with the same failure: `feedback-flow › shows all entry points` exceeding Jest's default 5s per-test timeout. Local isolation passes, and a single CI re-run goes green — documented in #542 with the instruction to raise the timeout on recurrence rather than delete the job. `test:e2e` now passes `--testTimeout=20000` so cold-start renders on CI runners stop tipping the default. - [x] `npm run test:e2e` — 7 suites / 60 tests pass locally with the new timeout - [x] `E2E jest` green on the previous run of this change without a re-run (feedback-flow suite still ~18s on CI; 20s per-test margin holds) - [ ] After merge, #542 can be closed if the next few PR runs stay green
RonenMars
force-pushed
the
docs/cloud-dev-environment-18a1
branch
from
August 4, 2026 15:34
fba0e10 to
4b5cc9e
Compare
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
1 participant
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.
What
Sets up and documents a working development environment for this repo on the cloud (headless Linux) VM, and records the durable, non-obvious startup/run caveats in
AGENTS.mdunder a new cloud-VM instructions section.No application code is changed — this PR only adds documentation. Environment setup itself (Node toolchain, dependency install) is handled by the VM startup update script (
npm install) plus a one-time pinned-Node snippet in the agent's~/.bashrc.Environment set up & verified
The runnable surface on Linux is the JS toolchain + Expo Web (native iOS/Android builds and Maestro E2E need macOS/Xcode/simulators and are documented as not runnable here).
npm ci(startup script usesnpm install)patch-packageappliednpm run lintnpm run typechecknpm run test:cinpm run test:scriptsnpx expo start --web --port 8081Hello-world (core flow) verified end to end
Started the bundled mock streamer (
e2e/mock-server.js) behind a small dev-only CORS proxy, then in the browser completed onboarding → added a server → the live session list populated from the mock streamer (my-projectonmain/feature/auth/fix/login,other-projectonmain, with running/waiting/idle statuses). Mock server logs confirm the client hit/api/profiles,/api/sessions,/api/conversations/count, and a session-detail/outputfetch.Expected web-parity limitations (documented in
docs/expo-web-support.md, not env bugs): anexpo-notificationsdev red-box on load and a blank session-detail terminal.Node
Pinned
.nvmrcversion (24.15.0) installed vianvm; a guarded snippet in~/.bashrcmakes login/interactive shells prefer it over the sandbox's shadowingnode. Node 22.x also meets the repo's stated>= 22.13minimum.