vibe64 0.1.32 → 0.1.34

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (294) hide show
  1. package/bin/run.js +1717 -1648
  2. package/bin/server.js +81 -68
  3. package/bin/upgrade-state.js +5438 -5189
  4. package/dist/assets/{GithubBrowserTabs-2bEGbRAs.js → GithubBrowserTabs-DO5PHon-.js} +1 -1
  5. package/dist/assets/GithubMarkdown-BQ6MfCDJ.js +3 -0
  6. package/dist/assets/GithubMarkdown-U7-j-qNI.css +1 -0
  7. package/dist/assets/StudioErrorNotice-sQfmeR-z.js +1 -0
  8. package/dist/assets/VAlert-P256xaE0.js +1 -0
  9. package/dist/assets/VAutocomplete-BDb95qJX.js +1 -0
  10. package/dist/assets/VAvatar-9ilDR2r2.css +1 -0
  11. package/dist/assets/VAvatar-DPzqDH4r.js +1 -0
  12. package/dist/assets/VBtn-B2MBK2DL.js +1 -0
  13. package/dist/assets/VCard-mXy0k4aS.js +1 -0
  14. package/dist/assets/VCheckbox-C7A1ZW4D.js +1 -0
  15. package/dist/assets/VChip-CcI-Oo2J.js +1 -0
  16. package/dist/assets/VDialog-Bu3EfKb1.js +1 -0
  17. package/dist/assets/VDivider-BMEqUoAB.js +1 -0
  18. package/dist/assets/VExpansionPanels-Dgjrop0V.js +1 -0
  19. package/dist/assets/VMenu-C_x18lwb.js +1 -0
  20. package/dist/assets/VOverlay-CeMZurIN.js +1 -0
  21. package/dist/assets/VRadioGroup-CUu2-KIP.js +1 -0
  22. package/dist/assets/VRow-Cpw7OHQV.js +1 -0
  23. package/dist/assets/{VSelect-DY-ZuBJJ.js → VSelect-DL3HaA5m.js} +1 -1
  24. package/dist/assets/VSheet-DZWsu0kL.js +1 -0
  25. package/dist/assets/VSkeletonLoader-CttxM1tw.js +1 -0
  26. package/dist/assets/VSpacer-Dhmsvk4t.js +1 -0
  27. package/dist/assets/{VSwitch-Bm1bwl2V.js → VSwitch-BRHeDJkH.js} +1 -1
  28. package/dist/assets/VTextField-BR2eZeFT.js +1 -0
  29. package/dist/assets/VTextarea-DbqamXJd.js +1 -0
  30. package/dist/assets/Vibe64AsyncModuleState-Dx7YKRPp.js +1 -0
  31. package/dist/assets/Vibe64DashboardBackButton-DD9UR77P.css +1 -0
  32. package/dist/assets/Vibe64DashboardBackButton-yE6cyYg2.js +1 -0
  33. package/dist/assets/Vibe64DashboardPageHeader-BXQR00HK.js +1 -0
  34. package/dist/assets/Vibe64DashboardPageHeader-Gm1IvlHx.css +1 -0
  35. package/dist/assets/Vibe64DashboardShell-CuCVMhOc.js +1 -0
  36. package/dist/assets/Vibe64DashboardShell-MBkUHjs-.css +1 -0
  37. package/dist/assets/Vibe64DatabaseWorkspace-BONJdxBS.js +18 -0
  38. package/dist/assets/{Vibe64DatabaseWorkspace-C39Jvver.css → Vibe64DatabaseWorkspace-CR4pzzcf.css} +1 -1
  39. package/dist/assets/Vibe64OutputControls-DAAmA09l.js +8 -0
  40. package/dist/assets/{Vibe64OutputControls-CsZFv12r.css → Vibe64OutputControls-DPBsyDZM.css} +1 -1
  41. package/dist/assets/{Vibe64RepositoryWorkspace-ebUaYOU4.js → Vibe64RepositoryWorkspace-ByQlZbyO.js} +2 -2
  42. package/dist/assets/{Vibe64RepositoryWorkspace-Cqm6TOFk.css → Vibe64RepositoryWorkspace-CVHcT93M.css} +1 -1
  43. package/dist/assets/Vibe64SessionFiles-B0u9HKdF.js +107 -0
  44. package/dist/assets/Vibe64SessionFiles-NjOMVwPR.css +1 -0
  45. package/dist/assets/Vibe64TemporaryAiFixAction-BGlcrq4d.js +1 -0
  46. package/dist/assets/Vibe64UiStoryboardView-3WXph5bz.css +1 -0
  47. package/dist/assets/Vibe64UiStoryboardView-Brlwdvqi.js +7 -0
  48. package/dist/assets/Vibe64UnavailableSessions-zwlWlcZD.js +1 -0
  49. package/dist/assets/_sessionId_-CvOkQbVy.js +1 -0
  50. package/dist/assets/{_sessionTool_-B39BIzzZ.js → _sessionTool_-Dwod5ns9.js} +1 -1
  51. package/dist/assets/_slug_-B31c15cc.css +1 -0
  52. package/dist/assets/_slug_-Dy35qLo1.js +1 -0
  53. package/dist/assets/access-BVu5XYm2.js +1 -0
  54. package/dist/assets/app-DRXCcv05.css +1 -0
  55. package/dist/assets/app-zt7HwQKT.js +1 -0
  56. package/dist/assets/assistantRouting-CwbwfkwB.js +3 -0
  57. package/dist/assets/{changes-ByjS7QGx.js → changes-olY8cnFK.js} +1 -1
  58. package/dist/assets/{client-C-tpoG6F.js → client-BrV4QPwG.js} +1 -1
  59. package/dist/assets/createSimpleFunctional-CZTGuNuR.js +1 -0
  60. package/dist/assets/dashboard-BnXD-H4R.js +1 -0
  61. package/dist/assets/definitions-DaOPIkyB.js +1 -0
  62. package/dist/assets/env-DJhnLOH7.css +1 -0
  63. package/dist/assets/env-DN0vW4EI.js +1 -0
  64. package/dist/assets/{error-DFKtZBJ8.js → error-DgrgRbJJ.js} +1 -1
  65. package/dist/assets/{error-DE4zo8Lk.js → error-Dug56can.js} +1 -1
  66. package/dist/assets/health-7oIQODer.css +1 -0
  67. package/dist/assets/health-Z6m96GDr.js +1 -0
  68. package/dist/assets/history-BOwbCRQP.css +1 -0
  69. package/dist/assets/history-BxlpB-YH.js +1 -0
  70. package/dist/assets/incoming-BOxRVlOM.js +2 -0
  71. package/dist/assets/incoming-DWDrmxyH.css +1 -0
  72. package/dist/assets/index-BUq-MczL.js +86 -0
  73. package/dist/assets/{index-D4MsP3dq.css → index-DtmBqE3h.css} +1 -1
  74. package/dist/assets/{integrations-B4txOZfY.js → integrations-BFltGDVI.js} +1 -1
  75. package/dist/assets/issues-1iS5zoed.js +1 -0
  76. package/dist/assets/issues-XnpGgdmn.css +1 -0
  77. package/dist/assets/layout-BkWVNT37.js +1 -0
  78. package/dist/assets/lazy-NHSwD9FS.js +1 -0
  79. package/dist/assets/mdi-C54lQ0i_.js +1 -0
  80. package/dist/assets/{pages-BW2l8fNe.js → pages-DuMgH61T.js} +1 -1
  81. package/dist/assets/{placement-JxzrmUR3.js → placement-CwTqWLQH.js} +1 -1
  82. package/dist/assets/placement-DLsU3pCW.js +1 -0
  83. package/dist/assets/pull-requests-BJOwNL4k.js +1 -0
  84. package/dist/assets/pull-requests-CdbhyFOv.css +1 -0
  85. package/dist/assets/{repository-BTC3lkrh.js → repository-JWLVST3D.js} +1 -1
  86. package/dist/assets/{VAvatar-CAFvgSUo.js → ripple-BVltMmyV.js} +2 -2
  87. package/dist/assets/ripple-DqhAt1Ze.css +1 -0
  88. package/dist/assets/runtime-core.esm-bundler-DGXg_mpN.js +3 -0
  89. package/dist/assets/{session-CG-TUCJt.css → session-5qADMzDP.css} +1 -1
  90. package/dist/assets/session-C5Nj8Dlq.js +1 -0
  91. package/dist/assets/settings-BopLnpB0.css +1 -0
  92. package/dist/assets/settings-c273Ikrm.js +1 -0
  93. package/dist/assets/ssrBoot-Rlh6kLbD.js +1 -0
  94. package/dist/assets/{studioGateApi-C0GvzVlt.js → studioGateApi-DhA9IJGZ.js} +1 -1
  95. package/dist/assets/{studioUrls-CIab-Axb.js → studioUrls-Dj8rXeXO.js} +1 -1
  96. package/dist/assets/{useApi-BPuI6ZR9-Dr8wK_Co.js → useApi-BPuI6ZR9-CFWU1m37.js} +1 -1
  97. package/dist/assets/useArchivedVibe64Sessions-CVZx2Rtm.js +1 -0
  98. package/dist/assets/useCommand-DWuxfAV0.js +1 -0
  99. package/dist/assets/useEndpointResource-MWVNfmMa.js +1 -0
  100. package/dist/assets/{usePaths-DVTieF_G.js → usePaths-Db88-HOm.js} +1 -1
  101. package/dist/assets/{useUiFeedback-Tzi-PRlX.js → useUiFeedback-0FqKuZRP.js} +1 -1
  102. package/dist/assets/useVibe64ConversationLog-8cKh1eDm.js +1 -0
  103. package/dist/assets/useVibe64DatabaseTools-BcRG1s3i.js +1 -0
  104. package/dist/assets/useVibe64LearningMode-Bl0dGdCh.js +28 -0
  105. package/dist/assets/useVibe64LearningMode-C3PcXdVg.css +1 -0
  106. package/dist/assets/useVibe64ProjectScope-DOEVkBqX.js +1 -0
  107. package/dist/assets/useVibe64SessionData-DFTyLzci.js +1 -0
  108. package/dist/assets/useVibe64SessionSelection-j9lsllx4.js +1 -0
  109. package/dist/assets/useVibe64SystemGraph-tNkIwSBQ.js +1 -0
  110. package/dist/assets/{useVibe64Terminal-C2XJ9Y1K.js → useVibe64Terminal-BPnN25WH.js} +1 -1
  111. package/dist/assets/vibe64AssistantHost-DdE_-lZF.js +1 -0
  112. package/dist/assets/vibe64LessonDashboard-DlKYjisq.js +1 -0
  113. package/dist/assets/vibe64ProjectScope.local-DqT6e5un.js +1 -0
  114. package/dist/assets/vibe64RepositoryRealtime-DXk0Jai3.js +1 -0
  115. package/dist/assets/vibe64SessionFocus-OJ2toBd9.css +1 -0
  116. package/dist/assets/vibe64SessionFocus-kqPOPaOH.js +1 -0
  117. package/dist/assets/{vibe64SessionInfo-D8l22MFm.js → vibe64SessionInfo-BHxtTrLX.js} +1 -1
  118. package/dist/assets/vibe64SessionToolDefinitions-NfLd1HZI.js +1 -0
  119. package/dist/assets/vue-flow-core-BlVEnES8.js +26 -0
  120. package/dist/index.html +51 -48
  121. package/docs/colleague-usage/account-profile-and-appearance.md +29 -0
  122. package/docs/colleague-usage/ai-accounts-and-routing.md +23 -4
  123. package/docs/colleague-usage/ai-balance-and-allowance.md +4 -0
  124. package/docs/colleague-usage/architecture-explanations.md +99 -0
  125. package/docs/colleague-usage/auto-workflow.md +49 -11
  126. package/docs/colleague-usage/coding-agent-failures.md +94 -0
  127. package/docs/colleague-usage/coding-agent-goal-pause.md +110 -0
  128. package/docs/colleague-usage/coding-agent-goals.md +140 -38
  129. package/docs/colleague-usage/coding-agent-history.md +20 -2
  130. package/docs/colleague-usage/coding-agent-recovery.md +136 -0
  131. package/docs/colleague-usage/coding-agents.md +138 -150
  132. package/docs/colleague-usage/colleague-recovery.md +28 -5
  133. package/docs/colleague-usage/colleague-upgrade-recovery.md +4 -0
  134. package/docs/colleague-usage/colleague-watches.md +84 -0
  135. package/docs/colleague-usage/colleague.md +18 -34
  136. package/docs/colleague-usage/connected-contributions.md +196 -0
  137. package/docs/colleague-usage/connected-projects.md +196 -0
  138. package/docs/colleague-usage/conversation-context.md +67 -1
  139. package/docs/colleague-usage/dashboard-navigation.md +79 -5
  140. package/docs/colleague-usage/database.md +11 -0
  141. package/docs/colleague-usage/developing-vibe64.md +137 -0
  142. package/docs/colleague-usage/development-copies.md +20 -0
  143. package/docs/colleague-usage/development-env.md +34 -0
  144. package/docs/colleague-usage/file-interfaces.md +156 -0
  145. package/docs/colleague-usage/github-work.md +88 -1
  146. package/docs/colleague-usage/health-checks.md +32 -0
  147. package/docs/colleague-usage/incoming-changes.md +94 -0
  148. package/docs/colleague-usage/learning-chat-retention.md +11 -2
  149. package/docs/colleague-usage/learning-code-questions.md +55 -0
  150. package/docs/colleague-usage/learning-course-catalogue.md +118 -0
  151. package/docs/colleague-usage/learning-diagrams-and-voice.md +97 -0
  152. package/docs/colleague-usage/learning-history.md +17 -9
  153. package/docs/colleague-usage/learning-lesson-watch.md +95 -0
  154. package/docs/colleague-usage/learning-mode-ui.md +187 -85
  155. package/docs/colleague-usage/learning-native-session.md +12 -10
  156. package/docs/colleague-usage/learning-practical-exercises.md +71 -0
  157. package/docs/colleague-usage/learning-practical-gestures.md +18 -1
  158. package/docs/colleague-usage/learning-practice-projects.md +55 -4
  159. package/docs/colleague-usage/learning-session-creation.md +7 -7
  160. package/docs/colleague-usage/learning-teacher-guide.md +52 -0
  161. package/docs/colleague-usage/learning-with-colleague.md +59 -80
  162. package/docs/colleague-usage/lesson-authoring.md +12 -4
  163. package/docs/colleague-usage/lesson-practical-assessment.md +3 -1
  164. package/docs/colleague-usage/managed-app-access.md +6 -0
  165. package/docs/colleague-usage/message-delivery-recovery.md +56 -0
  166. package/docs/colleague-usage/plans.md +14 -7
  167. package/docs/colleague-usage/preview-browser-checks.md +61 -0
  168. package/docs/colleague-usage/preview-lesson-presentation.md +56 -0
  169. package/docs/colleague-usage/preview-starting-application.md +92 -0
  170. package/docs/colleague-usage/preview.md +70 -96
  171. package/docs/colleague-usage/project-architecture.md +229 -0
  172. package/docs/colleague-usage/project-language-tools.md +31 -0
  173. package/docs/colleague-usage/project-messages.md +106 -0
  174. package/docs/colleague-usage/project-settings.md +22 -0
  175. package/docs/colleague-usage/project-setup.md +29 -2
  176. package/docs/colleague-usage/session-terminal.md +42 -0
  177. package/docs/colleague-usage/sessions.md +122 -52
  178. package/docs/colleague-usage/teaching-content.md +12 -6
  179. package/docs/colleague-usage/temporary-chat-context.md +29 -0
  180. package/docs/colleague-usage/temporary-chats.md +95 -2
  181. package/docs/colleague-usage/voice-chat.md +10 -43
  182. package/docs/colleague-usage/voice-face-and-speaking-voice.md +73 -0
  183. package/docs/colleague-usage/workspace-preparation.md +89 -0
  184. package/docs/training-content.md +208 -7
  185. package/node_modules/@jskit-ai/assistant-core/package.json +1 -1
  186. package/node_modules/@jskit-ai/assistant-runtime/README.md +29 -0
  187. package/node_modules/@jskit-ai/assistant-runtime/package.json +1 -1
  188. package/node_modules/@jskit-ai/assistant-voice/package.json +1 -1
  189. package/node_modules/@jskit-ai/connector-google-calendar/package.json +1 -1
  190. package/node_modules/@jskit-ai/connectors-catalog/package.json +1 -1
  191. package/node_modules/@jskit-ai/connectors-core/package.json +1 -1
  192. package/node_modules/@jskit-ai/http-runtime/package.json +1 -1
  193. package/node_modules/@jskit-ai/kernel/package.json +1 -1
  194. package/node_modules/@jskit-ai/payments-core/package.json +1 -1
  195. package/node_modules/@jskit-ai/realtime/package.json +1 -1
  196. package/node_modules/@jskit-ai/resource-core/package.json +1 -1
  197. package/node_modules/@jskit-ai/resource-crud-core/package.json +1 -1
  198. package/node_modules/@jskit-ai/uploads-runtime/package.json +1 -1
  199. package/node_modules/@local/vibe64-core/package.json +1 -0
  200. package/node_modules/@local/vibe64-execution/src/host/execHelper.js +280 -272
  201. package/node_modules/@local/vibe64-genesis/README.md +15 -0
  202. package/node_modules/@local/vibe64-genesis/bin/vibe64-genesis-host-context +879 -1225
  203. package/node_modules/@local/vibe64-genesis/package.json +2 -1
  204. package/node_modules/@local/vibe64-genesis/src/server/index.js +496 -418
  205. package/node_modules/@local/vibe64-genesis/src/server/promptContext.js +165 -146
  206. package/node_modules/@local/vibe64-runtime/src/server/agentSessionCommandHook.js +8 -8
  207. package/node_modules/@local/vibe64-runtime/src/server/codexAppServerProcess.js +128 -129
  208. package/node_modules/@local/vibe64-system-graph/README.md +136 -6
  209. package/node_modules/@local/vibe64-terminals/package.json +3 -0
  210. package/node_modules/@local/vibe64-terminals/src/server/sessionWorkOperationCommand.js +1527 -1326
  211. package/node_modules/@local/vibe64-training/package.json +6 -1
  212. package/node_modules/@local/vibe64-voice/package.json +1 -0
  213. package/package.json +16 -16
  214. package/server.bundle.mjs +42853 -40268
  215. package/dist/assets/StudioErrorNotice-Ccjvcn9C.js +0 -1
  216. package/dist/assets/VAlert-B7ciJKQL.js +0 -1
  217. package/dist/assets/VAutocomplete-QjMk5d_j.js +0 -1
  218. package/dist/assets/VAvatar-nHaK192T.css +0 -1
  219. package/dist/assets/VBtn-Kl_qcBsy.js +0 -1
  220. package/dist/assets/VCard-nrJPeo91.js +0 -1
  221. package/dist/assets/VCheckbox-DTRAWOIf.js +0 -1
  222. package/dist/assets/VChip-Dfs5jX0f.js +0 -1
  223. package/dist/assets/VDialog-Dt1VjJg1.js +0 -1
  224. package/dist/assets/VDivider-DFsS0OTx.js +0 -1
  225. package/dist/assets/VExpansionPanels-CYKU0cAr.js +0 -1
  226. package/dist/assets/VMenu-BLxobsuU.js +0 -1
  227. package/dist/assets/VOverlay-BvFVZKNS.js +0 -1
  228. package/dist/assets/VRadioGroup-DzQzpCfg.js +0 -1
  229. package/dist/assets/VRow-BR2RMCM1.js +0 -1
  230. package/dist/assets/VSheet-BA95RNmA.js +0 -1
  231. package/dist/assets/VSkeletonLoader-hpJqr0HL.js +0 -1
  232. package/dist/assets/VSpacer-B1l1hVvU.js +0 -1
  233. package/dist/assets/VTextField-CA_p3N4d.js +0 -1
  234. package/dist/assets/VTextarea-NyCqY4h5.js +0 -1
  235. package/dist/assets/Vibe64AsyncModuleState-DEFlqJ97.js +0 -1
  236. package/dist/assets/Vibe64DashboardShell-BNv2I-P8.js +0 -1
  237. package/dist/assets/Vibe64DashboardShell-w20wNTGW.css +0 -1
  238. package/dist/assets/Vibe64DatabaseWorkspace-CuY5lN1o.js +0 -43
  239. package/dist/assets/Vibe64OutputControls-D2JuYlYU.js +0 -8
  240. package/dist/assets/Vibe64SessionFiles-C-rWehq_.js +0 -34
  241. package/dist/assets/Vibe64SessionFiles-Dsr6KQNP.css +0 -1
  242. package/dist/assets/Vibe64SubsystemsView-BvdU_o6H.css +0 -1
  243. package/dist/assets/Vibe64SubsystemsView-DJCjSzQM.js +0 -1
  244. package/dist/assets/Vibe64SystemWorldView-B91ioQaO.js +0 -4312
  245. package/dist/assets/Vibe64SystemWorldView-BXiQ7_Qb.css +0 -1
  246. package/dist/assets/Vibe64UnavailableSessions-OvnoD3ZB.js +0 -1
  247. package/dist/assets/_sessionId_-JTvMh54L.js +0 -1
  248. package/dist/assets/_slug_-DP_heCDa.js +0 -1
  249. package/dist/assets/_slug_-DmBZGb0q.css +0 -1
  250. package/dist/assets/access-C8GQIS19.js +0 -1
  251. package/dist/assets/app-B83lF61Y.js +0 -1
  252. package/dist/assets/app-ByLIQ3SB.css +0 -1
  253. package/dist/assets/assistantRouting-TDtryU6o.js +0 -1
  254. package/dist/assets/createSimpleFunctional-DPIT6zsT.js +0 -1
  255. package/dist/assets/dashboard-CWGFPojJ.js +0 -1
  256. package/dist/assets/definitions-BeLcvOW3.js +0 -1
  257. package/dist/assets/display-BLmcO-5p.js +0 -1
  258. package/dist/assets/env-7bqFyF_E.css +0 -1
  259. package/dist/assets/env-BVwxNL8M.js +0 -1
  260. package/dist/assets/health-BzNhp7r8.js +0 -1
  261. package/dist/assets/health-DoHTXTGx.css +0 -1
  262. package/dist/assets/history-BPeZGofK.js +0 -1
  263. package/dist/assets/history-iMQxp5AR.css +0 -1
  264. package/dist/assets/httpClient-BaaZuFvF.js +0 -1
  265. package/dist/assets/index-5sKwLHOH.js +0 -86
  266. package/dist/assets/issues-DCEhGlfn.css +0 -1
  267. package/dist/assets/issues-wby50y9b.js +0 -3
  268. package/dist/assets/layout-YCn17mK1.js +0 -1
  269. package/dist/assets/lazy-CvQfXeLg.js +0 -1
  270. package/dist/assets/mdi-C31_SZp-.js +0 -1
  271. package/dist/assets/placement-C4R2t6rl.js +0 -1
  272. package/dist/assets/pull-requests-BNK6mq2u.css +0 -1
  273. package/dist/assets/pull-requests-lNQAigaC.js +0 -1
  274. package/dist/assets/runtime-core.esm-bundler-DMrccYS5.js +0 -3
  275. package/dist/assets/session-D38nzG41.js +0 -1
  276. package/dist/assets/settings-CFyUJ_kR.js +0 -1
  277. package/dist/assets/settings-vWsAEoE9.css +0 -1
  278. package/dist/assets/useArchivedVibe64Sessions-C2DSq2Z4.js +0 -1
  279. package/dist/assets/useCommand-BzThFLYP.js +0 -1
  280. package/dist/assets/useEndpointResource-C2KD4Ub_.js +0 -1
  281. package/dist/assets/useVibe64ConversationLog-CMUlXJtU.js +0 -1
  282. package/dist/assets/useVibe64DatabaseTools-DBcKhm6B.js +0 -1
  283. package/dist/assets/useVibe64LearningMode-BPRWM5Rp.js +0 -28
  284. package/dist/assets/useVibe64LearningMode-PJUv0O25.css +0 -1
  285. package/dist/assets/useVibe64SessionData-CdtJbAIx.js +0 -1
  286. package/dist/assets/useVibe64SessionSelection-aR0f6xVT.js +0 -1
  287. package/dist/assets/useVibe64SystemGraph-DeTPBn0e.js +0 -1
  288. package/dist/assets/vibe64AssistantHost-Dgyz4TrT.js +0 -1
  289. package/dist/assets/vibe64ProjectScope.local-GOSMVDRi.js +0 -1
  290. package/dist/assets/vibe64RepositoryRealtime-t5Al8BlU.js +0 -1
  291. package/dist/assets/vibe64SessionFocus-CcN6Grgw.js +0 -1
  292. package/dist/assets/vibe64SessionFocus-ChabllPA.css +0 -1
  293. package/dist/assets/vibe64SessionToolDefinitions-BaO1DEup.js +0 -1
  294. /package/dist/assets/{vibe64RepositoryRealtime-D_mq1dFE.css → Vibe64TemporaryAiFixAction-D_mq1dFE.css} +0 -0
@@ -28,12 +28,27 @@ restoration failed: ask the coding agent to recover the managed browser run
28
28
  before using Preview. Colleague can inspect output status and explain recovery;
29
29
  it must not claim the normal app is restored from a test exit code alone.
30
30
 
31
+ Use **Suspend preview**, beside the circular **Reload preview** button, to unload
32
+ only this displayed page and reduce browser CPU use. Unsaved changes inside the
33
+ page may be lost. The app server, coding agents and goals continue running;
34
+ other Preview windows are unaffected. **Resume preview** reopens the saved route
35
+ with the existing app identity. The suspended page also shows a Resume button.
36
+ Switching to **Dashboard** and back keeps it suspended. This choice belongs to
37
+ this Preview instance; it does not suspend a different session. Suspending an outer Preview also unloads any
38
+ nested pages inside it. Colleague can explain the control; the person operates
39
+ it in their browser.
40
+
31
41
  Open the project's **Preview** tab. On mobile, use **Show project** from chat,
32
42
  then **Show preview controls** to expand the toolbar. If the selected output needs settings,
33
43
  choose **Preview options**, fill the required fields and choose **Run**.
34
44
  **Remember for this project** saves those ordinary settings in this browser for
35
45
  future sessions. **Cancel** leaves the current run alone.
36
46
 
47
+ Preview checks the current output, workspace setup and resource declarations
48
+ together. Later checks reread changes to those declarations. Invalid resource
49
+ estimates retain their diagnostic and generic fallback; they do not by themselves
50
+ make an otherwise valid output unavailable.
51
+
37
52
  If the previewed application shows its own login screen, enter that application's
38
53
  credentials. Its login and realtime connection run through the Preview address.
39
54
  HTTPS previews retain the HTTPS scheme for applications that use it to set
@@ -43,6 +58,12 @@ and page navigation, so opening the editor on `localhost` also works. If a tab
43
58
  shows an expired Preview access error after a restart, use **Reload preview**
44
59
  to obtain its current address.
45
60
 
61
+ Longer application requests keep the same Preview idle allowance when an HTTP
62
+ connection is reused. If a save or archive still reports a connection error,
63
+ check its resulting state before retrying: losing the reply does not prove the
64
+ operation failed. Colleague can help inspect the state through its supported
65
+ actions; it must not repeat an uncertain write automatically.
66
+
46
67
  Preview lets the application request your microphone and play audio. Use its
47
68
  microphone control and allow access when your browser asks. Permission is still
48
69
  your choice; embedding an app does not grant it automatically. Use HTTPS for
@@ -50,6 +71,12 @@ remote previews or localhost on your own machine. If you denied access, change
50
71
  the site's microphone permission in the browser and retry. Colleague can explain
51
72
  these steps but cannot grant browser permission or record on your behalf.
52
73
 
74
+ While **Preparing workspace** is running, Preview waits before reading or starting
75
+ the app. Use **Expand** on the preparation card to inspect progress and logs.
76
+ Preview checks the app automatically when setup finishes. If setup fails, its
77
+ failure stays visible; fix the cause and use the preparation card's **Retry**.
78
+ Errors that remain after setup finishes are still reported as Preview errors.
79
+
53
80
  If automatic Preview opening meets a busy exercise preparation or assistant write
54
81
  operation, it waits and retries the same Preview through the existing cooldown.
55
82
  The message says **Waiting for the current workspace operation to finish. Preview
@@ -61,6 +88,33 @@ retry after you inspect the failure.
61
88
  application again. If startup fails, inspect the message and **Show run output**
62
89
  before retrying. Hiding run output closes only the terminal view; it does not
63
90
  stop the application.
91
+ The top Preview toolbar shows **Stop preview** while the application is running.
92
+ Stop waits for the application's owned work and managed browser to close; it
93
+ does not close the coding session, chat, source checkout or shared services.
94
+ On managed hosts, service cleanup runs before remaining processes are terminated.
95
+ Wait for Stop to finish; a cleanup failure is not a successful stop.
96
+ Stopping Preview closes its browser process but keeps the coding assistant's
97
+ managed-browser registration. The same assistant can run another managed browser
98
+ check or test suite afterward without reopening its conversation.
99
+ It stays stopped after navigation, reload or reopening the session. Use the
100
+ toolbar's **Start preview** or **Restart preview** deliberately to run it again.
101
+
102
+ A Preview also stops when the platform restarts, for example during an update.
103
+ The pane then removes the old page instead of leaving it looking alive. It shows
104
+ **Preview state was lost after a server restart** with **Restart preview**, or,
105
+ once that has been seen, **Preview is not running** with a **Start preview**
106
+ button in the middle of the pane. Starting it runs the session's current code.
107
+ If Stop reports incomplete cleanup, retry Stop before starting. Browser tests
108
+ may temporarily run an isolated target, then restore the prior stopped choice.
109
+ Managed suites without `--target` also restore the previous running or stopped
110
+ Preview state, including after an assertion failure or cancellation. An explicitly
111
+ supplied external `PLAYWRIGHT_BASE_URL` does not start or stop managed Preview.
112
+ The selected target and its parameter values remain saved while stopped, including
113
+ after browser tests or an editor restart, for the next explicit Start.
114
+ If Preview reports an invalid saved stop state, use the explicit Stop action
115
+ before retrying Start; automatic recovery does not overwrite that state.
116
+ Colleague can offer the existing authorized stop/start actions, but a how-to
117
+ question alone does not authorize either action.
64
118
  Retrying the same output reuses its running application when its settings and
65
119
  environment still match. It does not start another process merely because a
66
120
  new Preview address could be allocated. Use **Restart preview** when you intend
@@ -81,6 +135,12 @@ have separate Preview addresses. Use the current editor’s **Preview** controls
81
135
  an address from a discarded environment is no longer valid. No namespace or port
82
136
  field is required. Colleague uses the current Preview result rather than
83
137
  constructing an address.
138
+ An HTTPS Preview can also appear inside another editor's iframe. Its first
139
+ navigation saves a secure Preview cookie, then removes the token from the address;
140
+ the nested app should load without a token error. If the browser blocks that
141
+ cookie, open the Preview in its own tab and ask the coding agent to check the
142
+ browser's cookie policy and the current Preview address. Colleague can explain
143
+ those steps but cannot change the browser's cookie settings.
84
144
  If two temporary editors show the same address, their host routing configuration
85
145
  needs correction. Restart the affected Previews after the host update; changing
86
146
  an application's listening port is not required.
@@ -98,102 +158,16 @@ and reopen the project. Save work as needed before doing so; this stops the othe
98
158
  sessions’ running tools too. A failed Close reports cleanup failure. Do not claim
99
159
  resources were released until Close succeeds. Colleague can explain the result
100
160
  and use the existing authorized project-close action; it does not execute shell
101
- commands or invent application-specific teardown steps.
161
+ commands or invent application-specific teardown steps. If shared services were
162
+ cleaned up but another close controller failed, the project remains open and
163
+ Preview can start those services again; retry Close after addressing the reported
164
+ controller.
102
165
 
103
166
  ## Browser checks from chat
104
167
 
105
- Ask the coding agent in chat to test the running application in a browser and
106
- specify the flow to check. The agent uses the session's managed browser tools;
107
- you do not need to provide an execution ID or change application code to enable
108
- them. Application login may still require your credentials or interaction.
109
-
110
- The coding agent runs managed test suites and live Preview browser checks one
111
- after the other. A suite owns Preview until its cleanup and restoration finish;
112
- the agent can read status and logs while waiting, then confirms there is no
113
- active test run and the restored Preview is ready before live inspection. This
114
- also applies after cancelling a suite. If restoration fails, ask the coding
115
- agent to recover that existing run before another check. **Test Preview**
116
- identifies the test environment while it is selected. Colleague can explain the
117
- sequence and offer coding-agent assistance through the existing chat controls.
118
- While a suite runs in the background, the coding agent waits on its existing
119
- execution and checks logs when output or state changes, rather than repeatedly
120
- reading unchanged logs between short waits.
121
- Where its command tool supports `yield_time_ms`, an empty progress wait uses
122
- `30000`; shorter waits are for interactive input or a specific immediate check.
123
-
124
- The coding agent can read `vibe64-helper playwright --help` before a project has
125
- browser tests or a matching test runtime. Help starts neither Preview nor a browser.
126
- An actual suite still requires the project's installed Playwright version and a
127
- matching managed runtime. A version error is a test-runtime blocker; interactive
128
- checks can use the existing managed Preview browser. Report the exact required
129
- version to the platform operator instead of installing a separate browser.
130
-
131
- Before a suite, the coding agent can run `vibe64-helper playwright readiness`.
132
- It distinguishes absent tests, uninstalled dependencies, an unsupported exact
133
- runtime and a supported installed dependency without starting Preview or a
134
- browser. `ready` confirms dependency/runtime availability, not passing tests or
135
- application readiness. `status` separately reports an active test run. Colleague
136
- can explain these outcomes and delegate investigation to the coding chat; it
137
- does not receive shell access through this guide.
138
-
139
- If the agent reports “Browser testing requires a live assistant execution owner,”
140
- the browser test did not start. This is an assistant runtime problem. After the
141
- host runtime has been fixed and restarted, send a new chat message asking the
142
- agent to retry the check. Colleague can explain this recovery and inspect Preview
143
- state through its existing actions; it does not receive shell or browser-test
144
- access from this guide.
145
-
146
- ## Lesson presentation in Preview
147
-
148
- When a host opens a declared lesson diagram, Preview offers **App preview** and
149
- **Colleague presentation**. App preview returns to the running application;
150
- Colleague presentation shows the same retained diagram. Switching changes neither
151
- the application process nor its frame. **Minimise presentation** returns to the
152
- application while retaining the diagram; **Restore presentation** brings it back.
153
- On phones, return to the workspace from Colleague to use these same Preview choices.
154
-
155
- The host reads your pinned diagram for your signed-in lesson attempt even while
156
- its exercise project is selected. You need not leave the project to load it. If
157
- loading fails, use **Reload presentation** for the same attempt; do not start a
158
- new lesson or treat the failure as an assessment result.
159
-
160
- Hiding a diagram pauses its motion when its declared controller supports pause.
161
- Showing it does not replay a transition automatically. A diagram failure offers
162
- **Reload diagram**; a failed resource read offers **Reload presentation**, which
163
- reads the same attempt and declared visual again. Neither recovery grades an
164
- assessment or changes the lesson version. Missing or changed pinned content needs
165
- the owner's normal recovery. Colleague's visual commands become available only
166
- when the host supplies authenticated resource delivery and browser acknowledgement;
167
- this Preview composition alone does not activate those tools or synchronise speech.
168
-
169
- With the authenticated host connected, you can ask Colleague to show a declared
170
- lesson visual or demonstrate its next step. It uses your saved prepared exercise
171
- and waits for the diagram to be ready or the transition to finish. Ask it to read
172
- the displayed diagram state if you are unsure. If the browser disconnects or the
173
- exercise view changes, reopen the same lesson and retry deliberately; a missing
174
- acknowledgement is not proof the transition failed, so keep the original command
175
- identity on a retry. These commands do not mark learner work correct or prove
176
- spoken narration finished.
177
-
178
- ### Diagram explanations and sound
179
-
180
- A host-enabled teaching cue first shows the declared diagram, then uses one final
181
- Colleague explanation. Its motion starts when that explanation actually becomes
182
- audible. Tool progress is not narration. With spoken replies off, read the final
183
- explanation and press **Continue** to watch. If sound has not started, **Play diagram
184
- without sound** is an explicit alternative; sound failure also offers Continue.
185
- Neither option pretends that audio played.
186
-
187
- Hiding Preview, changing the exercise, reloading its diagram or stopping the
188
- explanation retires the current cue. Supported motion pauses and its semantic
189
- state remains readable; showing Preview alone does not replay it. Deliberately
190
- hiding the diagram interrupts sound only while this cue's exact explanation is
191
- still audible. The normal voice stop also clears queued speech for that same
192
- voice binding; it does not pause audio for later resumption. Minimising Colleague
193
- alone keeps voice playing, and a newer answer or another conversation is never
194
- stopped by this diagram control. Ask Colleague to repeat the explanation explicitly
195
- when needed. Colleague waits for the actual
196
- diagram and required audio completion receipt before another teaching cue or
197
- question. An unconfirmed receipt needs its current status checked, not an inferred
198
- pass or automatic replay. On phones, opening a teaching presentation minimises
199
- Colleague's frame while retaining the conversation, microphone and typed draft.
168
+ For managed browser checks, test ownership and recovery, read
169
+ [Browser checks from chat](preview-browser-checks.md).
170
+
171
+ For lesson diagrams shown over Preview, see [Lesson presentation in Preview](preview-lesson-presentation.md).
172
+
173
+ To choose which application Preview starts, see [Choose a starting application](preview-starting-application.md).
@@ -0,0 +1,229 @@
1
+ # Browse your project's architecture
2
+
3
+ Open **Dashboard → Architecture**. The sheet shows UI pages, screens or scenes
4
+ above the Engine subsystem map. UI parents sit above their children; registered
5
+ web routes show their host-relative paths. Independent roots remain independent.
6
+ Hierarchy comes from recorded navigation, including explicit registration and
7
+ filesystem routing when the selected technology uses it. Paths alone do not
8
+ prove a parent relationship.
9
+
10
+ Engine subsystems are circles showing a readable name, directory root, purpose,
11
+ available public declarations and measured source size. Declared application
12
+ entries say **Start here**. Supporting directories are subdued. Circle diameters
13
+ use a bounded logarithmic source-line scale: larger owners look larger, while
14
+ even tiny owners retain a readable minimum and huge owners cannot dominate
15
+ the canvas. Unknown source sizes receive the minimum. Source size does
16
+ not prove architectural importance. The map keeps every indexed source owner,
17
+ including directories outside Stack's default subsystem parents. The canonical
18
+ list and responsibilities come from `genesis/subsystems.md`; Architecture is the
19
+ single subsystem/Program view, replacing the older list screen. Each subsystem
20
+ has one directory root; a nested owner keeps its own files. The current map
21
+ does not impose layers or draw Engine import arrows.
22
+
23
+ **Shared libraries** form a fixed vertical stack on the right. The project must
24
+ designate them explicitly; a package name or many consumers does not make an
25
+ owner a library. **External dependencies**, farther right, lists observed direct
26
+ packages alphabetically. Select a package name to read its available public
27
+ declarations and import paths in a compact panel. Package internals stay opaque:
28
+ there is no source tree or invented source-line count. Close the panel with **×**.
29
+ Package and source-owner discovery belong to the selected analysers, so the
30
+ viewer needs no language or package-manager-specific controls.
31
+
32
+ For text ownership, generation triggers and freshness, see
33
+ [Where Architecture explanations come from](architecture-explanations.md).
34
+
35
+ ## Explore by zooming
36
+
37
+ 1. Click or tap a subsystem to enter with a smooth zoom. Alternatively,
38
+ place the pointer over it and scroll or pinch in. That initial
39
+ element owns the gesture even if the moving sheet puts a neighbour under the
40
+ pointer. The circle grows and moves towards the centre together.
41
+ 2. At reading size it becomes a square on the same canvas. A faint circle remains
42
+ behind it. A compact skeleton appears while the interface is prepared.
43
+ 3. **Explanation** shows the subsystem’s full authored responsibility inline.
44
+ The shortcuts follow reading order: **Explanation**, **Programs** when present,
45
+ **Interface**, then **Files**.
46
+ **Programs** lists its associated capabilities. Select a Program to open its
47
+ own compact view inside Architecture, with an opening preview, **Main source file**
48
+ and **Supporting files**. **Read full explanation** opens the complete authored
49
+ text in a separate scrollable dialog, filling the screen on phones. Close it
50
+ with **×**, Esc or a click outside on desktop to return to the unchanged Program
51
+ view. The subsystem list limits each Program preview to two lines. Click a source icon to open that file with the shared
52
+ Files viewer. A gold border, star and **Main · …** identify the mandatory main
53
+ source; supporting icons say **Part of · …**. A library can participate in
54
+ another subsystem’s Program without changing source ownership.
55
+ There are no links to the raw Genesis subsystem or Program documents here.
56
+ If Program descriptions need refresh, correct the authored declarations through
57
+ normal Files editing and use **Architecture options → Re-scan project**.
58
+ The subsystem responsibility stays readable while Program evidence is invalid.
59
+ **Interface** lists recorded functions, methods, components, values and types.
60
+ Select a signature to reach its implementation and exact declaration.
61
+ Unknown return information is omitted. Drag across text to select and copy it;
62
+ selecting signature text does not open the implementation.
63
+ 4. Graphical **Files** appear below the interface as soon as the selected
64
+ subsystem's detail is ready. Use the **Files** shortcut at the top to reach them immediately, or scroll down.
65
+ **Interface**, **Explanation** and **Programs** jump to their sections in the same retained document. Direct files appear before subdirectories at every level.
66
+ Open a folder's disclosure arrow; **Find a file** filters
67
+ names and paths and exposes matching folders. File bars and icon heights
68
+ compare measured source size within this subsystem. A dash means unavailable
69
+ size. Icons and extension labels distinguish file types. **Sort** offers
70
+ **Name**, **File type** and **Size · largest first**; unavailable sizes come
71
+ last. Folders remain alphabetical below files. Sorting retains folder state
72
+ and search. **Entry** marks a file with recorded boundary evidence; hover for details.
73
+ 5. Click or tap a file icon once, or focus it and press Enter. Only that
74
+ file's interface opens inside the square. Selecting a subsystem signature
75
+ likewise opens only its implementation file, with the requested declaration
76
+ selected. The project-wide Files workspace does not open.
77
+ 6. The file is a document with an **Explanation** field and **File exports**.
78
+ **Generate explanation** fills an empty field; **Update explanation** refreshes
79
+ saved text. Reopening displays the saved explanation directly, without a chat.
80
+ Select a callable signature to reveal its **Pseudocode** field and use
81
+ **Generate pseudocode**, **Update pseudocode** or **Code**. **Code · whole file**
82
+ uses the same editor, Save now, autosave, Undo/Redo and download controls as
83
+ Files, with its file browser hidden. **Interface** returns to the document.
84
+ **Part of …** and **Main Program file** open the dedicated Program view. Helper
85
+ progress and **Stop** stay in the field while generation runs. These cached
86
+ interpretations check saved source and remain informational; they do not change
87
+ Genesis documents or enter the coding agent's context.
88
+ See [Read file interfaces](file-interfaces.md).
89
+ 7. Scroll out on the uncovered canvas outside the square to return through the
90
+ enclosing views, or use the breadcrumb: **Engine → subsystem → Program → file**.
91
+ Inside the square, a mouse wheel, two-finger touchpad movement or a one-finger
92
+ phone swipe scrolls its contents. Reaching the top or bottom does not turn
93
+ scrolling into zoom. Pinch or Ctrl-scroll explicitly zooms anywhere, including
94
+ over file icons. Pinching changes magnification; opening a file uses a click
95
+ or tap. Zoom out never opens an icon or pulls a new target towards
96
+ the centre. Returning from a file restores the enclosing reading view before
97
+ its icon grew, keeping the square's surrounding canvas accessible. **×** at
98
+ the top right or Esc goes back one level; both retain the enclosing view's state.
99
+ Esc also works after generation temporarily releases keyboard focus.
100
+ A compact reminder beneath the breadcrumb shows these scroll, zoom and return rules.
101
+
102
+ **← Back**, **×** and Esc retrace Program and file links, including links to
103
+ another subsystem. Back restores the previous file and exact declaration, or
104
+ the Program and its source icons. With no nested view history,
105
+ it returns to the enclosing subsystem or map. **×** and Esc always close the
106
+ current level; breadcrumbs jump directly to their named view.
107
+
108
+ The map stays mounted while hidden, retaining its arrangement. The file browser
109
+ stays mounted behind a file interface, retaining its search, folder disclosures
110
+ and selection. The latest file viewer also stays mounted while hidden within
111
+ that subsystem, including behind a Program view. Re-entering a subsystem and interrupted gestures use the same
112
+ navigation. The file viewer reuses the sheet's analysis; hiding views suspends
113
+ their reads while retaining existing facts. A session change resets the local view. The square has compact
114
+ signature rows instead of equal-height cards. The square fits the canvas height;
115
+ long interfaces and file lists scroll inside it while the breadcrumb stays visible.
116
+ Resizing the window or chat divider keeps the open square visible, preserving
117
+ its zoom, scroll position and selected declaration. Returning through file links
118
+ uses the resized enclosing view.
119
+ Drag empty canvas outside the square to pan. There is no source-subsystem
120
+ side pane, extra toolbar row or pane-balance slider.
121
+
122
+ ## Read the API evidence
123
+
124
+ **Imported by other subsystems** identifies particular declarations named in
125
+ cross-boundary imports, with consumer counts. It does not prove runtime calls or
126
+ intended API membership. **Declared API** shows explicit package/module exports;
127
+ **Exports from externally used files** are exports from files imported across
128
+ the boundary; use of those individual exports is not established. **Other available exports** is collapsed initially and
129
+ can include internal or unused declarations. **Find a signature** searches these
130
+ groups. **Import paths** are the names another part imports to access the API, such as
131
+ `@local/vibe64-voice/client`. They explain how to reach an interface; the
132
+ signatures explain what it offers. They remain secondary detail.
133
+ Hover a group heading for its definition. Short notices keep missing intended
134
+ API and partial import coverage visible beside the signatures.
135
+
136
+ Expand **Imported by …** beneath a signature to see full paths of its importing
137
+ files. Click a path to open that file inside Architecture; **← Back**, **×** or Esc
138
+ returns to the signature list with the disclosure retained. The same disclosure
139
+ is available under **Other available exports** and **Declared API**. Imports within
140
+ the same subsystem are included; the group still reflects cross-boundary
141
+ classification. **No recorded imports** means the current analysis found none,
142
+ not that an export is unused. **Source file imported
143
+ by …** shows file-level evidence only: these consumers import the source file,
144
+ without proving that they import the particular export. These groups do not divide
145
+ public from private or used from unused. The list reflects recorded imports,
146
+ not every possible runtime consumer.
147
+
148
+ Missing declarations do not mean an empty API. Import coverage is shown explicitly;
149
+ namespace, dynamic, build-dependent or unresolved imports may remain partial.
150
+ Signatures link only when analysis identifies one implementation declaration;
151
+ re-export aliases retain their public name and lead to the original source.
152
+ External package declarations have no project source link.
153
+
154
+ Ordinary source indexing retains an unchanged UI map. If source or Stack changes
155
+ invalidate that evidence, **UI map needs refresh** offers **Re-scan project** to
156
+ run the project's configured inspector. Engine files remain browsable meanwhile.
157
+
158
+ A coding conversation can inspect source and propose corrections to the
159
+ subsystem responsibilities, public-operation explanations and boundary roots in
160
+ Genesis's editable Blueprint, Program and subsystem map. It can also author
161
+ Vibe64's **Architecture layout** Stack section: exact roots grouped for presentation, with explicitly designated libraries/support. This changes
162
+ presentation, not native ownership. Require source citations and separate
163
+ declared intent from observed usage when reviewing a proposal. An AI can
164
+ identify a directory root outside default Stack grouping; it must not invent
165
+ an owner or treat import counts as proof of responsibility.
166
+
167
+ ## Follow UI calls
168
+
169
+ UI-call arrows are hidden initially. Select a page to show only its evidenced
170
+ connections, including calls through components. Click empty canvas to clear
171
+ that focus. **Architecture options → Show all UI calls** shows every resolved
172
+ connection; **Hide UI calls** hides them. UI hierarchy connectors remain visible.
173
+
174
+ Purple arrows identify protocol, operation and receiving controller file. They
175
+ run from the page to that file's separate port on its subsystem's left edge.
176
+ Zoom into the receiving subsystem; **Receives UI calls** opens the corresponding
177
+ file. An exact controller declaration is selected when the inspector supplies
178
+ its identity. Otherwise the file's interface opens without guessing a function.
179
+ HTTP, RPC, WebSocket and local calls use the same validated observation contract.
180
+ Unresolved or ambiguous calls stay explicit; they never produce guessed arrows.
181
+ **UI calls not analysed** identifies unconfigured discovery. An absent arrow
182
+ does not prove that no runtime call exists.
183
+
184
+ ## Arrange, fit and refresh
185
+
186
+ Drag empty space to pan. **Fit** returns to the complete map. **Architecture
187
+ options** (**⋯**) contains **Fit UI**, **Fit Engine**, **Zoom in**, **Zoom out**, the
188
+ UI-call toggle, **Reset arrangement**, **Reload architecture** and **Re-scan project**. On mobile use the
189
+ top bar's **Show project** control if chat fills the screen, then use the same
190
+ menu, pinch and pan; folder and file controls remain keyboard accessible.
191
+ The existing chat divider controls workspace width.
192
+
193
+ Use a subsystem's **⠿** grip to arrange it within the application map. Ordinary
194
+ circle clicks open it. Left/Right arrow keys move a focused grip sideways.
195
+ Libraries and the dependency column retain their fixed side positions.
196
+ **Reset arrangement** restores analysis order. Arrangement is local to the
197
+ retained view and changes no source ownership or relationship.
198
+
199
+ Opening reads existing facts without running inspectors. A failed load shows
200
+ **Retry loading**; **Reload architecture** rereads existing snapshots. If a local
201
+ preview was restarted, reload its browser tab to reconnect. **Re-scan project**
202
+ rebuilds the whole project browsing index through Stack's declared finite inspectors.
203
+ Source parsing runs once; UI inspectors use that scan before Genesis checks
204
+ the inputs again and saves it. Previously loaded facts remain available during
205
+ the scan. Existing indexes are read as saved; opening a file never triggers it.
206
+ It reads existing Genesis documents; it does not rewrite Program or generate
207
+ file or function explanations. This project-wide action is in Architecture
208
+ options, never the file view. The running stage and elapsed seconds show what is happening.
209
+ Leaving Architecture does not stop the scan. Returning restores its original
210
+ elapsed time, and other viewers of that session see the same progress. While it
211
+ runs, **Cancel analysis** replaces **Re-scan project**; a racing second request
212
+ joins the existing scan instead of starting another one. Progress and completion
213
+ arrive through live updates. Returning or reconnecting rereads the server state,
214
+ including a failure that happened while the view was closed. Use **Reload
215
+ architecture** if a connection warning persists. Scan status lasts for the current
216
+ server process; it does not claim that an interrupted scan survived a server restart.
217
+ **Cancel analysis** waits for cleanup and preserves the previous valid index.
218
+ Large refreshes have a ten-minute request budget; inspectors retain their own
219
+ finite limits. Invalid output, changed source or missing prerequisites leaves
220
+ the previous index and an inline error. **Command output** shows bounded inspector
221
+ diagnostics; no second blocking dialog is opened. Correct the declaration/command or
222
+ finish preparation, then retry. Missing page evidence asks for Stack navigation
223
+ inputs and a technology inspector. An Engine-only project needs no UI pages.
224
+
225
+ Colleague can explain these controls and offer supported navigation through its
226
+ existing authorized actions. A how-to answer does not authorize execution.
227
+ Source inspection, explanations and declaration changes belong to the coding
228
+ conversation; usage knowledge grants Colleague no source, shell or screenshot
229
+ access.
@@ -0,0 +1,31 @@
1
+ # Project language tools
2
+
3
+ Preparation and Preview run the commands declared by the project. Those commands
4
+ name their required runtimes: `nodejs`, `php`, `composer`, `python`, `ruby`, `go`,
5
+ `java`, `kotlin`, `csharp`, `rust`, `cpp` or `shell`. Database CLI requirements
6
+ use `mysql`/`mariadb`, `postgresql` or `sqlite`; selecting a CLI does not create a
7
+ database or run a migration.
8
+
9
+ Managed hosts supply the selected pinned runtime packs. Standalone Vibe64 can
10
+ use the developer's installed tools through its ordinary PATH and does not
11
+ require a hosted Nix installation. Kotlin includes the Java toolchain on managed
12
+ hosts; Rust includes the native linker tools. Projects needing native
13
+ extensions or Go C integration also declare their required build toolchain.
14
+ JSKIT, Vue and Laravel use the tools specified by their project commands rather
15
+ than a separate framework runtime.
16
+
17
+ If **Preparing workspace** fails, expand its output, correct the reported cause
18
+ and choose **Retry**. If Preview cannot start, use **Show run output**. On mobile,
19
+ open **Show project** first. A missing runtime needs installation by the host
20
+ administrator; changing the declaration to `shell` does not supply the missing
21
+ tool. Standalone users install/configure the missing tool in their own environment
22
+ and retry the project command.
23
+
24
+ Connected development uses the same runtime requirements. Having a compiler or
25
+ interpreter installed does not prove that the project consumes the selected
26
+ library: the project's declared verification must demonstrate that. Normal
27
+ release inputs and unrelated sessions keep their own source selection.
28
+
29
+ Colleague can explain preparation errors and offer its supported status/retry
30
+ actions. These instructions do not give it shell access or permission to install
31
+ host software. The coding agent can repair project commands after being asked.
@@ -0,0 +1,106 @@
1
+ # Message another coding session
2
+
3
+ Open the destination project and select the session that should receive requests.
4
+ Its Main chat must have an available assistant. This is the same project/session
5
+ selection on desktop and mobile; a temporary chat is never the recipient.
6
+
7
+ Ask your coding assistant to send the request. For example: “Tell jskit-ai to
8
+ review the changes, publish if already authorized, and ping this project with
9
+ the package versions.” The coding assistant uses:
10
+
11
+ ```sh
12
+ vibe64-helper session message-project jskit-ai "Review the changes, then ping vibe64-online with the result and published versions."
13
+ ```
14
+
15
+ Without `--session`, the destination's **currently selected session** receives the
16
+ message in Main. To address a particular session, including another session in
17
+ this same project, copy its ID from **Session info** and use:
18
+
19
+ ```sh
20
+ vibe64-helper session message-project compas-next --session 2026-10-11_14-18-36 "Please review the shared controller change."
21
+ ```
22
+
23
+ The exact session receives the message even if a different session is selected or
24
+ pinned. It must be active and have an available assistant; the project must remain
25
+ open. This command does not switch tabs or change the project's selection.
26
+ Sending to your own session fails with a clear error before delivery or a sent
27
+ receipt is created. Choose the other session explicitly; if no other recipient
28
+ exists, report the limitation to the person instead of repeating the command.
29
+ New messages appear as bubbles with a robot avatar outside, the source project's name
30
+ and a link to its session, on a neutral background distinct from human messages.
31
+ They share the human message width limit on desktop and mobile. Markdown paragraphs,
32
+ lists, links and code are rendered; long messages have **Read more** and **Show less**.
33
+ Received messages appear on
34
+ the left; sent messages appear on the right, with their timestamp and delivery
35
+ status inside the bubble. They are not human messages.
36
+ The **From** and **To** lines show the current session name when it is available,
37
+ for example **FileTransfer (2026-10-11_14-18-36)**. Unnamed sessions, or sessions
38
+ whose name cannot be loaded, show only their ID. The link still opens that exact
39
+ session; renaming it does not change message routing.
40
+ Bubbles show the actual message, without the internal permission and reply-command
41
+ instructions supplied to the receiving assistant.
42
+ Ordinary replies and progress updates to you use indented, shaded chat bubbles
43
+ beneath the assistant's name. Messages between projects instead use neutral,
44
+ outlined bubbles with explicit **To**/**From** project links, so the recipient
45
+ remains clear.
46
+ The sender's Main chat retains the message body, destination session and delivery
47
+ status, including when the command came from a temporary conversation. Sending is
48
+ **fire-and-forget**: after checking access, the open project and its addressed
49
+ assistant, the command returns an acceptance receipt identifying that session
50
+ and message. It does not wait for native delivery, an acknowledgement or task
51
+ completion. Ask the recipient to ping back later if you need a result.
52
+ **Accepted · delivery not confirmed** is not proof of delivery. **Delivered to
53
+ assistant** confirms native acceptance, not task completion. **Delivery failed**
54
+ includes the reported failure; it also remains in the workspace log. Do not resend solely
55
+ because no immediate reply appeared. Pending dispatch is not a durable inbox and
56
+ is not promised to survive a daemon shutdown.
57
+ The recipient uses the same command to send requested answers, results or blockers
58
+ back to the exact source project and session, using `--session` from its reply instructions. An ordinary chat answer is shown to the person; it is
59
+ not sent to the other assistant. Completed reports need no acknowledgement unless
60
+ one was requested. Replies retain the original sender as their destination even when project selection changes.
61
+
62
+ A closed or closing project, missing selected session, unavailable assistant or
63
+ denied project access returns an error. An explicit missing or inactive session fails
64
+ without falling back to the selected session. Nothing is held for a future session, and
65
+ the command never opens a project or selects a fallback. Resolve the reported
66
+ condition before trying again. After a transport timeout, inspect the returned
67
+ message reference/history before resending; do not assume delivery failed.
68
+
69
+ An optional final message ID can correlate retries in the same destination
70
+ session. Without `--session`, a changed selection means a different recipient;
71
+ check it before retrying. Use a known session ID for a specific colleague.
72
+ If the recipient is unclear, ask instead of guessing.
73
+ Keep tracking IDs in that argument rather than at the start of visible messages.
74
+ Write naturally in Markdown: lead with the result or request, use short paragraphs
75
+ and useful bullets, and format commands and paths as code. Include essential
76
+ evidence without dumping logs.
77
+
78
+ Messages from assistants retain existing permissions. They are not fresh human
79
+ authorization to publish, deploy or perform restricted operations. Learning
80
+ sessions cannot send project messages.
81
+ Agents may coordinate development and releases within work the person has already
82
+ authorized. Messages cannot override restrictions such as “test only, no edits.”
83
+ If new permission is needed, the recipient asks the person once and reports the
84
+ blocker to the sender once. They stop that exchange until a decision arrives and
85
+ continue independent authorized work. Send useful results, consequential questions
86
+ or blockers; avoid acknowledgement-only replies and polling. The assistant tells
87
+ the person what it sent. These are agent instructions, not a guarantee that a model
88
+ will never repeat itself.
89
+
90
+ Older messages retain their original presentation; no sent history is reconstructed.
91
+
92
+ Colleague can explain how to select the destination and offer its existing
93
+ project/session controls. This command is available to coding assistants;
94
+ Colleague has no shell access and cannot claim it sent a message itself.
95
+
96
+ Message commands are included in Main and temporary coding-agent instructions.
97
+ Host-specific guidance shares the same bounded instruction budget; adding it must
98
+ not prevent either conversation from starting.
99
+
100
+ Installed host instructions reach coding assistants through the host environment
101
+ filter. On a configured VPS they include the local update and SSH restore commands;
102
+ hosts without that facility do not advertise it.
103
+
104
+ If the destination has a pinned source session, that is its server-selected
105
+ session for messages without `--session`, even while someone browses another tab. Unpinning restores ordinary
106
+ selection. Pinning does not change message permissions or acknowledgement rules.
@@ -11,11 +11,33 @@ wait for its saved result. Changes to collaboration style apply to future work;
11
11
  they do not rewrite past messages. Engineering choices do not migrate existing
12
12
  code automatically. Prompt suggestions can be changed separately from those choices.
13
13
 
14
+ **Connected projects** maintains the source-owned `vibe64.connections.json` list.
15
+ Add a name, GitHub URL and Dependency/Composition relationship.
16
+ Package type can inherit the Stack default or explicitly select npm (Node.js),
17
+ Composer (PHP), pip (Python), Bundler (Ruby), Go modules, Cargo (Rust), Maven,
18
+ Gradle, NuGet (.NET) or custom; it is independent of the relationship.
19
+ Custom requires a Preparation script path relative to this project, with its
20
+ runtime declared in Stack. Every other type disables and clears the script; the
21
+ project's own declared Verify command, not Vibe64, treats that source.
22
+ Use **Save connected projects** for the list; ordinary project Save publishes
23
+ that source edit. See **Configure connected projects** for access and recovery.
24
+
14
25
  Hosted repository settings can also specify whether GitHub Save permits direct
15
26
  commits/pushes or requires pull requests. GitHub still enforces your repository
16
27
  permissions and branch rules. A hosted development database scope change requires
17
28
  the owner and no open sessions; it does not merge or restore database contents.
18
29
 
30
+ With **One database shared by this project** selected, you can check **Allow
31
+ multiple sessions with this shared database**, then choose **Save database choice**.
32
+ The warning reads **All sessions will share the same database.** The checkbox and
33
+ warning appear only for that choice, on desktop and mobile. The override permits
34
+ the normal maximum of three open sessions. You can change it while sessions are
35
+ open. Turning it off preserves every existing session and its data; it blocks
36
+ additional sessions while one or more remain open. The New session control
37
+ updates after saving without reloading the page. Changing the database scope
38
+ itself still requires closed sessions. Colleague can explain or, when requested,
39
+ save this override through the same authorized settings action.
40
+
19
41
  If a load or save fails, read its error, retry the read and inspect the saved state
20
42
  before sending the change again. Disabled controls may reflect missing authority
21
43
  or active work; changing pages does not bypass those restrictions.