MVP integration: wire projects-signals-mobile UI to the complete loop #17

Closed
opened 2026-07-23 21:25:14 +00:00 by puter · 0 comments
Owner

Parent: #4 and #14. Treat origin/codex/projects-signals-mobile as the source for the mobile frontend and AI Elements UI. Integrate it into puter/issue-14-integration / PR #16 while preserving all newer backend, Effect primitives, AgentOS checkout, Gitea lifecycle, and smoke changes. Replace demo or derived-only interactions with real functions: organization/project selection, signals, issue creation/dispatch, run state, artifacts/verification, PR metadata/review link, and assistant message send. Keep desktop project-loop UI where useful; mobile routes must be functional and responsive. Resolve route/package/lock conflicts, run web tests/typecheck/build and integrated backend/agent smoke, then update PR #16 rather than opening a competing final integration PR.

Parent: #4 and #14. Treat origin/codex/projects-signals-mobile as the source for the mobile frontend and AI Elements UI. Integrate it into puter/issue-14-integration / PR #16 while preserving all newer backend, Effect primitives, AgentOS checkout, Gitea lifecycle, and smoke changes. Replace demo or derived-only interactions with real functions: organization/project selection, signals, issue creation/dispatch, run state, artifacts/verification, PR metadata/review link, and assistant message send. Keep desktop project-loop UI where useful; mobile routes must be functional and responsive. Resolve route/package/lock conflicts, run web tests/typecheck/build and integrated backend/agent smoke, then update PR #16 rather than opening a competing final integration PR.
puter closed this issue 2026-07-27 09:47:44 +00:00
Sign in to join this conversation.
No Label
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: puter/zopu-code#17
No description provided.