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.
- package/bin/run.js +1717 -1648
- package/bin/server.js +81 -68
- package/bin/upgrade-state.js +5438 -5189
- package/dist/assets/{GithubBrowserTabs-2bEGbRAs.js → GithubBrowserTabs-DO5PHon-.js} +1 -1
- package/dist/assets/GithubMarkdown-BQ6MfCDJ.js +3 -0
- package/dist/assets/GithubMarkdown-U7-j-qNI.css +1 -0
- package/dist/assets/StudioErrorNotice-sQfmeR-z.js +1 -0
- package/dist/assets/VAlert-P256xaE0.js +1 -0
- package/dist/assets/VAutocomplete-BDb95qJX.js +1 -0
- package/dist/assets/VAvatar-9ilDR2r2.css +1 -0
- package/dist/assets/VAvatar-DPzqDH4r.js +1 -0
- package/dist/assets/VBtn-B2MBK2DL.js +1 -0
- package/dist/assets/VCard-mXy0k4aS.js +1 -0
- package/dist/assets/VCheckbox-C7A1ZW4D.js +1 -0
- package/dist/assets/VChip-CcI-Oo2J.js +1 -0
- package/dist/assets/VDialog-Bu3EfKb1.js +1 -0
- package/dist/assets/VDivider-BMEqUoAB.js +1 -0
- package/dist/assets/VExpansionPanels-Dgjrop0V.js +1 -0
- package/dist/assets/VMenu-C_x18lwb.js +1 -0
- package/dist/assets/VOverlay-CeMZurIN.js +1 -0
- package/dist/assets/VRadioGroup-CUu2-KIP.js +1 -0
- package/dist/assets/VRow-Cpw7OHQV.js +1 -0
- package/dist/assets/{VSelect-DY-ZuBJJ.js → VSelect-DL3HaA5m.js} +1 -1
- package/dist/assets/VSheet-DZWsu0kL.js +1 -0
- package/dist/assets/VSkeletonLoader-CttxM1tw.js +1 -0
- package/dist/assets/VSpacer-Dhmsvk4t.js +1 -0
- package/dist/assets/{VSwitch-Bm1bwl2V.js → VSwitch-BRHeDJkH.js} +1 -1
- package/dist/assets/VTextField-BR2eZeFT.js +1 -0
- package/dist/assets/VTextarea-DbqamXJd.js +1 -0
- package/dist/assets/Vibe64AsyncModuleState-Dx7YKRPp.js +1 -0
- package/dist/assets/Vibe64DashboardBackButton-DD9UR77P.css +1 -0
- package/dist/assets/Vibe64DashboardBackButton-yE6cyYg2.js +1 -0
- package/dist/assets/Vibe64DashboardPageHeader-BXQR00HK.js +1 -0
- package/dist/assets/Vibe64DashboardPageHeader-Gm1IvlHx.css +1 -0
- package/dist/assets/Vibe64DashboardShell-CuCVMhOc.js +1 -0
- package/dist/assets/Vibe64DashboardShell-MBkUHjs-.css +1 -0
- package/dist/assets/Vibe64DatabaseWorkspace-BONJdxBS.js +18 -0
- package/dist/assets/{Vibe64DatabaseWorkspace-C39Jvver.css → Vibe64DatabaseWorkspace-CR4pzzcf.css} +1 -1
- package/dist/assets/Vibe64OutputControls-DAAmA09l.js +8 -0
- package/dist/assets/{Vibe64OutputControls-CsZFv12r.css → Vibe64OutputControls-DPBsyDZM.css} +1 -1
- package/dist/assets/{Vibe64RepositoryWorkspace-ebUaYOU4.js → Vibe64RepositoryWorkspace-ByQlZbyO.js} +2 -2
- package/dist/assets/{Vibe64RepositoryWorkspace-Cqm6TOFk.css → Vibe64RepositoryWorkspace-CVHcT93M.css} +1 -1
- package/dist/assets/Vibe64SessionFiles-B0u9HKdF.js +107 -0
- package/dist/assets/Vibe64SessionFiles-NjOMVwPR.css +1 -0
- package/dist/assets/Vibe64TemporaryAiFixAction-BGlcrq4d.js +1 -0
- package/dist/assets/Vibe64UiStoryboardView-3WXph5bz.css +1 -0
- package/dist/assets/Vibe64UiStoryboardView-Brlwdvqi.js +7 -0
- package/dist/assets/Vibe64UnavailableSessions-zwlWlcZD.js +1 -0
- package/dist/assets/_sessionId_-CvOkQbVy.js +1 -0
- package/dist/assets/{_sessionTool_-B39BIzzZ.js → _sessionTool_-Dwod5ns9.js} +1 -1
- package/dist/assets/_slug_-B31c15cc.css +1 -0
- package/dist/assets/_slug_-Dy35qLo1.js +1 -0
- package/dist/assets/access-BVu5XYm2.js +1 -0
- package/dist/assets/app-DRXCcv05.css +1 -0
- package/dist/assets/app-zt7HwQKT.js +1 -0
- package/dist/assets/assistantRouting-CwbwfkwB.js +3 -0
- package/dist/assets/{changes-ByjS7QGx.js → changes-olY8cnFK.js} +1 -1
- package/dist/assets/{client-C-tpoG6F.js → client-BrV4QPwG.js} +1 -1
- package/dist/assets/createSimpleFunctional-CZTGuNuR.js +1 -0
- package/dist/assets/dashboard-BnXD-H4R.js +1 -0
- package/dist/assets/definitions-DaOPIkyB.js +1 -0
- package/dist/assets/env-DJhnLOH7.css +1 -0
- package/dist/assets/env-DN0vW4EI.js +1 -0
- package/dist/assets/{error-DFKtZBJ8.js → error-DgrgRbJJ.js} +1 -1
- package/dist/assets/{error-DE4zo8Lk.js → error-Dug56can.js} +1 -1
- package/dist/assets/health-7oIQODer.css +1 -0
- package/dist/assets/health-Z6m96GDr.js +1 -0
- package/dist/assets/history-BOwbCRQP.css +1 -0
- package/dist/assets/history-BxlpB-YH.js +1 -0
- package/dist/assets/incoming-BOxRVlOM.js +2 -0
- package/dist/assets/incoming-DWDrmxyH.css +1 -0
- package/dist/assets/index-BUq-MczL.js +86 -0
- package/dist/assets/{index-D4MsP3dq.css → index-DtmBqE3h.css} +1 -1
- package/dist/assets/{integrations-B4txOZfY.js → integrations-BFltGDVI.js} +1 -1
- package/dist/assets/issues-1iS5zoed.js +1 -0
- package/dist/assets/issues-XnpGgdmn.css +1 -0
- package/dist/assets/layout-BkWVNT37.js +1 -0
- package/dist/assets/lazy-NHSwD9FS.js +1 -0
- package/dist/assets/mdi-C54lQ0i_.js +1 -0
- package/dist/assets/{pages-BW2l8fNe.js → pages-DuMgH61T.js} +1 -1
- package/dist/assets/{placement-JxzrmUR3.js → placement-CwTqWLQH.js} +1 -1
- package/dist/assets/placement-DLsU3pCW.js +1 -0
- package/dist/assets/pull-requests-BJOwNL4k.js +1 -0
- package/dist/assets/pull-requests-CdbhyFOv.css +1 -0
- package/dist/assets/{repository-BTC3lkrh.js → repository-JWLVST3D.js} +1 -1
- package/dist/assets/{VAvatar-CAFvgSUo.js → ripple-BVltMmyV.js} +2 -2
- package/dist/assets/ripple-DqhAt1Ze.css +1 -0
- package/dist/assets/runtime-core.esm-bundler-DGXg_mpN.js +3 -0
- package/dist/assets/{session-CG-TUCJt.css → session-5qADMzDP.css} +1 -1
- package/dist/assets/session-C5Nj8Dlq.js +1 -0
- package/dist/assets/settings-BopLnpB0.css +1 -0
- package/dist/assets/settings-c273Ikrm.js +1 -0
- package/dist/assets/ssrBoot-Rlh6kLbD.js +1 -0
- package/dist/assets/{studioGateApi-C0GvzVlt.js → studioGateApi-DhA9IJGZ.js} +1 -1
- package/dist/assets/{studioUrls-CIab-Axb.js → studioUrls-Dj8rXeXO.js} +1 -1
- package/dist/assets/{useApi-BPuI6ZR9-Dr8wK_Co.js → useApi-BPuI6ZR9-CFWU1m37.js} +1 -1
- package/dist/assets/useArchivedVibe64Sessions-CVZx2Rtm.js +1 -0
- package/dist/assets/useCommand-DWuxfAV0.js +1 -0
- package/dist/assets/useEndpointResource-MWVNfmMa.js +1 -0
- package/dist/assets/{usePaths-DVTieF_G.js → usePaths-Db88-HOm.js} +1 -1
- package/dist/assets/{useUiFeedback-Tzi-PRlX.js → useUiFeedback-0FqKuZRP.js} +1 -1
- package/dist/assets/useVibe64ConversationLog-8cKh1eDm.js +1 -0
- package/dist/assets/useVibe64DatabaseTools-BcRG1s3i.js +1 -0
- package/dist/assets/useVibe64LearningMode-Bl0dGdCh.js +28 -0
- package/dist/assets/useVibe64LearningMode-C3PcXdVg.css +1 -0
- package/dist/assets/useVibe64ProjectScope-DOEVkBqX.js +1 -0
- package/dist/assets/useVibe64SessionData-DFTyLzci.js +1 -0
- package/dist/assets/useVibe64SessionSelection-j9lsllx4.js +1 -0
- package/dist/assets/useVibe64SystemGraph-tNkIwSBQ.js +1 -0
- package/dist/assets/{useVibe64Terminal-C2XJ9Y1K.js → useVibe64Terminal-BPnN25WH.js} +1 -1
- package/dist/assets/vibe64AssistantHost-DdE_-lZF.js +1 -0
- package/dist/assets/vibe64LessonDashboard-DlKYjisq.js +1 -0
- package/dist/assets/vibe64ProjectScope.local-DqT6e5un.js +1 -0
- package/dist/assets/vibe64RepositoryRealtime-DXk0Jai3.js +1 -0
- package/dist/assets/vibe64SessionFocus-OJ2toBd9.css +1 -0
- package/dist/assets/vibe64SessionFocus-kqPOPaOH.js +1 -0
- package/dist/assets/{vibe64SessionInfo-D8l22MFm.js → vibe64SessionInfo-BHxtTrLX.js} +1 -1
- package/dist/assets/vibe64SessionToolDefinitions-NfLd1HZI.js +1 -0
- package/dist/assets/vue-flow-core-BlVEnES8.js +26 -0
- package/dist/index.html +51 -48
- package/docs/colleague-usage/account-profile-and-appearance.md +29 -0
- package/docs/colleague-usage/ai-accounts-and-routing.md +23 -4
- package/docs/colleague-usage/ai-balance-and-allowance.md +4 -0
- package/docs/colleague-usage/architecture-explanations.md +99 -0
- package/docs/colleague-usage/auto-workflow.md +49 -11
- package/docs/colleague-usage/coding-agent-failures.md +94 -0
- package/docs/colleague-usage/coding-agent-goal-pause.md +110 -0
- package/docs/colleague-usage/coding-agent-goals.md +140 -38
- package/docs/colleague-usage/coding-agent-history.md +20 -2
- package/docs/colleague-usage/coding-agent-recovery.md +136 -0
- package/docs/colleague-usage/coding-agents.md +138 -150
- package/docs/colleague-usage/colleague-recovery.md +28 -5
- package/docs/colleague-usage/colleague-upgrade-recovery.md +4 -0
- package/docs/colleague-usage/colleague-watches.md +84 -0
- package/docs/colleague-usage/colleague.md +18 -34
- package/docs/colleague-usage/connected-contributions.md +196 -0
- package/docs/colleague-usage/connected-projects.md +196 -0
- package/docs/colleague-usage/conversation-context.md +67 -1
- package/docs/colleague-usage/dashboard-navigation.md +79 -5
- package/docs/colleague-usage/database.md +11 -0
- package/docs/colleague-usage/developing-vibe64.md +137 -0
- package/docs/colleague-usage/development-copies.md +20 -0
- package/docs/colleague-usage/development-env.md +34 -0
- package/docs/colleague-usage/file-interfaces.md +156 -0
- package/docs/colleague-usage/github-work.md +88 -1
- package/docs/colleague-usage/health-checks.md +32 -0
- package/docs/colleague-usage/incoming-changes.md +94 -0
- package/docs/colleague-usage/learning-chat-retention.md +11 -2
- package/docs/colleague-usage/learning-code-questions.md +55 -0
- package/docs/colleague-usage/learning-course-catalogue.md +118 -0
- package/docs/colleague-usage/learning-diagrams-and-voice.md +97 -0
- package/docs/colleague-usage/learning-history.md +17 -9
- package/docs/colleague-usage/learning-lesson-watch.md +95 -0
- package/docs/colleague-usage/learning-mode-ui.md +187 -85
- package/docs/colleague-usage/learning-native-session.md +12 -10
- package/docs/colleague-usage/learning-practical-exercises.md +71 -0
- package/docs/colleague-usage/learning-practical-gestures.md +18 -1
- package/docs/colleague-usage/learning-practice-projects.md +55 -4
- package/docs/colleague-usage/learning-session-creation.md +7 -7
- package/docs/colleague-usage/learning-teacher-guide.md +52 -0
- package/docs/colleague-usage/learning-with-colleague.md +59 -80
- package/docs/colleague-usage/lesson-authoring.md +12 -4
- package/docs/colleague-usage/lesson-practical-assessment.md +3 -1
- package/docs/colleague-usage/managed-app-access.md +6 -0
- package/docs/colleague-usage/message-delivery-recovery.md +56 -0
- package/docs/colleague-usage/plans.md +14 -7
- package/docs/colleague-usage/preview-browser-checks.md +61 -0
- package/docs/colleague-usage/preview-lesson-presentation.md +56 -0
- package/docs/colleague-usage/preview-starting-application.md +92 -0
- package/docs/colleague-usage/preview.md +70 -96
- package/docs/colleague-usage/project-architecture.md +229 -0
- package/docs/colleague-usage/project-language-tools.md +31 -0
- package/docs/colleague-usage/project-messages.md +106 -0
- package/docs/colleague-usage/project-settings.md +22 -0
- package/docs/colleague-usage/project-setup.md +29 -2
- package/docs/colleague-usage/session-terminal.md +42 -0
- package/docs/colleague-usage/sessions.md +122 -52
- package/docs/colleague-usage/teaching-content.md +12 -6
- package/docs/colleague-usage/temporary-chat-context.md +29 -0
- package/docs/colleague-usage/temporary-chats.md +95 -2
- package/docs/colleague-usage/voice-chat.md +10 -43
- package/docs/colleague-usage/voice-face-and-speaking-voice.md +73 -0
- package/docs/colleague-usage/workspace-preparation.md +89 -0
- package/docs/training-content.md +208 -7
- package/node_modules/@jskit-ai/assistant-core/package.json +1 -1
- package/node_modules/@jskit-ai/assistant-runtime/README.md +29 -0
- package/node_modules/@jskit-ai/assistant-runtime/package.json +1 -1
- package/node_modules/@jskit-ai/assistant-voice/package.json +1 -1
- package/node_modules/@jskit-ai/connector-google-calendar/package.json +1 -1
- package/node_modules/@jskit-ai/connectors-catalog/package.json +1 -1
- package/node_modules/@jskit-ai/connectors-core/package.json +1 -1
- package/node_modules/@jskit-ai/http-runtime/package.json +1 -1
- package/node_modules/@jskit-ai/kernel/package.json +1 -1
- package/node_modules/@jskit-ai/payments-core/package.json +1 -1
- package/node_modules/@jskit-ai/realtime/package.json +1 -1
- package/node_modules/@jskit-ai/resource-core/package.json +1 -1
- package/node_modules/@jskit-ai/resource-crud-core/package.json +1 -1
- package/node_modules/@jskit-ai/uploads-runtime/package.json +1 -1
- package/node_modules/@local/vibe64-core/package.json +1 -0
- package/node_modules/@local/vibe64-execution/src/host/execHelper.js +280 -272
- package/node_modules/@local/vibe64-genesis/README.md +15 -0
- package/node_modules/@local/vibe64-genesis/bin/vibe64-genesis-host-context +879 -1225
- package/node_modules/@local/vibe64-genesis/package.json +2 -1
- package/node_modules/@local/vibe64-genesis/src/server/index.js +496 -418
- package/node_modules/@local/vibe64-genesis/src/server/promptContext.js +165 -146
- package/node_modules/@local/vibe64-runtime/src/server/agentSessionCommandHook.js +8 -8
- package/node_modules/@local/vibe64-runtime/src/server/codexAppServerProcess.js +128 -129
- package/node_modules/@local/vibe64-system-graph/README.md +136 -6
- package/node_modules/@local/vibe64-terminals/package.json +3 -0
- package/node_modules/@local/vibe64-terminals/src/server/sessionWorkOperationCommand.js +1527 -1326
- package/node_modules/@local/vibe64-training/package.json +6 -1
- package/node_modules/@local/vibe64-voice/package.json +1 -0
- package/package.json +16 -16
- package/server.bundle.mjs +42853 -40268
- package/dist/assets/StudioErrorNotice-Ccjvcn9C.js +0 -1
- package/dist/assets/VAlert-B7ciJKQL.js +0 -1
- package/dist/assets/VAutocomplete-QjMk5d_j.js +0 -1
- package/dist/assets/VAvatar-nHaK192T.css +0 -1
- package/dist/assets/VBtn-Kl_qcBsy.js +0 -1
- package/dist/assets/VCard-nrJPeo91.js +0 -1
- package/dist/assets/VCheckbox-DTRAWOIf.js +0 -1
- package/dist/assets/VChip-Dfs5jX0f.js +0 -1
- package/dist/assets/VDialog-Dt1VjJg1.js +0 -1
- package/dist/assets/VDivider-DFsS0OTx.js +0 -1
- package/dist/assets/VExpansionPanels-CYKU0cAr.js +0 -1
- package/dist/assets/VMenu-BLxobsuU.js +0 -1
- package/dist/assets/VOverlay-BvFVZKNS.js +0 -1
- package/dist/assets/VRadioGroup-DzQzpCfg.js +0 -1
- package/dist/assets/VRow-BR2RMCM1.js +0 -1
- package/dist/assets/VSheet-BA95RNmA.js +0 -1
- package/dist/assets/VSkeletonLoader-hpJqr0HL.js +0 -1
- package/dist/assets/VSpacer-B1l1hVvU.js +0 -1
- package/dist/assets/VTextField-CA_p3N4d.js +0 -1
- package/dist/assets/VTextarea-NyCqY4h5.js +0 -1
- package/dist/assets/Vibe64AsyncModuleState-DEFlqJ97.js +0 -1
- package/dist/assets/Vibe64DashboardShell-BNv2I-P8.js +0 -1
- package/dist/assets/Vibe64DashboardShell-w20wNTGW.css +0 -1
- package/dist/assets/Vibe64DatabaseWorkspace-CuY5lN1o.js +0 -43
- package/dist/assets/Vibe64OutputControls-D2JuYlYU.js +0 -8
- package/dist/assets/Vibe64SessionFiles-C-rWehq_.js +0 -34
- package/dist/assets/Vibe64SessionFiles-Dsr6KQNP.css +0 -1
- package/dist/assets/Vibe64SubsystemsView-BvdU_o6H.css +0 -1
- package/dist/assets/Vibe64SubsystemsView-DJCjSzQM.js +0 -1
- package/dist/assets/Vibe64SystemWorldView-B91ioQaO.js +0 -4312
- package/dist/assets/Vibe64SystemWorldView-BXiQ7_Qb.css +0 -1
- package/dist/assets/Vibe64UnavailableSessions-OvnoD3ZB.js +0 -1
- package/dist/assets/_sessionId_-JTvMh54L.js +0 -1
- package/dist/assets/_slug_-DP_heCDa.js +0 -1
- package/dist/assets/_slug_-DmBZGb0q.css +0 -1
- package/dist/assets/access-C8GQIS19.js +0 -1
- package/dist/assets/app-B83lF61Y.js +0 -1
- package/dist/assets/app-ByLIQ3SB.css +0 -1
- package/dist/assets/assistantRouting-TDtryU6o.js +0 -1
- package/dist/assets/createSimpleFunctional-DPIT6zsT.js +0 -1
- package/dist/assets/dashboard-CWGFPojJ.js +0 -1
- package/dist/assets/definitions-BeLcvOW3.js +0 -1
- package/dist/assets/display-BLmcO-5p.js +0 -1
- package/dist/assets/env-7bqFyF_E.css +0 -1
- package/dist/assets/env-BVwxNL8M.js +0 -1
- package/dist/assets/health-BzNhp7r8.js +0 -1
- package/dist/assets/health-DoHTXTGx.css +0 -1
- package/dist/assets/history-BPeZGofK.js +0 -1
- package/dist/assets/history-iMQxp5AR.css +0 -1
- package/dist/assets/httpClient-BaaZuFvF.js +0 -1
- package/dist/assets/index-5sKwLHOH.js +0 -86
- package/dist/assets/issues-DCEhGlfn.css +0 -1
- package/dist/assets/issues-wby50y9b.js +0 -3
- package/dist/assets/layout-YCn17mK1.js +0 -1
- package/dist/assets/lazy-CvQfXeLg.js +0 -1
- package/dist/assets/mdi-C31_SZp-.js +0 -1
- package/dist/assets/placement-C4R2t6rl.js +0 -1
- package/dist/assets/pull-requests-BNK6mq2u.css +0 -1
- package/dist/assets/pull-requests-lNQAigaC.js +0 -1
- package/dist/assets/runtime-core.esm-bundler-DMrccYS5.js +0 -3
- package/dist/assets/session-D38nzG41.js +0 -1
- package/dist/assets/settings-CFyUJ_kR.js +0 -1
- package/dist/assets/settings-vWsAEoE9.css +0 -1
- package/dist/assets/useArchivedVibe64Sessions-C2DSq2Z4.js +0 -1
- package/dist/assets/useCommand-BzThFLYP.js +0 -1
- package/dist/assets/useEndpointResource-C2KD4Ub_.js +0 -1
- package/dist/assets/useVibe64ConversationLog-CMUlXJtU.js +0 -1
- package/dist/assets/useVibe64DatabaseTools-DBcKhm6B.js +0 -1
- package/dist/assets/useVibe64LearningMode-BPRWM5Rp.js +0 -28
- package/dist/assets/useVibe64LearningMode-PJUv0O25.css +0 -1
- package/dist/assets/useVibe64SessionData-CdtJbAIx.js +0 -1
- package/dist/assets/useVibe64SessionSelection-aR0f6xVT.js +0 -1
- package/dist/assets/useVibe64SystemGraph-DeTPBn0e.js +0 -1
- package/dist/assets/vibe64AssistantHost-Dgyz4TrT.js +0 -1
- package/dist/assets/vibe64ProjectScope.local-GOSMVDRi.js +0 -1
- package/dist/assets/vibe64RepositoryRealtime-t5Al8BlU.js +0 -1
- package/dist/assets/vibe64SessionFocus-CcN6Grgw.js +0 -1
- package/dist/assets/vibe64SessionFocus-ChabllPA.css +0 -1
- package/dist/assets/vibe64SessionToolDefinitions-BaO1DEup.js +0 -1
- /package/dist/assets/{vibe64RepositoryRealtime-D_mq1dFE.css → Vibe64TemporaryAiFixAction-D_mq1dFE.css} +0 -0
|
@@ -0,0 +1,137 @@
|
|
|
1
|
+
# Develop Vibe64 with library source
|
|
2
|
+
|
|
3
|
+
This is a coding-agent and developer workflow for working on Vibe64 itself.
|
|
4
|
+
Colleague can explain it; it cannot edit source or run shell commands.
|
|
5
|
+
|
|
6
|
+
## Prepare the connected checkouts
|
|
7
|
+
|
|
8
|
+
The Vibe64 repository declares its libraries in `vibe64.connections.json`.
|
|
9
|
+
**Prepare workspace** creates or reuses this session's isolated contribution
|
|
10
|
+
sources and writes its ignored `.development/connected.json` selection. The
|
|
11
|
+
checked-in Preview command supplies that map to `dev:example`. It consumes the
|
|
12
|
+
selected npm sources without modifying release manifests or installing over the
|
|
13
|
+
editable checkouts. Vibe64's own composition treats only npm dependencies and
|
|
14
|
+
custom connections; a connection with another package type, such as pip, stops
|
|
15
|
+
Preview with "has no treatment for pip connections". Choose npm or custom for
|
|
16
|
+
Vibe64's connections. See [Connected projects](connected-projects.md) for Settings,
|
|
17
|
+
preparation and contribution Save.
|
|
18
|
+
|
|
19
|
+
For a local prepared map, run
|
|
20
|
+
`npm run dev:example -- --connected-sources .development/connected.json`.
|
|
21
|
+
An explicitly supplied missing or invalid map fails; it never falls back to
|
|
22
|
+
another checkout. The map takes precedence over manual source variables below.
|
|
23
|
+
|
|
24
|
+
## Select checkouts manually
|
|
25
|
+
|
|
26
|
+
In the Vibe64 project's **Env → Development**, set either or both entries:
|
|
27
|
+
|
|
28
|
+
| Entry | Value |
|
|
29
|
+
| --- | --- |
|
|
30
|
+
| `VIBE64_JSKIT_SOURCE_ROOT` | Absolute path to the JSKIT checkout |
|
|
31
|
+
| `VIBE64_GENESIS_SOURCE_ROOT` | Absolute path to the Genesis checkout |
|
|
32
|
+
|
|
33
|
+
Hosted development uses connected sources (above) instead of these entries;
|
|
34
|
+
remove any old `sessions/pinned/source` values from **Env → Development**.
|
|
35
|
+
A connected checkout's own session still owns its tests and setup.
|
|
36
|
+
For laptop development, export these variables with ordinary local checkout
|
|
37
|
+
paths before running the development command. Do not set them in Production.
|
|
38
|
+
Keep each selected checkout prepared with its own normal dependency setup.
|
|
39
|
+
Public's **Workspace setup** installs dependencies and rebuilds its native terminal
|
|
40
|
+
dependency with the declared Node and C++ runtimes. If Preview reports a missing
|
|
41
|
+
`node-pty` binary, let the assistant finish and use **Prepare workspace** or
|
|
42
|
+
**Retry** to run that setup. An ordinary managed command may lack the C++ tools
|
|
43
|
+
that the setup operation declares.
|
|
44
|
+
|
|
45
|
+
Vibe64 owns its own source, so it does not need `VIBE64_PUBLIC_SOURCE_ROOT`.
|
|
46
|
+
The selected Genesis repository supplies both compiler and Stack packages.
|
|
47
|
+
An unset entry uses the normal installed packages. A configured missing source,
|
|
48
|
+
missing required package, invalid export or incompatible external dependency is
|
|
49
|
+
an error; Vibe64 does not silently substitute a published package.
|
|
50
|
+
|
|
51
|
+
## Start or check development
|
|
52
|
+
|
|
53
|
+
Use **Start preview**, or run `npm run dev:example` locally. The launch resolves
|
|
54
|
+
the prepared map or explicitly selected manual sources and composes a disposable application under
|
|
55
|
+
`.vibe64-local/source-development`. The normal `node_modules`, package manifest
|
|
56
|
+
and release lockfile remain unchanged. The example project's source and state
|
|
57
|
+
remain in the original development location, outside that disposable app.
|
|
58
|
+
|
|
59
|
+
To run two local examples at once, give each a different `--state-dir` and
|
|
60
|
+
`--port`. Each state directory supplies its own runtime namespace, so starting
|
|
61
|
+
Codex in one example does not replace the other's shared Codex server.
|
|
62
|
+
Conversations within the same example continue sharing their account's server.
|
|
63
|
+
|
|
64
|
+
Source changes restart the composed development app after its previous process
|
|
65
|
+
exits. The initial scan, including existing skill symlinks, does not restart it.
|
|
66
|
+
Each restart logs its triggering path. Dependency directories and generated state
|
|
67
|
+
are excluded from watching.
|
|
68
|
+
After changing a project's pin, use **Restart preview** so the next launch
|
|
69
|
+
resolves the new selection. The log reports the resolved source roots and selected
|
|
70
|
+
local packages. No npm publication is needed for these edits.
|
|
71
|
+
|
|
72
|
+
For a personally installed Claude CLI, sign in using `claude auth login`, then
|
|
73
|
+
launch the example with `VIBE64_CLAUDE_COMMAND=/absolute/path/to/claude` set in
|
|
74
|
+
your shell. The launcher preserves this explicit tool selection for account
|
|
75
|
+
discovery and chat. Open **AI Accounts** and use **Refresh** to confirm the
|
|
76
|
+
connection. A Claude website login alone does not sign in the CLI. Without an
|
|
77
|
+
explicit command, the installed managed-runtime command remains the default.
|
|
78
|
+
|
|
79
|
+
To hear read-aloud and use **Talk** in a local example, run a speech service (for
|
|
80
|
+
example `jskit-assistant-voice serve`, which listens on `127.0.0.1:3092`) and
|
|
81
|
+
launch with `VIBE64_VOICE_ENDPOINT=ws://127.0.0.1:3092/v1/voice` and
|
|
82
|
+
`VIBE64_VOICE_ACCESS_TOKEN_FILE=/absolute/path/to/token` set in your shell. The
|
|
83
|
+
launcher preserves these two settings like the Claude command; set both or
|
|
84
|
+
neither. Without them, voice controls report that speaking voices could not load
|
|
85
|
+
and text chat keeps working.
|
|
86
|
+
|
|
87
|
+
Each example keeps its frontend dependency cache under its own state directory.
|
|
88
|
+
Keep that directory between runs so normal restarts can reuse the prepared cache.
|
|
89
|
+
When a host supplies Preview routing, the example uses the host’s Preview socket
|
|
90
|
+
directory, including its default when no explicit directory is configured, so its
|
|
91
|
+
own project outputs remain reachable through that host. Same-user child processes
|
|
92
|
+
retain the host runtime directory through the execution gateway; you do not need
|
|
93
|
+
to create socket directories or change permissions manually.
|
|
94
|
+
Each example has a distinct Preview namespace while keeping its session data
|
|
95
|
+
isolated. Standalone runs keep sockets under their writable state directory.
|
|
96
|
+
Its API and conversation connection use a consistent origin through the internal
|
|
97
|
+
proxy, including when opened through HTTPS Preview. If an already-running example predates a launcher fix, use
|
|
98
|
+
**Restart preview** to apply it while retaining its example project and sessions.
|
|
99
|
+
|
|
100
|
+
For a slow agent startup, a developer can launch with `LOG_LEVEL=debug npm run
|
|
101
|
+
dev:example` and retain the server log. Claude startup records identify temporary
|
|
102
|
+
`catalogue` and `usage` queries. Managed Git records include `phaseElapsedMs`:
|
|
103
|
+
cumulative milliseconds through session lookup, authorization, account and
|
|
104
|
+
credential lookup, then command start and finish. Subtract command start from
|
|
105
|
+
finish to measure execution separately from admission. These extra diagnostic
|
|
106
|
+
fields are absent at the normal log level; they do not change execution or
|
|
107
|
+
automatically retry a command.
|
|
108
|
+
|
|
109
|
+
Focused checks also use the selected sources:
|
|
110
|
+
|
|
111
|
+
- Server: `npm test -- tests/server/<name>.test.js`.
|
|
112
|
+
- Client: `npm run test:client:file -- tests/client/<name>.vitest.js`.
|
|
113
|
+
|
|
114
|
+
Run tests in the project that owns them. For a JSKIT test, the editing agent sends
|
|
115
|
+
JSKIT's agent the changed files, exact focused command and selected checkout. Its
|
|
116
|
+
owner checks for another active test, runs or queues the check, and returns the
|
|
117
|
+
result and log location. Relevant checks are already covered by the standing
|
|
118
|
+
development permission; do not create another human-approval exchange.
|
|
119
|
+
|
|
120
|
+
## Recover and release
|
|
121
|
+
|
|
122
|
+
New Hello Node examples include Node's default connected package type, `npm`.
|
|
123
|
+
An existing example is preserved on restart. If current Genesis reports
|
|
124
|
+
`STACK_PROJECT_CONTRACTS_INCOMPLETE` or `STACK_SECTION_AMBIGUOUS`, explicitly
|
|
125
|
+
reconcile or decide that example's Stack section before retrying; restarting does not rewrite its
|
|
126
|
+
source or discard its state.
|
|
127
|
+
|
|
128
|
+
If a source is unavailable, correct its path or pin and restart Preview. If a
|
|
129
|
+
package reports missing dependencies or outputs, have its owner prepare and check
|
|
130
|
+
that checkout. If the previous development app has not stopped, use **Stop
|
|
131
|
+
preview** and inspect the cleanup log before retrying; a second app must not be
|
|
132
|
+
started over it.
|
|
133
|
+
|
|
134
|
+
Use the normal publication process when releasing library changes, then update
|
|
135
|
+
Vibe64's published dependency versions and lockfile. Production builds use the
|
|
136
|
+
normal installation, not the disposable development composition. Development
|
|
137
|
+
permission does not itself authorize publication or deployment.
|
|
@@ -0,0 +1,20 @@
|
|
|
1
|
+
# Conversations in a development copy
|
|
2
|
+
|
|
3
|
+
A host can populate a disposable development environment from an existing workspace.
|
|
4
|
+
The host performs this before starting the editor. Copied history remains readable,
|
|
5
|
+
but work from the parent starts interrupted, goals and watches paused, and running
|
|
6
|
+
background tasks failed. The copy does not stop or modify the parent's work.
|
|
7
|
+
|
|
8
|
+
Open the copied project and session normally. Review retained pending input before
|
|
9
|
+
sending another message: preparation does not replay it. Resume the goal explicitly
|
|
10
|
+
when you want it to continue in this test environment. An expired copied AI account
|
|
11
|
+
still requires the normal sign-in through **AI Accounts**.
|
|
12
|
+
|
|
13
|
+
Copied workflows remain stopped even if an outstanding delivery receipt is later
|
|
14
|
+
confirmed. Their saved requests and helper history remain available for review.
|
|
15
|
+
Learning conversations keep their original learner and content bindings.
|
|
16
|
+
|
|
17
|
+
Colleague can explain these states and offer supported conversation or goal actions.
|
|
18
|
+
History preparation grants no new permissions or shell access. Creating/resetting
|
|
19
|
+
the environment uses its host's development workflow. Desktop and mobile use the
|
|
20
|
+
same conversation and goal controls.
|
|
@@ -1,8 +1,20 @@
|
|
|
1
1
|
# Development credentials for agents and browsers
|
|
2
2
|
|
|
3
|
+
An installed Elastic Beanstalk runtime uses ID `awsebcli` and command `eb` in
|
|
4
|
+
coding and terminal execution. Its installation and AWS credential policy belong
|
|
5
|
+
to the host; standalone Vibe64 does not install that CLI or configure credentials
|
|
6
|
+
automatically. Use the host's setup instructions when it provides a managed EB
|
|
7
|
+
launcher. Development Env reaches it through the same command environment as
|
|
8
|
+
other project tools.
|
|
9
|
+
|
|
3
10
|
Open the project's **Env** view and select **Development**. Enter the variable
|
|
4
11
|
name and value, enable **Secret** for credentials, then choose **Add** or
|
|
5
12
|
**Replace value**. Existing editable rows also offer **Save**.
|
|
13
|
+
Stack defaults are editable fallbacks: saving one creates a project override,
|
|
14
|
+
and removing that override reveals the current declared default again. Defaults
|
|
15
|
+
are user-owned in Env; platform-injected runtime values remain system-owned and
|
|
16
|
+
non-editable, even when Stack declares the same name. Reserved Vibe64-prefixed
|
|
17
|
+
names require a Stack declaration before a user can supply them.
|
|
6
18
|
|
|
7
19
|
Saved development values are available to the coding agent, its managed browser,
|
|
8
20
|
and managed Playwright commands. For an authorized external site, tell the coding
|
|
@@ -18,6 +30,14 @@ failure blocks that command and should be reported for investigation. Provisioni
|
|
|
18
30
|
a newly declared resource and running application migrations remain preparation
|
|
19
31
|
steps; configured names alone do not prove either has completed.
|
|
20
32
|
|
|
33
|
+
For a long-running shell task, the coding agent can request its native tool's
|
|
34
|
+
background mode and timeout. Binding the command to the Vibe64 session preserves
|
|
35
|
+
those settings; the coding tool still applies its own supported limits. This is
|
|
36
|
+
not a promise that the process survives a workspace restart. Use the project's
|
|
37
|
+
declared managed outputs/services for persistent application servers. If a task
|
|
38
|
+
unexpectedly runs in the foreground or times out, report its requested settings
|
|
39
|
+
and returned task ID rather than starting a duplicate or detaching another copy.
|
|
40
|
+
|
|
21
41
|
The coding agent can read `vibe64-helper session status --json` for current
|
|
22
42
|
resource readiness, environment names, declared Workspace setup commands and
|
|
23
43
|
managed tool entry points. This read exposes no environment values and starts
|
|
@@ -26,9 +46,23 @@ no preparation. Repeat it after changing resource declarations. A
|
|
|
26
46
|
credentials. In the session chat, wait for the assistant to finish, then choose
|
|
27
47
|
**Prepare workspace**, or **Retry** on a failed preparation. Adding a resource
|
|
28
48
|
requires preparation even if the dependency-install command has not changed.
|
|
49
|
+
An earlier successful preparation does not cover a changed setup recipe or newly
|
|
50
|
+
unprepared resources. Preparation retry checks the current requirements before
|
|
51
|
+
starting; the session's other work must finish first.
|
|
29
52
|
Colleague can inspect preparation and retry it through its existing session
|
|
30
53
|
actions when asked; it does not run these shell helpers itself.
|
|
31
54
|
|
|
55
|
+
For a reference application that must remain warm between tests, ask the coding
|
|
56
|
+
agent to declare a **per-session supporting service** in the project's Stack.
|
|
57
|
+
Starting that session's declared output starts its service; later test runs reuse
|
|
58
|
+
it. Each session needs its own endpoint and readiness check. **Stop preview**
|
|
59
|
+
stops the displayed app, not these supporting services. Archiving/closing the
|
|
60
|
+
session stops its supporting instances, and closing the project stops all of them.
|
|
61
|
+
The project command remains responsible for endpoint selection and clean shutdown.
|
|
62
|
+
Development Env values are shared across the project, so setting a port there does
|
|
63
|
+
not give different sessions different ports. Colleague can explain this and offer
|
|
64
|
+
to ask the coding agent to configure it; it cannot run a shell command itself.
|
|
65
|
+
|
|
32
66
|
Long-running processes retain their startup values. After changing credentials, ask the
|
|
33
67
|
coding agent to close its managed browser with `vibe64-helper preview browser
|
|
34
68
|
close` before retrying; its next browser command starts a fresh process with the
|
|
@@ -0,0 +1,156 @@
|
|
|
1
|
+
# Read file interfaces and exact code
|
|
2
|
+
|
|
3
|
+
See [Where Architecture explanations come from](architecture-explanations.md)
|
|
4
|
+
for authorship, cache ownership and freshness.
|
|
5
|
+
|
|
6
|
+
## Read Markdown files formatted
|
|
7
|
+
|
|
8
|
+
A Markdown file (`.md`, `.markdown`) opens formatted, as a readable document with
|
|
9
|
+
headings, lists, tables, quotes and code blocks. Use the header button to switch:
|
|
10
|
+
**Markdown** shows the source text for editing, and **Rendered** returns to the
|
|
11
|
+
formatted document. The formatted view shows your unsaved edits too. Links to
|
|
12
|
+
other files in the project open them in Files; web links open in a new browser
|
|
13
|
+
tab. Images stored in the project are shown. Raw HTML in a document is limited to
|
|
14
|
+
safe formatting, so scripts never run. This works the same on a phone.
|
|
15
|
+
Architecture's single-file view keeps **Interface** and **Code**.
|
|
16
|
+
|
|
17
|
+
## Read a source file's interface
|
|
18
|
+
|
|
19
|
+
Open **Dashboard → Files → Repo**, then select a source file. The default view is
|
|
20
|
+
**Interface**, showing **File exports** available from the
|
|
21
|
+
project's selected language parser. Visibility follows that language's conventions.
|
|
22
|
+
Callable signatures show indexed parameters and return information when available.
|
|
23
|
+
The view explains that definitions can be operations, components, values or types.
|
|
24
|
+
File exports are not automatically the subsystem's intended API. Select a
|
|
25
|
+
definition to read its details.
|
|
26
|
+
Unrecorded return information is omitted; this does not mean a function returns
|
|
27
|
+
nothing. Coverage is partial; an empty list does not prove there is no public interface.
|
|
28
|
+
For Python, a static `__all__` list determines module exports. Dynamic or
|
|
29
|
+
conditional exports leave coverage partial and use naming conventions; review
|
|
30
|
+
the analysis warning rather than treating the list as complete.
|
|
31
|
+
Public values, properties, types and callables follow the selected language's
|
|
32
|
+
declarations. For example, a Rust item declared `pub(crate)` displays **Visibility:
|
|
33
|
+
crate**; it is available within that scope, not an unrestricted external API.
|
|
34
|
+
Symbol **Code** retains declaration keywords, modifiers, decorators and attached
|
|
35
|
+
attributes. A grouped declaration can include more than one named value. Build
|
|
36
|
+
configuration, macro expansion and conditional compilation remain outside static
|
|
37
|
+
coverage; use the project's declared preparation/verification for runtime proof.
|
|
38
|
+
|
|
39
|
+
**Part of …** and **Main Program file** open the capability’s Program view
|
|
40
|
+
inside Architecture. That view contains a short opening preview, **Read full
|
|
41
|
+
explanation** for the complete text in a separate scrollable dialog, a clearly marked
|
|
42
|
+
**Main source file** and **Supporting files**. Select a source icon to open its
|
|
43
|
+
file interface; **← Back**, **×** or Esc returns to the Program. The browser
|
|
44
|
+
retains its directory navigation. Program membership never links to a raw Genesis
|
|
45
|
+
Markdown document or guesses an entry file.
|
|
46
|
+
|
|
47
|
+
Main file icons have a gold border, star and **Main · …** label. The anchor is the
|
|
48
|
+
place to start reading, not necessarily an executable entry point. It belongs to
|
|
49
|
+
the Program’s owning subsystem; supporting files may be shared libraries elsewhere.
|
|
50
|
+
Program explanations describe the capability rather than each individual function.
|
|
51
|
+
The file’s **Explanation** is a separate informational overview of its saved source.
|
|
52
|
+
|
|
53
|
+
Genesis requires exactly one explicit main source per Program. After deliberate
|
|
54
|
+
changes to the authored subsystem map or Program, use **Architecture options →
|
|
55
|
+
Re-scan project** to load their current owners and memberships. Missing main
|
|
56
|
+
anchors require correction rather than an inferred file or document link.
|
|
57
|
+
|
|
58
|
+
The file opens as a document, with an **Explanation** field above its exports.
|
|
59
|
+
An empty field offers **Generate explanation**. Press it to fill the field through
|
|
60
|
+
the configured Helper. Saved text is shown automatically when you reopen the file;
|
|
61
|
+
**Update explanation** replaces it with a newly generated answer. Existing text
|
|
62
|
+
stays readable while an update runs. A short status marks an out-of-date answer.
|
|
63
|
+
These explanations describe the saved file, not a chat transcript or an authored
|
|
64
|
+
Genesis Program. A file explanation needs no project index.
|
|
65
|
+
The file overview explains its scope, responsibilities, main parts and behavior.
|
|
66
|
+
It does not carry an individual function's parameter/return contract, even when
|
|
67
|
+
the file contains callable exports. Manifests explain what they configure.
|
|
68
|
+
Press **Update explanation** to refresh an older answer marked out of date after
|
|
69
|
+
this guidance change.
|
|
70
|
+
|
|
71
|
+
Select a callable signature to reveal its **Pseudocode** field directly beneath
|
|
72
|
+
that signature. **Generate pseudocode** fills it with a purpose statement and
|
|
73
|
+
English steps. Function explanations identify **Inputs** and **Outputs and use**:
|
|
74
|
+
what callers pass, what is returned, and which returned data or operations they
|
|
75
|
+
read or invoke. Required options, important defaults, live state, snapshots,
|
|
76
|
+
awaitable results and side effects are distinguished when evidenced. Inapplicable
|
|
77
|
+
sections are omitted; missing real contracts remain explicit. The Helper is asked
|
|
78
|
+
for a purpose sentence, that caller interface, then up to twelve concise steps,
|
|
79
|
+
grouping related operations in large declarations.
|
|
80
|
+
A saved answer appears when that declaration is selected;
|
|
81
|
+
**Update pseudocode** regenerates it. **Code** shows the exact declaration; **Pseudocode** returns to saved steps without generating again.
|
|
82
|
+
Components, values and types offer Code without an inapplicable pseudocode field.
|
|
83
|
+
**Code · whole file** opens the source view; **Interface** returns to the document.
|
|
84
|
+
The Architecture reader's source view uses the full width without an explanation
|
|
85
|
+
chat dock. Discussion belongs in the project's agent conversation.
|
|
86
|
+
Opening a file or selecting a signature makes no Helper query.
|
|
87
|
+
|
|
88
|
+
Both generated fields use the existing private source-editor cache, keyed to saved
|
|
89
|
+
source, person, project/session, verified Helper profile and prompt revision.
|
|
90
|
+
Source changes mark the text out of date. It remains informational and is not
|
|
91
|
+
supplied to coding agents. Generating or updating starts only on an explicit
|
|
92
|
+
button press. A missing Helper disables generation, but saved text and Code stay
|
|
93
|
+
readable. Configure the Helper in **Model routing** and connect its account in
|
|
94
|
+
**AI Accounts** if necessary.
|
|
95
|
+
|
|
96
|
+
While generating, the field shows **Generating explanation…**, **Stop**, and any
|
|
97
|
+
actual Helper progress. No transcript, user prompt or follow-up composer appears
|
|
98
|
+
in the document. Stopping or a failure retains earlier saved text and offers
|
|
99
|
+
**Retry**. To discuss the code, use the coding agent or a temporary conversation.
|
|
100
|
+
The Code editor's existing **Explain file or selection** conversation remains a
|
|
101
|
+
separate facility. A file explanation receives the complete saved source when it
|
|
102
|
+
fits the 60,000-character input limit; larger files use an explicitly labelled
|
|
103
|
+
bounded excerpt. Indexed function pseudocode uses the complete validated declaration
|
|
104
|
+
within that same character limit, including functions longer than 240 lines.
|
|
105
|
+
|
|
106
|
+
An out-of-date index disables symbol-range use. **Architecture → ⋯ → Re-scan project** rebuilds
|
|
107
|
+
the whole project browsing index: signatures, imports and UI links. It reads existing
|
|
108
|
+
Genesis documents; it does not rewrite Program or ask the Helper for explanations.
|
|
109
|
+
The running stage and elapsed seconds show progress, with **Cancel analysis** in
|
|
110
|
+
Architecture. An inspector failure offers **Command output** inline and retains
|
|
111
|
+
the preceding index. Fix the reported command or prepare the missing dependency,
|
|
112
|
+
then retry. **Code · whole file** and authored Program context remain
|
|
113
|
+
available without a supported parser. Unsaved edits disable generated
|
|
114
|
+
explanations and indexed range use until saved. Save with the existing **Save now**
|
|
115
|
+
control; conflicts retain the existing draft and recovery workflow. A source change
|
|
116
|
+
between selection and explanation is rejected rather than describing the wrong
|
|
117
|
+
range. For a symbol, the server resolves its indexed identity and checks that
|
|
118
|
+
declaration against the saved file; browser-supplied selection coordinates do
|
|
119
|
+
not determine the symbol explanation. Missing or invalid analysis points to the
|
|
120
|
+
Architecture menu; no file button scans the project. Oversized analysis retains
|
|
121
|
+
Code and ordinary selection
|
|
122
|
+
explanations. Binary/download-only files retain their normal preview/download
|
|
123
|
+
controls.
|
|
124
|
+
|
|
125
|
+
Colleague can explain these steps and offer supported navigation. It cannot read
|
|
126
|
+
source text or request source investigation through usage knowledge; such work
|
|
127
|
+
belongs to the coding conversation and its existing authorized operations.
|
|
128
|
+
|
|
129
|
+
Vue single-file components expose a **default component** interface even when
|
|
130
|
+
they use script setup or contain only a template. Its **Code** covers the complete
|
|
131
|
+
component declaration. Explicit functions and other public declarations remain
|
|
132
|
+
available according to the selected language analysis.
|
|
133
|
+
|
|
134
|
+
From Architecture, enter a subsystem and use its **Files** shortcut to reach the graphical files. Click or tap a
|
|
135
|
+
file icon once or press Enter to open only that file inside the
|
|
136
|
+
subsystem square. Selecting a subsystem public signature goes directly to its
|
|
137
|
+
implementation file and selects that exact declaration, including a resolved
|
|
138
|
+
re-export's original implementation. The same interface and explanation service
|
|
139
|
+
is used; there is no project-wide folder tree, Open file or Find in files in
|
|
140
|
+
this file view. Whole-file Code uses the shared Files editor, with Save now, autosave, Undo/Redo,
|
|
141
|
+
download and conflict controls; only its browser is hidden. A mouse wheel, two-finger touchpad
|
|
142
|
+
movement or a one-finger phone swipe scrolls the file, even at a scroll boundary.
|
|
143
|
+
Scroll out on the canvas outside the square, or Ctrl-scroll/pinch anywhere, to
|
|
144
|
+
return to its file icons. Outward zoom never opens a file. **×** at the top right
|
|
145
|
+
or Esc goes back one level. The subsystem breadcrumb returns to its retained interface and file browser;
|
|
146
|
+
**Engine** to the retained map. Use Dashboard Files for editing and project-wide
|
|
147
|
+
browsing. A stale, ambiguous or unavailable implementation identity never
|
|
148
|
+
selects a guessed declaration.
|
|
149
|
+
|
|
150
|
+
After following a cited source to another file, **← Back** restores the previous
|
|
151
|
+
file and selected declaration. This history also covers links across subsystems;
|
|
152
|
+
**×**, Esc and the subsystem breadcrumb return to the enclosing browser instead.
|
|
153
|
+
|
|
154
|
+
**Analysis details** holds coverage, visibility and missing-Helper information.
|
|
155
|
+
The file view keeps this secondary information collapsed. Program diagnostics remain inside **Analysis details**. **Code** and saved function explanations remain available
|
|
156
|
+
independently.
|
|
@@ -5,18 +5,105 @@ are separate operations. A different session has its own worktree. Check which
|
|
|
5
5
|
project, session and branch you are using before saving or creating a pull request.
|
|
6
6
|
|
|
7
7
|
Open **Changes** in Dashboard to inspect the work. Use the session's **Save**
|
|
8
|
-
control for its native review and save workflow.
|
|
8
|
+
control for its native review and save workflow. When the selected session has
|
|
9
|
+
unsaved changes, the **Save** button is red, matching the red save icon on that
|
|
10
|
+
session's tab. Managed Vibe64 Git saves a version;
|
|
9
11
|
GitHub workflows use your repository permissions and the project's direct-push or
|
|
10
12
|
pull-request policy. **Update this session (rebase)** reconciles newer saved project
|
|
11
13
|
work when offered; Save does not silently perform that update for you. A failed or
|
|
12
14
|
uncertain publication needs a state check before another request.
|
|
13
15
|
|
|
16
|
+
Whenever Save or Update reports a problem, its activity panel offers **Fix it with
|
|
17
|
+
AI**, which opens a temporary repair chat with the exact error and asks it to
|
|
18
|
+
preserve all work. Ordinary failures also keep **Retry**; conflicts and diverged
|
|
19
|
+
history offer only the repair, because retrying alone cannot succeed. Review the
|
|
20
|
+
repair's result, then retry the operation. Selecting the button requires the
|
|
21
|
+
person's interaction; Colleague can explain it.
|
|
22
|
+
|
|
23
|
+
For Genesis projects, Save checks the selected Stack contracts before asking the
|
|
24
|
+
assistant to name the version. If it reports a missing **Connected development**
|
|
25
|
+
section, the project needs its Stack reconciled; retrying Save alone does not
|
|
26
|
+
repair it. Ask the coding agent to reconcile the existing selected component as
|
|
27
|
+
the error directs, preserving the project's authored setup and output sections.
|
|
28
|
+
This does not require installing dependencies or preparing the database. Review
|
|
29
|
+
the repair, then use **Save** again. The failed preflight leaves your source and
|
|
30
|
+
published version unchanged. Colleague can explain this recovery; the coding
|
|
31
|
+
agent performs the source repair. These steps apply on desktop and mobile.
|
|
32
|
+
|
|
33
|
+
If assistant naming is unavailable, Save uses a checkpoint-based version name
|
|
34
|
+
and continues. A successful Save clears that nonfatal diagnostic from its current
|
|
35
|
+
failure status; the fallback notice remains in its progress history. Check the
|
|
36
|
+
final Save result and the session's **All work is saved** indicator rather than
|
|
37
|
+
treating the naming notice as a failed push.
|
|
38
|
+
|
|
39
|
+
If a push loses its response, Vibe64 checks the exact prepared commit on the
|
|
40
|
+
remote before treating it as failed. If the remote cannot be read, restore access
|
|
41
|
+
and inspect the session's work again. Recovery uses the original Save operation
|
|
42
|
+
and Git evidence, including after an editor restart, without another push. A
|
|
43
|
+
failed local update after publication uses the same recovery. If Git confirms
|
|
44
|
+
that nothing was published, the original rejection remains visible or an
|
|
45
|
+
uncertain attempt becomes explicitly retryable. Colleague can inspect work and
|
|
46
|
+
explain that result; a new Save still requires your instruction.
|
|
47
|
+
|
|
48
|
+
Save and Update can take time. Existing temporary chats remain readable, and
|
|
49
|
+
plain text typed in an existing chat is saved without waiting for the source
|
|
50
|
+
operation. A new assistant send or change to its model or attachments waits
|
|
51
|
+
until that operation finishes. If the Update request loses its response, inspect
|
|
52
|
+
the current Update operation in this session before starting another one; a
|
|
53
|
+
disconnected browser does not prove that Update failed or succeeded.
|
|
54
|
+
|
|
55
|
+
Use **Dismiss** to hide an inactive Save or Update notice. This browser remembers
|
|
56
|
+
each dismissed operation in that project and session, including after reload or
|
|
57
|
+
dismissing another notice. A new failed attempt still appears. Dismiss changes
|
|
58
|
+
only the notice; it does not resolve a repository failure or stop active work.
|
|
59
|
+
On phones, reveal chat to reach the notice and its controls.
|
|
60
|
+
|
|
61
|
+
## Apply an Update after resolving conflicts
|
|
62
|
+
|
|
63
|
+
If Update reports conflicting files, repair them manually, in Main chat, or with
|
|
64
|
+
**Fix it with AI**. Preserve the intended changes from both versions. Wait for
|
|
65
|
+
coding work to finish, then:
|
|
66
|
+
|
|
67
|
+
1. Select **Review resolved conflicts** on the Update error. If an Update repair
|
|
68
|
+
chat is open, the same control appears beside **Check Update** in its repair
|
|
69
|
+
status area.
|
|
70
|
+
2. Review every file listed in **Apply resolved Update**. Select **Cancel** if
|
|
71
|
+
further repair is needed; cancelling leaves the files unchanged.
|
|
72
|
+
3. Select **I've resolved these conflicts — apply Update** to acknowledge the
|
|
73
|
+
repair and run Update. This works even when no repair chat exists or its AI
|
|
74
|
+
was stopped or failed. It does not Save, push or publish the work.
|
|
75
|
+
|
|
76
|
+
On phones, reveal chat to reach the Update error or repair tab; the file review
|
|
77
|
+
and confirmation are the same as on desktop. The controls wait while an assistant
|
|
78
|
+
or repository operation is busy. A changed conflict invalidates an open review.
|
|
79
|
+
If Update refuses a stale review or finds remaining conflicts, inspect the new
|
|
80
|
+
diagnostic, finish the repair and review again. This manual action does not send
|
|
81
|
+
another AI request. Successful Update may still require workspace preparation;
|
|
82
|
+
its result does not establish that application tests passed.
|
|
83
|
+
|
|
84
|
+
**Check Update** is a plain retry, not an acknowledgement that conflicting files
|
|
85
|
+
are resolved. A completed **Fix it with AI** repair still submits its recorded
|
|
86
|
+
review automatically, subject to the same repository checks.
|
|
87
|
+
|
|
88
|
+
Colleague can explain these steps and offer a supported Update after a coding
|
|
89
|
+
agent verifies the repair. A how-to question does not authorize it. Main coding
|
|
90
|
+
chat can repair files but has no Vibe64 Update command; the person can use the
|
|
91
|
+
review control without starting another AI conversation.
|
|
92
|
+
|
|
93
|
+
## Issues and pull requests
|
|
94
|
+
|
|
14
95
|
Use **Issues** or **Pull requests** in the project Dashboard for the repository's
|
|
15
96
|
records. Search or select the exact issue/PR before changing it or adding a comment.
|
|
16
97
|
External writes use the connected person's GitHub identity; missing sign-in or
|
|
17
98
|
repository access cannot be bypassed by using another workspace account.
|
|
18
99
|
On mobile, reveal the project and choose the corresponding **Dashboard section**.
|
|
19
100
|
|
|
101
|
+
Creating a pull request uses the same connected-work checks as Main Save. Save
|
|
102
|
+
connected work first, merge its submitted revisions in the receiving projects,
|
|
103
|
+
and Update those connected sessions to the accepted source before creating the
|
|
104
|
+
pull request. Changed source or revoked receiving access stops publication;
|
|
105
|
+
creating a pull request does not bypass those checks.
|
|
106
|
+
|
|
20
107
|
Colleague can explain these workflows, open their views, inspect bounded saved-work
|
|
21
108
|
status, request native Save/Update, and use supported issue/PR actions when asked.
|
|
22
109
|
It delegates code/diff investigation to a coding agent rather than reading the
|
|
@@ -0,0 +1,32 @@
|
|
|
1
|
+
# Check that this installation is ready (Health)
|
|
2
|
+
|
|
3
|
+
**Dashboard → Health** (the **Studio Health** page) runs this installation's readiness checks and shows each
|
|
4
|
+
one as pass or fail, with what was expected and what was observed. Use **Refresh**
|
|
5
|
+
to run them again after fixing something. On a phone, open Dashboard, then choose
|
|
6
|
+
**Health** from the section menu.
|
|
7
|
+
|
|
8
|
+
| Check | Group | What a failure means |
|
|
9
|
+
| --- | --- | --- |
|
|
10
|
+
| Workspace services | Studio | The Vibe64 installation or its project list cannot be read. |
|
|
11
|
+
| AI connection | Credentials | No AI provider is connected; open **Account settings → AI Accounts**. |
|
|
12
|
+
| Node.js, Git, GitHub CLI, ripgrep, Codex CLI, Genesis | Runtime | That program is missing or the wrong version on this machine; install it with the system's normal installer. |
|
|
13
|
+
| Playwright runtime, Pinned browser | Browser | Only automated browser tests need these; other work is unaffected. |
|
|
14
|
+
|
|
15
|
+
GitHub sign-in is not a Health check. **Account settings → GitHub** shows the
|
|
16
|
+
**GitHub Connection** card: **Connection ready** means Vibe64 can use GitHub.
|
|
17
|
+
That card also holds **Git user.name**, **Git user.email** and **Save Git identity**.
|
|
18
|
+
|
|
19
|
+
Health only reads. It never installs software, signs in or repairs anything, and
|
|
20
|
+
a pass is not proof that a particular project builds.
|
|
21
|
+
|
|
22
|
+
## Ask Colleague
|
|
23
|
+
|
|
24
|
+
Ask Colleague "check my setup" (or similar). Colleague runs the same Health checks
|
|
25
|
+
and tells you which ones fail and what to do next for your system. It can open
|
|
26
|
+
**Account settings** for you. Installing programs, signing in to GitHub or an AI
|
|
27
|
+
provider, and entering keys are things you do yourself; never paste a key or
|
|
28
|
+
password into chat. Long command output stays on the Health page; Colleague sees a
|
|
29
|
+
short summary of each check.
|
|
30
|
+
|
|
31
|
+
Local Vibe64's Lesson 0, **Set yourself up**, walks through these checks one step
|
|
32
|
+
at a time.
|
|
@@ -0,0 +1,94 @@
|
|
|
1
|
+
# Review incoming contributions
|
|
2
|
+
|
|
3
|
+
Open the receiving GitHub project and choose **Dashboard → Incoming changes**.
|
|
4
|
+
On a phone, choose **Show project**, then **Dashboard section → Incoming changes**.
|
|
5
|
+
Select or create a working session if asked; its checkout supplies Git storage,
|
|
6
|
+
while the queue and integration target belong to the project and are shared by
|
|
7
|
+
all its sessions. The menu badge counts pending contributions when a read succeeds.
|
|
8
|
+
|
|
9
|
+
The default **Contribution state** is **Pending**. Use **Merged**, **Discarded**,
|
|
10
|
+
**Unresolved**, or **All** to inspect other outcomes. **Previous page** and **Next
|
|
11
|
+
page** keep large lists manageable. Only branches named
|
|
12
|
+
`vibe64-incoming/<contribution-id>` and their `_discarded` counterparts appear;
|
|
13
|
+
ordinary feature branches are not submissions. No separate queue needs copying
|
|
14
|
+
to another machine.
|
|
15
|
+
|
|
16
|
+
Choose **Review** beside a contribution. It shows the commit title, changed-file
|
|
17
|
+
count, exact contribution and target commits, and a bounded diff. A truncated
|
|
18
|
+
diff is labelled; ask a coding agent to inspect the complete change before
|
|
19
|
+
integration. **Back** returns to your preceding project page, with Dashboard as
|
|
20
|
+
the direct-entry fallback. **All incoming changes** returns to the retained list
|
|
21
|
+
filter and page.
|
|
22
|
+
|
|
23
|
+
**Merge into <target>** opens a confirmation for the reviewed commit. **Merge
|
|
24
|
+
contribution** integrates it by fast-forward or an ordinary merge commit, keeping
|
|
25
|
+
its ancestry and contribution branch. It does not update session files or save
|
|
26
|
+
unsaved work. Use the ordinary session Update workflow to consume accepted work.
|
|
27
|
+
The contribution then appears under Merged.
|
|
28
|
+
|
|
29
|
+
**Discard contribution** asks for confirmation, then renames the branch with
|
|
30
|
+
`_discarded` appended. Commits, author checkout and unsaved work remain. Discard
|
|
31
|
+
does not satisfy a dependency or unblock its originating project's Save.
|
|
32
|
+
|
|
33
|
+
Your current GitHub account must have write access to the receiving repository.
|
|
34
|
+
Archived or disabled repositories refuse mutations. A project configured to
|
|
35
|
+
require pull requests refuses direct Incoming merges; GitHub's own protections
|
|
36
|
+
also apply. Colleague must report the constraint, not change that policy merely
|
|
37
|
+
to make Merge succeed.
|
|
38
|
+
|
|
39
|
+
If a branch or target changed since Review, refresh and review again. Vibe64
|
|
40
|
+
rebuilds generated Genesis maps from the proposed merged source; generated-only
|
|
41
|
+
conflicts do not need AI or manual edits. Authored conflicts
|
|
42
|
+
leave the remote target and receiving session files unchanged. Vibe64 retains a
|
|
43
|
+
private checkpoint of that session's complete work before offering **Fix it with
|
|
44
|
+
AI**. The existing Temporary AI chat starts with Senior in this receiving session;
|
|
45
|
+
its Senior model and account must be available. It uses the working session
|
|
46
|
+
currently selected in the receiving project and receives the exact reviewed
|
|
47
|
+
commits and conflicting paths. It repairs those
|
|
48
|
+
working files without committing, rebasing or publishing. You can also repair
|
|
49
|
+
them manually. Preserve unrelated work and inspect both sides' intended behavior.
|
|
50
|
+
|
|
51
|
+
When repair finishes, return to **Incoming changes → Review resolved conflicts**.
|
|
52
|
+
This displays the proposed merge using the repaired conflicting files and the
|
|
53
|
+
ordinary merge result for every other authored file, with regenerated Genesis
|
|
54
|
+
maps included in the diff. Do not hand-edit generated maps. If regeneration
|
|
55
|
+
fails, the merge stops without publishing or changing your session files.
|
|
56
|
+
Unrelated local changes are excluded.
|
|
57
|
+
Review that diff, then explicitly choose **Merge into <target> → Merge contribution**.
|
|
58
|
+
Vibe64 rechecks the candidate, receiving worktree/index/HEAD and both remote heads.
|
|
59
|
+
Changed inputs require another review. AI completion alone never publishes or
|
|
60
|
+
proves a merge. The merge preserves both parents; local files, staged changes and
|
|
61
|
+
the contribution branch remain available. Use ordinary Update to reconcile the
|
|
62
|
+
receiving session afterwards.
|
|
63
|
+
|
|
64
|
+
Temporary chat and private checkpoints retain their existing recovery lifecycle.
|
|
65
|
+
Reloading clears the transient merge review: refresh, try Merge to rediscover any
|
|
66
|
+
remaining conflict, then review the resolved files again. This does not restart
|
|
67
|
+
AI or discard its edits. After an uncertain response, **Refresh** inspects Git before another action is enabled.
|
|
68
|
+
An unavailable remote or incomplete history is an error, not proof of merging.
|
|
69
|
+
|
|
70
|
+
An interrupted discard can leave both branches. The default view points to
|
|
71
|
+
**Review interrupted discards**. Under Unresolved, **Finish discard** is available
|
|
72
|
+
only when both branches still identify the same commit. Different heads require
|
|
73
|
+
a coding agent's inspection; do not erase one to clear the warning. A discarded
|
|
74
|
+
commit already contained in the integration target still counts as merged.
|
|
75
|
+
|
|
76
|
+
Colleague can list and inspect bounded contribution summaries and perform an
|
|
77
|
+
explicitly requested Merge or Discard through these same authorized actions.
|
|
78
|
+
It receives exact review identities but no source contents or diffs. A how-to
|
|
79
|
+
question does not authorize a mutation; code review and conflict resolution
|
|
80
|
+
belong to a coding agent. GitHub login and permission grants remain human steps.
|
|
81
|
+
|
|
82
|
+
This receiving view supports configured GitHub projects. The originating task's
|
|
83
|
+
ordinary workspace preparation prepares its configured connected sources through
|
|
84
|
+
the existing receiving-project permissions and Stack recipe. See
|
|
85
|
+
[Connected projects](connected-projects.md) for that setup and Save flow.
|
|
86
|
+
Local-folder repositories do not provide this GitHub Incoming queue.
|
|
87
|
+
|
|
88
|
+
|
|
89
|
+
To revise a discarded contribution, return to its originating session and use
|
|
90
|
+
Save's **Review replacement contribution** recovery control. Confirm the exact
|
|
91
|
+
revision to prepare a new contribution, then open that replacement session.
|
|
92
|
+
The old branch and checkout remain; unsaved old edits are not copied silently.
|
|
93
|
+
See [connected-project replacement and retry](connected-projects.md) for the
|
|
94
|
+
preparation, submission and acceptance steps. Discard never unblocks Main Save.
|
|
@@ -3,7 +3,7 @@
|
|
|
3
3
|
On an installation with supported Learning controls, the Working/Learning filter
|
|
4
4
|
changes which sessions you see in the existing chat panel. Hiding a lesson chat
|
|
5
5
|
does not stop its work, discard its draft or send another message. Return to that
|
|
6
|
-
saved lesson conversation to see its retained history and draft. The
|
|
6
|
+
saved lesson conversation to see its retained history and draft. The **L** button
|
|
7
7
|
switch preserves where you were reading in each mode. Ordinary session selection
|
|
8
8
|
and collapsing or reopening chat keep their existing scroll-to-latest behavior.
|
|
9
9
|
|
|
@@ -31,7 +31,8 @@ Helper or changed lesson access leaves the name unchanged. A manual rename wins
|
|
|
31
31
|
over an automatic name. Do not repeat a lesson message just to obtain a name;
|
|
32
32
|
use Rename session when it is available. These rules also apply on phones.
|
|
33
33
|
They do not show a Working-session Archive button, source branch or repository
|
|
34
|
-
save-status icon.
|
|
34
|
+
save-status icon. To end a lesson, ask Colleague (see
|
|
35
|
+
[Lesson history and resume](learning-history.md)); an ordinary
|
|
35
36
|
Working tab keeps its existing Archive and repository status.
|
|
36
37
|
|
|
37
38
|
A lesson without a practice project has no project workspace to Save, prepare,
|
|
@@ -48,6 +49,14 @@ not keep a lesson chat visible after your own lesson list no longer grants acces
|
|
|
48
49
|
Colleague can explain the supported controls and offer authorized
|
|
49
50
|
operations; an offer is not permission to start or repeat a lesson.
|
|
50
51
|
|
|
52
|
+
Opening or reconnecting a lesson chat verifies your saved attempt and the exact
|
|
53
|
+
pinned lesson identity. Damage to unrelated teaching files does not prevent
|
|
54
|
+
reading that chat history. Teaching, grading and preparing exercise content still
|
|
55
|
+
require full content validation; an open chat does not prove the installed course
|
|
56
|
+
is healthy. If content validation fails, ask the owner to restore the exact pinned
|
|
57
|
+
snapshot before continuing. A changed pin or selected lesson descriptor still
|
|
58
|
+
prevents admission. Colleague can explain this recovery without changing your pin.
|
|
59
|
+
|
|
51
60
|
When the Main teacher has delivered a question, a typed answer carries that
|
|
52
61
|
question's reference through the same Send operation. Speech captures the
|
|
53
62
|
reference when that recording starts. A later question cannot silently become
|