specrails-desktop 2.20.1 → 2.22.0
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/README.md +3 -2
- package/client/dist/assets/{ActivityFeedPage-3WSqRYVx.js → ActivityFeedPage-roDyKGuv.js} +1 -1
- package/client/dist/assets/AgentBrowserCapture-BsXnWa4j.js +1 -0
- package/client/dist/assets/{AgentModeCodePane-Cnsea6eZ.js → AgentModeCodePane-o97EJvbJ.js} +2 -2
- package/client/dist/assets/AgentModeJobsPane-CLtpPxPM.js +1 -0
- package/client/dist/assets/AgentsPage-eNSo_ZcC.js +86 -0
- package/client/dist/assets/AnalyticsPage-cAJ60_Ex.js +1 -0
- package/client/dist/assets/{BarChart-C6If656N.js → BarChart-NLtK7xAY.js} +1 -1
- package/client/dist/assets/CodePage-B5rum8ZB.js +2 -0
- package/client/dist/assets/DesktopAnalyticsPage-DSuvG6Tq.js +1 -0
- package/client/dist/assets/DocsDialog-Bo38G3Yc.js +11 -0
- package/client/dist/assets/DocsPage-BNkiBBrC.js +11 -0
- package/client/dist/assets/{ExportDropdown-CezTK0EX.js → ExportDropdown-DCV8PN4-.js} +1 -1
- package/client/dist/assets/IntegrationsPage-BMJOzpPz.js +3 -0
- package/client/dist/assets/InteractiveJobComposer-aLduNs5R.js +19 -0
- package/client/dist/assets/JobDetailModal-kpkUWJIS.js +1 -0
- package/client/dist/assets/JobDetailPage-CFeqlrPU.js +1 -0
- package/client/dist/assets/JobsPage-fuwhXy2I.js +1 -0
- package/client/dist/assets/LoopBuilderPage-DP66322C.js +7 -0
- package/client/dist/assets/LoopPreviewModal-CpmBhE31.js +1 -0
- package/client/dist/assets/LoopsPage-CvQ18VUx.js +1 -0
- package/client/dist/assets/ProjectSettingsDialog-Deq4pwvq.js +1 -0
- package/client/dist/assets/TemplatePreviewModal-DziOj2Ct.js +1 -0
- package/client/dist/assets/agent-Csh4kP2S.js +1 -0
- package/client/dist/assets/agent-Cz_jgQX32.js +1 -0
- package/client/dist/assets/agent-D3vcIvaz2.js +1 -0
- package/client/dist/assets/agent-Dnbt0V4e.js +1 -0
- package/client/dist/assets/agent-HolR7QrZ.js +1 -0
- package/client/dist/assets/agent-Ka0rRWJy.js +1 -0
- package/client/dist/assets/agent-Te3yysMd.js +1 -0
- package/client/dist/assets/agent-vM4_iLDk2.js +1 -0
- package/client/dist/assets/{upload-CRtTj4Co.js → brain-kFJuEDNH.js} +1 -1
- package/client/dist/assets/{browser-DEEO-OSi.js → browser-BPkhILSJ.js} +1 -1
- package/client/dist/assets/{browser-BTivfZKE2.js → browser-BijVYG0Y2.js} +1 -1
- package/client/dist/assets/{browser-bpO3onlS.js → browser-BqLqJVVT.js} +1 -1
- package/client/dist/assets/{browser-DlSXtfu5.js → browser-Cc0iDqUi.js} +1 -1
- package/client/dist/assets/browser-CdS6O1Qb.js +1 -0
- package/client/dist/assets/{browser-BKP6hqQC2.js → browser-Cvg-QHvd2.js} +1 -1
- package/client/dist/assets/{browser-INCUyduh.js → browser-FRv8P02E.js} +1 -1
- package/client/dist/assets/{browser-DlKLfT612.js → browser-rWKj-RR_2.js} +1 -1
- package/client/dist/assets/code-BRcDlze52.js +1 -0
- package/client/dist/assets/code-BdMy3Ffq.js +1 -0
- package/client/dist/assets/code-CeQ0FZpC.js +1 -0
- package/client/dist/assets/code-CqCcRThR.js +1 -0
- package/client/dist/assets/code-DgeHz9CB.js +1 -0
- package/client/dist/assets/code-DzC1rMk12.js +1 -0
- package/client/dist/assets/code-UPVvmAKM2.js +1 -0
- package/client/dist/assets/code-thSEptMx.js +1 -0
- package/client/dist/assets/{common-QjVnq9XP2.js → common-BM3LFLCE2.js} +1 -1
- package/client/dist/assets/{common-CeQUwuHt2.js → common-Bwafujnc2.js} +1 -1
- package/client/dist/assets/{common-Bb64s3Bm.js → common-C-vU-j-I.js} +1 -1
- package/client/dist/assets/{common-KbQuTSGg.js → common-C5HKSbbz.js} +1 -1
- package/client/dist/assets/{common-BPQQkgJZ.js → common-CYaT2yHp.js} +1 -1
- package/client/dist/assets/{common-DPxotRK9.js → common-DhWTkocg.js} +1 -1
- package/client/dist/assets/{common-k5MTOHpn.js → common-DiPTT7V_2.js} +1 -1
- package/client/dist/assets/{common-C8ZD5upH2.js → common-DmqBPwZG.js} +1 -1
- package/client/dist/assets/{cssMode-DsArsSCT.js → cssMode-DBHbkBvI.js} +1 -1
- package/client/dist/assets/dashboard-BaStj_a_.js +1 -0
- package/client/dist/assets/dashboard-Bi6ugu5Q.js +1 -0
- package/client/dist/assets/dashboard-BmqTn3L02.js +1 -0
- package/client/dist/assets/dashboard-CvT8lOCT.js +1 -0
- package/client/dist/assets/dashboard-D7Pmeavq2.js +1 -0
- package/client/dist/assets/dashboard-DAnWdAac2.js +1 -0
- package/client/dist/assets/dashboard-JnYy2WLg.js +1 -0
- package/client/dist/assets/dashboard-L47YsFS_.js +1 -0
- package/client/dist/assets/{dist-js-BQn4yxaw.js → dist-js-BZSiJDbG.js} +1 -1
- package/client/dist/assets/{dist-js-BAWSqVtr.js → dist-js-DKpmIJlQ.js} +1 -1
- package/client/dist/assets/{editor.main-G3Sl9C67.js → editor.main-C9J2ikJK.js} +2 -2
- package/client/dist/assets/{freemarker2-pBzQNgFi.js → freemarker2-J5iIIIK-.js} +1 -1
- package/client/dist/assets/{handlebars-CtBTCnBI.js → handlebars-DSw1l_tw.js} +1 -1
- package/client/dist/assets/{html-Dx3DYBzY.js → html-h2-wE1Lj.js} +1 -1
- package/client/dist/assets/{htmlMode-In7frFOo.js → htmlMode-Cc_ij7lW.js} +1 -1
- package/client/dist/assets/index-DM6heiGa.js +155 -0
- package/client/dist/assets/index-DPX6_xIC.css +2 -0
- package/client/dist/assets/{javascript-BKcn-YkN.js → javascript-C1q3xv6N.js} +1 -1
- package/client/dist/assets/jira-B3613-gj.js +1 -0
- package/client/dist/assets/jira-BHAKtc4B.js +1 -0
- package/client/dist/assets/jira-Be369RIR2.js +1 -0
- package/client/dist/assets/jira-CPpgA-5z2.js +1 -0
- package/client/dist/assets/jira-D5efgwp_.js +1 -0
- package/client/dist/assets/jira-DS7ownDy.js +1 -0
- package/client/dist/assets/jira-bDs7Im2C.js +1 -0
- package/client/dist/assets/jira-uNH1gETL2.js +1 -0
- package/client/dist/assets/jobs-1GV2-4zd2.js +1 -0
- package/client/dist/assets/jobs-26F9gGcE.js +1 -0
- package/client/dist/assets/jobs-BgQzB0Sx2.js +1 -0
- package/client/dist/assets/jobs-BqWui9_f.js +1 -0
- package/client/dist/assets/jobs-CE8qeIYj.js +1 -0
- package/client/dist/assets/jobs-D5sZzgLs.js +1 -0
- package/client/dist/assets/jobs-DzeuASRf.js +1 -0
- package/client/dist/assets/jobs-Wh7dn28q2.js +1 -0
- package/client/dist/assets/{jsonMode-jNREoQ3C.js → jsonMode-CeaCdEhr.js} +1 -1
- package/client/dist/assets/{lib-C-g8QbZl.js → lib-B2nCKzmA.js} +1 -1
- package/client/dist/assets/{liquid-CtRkGqBu.js → liquid-eFsVK0V-.js} +1 -1
- package/client/dist/assets/loops-BvEenWBy.js +1 -0
- package/client/dist/assets/loops-CBiWd9Hf.js +1 -0
- package/client/dist/assets/loops-DNGiYKll2.js +1 -0
- package/client/dist/assets/{loops-Y3FQsUCh.js → loops-DjOtVXRo.js} +1 -1
- package/client/dist/assets/loops-HTHf-xu32.js +1 -0
- package/client/dist/assets/loops-YYV2bwjd.js +1 -0
- package/client/dist/assets/loops-hXgncEpF2.js +1 -0
- package/client/dist/assets/loops-kYbydDyN.js +1 -0
- package/client/dist/assets/{lspLanguageFeatures-Cl3gvD_W.js → lspLanguageFeatures-DT3-bbhn.js} +1 -1
- package/client/dist/assets/{mdx-B_nJldHz.js → mdx-Fuwnh1cX.js} +1 -1
- package/client/dist/assets/{monaco.contribution-PUeaZk8T.js → monaco.contribution-Desq7oq4.js} +2 -2
- package/client/dist/assets/{python-DS1Ce-A6.js → python-BgoEs6Cj.js} +1 -1
- package/client/dist/assets/{razor-L41Qg9OK.js → razor-CM1sPMMq.js} +1 -1
- package/client/dist/assets/{settings-BPq9nCJm.js → settings-BOHOmHkb.js} +1 -1
- package/client/dist/assets/{settings-r8Qq2Gzp2.js → settings-BlEA_7h02.js} +1 -1
- package/client/dist/assets/{settings-C-m3yEZ2.js → settings-BsJMsWGc.js} +1 -1
- package/client/dist/assets/{settings-zZr7NzuB.js → settings-D6qY9_UI.js} +1 -1
- package/client/dist/assets/{settings-VgCsjaYf.js → settings-DZJeXoRV.js} +1 -1
- package/client/dist/assets/settings-Mr7MnJbf.js +1 -0
- package/client/dist/assets/{settings-BWHGtmU12.js → settings-TNga5gIF2.js} +1 -1
- package/client/dist/assets/{settings-DZj7Uqy32.js → settings-lFoaYT-s2.js} +1 -1
- package/client/dist/assets/setup-B590KsTX.js +1 -0
- package/client/dist/assets/setup-BkyGoby6.js +1 -0
- package/client/dist/assets/setup-CEj6uY3-2.js +1 -0
- package/client/dist/assets/setup-CbIerFGf2.js +1 -0
- package/client/dist/assets/setup-CmU6bTCV2.js +1 -0
- package/client/dist/assets/setup-D674kWQH.js +1 -0
- package/client/dist/assets/setup-VNqXyB6Y.js +1 -0
- package/client/dist/assets/setup-iY8vH8pB.js +1 -0
- package/client/dist/assets/specs-C9Sd7BhH2.js +1 -0
- package/client/dist/assets/specs-CBDvEYKv.js +1 -0
- package/client/dist/assets/specs-CIPr9reA2.js +1 -0
- package/client/dist/assets/specs-CWtKcVDC.js +1 -0
- package/client/dist/assets/specs-CmEZY57v.js +1 -0
- package/client/dist/assets/specs-D2clrt2c2.js +1 -0
- package/client/dist/assets/specs-DTplt2XM.js +1 -0
- package/client/dist/assets/specs-PozUNhqb.js +1 -0
- package/client/dist/assets/{tsMode-BC1g186U.js → tsMode-BmT8WogI.js} +1 -1
- package/client/dist/assets/{typescript-BGlRGvJW.js → typescript-CQrQPsoW.js} +1 -1
- package/client/dist/assets/upload-CLAzW1mS.js +1 -0
- package/client/dist/assets/{value-D9aLbxw-.js → value-DSwzyyWR.js} +1 -1
- package/client/dist/assets/{workers-CXcXtO3b.js → workers-U0UXyLUf.js} +1 -1
- package/client/dist/assets/{xml-JdZZaIhJ.js → xml-WRxJs8_I.js} +1 -1
- package/client/dist/assets/{yaml-Cm82BVBt.js → yaml-CjpSTjJU.js} +1 -1
- package/client/dist/index.html +14 -14
- package/docs/customizing.md +2 -2
- package/docs/gemini.md +15 -4
- package/docs/guide/de/insights/3-code-explorer.md +6 -0
- package/docs/guide/de/integrations/3-jira-integration.md +1 -1
- package/docs/guide/de/integrations/6-agent-chat.md +5 -0
- package/docs/guide/de/pipeline/1-rails-and-jobs.md +6 -6
- package/docs/guide/de/pipeline/2-the-job-detail-view.md +27 -2
- package/docs/guide/de/pipeline/3-batch-implement-and-multi-feature.md +9 -5
- package/docs/guide/de/pipeline/5-the-loop-builder.md +1 -1
- package/docs/guide/de/specs/1-specs-and-the-backlog.md +3 -2
- package/docs/guide/en/insights/3-code-explorer.md +6 -0
- package/docs/guide/en/integrations/3-jira-integration.md +1 -1
- package/docs/guide/en/integrations/6-agent-chat.md +5 -0
- package/docs/guide/en/pipeline/1-rails-and-jobs.md +6 -6
- package/docs/guide/en/pipeline/2-the-job-detail-view.md +27 -2
- package/docs/guide/en/pipeline/3-batch-implement-and-multi-feature.md +10 -4
- package/docs/guide/en/pipeline/5-the-loop-builder.md +1 -1
- package/docs/guide/en/specs/1-specs-and-the-backlog.md +3 -2
- package/docs/guide/es/insights/3-code-explorer.md +6 -0
- package/docs/guide/es/integrations/3-jira-integration.md +1 -1
- package/docs/guide/es/integrations/6-agent-chat.md +5 -0
- package/docs/guide/es/pipeline/1-rails-and-jobs.md +6 -6
- package/docs/guide/es/pipeline/2-the-job-detail-view.md +27 -2
- package/docs/guide/es/pipeline/3-batch-implement-and-multi-feature.md +9 -5
- package/docs/guide/es/pipeline/5-the-loop-builder.md +1 -1
- package/docs/guide/es/specs/1-specs-and-the-backlog.md +3 -2
- package/docs/guide/fr/insights/3-code-explorer.md +6 -0
- package/docs/guide/fr/integrations/3-jira-integration.md +1 -1
- package/docs/guide/fr/integrations/6-agent-chat.md +5 -0
- package/docs/guide/fr/pipeline/1-rails-and-jobs.md +6 -6
- package/docs/guide/fr/pipeline/2-the-job-detail-view.md +27 -2
- package/docs/guide/fr/pipeline/3-batch-implement-and-multi-feature.md +9 -5
- package/docs/guide/fr/pipeline/5-the-loop-builder.md +1 -1
- package/docs/guide/fr/specs/1-specs-and-the-backlog.md +3 -2
- package/docs/guide/it/insights/3-code-explorer.md +6 -0
- package/docs/guide/it/integrations/3-jira-integration.md +1 -1
- package/docs/guide/it/integrations/6-agent-chat.md +5 -0
- package/docs/guide/it/pipeline/1-rails-and-jobs.md +6 -6
- package/docs/guide/it/pipeline/2-the-job-detail-view.md +27 -2
- package/docs/guide/it/pipeline/3-batch-implement-and-multi-feature.md +10 -6
- package/docs/guide/it/pipeline/5-the-loop-builder.md +1 -1
- package/docs/guide/it/specs/1-specs-and-the-backlog.md +3 -2
- package/docs/guide/ja/insights/3-code-explorer.md +6 -0
- package/docs/guide/ja/integrations/3-jira-integration.md +1 -1
- package/docs/guide/ja/integrations/6-agent-chat.md +5 -0
- package/docs/guide/ja/pipeline/1-rails-and-jobs.md +6 -6
- package/docs/guide/ja/pipeline/2-the-job-detail-view.md +27 -2
- package/docs/guide/ja/pipeline/3-batch-implement-and-multi-feature.md +9 -5
- package/docs/guide/ja/pipeline/5-the-loop-builder.md +1 -1
- package/docs/guide/ja/specs/1-specs-and-the-backlog.md +3 -2
- package/docs/guide/pt/insights/3-code-explorer.md +6 -0
- package/docs/guide/pt/integrations/3-jira-integration.md +1 -1
- package/docs/guide/pt/integrations/6-agent-chat.md +5 -0
- package/docs/guide/pt/pipeline/1-rails-and-jobs.md +6 -6
- package/docs/guide/pt/pipeline/2-the-job-detail-view.md +27 -2
- package/docs/guide/pt/pipeline/3-batch-implement-and-multi-feature.md +9 -5
- package/docs/guide/pt/pipeline/5-the-loop-builder.md +1 -1
- package/docs/guide/pt/specs/1-specs-and-the-backlog.md +3 -2
- package/docs/guide/zh/insights/3-code-explorer.md +6 -0
- package/docs/guide/zh/integrations/3-jira-integration.md +1 -1
- package/docs/guide/zh/integrations/6-agent-chat.md +5 -0
- package/docs/guide/zh/pipeline/1-rails-and-jobs.md +6 -6
- package/docs/guide/zh/pipeline/2-the-job-detail-view.md +27 -2
- package/docs/guide/zh/pipeline/3-batch-implement-and-multi-feature.md +10 -6
- package/docs/guide/zh/pipeline/5-the-loop-builder.md +1 -1
- package/docs/guide/zh/specs/1-specs-and-the-backlog.md +3 -2
- package/docs/internals/README.md +5 -0
- package/docs/internals/adding-a-provider.md +15 -3
- package/docs/internals/api-reference.md +6 -5
- package/docs/internals/browser-capture-performance.md +93 -0
- package/docs/internals/code-explorer-story.md +135 -0
- package/docs/internals/gemini-mcp-registration.md +53 -0
- package/docs/internals/interactive-jobs.md +212 -0
- package/docs/internals/loop-step-log-explorer.md +146 -0
- package/docs/internals/safe-pr-review-flow.md +367 -0
- package/docs/mcp.md +1 -1
- package/docs/running-pipelines.md +6 -2
- package/package.json +1 -1
- package/server/dist/agent-chat-manager.js +211 -0
- package/server/dist/agent-chat-registry.js +20 -0
- package/server/dist/agent-chat-router.js +22 -0
- package/server/dist/agent-mcp-config.js +45 -4
- package/server/dist/agent-operator-prompt.js +149 -56
- package/server/dist/agent-store.js +25 -0
- package/server/dist/agent-tier.js +6 -1
- package/server/dist/browser-capture-manager.js +184 -34
- package/server/dist/browser-playwright.js +98 -13
- package/server/dist/code-explorer-router.js +92 -0
- package/server/dist/db.js +102 -0
- package/server/dist/file-provenance.js +54 -1
- package/server/dist/file-story-manager.js +170 -0
- package/server/dist/file-story.js +148 -0
- package/server/dist/file-summary-generator.js +5 -4
- package/server/dist/git-guardrails.js +62 -0
- package/server/dist/index.js +5 -0
- package/server/dist/integration-branch.js +63 -0
- package/server/dist/interactive-job-session.js +226 -18
- package/server/dist/jira/jira-adf.js +9 -0
- package/server/dist/jira/jira-materializer.js +27 -4
- package/server/dist/jira/jira-status-resolver.js +12 -4
- package/server/dist/jira/jira-sync-manager.js +130 -2
- package/server/dist/jira-router.js +1 -1
- package/server/dist/loop-effect.js +12 -0
- package/server/dist/loop-executors.js +92 -22
- package/server/dist/loop-run-manager.js +354 -28
- package/server/dist/mcp/guide.js +18 -7
- package/server/dist/mcp/tools/jira.js +1 -1
- package/server/dist/mcp/tools/jobs.js +14 -5
- package/server/dist/mcp/tools/rails.js +137 -12
- package/server/dist/mcp/tools/specs.js +35 -9
- package/server/dist/mcp/tools/types.js +49 -0
- package/server/dist/mobile/mobile-ws.js +4 -0
- package/server/dist/path-resolver.js +46 -0
- package/server/dist/pr-body.js +240 -0
- package/server/dist/pr-naming.js +210 -0
- package/server/dist/pr-publisher.js +68 -0
- package/server/dist/project-registry.js +77 -17
- package/server/dist/project-router-jobs.js +53 -13
- package/server/dist/project-router-settings.js +33 -0
- package/server/dist/project-router-terminals.js +16 -0
- package/server/dist/project-router-tickets.js +57 -3
- package/server/dist/project-router.js +52 -13
- package/server/dist/queue-manager.js +268 -83
- package/server/dist/rail-isolated-launch.js +324 -34
- package/server/dist/rail-isolation.js +32 -5
- package/server/dist/rail-pr-decision.js +519 -0
- package/server/dist/rail-pr-delivery.js +75 -0
- package/server/dist/rail-pr-store.js +175 -0
- package/server/dist/rail-worktrees-store.js +18 -0
- package/server/dist/rails-router.js +241 -17
- package/server/dist/rails-store.js +78 -1
- package/server/dist/setup-prerequisites.js +105 -0
- package/server/dist/smash-runner.js +3 -1
- package/server/dist/ticket-store.js +7 -3
- package/server/dist/workspace-resolution.js +27 -0
- package/server/dist/worktree-manager.js +42 -7
- package/server/dist/worktree-overlay.js +261 -0
- package/client/dist/assets/AgentBrowserCapture-BlGDZahz.js +0 -1
- package/client/dist/assets/AgentModeJobsPane-CyNR-9BO.js +0 -1
- package/client/dist/assets/AgentsPage-dNsEsY_x.js +0 -86
- package/client/dist/assets/AnalyticsPage-BAxmR0HQ.js +0 -1
- package/client/dist/assets/CodePage-Crc4BBQN.js +0 -2
- package/client/dist/assets/DesktopAnalyticsPage-IXSnbCce.js +0 -1
- package/client/dist/assets/DocsDialog-Bc4hx7oW.js +0 -11
- package/client/dist/assets/DocsPage-bEU4t9c6.js +0 -11
- package/client/dist/assets/IntegrationsPage-wq2CezEL.js +0 -3
- package/client/dist/assets/JobDetailPage-BBcPk3j8.js +0 -1
- package/client/dist/assets/JobsPage-DXrSPlwa.js +0 -1
- package/client/dist/assets/LogViewer-BoYbwvbU.js +0 -16
- package/client/dist/assets/LoopBuilderPage-CiUMAuWz.js +0 -7
- package/client/dist/assets/LoopsPage-Xrp6W5XW.js +0 -1
- package/client/dist/assets/ProjectSettingsDialog-BU98L5JD.js +0 -1
- package/client/dist/assets/agent-B7GdHP3Z.js +0 -1
- package/client/dist/assets/agent-BHmcgoJf.js +0 -1
- package/client/dist/assets/agent-BdY_fii4.js +0 -1
- package/client/dist/assets/agent-C32FOi9v.js +0 -1
- package/client/dist/assets/agent-CiFQxoaZ2.js +0 -1
- package/client/dist/assets/agent-CtAag7V6.js +0 -1
- package/client/dist/assets/agent-DE4Mp1fY2.js +0 -1
- package/client/dist/assets/agent-DK8qovyG2.js +0 -1
- package/client/dist/assets/browser-ZB1afzjZ.js +0 -1
- package/client/dist/assets/code-BFxE1Yt62.js +0 -1
- package/client/dist/assets/code-BefYOm5Q.js +0 -1
- package/client/dist/assets/code-BkXpJt99.js +0 -1
- package/client/dist/assets/code-C6Sq7_t8.js +0 -1
- package/client/dist/assets/code-CGj3w-2N.js +0 -1
- package/client/dist/assets/code-Dfsxc9o82.js +0 -1
- package/client/dist/assets/code-Y5urks5s2.js +0 -1
- package/client/dist/assets/code-wtcs0ivb.js +0 -1
- package/client/dist/assets/dashboard-B8032psZ.js +0 -1
- package/client/dist/assets/dashboard-BHGKtxty2.js +0 -1
- package/client/dist/assets/dashboard-CXnoUgN22.js +0 -1
- package/client/dist/assets/dashboard-Ccyxqy7d.js +0 -1
- package/client/dist/assets/dashboard-CoED_41r.js +0 -1
- package/client/dist/assets/dashboard-Dc5ZAgMN.js +0 -1
- package/client/dist/assets/dashboard-JMY8ueD3.js +0 -1
- package/client/dist/assets/dashboard-tkWr1aHD2.js +0 -1
- package/client/dist/assets/index-BHPbzyg6.css +0 -2
- package/client/dist/assets/index-n2PmJGF6.js +0 -152
- package/client/dist/assets/jira-BcZzX9122.js +0 -1
- package/client/dist/assets/jira-CTYs7LA12.js +0 -1
- package/client/dist/assets/jira-D2nN39e92.js +0 -1
- package/client/dist/assets/jira-DJxmIkyr.js +0 -1
- package/client/dist/assets/jira-DXMoAKWD.js +0 -1
- package/client/dist/assets/jira-IhC1ROIc.js +0 -1
- package/client/dist/assets/jira-Iw575fN8.js +0 -1
- package/client/dist/assets/jira-kbWZY7jH.js +0 -1
- package/client/dist/assets/jobs-BqF79kHz2.js +0 -1
- package/client/dist/assets/jobs-C1XM5urS.js +0 -1
- package/client/dist/assets/jobs-C5UjG0262.js +0 -1
- package/client/dist/assets/jobs-DBfaHTxC.js +0 -1
- package/client/dist/assets/jobs-DM4BDPdg.js +0 -1
- package/client/dist/assets/jobs-Da5OkZmf2.js +0 -1
- package/client/dist/assets/jobs-JJdnuQ03.js +0 -1
- package/client/dist/assets/jobs-SI34ML8I.js +0 -1
- package/client/dist/assets/loops-BR4FmOv12.js +0 -1
- package/client/dist/assets/loops-BgX_uudn.js +0 -1
- package/client/dist/assets/loops-Bpl2j2LP.js +0 -1
- package/client/dist/assets/loops-CQuuMlyZ.js +0 -1
- package/client/dist/assets/loops-DW8hSMdS2.js +0 -1
- package/client/dist/assets/loops-Q2muu8hW2.js +0 -1
- package/client/dist/assets/loops-q7CNDvfK.js +0 -1
- package/client/dist/assets/settings-CY8udi0e.js +0 -1
- package/client/dist/assets/setup-CNMdCHHt2.js +0 -1
- package/client/dist/assets/setup-Cag4XrbL2.js +0 -1
- package/client/dist/assets/setup-D9IHGoWU.js +0 -1
- package/client/dist/assets/setup-Dg6Ba3JT.js +0 -1
- package/client/dist/assets/setup-DyK36RIW.js +0 -1
- package/client/dist/assets/setup-G4ZvDKxX.js +0 -1
- package/client/dist/assets/setup-aTlGxuwi2.js +0 -1
- package/client/dist/assets/setup-kWsoAeHQ.js +0 -1
- package/client/dist/assets/specs-BFSUPa122.js +0 -1
- package/client/dist/assets/specs-BMzip1WY2.js +0 -1
- package/client/dist/assets/specs-BYeAbIEy.js +0 -1
- package/client/dist/assets/specs-C-mtLcXw.js +0 -1
- package/client/dist/assets/specs-CAzpvADd2.js +0 -1
- package/client/dist/assets/specs-CyRIw_IR.js +0 -1
- package/client/dist/assets/specs-DMm7gB_l.js +0 -1
- package/client/dist/assets/specs-DuottM0Z.js +0 -1
- /package/client/dist/assets/{abap-CpHUwCVK.js → abap-D0E4FfVW.js} +0 -0
- /package/client/dist/assets/{activity-DemHQS7l.js → activity--iN4Ad2R2.js} +0 -0
- /package/client/dist/assets/{activity-B_71BWg3.js → activity-6hM_ZSg9.js} +0 -0
- /package/client/dist/assets/{activity-DHv2V5Oi.js → activity-BZNfOdiS.js} +0 -0
- /package/client/dist/assets/{activity-D0rfjQzT2.js → activity-BuVo5sPB.js} +0 -0
- /package/client/dist/assets/{activity-BpTTj_PH.js → activity-CIOLxGvh.js} +0 -0
- /package/client/dist/assets/{activity-D2e62vbV2.js → activity-D2r2h3SE2.js} +0 -0
- /package/client/dist/assets/{activity-Ch-wbr0C2.js → activity-DtxrAUMo2.js} +0 -0
- /package/client/dist/assets/{addon-image-Ba-TY3wr.js → addon-image-CwoZj17F.js} +0 -0
- /package/client/dist/assets/{addon-ligatures-T4ARLiuu.js → addon-ligatures-CWDrED80.js} +0 -0
- /package/client/dist/assets/{addon-webgl-Cd73n8eh.js → addon-webgl-DMbGeI_u.js} +0 -0
- /package/client/dist/assets/{addspec-xwRX_Pnf.js → addspec-BMtLZLW62.js} +0 -0
- /package/client/dist/assets/{addspec-l_zU5gla.js → addspec-CP0HRuxY.js} +0 -0
- /package/client/dist/assets/{addspec-Dio-H5z0.js → addspec-CRuvWn8d.js} +0 -0
- /package/client/dist/assets/{addspec-D6L4ZteP.js → addspec-D-JLDsUV.js} +0 -0
- /package/client/dist/assets/{addspec-CrEm6Fzr2.js → addspec-DfhDbg5c.js} +0 -0
- /package/client/dist/assets/{addspec-B6Ns8KU02.js → addspec-bsNDdqRm2.js} +0 -0
- /package/client/dist/assets/{addspec-qGyH7MHy2.js → addspec-mgPOt5q02.js} +0 -0
- /package/client/dist/assets/{agents-OzxCLVW1.js → agents-78bTZGZh.js} +0 -0
- /package/client/dist/assets/{agents-hv3sqmPm2.js → agents-BLhWCmDS2.js} +0 -0
- /package/client/dist/assets/{agents-CHgCudUV.js → agents-BUdEi3-N.js} +0 -0
- /package/client/dist/assets/{agents-Dumx4JiM2.js → agents-BpoUaoW92.js} +0 -0
- /package/client/dist/assets/{agents-CnaPeSyw.js → agents-CWo-KyAB.js} +0 -0
- /package/client/dist/assets/{agents-Xh-zYHUx2.js → agents-DDtCJ5M02.js} +0 -0
- /package/client/dist/assets/{agents-DuhLEaQ_.js → agents-bvyRLczL.js} +0 -0
- /package/client/dist/assets/{agentstudio-CCthUdzR.js → agentstudio-BMQxc_bz.js} +0 -0
- /package/client/dist/assets/{agentstudio-CcH8Ckql2.js → agentstudio-COZriimI2.js} +0 -0
- /package/client/dist/assets/{agentstudio-Bo91kfUd2.js → agentstudio-CWgXG5W52.js} +0 -0
- /package/client/dist/assets/{agentstudio-VJOa_NVO.js → agentstudio-C_Jq8Tl4.js} +0 -0
- /package/client/dist/assets/{agentstudio-BIxikDf_.js → agentstudio-Dtq3dGYk.js} +0 -0
- /package/client/dist/assets/{agentstudio-Bz8cP8_c.js → agentstudio-jKMTdT70.js} +0 -0
- /package/client/dist/assets/{agentstudio-DARgYg5Z2.js → agentstudio-sI27TpBu2.js} +0 -0
- /package/client/dist/assets/{aiedit-5ZXN4cep2.js → aiedit-6CHdb_iv2.js} +0 -0
- /package/client/dist/assets/{aiedit-B7gAJZVC.js → aiedit-B03pD_Na.js} +0 -0
- /package/client/dist/assets/{aiedit-D92V-kUW.js → aiedit-BtRqRxML.js} +0 -0
- /package/client/dist/assets/{aiedit-D9ualLVJ.js → aiedit-eMN4eQPF.js} +0 -0
- /package/client/dist/assets/{aiedit-h48tJU0V2.js → aiedit-hknZlly82.js} +0 -0
- /package/client/dist/assets/{aiedit-xkA_mR2a2.js → aiedit-igmw-ZoZ2.js} +0 -0
- /package/client/dist/assets/{aiedit-7B2dvCv-.js → aiedit-pc5JDUq1.js} +0 -0
- /package/client/dist/assets/{analytics-slx4X1mu2.js → analytics-BWMUZ2Pq2.js} +0 -0
- /package/client/dist/assets/{analytics-uRNP6yAJ.js → analytics-Bj-SmKHa.js} +0 -0
- /package/client/dist/assets/{analytics-WF1I49ln.js → analytics-C5dpiS0o.js} +0 -0
- /package/client/dist/assets/{analytics-CBvaxOId.js → analytics-CCprAqk3.js} +0 -0
- /package/client/dist/assets/{analytics-BakymH7Z2.js → analytics-CR1TJqUi2.js} +0 -0
- /package/client/dist/assets/{analytics-B7bPj6u_2.js → analytics-DfNdXR0y2.js} +0 -0
- /package/client/dist/assets/{analytics-DZ74aQ54.js → analytics-rmHuJv0V.js} +0 -0
- /package/client/dist/assets/{apex-DlD7oJX6.js → apex-D_X_8J4d.js} +0 -0
- /package/client/dist/assets/{atom-one-dark-BrRN8wBy.js → atom-one-dark-BMDPFwRZ.js} +0 -0
- /package/client/dist/assets/{attachments-C11tOKZ_.js → attachments-BgBNSqQd.js} +0 -0
- /package/client/dist/assets/{attachments-Bnbyj2PN.js → attachments-BjyMmrwE.js} +0 -0
- /package/client/dist/assets/{attachments-CIeLa8l12.js → attachments-C9GTTJsx2.js} +0 -0
- /package/client/dist/assets/{attachments-DslHfa-L.js → attachments-DCZOL1RU.js} +0 -0
- /package/client/dist/assets/{attachments-C-gyrCOb.js → attachments-DL-bPy9E.js} +0 -0
- /package/client/dist/assets/{attachments-Cxrs0pyL2.js → attachments-DPCmkFZu2.js} +0 -0
- /package/client/dist/assets/{attachments-TTPsc0a52.js → attachments-rNn1ekRy2.js} +0 -0
- /package/client/dist/assets/{azcli-CmXFAbc-.js → azcli-PZLnZ3jH.js} +0 -0
- /package/client/dist/assets/{bat-DdNJq4hH.js → bat-KlBOxpO4.js} +0 -0
- /package/client/dist/assets/{bicep-Bppz7WOA.js → bicep-CgG9oF3V.js} +0 -0
- /package/client/dist/assets/{cameligo-0MRMdSmg.js → cameligo-6R45j6Ph.js} +0 -0
- /package/client/dist/assets/{chat-BvHrebKC2.js → chat-BgL3zv6x2.js} +0 -0
- /package/client/dist/assets/{chat-CZyiLJvQ.js → chat-Bh3NdgJs.js} +0 -0
- /package/client/dist/assets/{chat-DKYP7NnC.js → chat-Bom6bqK3.js} +0 -0
- /package/client/dist/assets/{chat-5mdg_YIc2.js → chat-DdwZjT8K2.js} +0 -0
- /package/client/dist/assets/{chat-wkTIy9rX.js → chat-Dnwg-NpQ.js} +0 -0
- /package/client/dist/assets/{chat-BpYxnkr4.js → chat-DsbwJhus.js} +0 -0
- /package/client/dist/assets/{chat-BGax2nV62.js → chat-vylxqR0P2.js} +0 -0
- /package/client/dist/assets/{clojure-B5dKj863.js → clojure-CLAAMO7J.js} +0 -0
- /package/client/dist/assets/{clsx-1dnHRn8W.js → clsx-CNmW0Nip.js} +0 -0
- /package/client/dist/assets/{coffee-DSbWjzk7.js → coffee-AruSygo-.js} +0 -0
- /package/client/dist/assets/{commands-uz_uKT242.js → commands-C4Y3C-PF2.js} +0 -0
- /package/client/dist/assets/{commands-Bb7MnPqn2.js → commands-CSDs9q_2.js} +0 -0
- /package/client/dist/assets/{commands-C_7zZwJf.js → commands-DkU0qliq.js} +0 -0
- /package/client/dist/assets/{commands-D_6B8lfU.js → commands-JWMfGDmr.js} +0 -0
- /package/client/dist/assets/{commands-DBc5llLi2.js → commands-RHOchN4n2.js} +0 -0
- /package/client/dist/assets/{commands-CQkdthjF.js → commands-u-4eEHCN.js} +0 -0
- /package/client/dist/assets/{commands-DhZNhSbl.js → commands-xHDDGfcP2.js} +0 -0
- /package/client/dist/assets/{cpp-SBF8SAh9.js → cpp-DEE5r4Pw.js} +0 -0
- /package/client/dist/assets/{csharp-Lzuq_1t-.js → csharp-BVXJUvbK.js} +0 -0
- /package/client/dist/assets/{csp-BEzxZqi1.js → csp-cXOF0JoV.js} +0 -0
- /package/client/dist/assets/{css-C3D3PKln.js → css-C_zQuAoy.js} +0 -0
- /package/client/dist/assets/{cypher-CQ3dEPmv.js → cypher-t95m_Q-O.js} +0 -0
- /package/client/dist/assets/{dart-DCPmxolI.js → dart-B4r1Tg-e.js} +0 -0
- /package/client/dist/assets/{dockerfile-B_2_aaTO.js → dockerfile-6mt7zHQw.js} +0 -0
- /package/client/dist/assets/{ecl-rADUeXsV.js → ecl-DEY_Fz_Q.js} +0 -0
- /package/client/dist/assets/{editor.api2-T7u8kQWG.js → editor.api2-C3B0tp2x.js} +0 -0
- /package/client/dist/assets/{elixir-DOd-TuJO.js → elixir-R6-q1c5t.js} +0 -0
- /package/client/dist/assets/{explore-BHEhNekP2.js → explore-B7fblXBb2.js} +0 -0
- /package/client/dist/assets/{explore-DAsroA482.js → explore-BHtEpoNN2.js} +0 -0
- /package/client/dist/assets/{explore-UwHHj2ux.js → explore-C0k8HrkN.js} +0 -0
- /package/client/dist/assets/{explore-DaXiW9-6.js → explore-CNBzrEPS.js} +0 -0
- /package/client/dist/assets/{explore-CWlAXx0f2.js → explore-D_mWBYCS2.js} +0 -0
- /package/client/dist/assets/{explore-DG1CtYqT.js → explore-Dahc1lOx.js} +0 -0
- /package/client/dist/assets/{explore-DMSGAnhK.js → explore-UvW1jEMa.js} +0 -0
- /package/client/dist/assets/{flow9-Bf7zg_j0.js → flow9-CNQvHBOt.js} +0 -0
- /package/client/dist/assets/{format-command-BHymDa4r.js → format-command-CuWuRvka.js} +0 -0
- /package/client/dist/assets/{fsharp-BqROZjbA.js → fsharp-vPZkFXwv.js} +0 -0
- /package/client/dist/assets/{go-oQTP5uLe.js → go-KUzBMYJ_.js} +0 -0
- /package/client/dist/assets/{graphql-CSHfTU3q.js → graphql-C3W0rCsD.js} +0 -0
- /package/client/dist/assets/{hcl-CeG-RoFJ.js → hcl-BOOMFSNX.js} +0 -0
- /package/client/dist/assets/{ini-B2Dv4ohc.js → ini-CFat1WJr.js} +0 -0
- /package/client/dist/assets/{integrations-CAF21FbQ.js → integrations-4KZnYECp.js} +0 -0
- /package/client/dist/assets/{integrations-CHCgning2.js → integrations-7W266oqF2.js} +0 -0
- /package/client/dist/assets/{integrations-B-JVE1_D.js → integrations-BNuauK3o.js} +0 -0
- /package/client/dist/assets/{integrations-BAujIDoE.js → integrations-CHy8tnpV.js} +0 -0
- /package/client/dist/assets/{integrations-DS5FFMes.js → integrations-Cl_wD5AI.js} +0 -0
- /package/client/dist/assets/{integrations-axZN4--n2.js → integrations-Cy8nZ_dv2.js} +0 -0
- /package/client/dist/assets/{integrations-CtsOpq2D2.js → integrations-zMqY4VU12.js} +0 -0
- /package/client/dist/assets/{java-aUDDeufb.js → java-Dee-CNAM.js} +0 -0
- /package/client/dist/assets/{julia-C5LbruO5.js → julia-CGNlLYuU.js} +0 -0
- /package/client/dist/assets/{kotlin-C6mOuSKk.js → kotlin-CY7lhknJ.js} +0 -0
- /package/client/dist/assets/{less-D5qC3caW.js → less-D0KN7hfJ.js} +0 -0
- /package/client/dist/assets/{lexon-Dr2La-fj.js → lexon-CuRJufPs.js} +0 -0
- /package/client/dist/assets/{lua-Zy6u5z6Z.js → lua-DHvH62Zf.js} +0 -0
- /package/client/dist/assets/{m3-C7XHeDz_.js → m3-tlthQ8Fo.js} +0 -0
- /package/client/dist/assets/{markdown-PiF7r-2h.js → markdown-Dbx1LgUZ.js} +0 -0
- /package/client/dist/assets/{mcp-B_nWlxZa2.js → mcp-CjVKXAhD2.js} +0 -0
- /package/client/dist/assets/{mcp-B8omp_Cd.js → mcp-Dcl-XxkR.js} +0 -0
- /package/client/dist/assets/{mcp-DTCCrYHz2.js → mcp-DtbxuH3V2.js} +0 -0
- /package/client/dist/assets/{mcp-DytBbASZ.js → mcp-H-gnQUdN.js} +0 -0
- /package/client/dist/assets/{mcp-D_oPS6Zc.js → mcp-N1nzp8oL.js} +0 -0
- /package/client/dist/assets/{mcp-Cb2jtHP72.js → mcp-XJNRfxVp2.js} +0 -0
- /package/client/dist/assets/{mcp-DPqm2C8-.js → mcp-sRmWE8WJ.js} +0 -0
- /package/client/dist/assets/{mips-nn07GiyE.js → mips-D_O3IUz_.js} +0 -0
- /package/client/dist/assets/{msdax-DaKFVMST.js → msdax-C_ZmCnRt.js} +0 -0
- /package/client/dist/assets/{mysql-C6d6xrbU.js → mysql-C-dCEYSX.js} +0 -0
- /package/client/dist/assets/{nav-Cibp2KWF.js → nav-40HzpIFb.js} +0 -0
- /package/client/dist/assets/{nav-DtTnF9xd.js → nav-8yPhBn00.js} +0 -0
- /package/client/dist/assets/{nav-Danf5sRf2.js → nav-B6PkGfTk2.js} +0 -0
- /package/client/dist/assets/{nav-Bqhyfbcj2.js → nav-BHqMLrS72.js} +0 -0
- /package/client/dist/assets/{nav-CQb9y1km.js → nav-CGy4yx3C.js} +0 -0
- /package/client/dist/assets/{nav-BAsYcqdw2.js → nav-CXEDcRdv2.js} +0 -0
- /package/client/dist/assets/{nav-BRrNlZkr.js → nav-EI_OhEAo.js} +0 -0
- /package/client/dist/assets/{objective-c-B6KMtI-k.js → objective-c-DZY9Aqxd.js} +0 -0
- /package/client/dist/assets/{pascal-DYr8MPE7.js → pascal-BVHLXoor.js} +0 -0
- /package/client/dist/assets/{pascaligo-B3pd-jJ_.js → pascaligo-XdG_6u3k.js} +0 -0
- /package/client/dist/assets/{perl-z2xUzoaL.js → perl-b9QV0BcD.js} +0 -0
- /package/client/dist/assets/{pgsql-DUvT-09-.js → pgsql-Du5FDOgT.js} +0 -0
- /package/client/dist/assets/{php-CGyOmJfy.js → php-WJD0z2Z_.js} +0 -0
- /package/client/dist/assets/{pla-CMqgvyD0.js → pla-CbciTf2w.js} +0 -0
- /package/client/dist/assets/{postiats-Dx5LUn4Z.js → postiats-C1QxmvVq.js} +0 -0
- /package/client/dist/assets/{powerquery-DazYxvJ6.js → powerquery-BEYDhPLZ.js} +0 -0
- /package/client/dist/assets/{powershell-B3nwlDka.js → powershell-CfaYw4XL.js} +0 -0
- /package/client/dist/assets/{protobuf-BGuu2u2s.js → protobuf-pwZEDOYa.js} +0 -0
- /package/client/dist/assets/{pug-Dbte1MXA.js → pug-5ftqSPVe.js} +0 -0
- /package/client/dist/assets/{qsharp-DJLwBOvG.js → qsharp-uI6qZMq4.js} +0 -0
- /package/client/dist/assets/{r-DmGBRSHj.js → r-BK54P1EG.js} +0 -0
- /package/client/dist/assets/{redis-VvUYn0a4.js → redis-DI0yd7kN.js} +0 -0
- /package/client/dist/assets/{redshift-6GdDrxg3.js → redshift-Dov26eyI.js} +0 -0
- /package/client/dist/assets/{restructuredtext-CfAB8aRU.js → restructuredtext-QqJ_1dC-.js} +0 -0
- /package/client/dist/assets/{ruby-CIYK6MXY.js → ruby-5WjveeVb.js} +0 -0
- /package/client/dist/assets/{rust-CTHZfjj9.js → rust-BzVSfqFH.js} +0 -0
- /package/client/dist/assets/{sb-CkKTdkz_.js → sb-DMIUfT-3.js} +0 -0
- /package/client/dist/assets/{scala-Bx-Wr9TM.js → scala-CSKA7lqt.js} +0 -0
- /package/client/dist/assets/{scheme-Dcfi6f83.js → scheme-CojOP2Qc.js} +0 -0
- /package/client/dist/assets/{scss-ByL-7PFQ.js → scss-DoBZGJG6.js} +0 -0
- /package/client/dist/assets/{shell-Csnb9Yqd.js → shell-YOaE4udl.js} +0 -0
- /package/client/dist/assets/{solidity-Dbw5-0QP.js → solidity-l3jSyVLu.js} +0 -0
- /package/client/dist/assets/{sophia-ZQ3saZQx.js → sophia-BhSGTaQJ.js} +0 -0
- /package/client/dist/assets/{sparql-BEtOel8u.js → sparql-qhk6QD9w.js} +0 -0
- /package/client/dist/assets/{sql-DGPDbzB7.js → sql-DoO3y21-.js} +0 -0
- /package/client/dist/assets/{st-GeW2MOgh.js → st-ChZAY8oG.js} +0 -0
- /package/client/dist/assets/{swift-BVYTN8jq.js → swift-D290Tr7_.js} +0 -0
- /package/client/dist/assets/{systemverilog-Deg2a8Lr.js → systemverilog-DsxzgJ-o.js} +0 -0
- /package/client/dist/assets/{tcl-6DnLmROF.js → tcl-BKDUHAAR.js} +0 -0
- /package/client/dist/assets/{terminal-CDiOAmBd2.js → terminal-BRm03iFA2.js} +0 -0
- /package/client/dist/assets/{terminal-CJN-mQMc.js → terminal-De2Brd23.js} +0 -0
- /package/client/dist/assets/{terminal-CYB4TiAd.js → terminal-DxQWCqSD2.js} +0 -0
- /package/client/dist/assets/{terminal-DsaDTq5N2.js → terminal-WSAvHXoU.js} +0 -0
- /package/client/dist/assets/{terminal-DTQ_dPqi2.js → terminal-Z7KsDM_n.js} +0 -0
- /package/client/dist/assets/{terminal-58ReNaya.js → terminal-cqfd3EDV.js} +0 -0
- /package/client/dist/assets/{terminal-DawP8xNL.js → terminal-xGbCZJHg.js} +0 -0
- /package/client/dist/assets/{tickets-DoRTUYRT.js → tickets-B7zT4IRf.js} +0 -0
- /package/client/dist/assets/{tickets-DBfFePwk2.js → tickets-BoXom7l8.js} +0 -0
- /package/client/dist/assets/{tickets-DvohTziT2.js → tickets-C3b8cHhd2.js} +0 -0
- /package/client/dist/assets/{tickets-Da15iaRw.js → tickets-CFXnJsYF.js} +0 -0
- /package/client/dist/assets/{tickets-CujsZvkf.js → tickets-CWYFvx1W2.js} +0 -0
- /package/client/dist/assets/{tickets-Df6pee-O2.js → tickets-DTHo9c3C.js} +0 -0
- /package/client/dist/assets/{tickets-CNvIilmP.js → tickets-SuX_HkK4.js} +0 -0
- /package/client/dist/assets/{twig-XbbXW9Yz.js → twig-UpZQaM8G.js} +0 -0
- /package/client/dist/assets/{typespec-CRlV8GhI.js → typespec-DzaKvN8i.js} +0 -0
- /package/client/dist/assets/{vb-BHE2izPH.js → vb-CZpbb7tk.js} +0 -0
- /package/client/dist/assets/{wgsl-Bf5vkfmY.js → wgsl-CNt3OIvl.js} +0 -0
|
@@ -18,7 +18,7 @@ SpecsBoard (esquerda) Rails (direita)
|
|
|
18
18
|
|
|
19
19
|
Um rail é uma **pista de execução**. Você arrasta um cartão de spec do SpecsBoard para um rail e depois aperta **▶ Play**. O rail dispara o pipeline e trabalha a spec de ponta a ponta, bem no diretório de trabalho do seu projeto — editando arquivos, rodando testes, tudo.
|
|
20
20
|
|
|
21
|
-
Você pode ter vários rails para organizar o trabalho em pistas nomeadas (uma para a feature em que está focado, outra na fila atrás dela). Mais sobre multi-rail e batching em [Batch implement e multi-feature](batch-implement-and-multi-feature).
|
|
21
|
+
Você pode ter vários rails para organizar o trabalho em pistas nomeadas (uma para a feature em que está focado, outra na fila atrás dela). Os rails são **dinâmicos**: o botão **+ Adicionar** no cabeçalho de Rails cria uma nova pista (até 12 por projeto) e pistas vazias e ociosas podem ser removidas. Cada rail é respaldado pelo servidor, então seu conjunto de pistas sobrevive a recargas e fica visível para o companion móvel e para o agente integrado — o agente pode até criar um rail sozinho quando todas as pistas estão ocupadas. Mais sobre multi-rail e batching em [Batch implement e multi-feature](batch-implement-and-multi-feature).
|
|
22
22
|
|
|
23
23
|
## Lançando um rail sobre uma spec
|
|
24
24
|
|
|
@@ -49,7 +49,7 @@ Um rail roda um **Loop** — a receita do trabalho. Três loops são **embutidos
|
|
|
49
49
|
| **Batch** | `/specrails:batch-implement` | Um job que percorre as specs do rail sequencialmente, em ondas que respeitam as dependências. Melhor para várias specs relacionadas. |
|
|
50
50
|
| **Freestyle** | Freestyle | O Claude implementa cada spec de forma autônoma, **ignorando** o pipeline. Um job independente por spec. Apenas Claude. |
|
|
51
51
|
|
|
52
|
-
O Freestyle é o caso atípico: ele pula a cadeia de agentes e entrega a spec crua ao Claude para trabalhar com suas ferramentas nativas. É aberto, então apertar Play abre primeiro uma confirmação, e um seletor de modelo por rail deixa você escolher Haiku / Sonnet / Opus. Ele só aparece quando o motor do rail é o Claude.
|
|
52
|
+
O Freestyle é o caso atípico: ele pula a cadeia de agentes e entrega a spec crua ao Claude para trabalhar com suas ferramentas nativas. É aberto, então apertar Play abre primeiro uma confirmação, e um seletor de modelo por rail deixa você escolher Haiku / Sonnet / Opus. Ele só aparece quando o motor do rail é o Claude. Uma execução Freestyle é também o único job que **fica aberto esperando por você**: converse com ele pelo compositor do detalhe do job e clique em **Finalize** quando estiver satisfeito (todos os outros jobs terminam sozinhos).
|
|
53
53
|
|
|
54
54
|
Além dos embutidos, você pode **construir seus próprios loops** — repetir um ciclo verify → fix → verify até atingir uma meta, encadear comandos de shell entre AI Steps e muito mais. Esses loops personalizados aparecem no mesmo seletor de Loop. Essa é a próxima grande ideia: [O Loop Builder](the-loop-builder).
|
|
55
55
|
|
|
@@ -57,11 +57,11 @@ Além dos embutidos, você pode **construir seus próprios loops** — repetir u
|
|
|
57
57
|
|
|
58
58
|
Toda vez que você aperta Play, a execução do rail vira um **job**. A regra mais importante para internalizar:
|
|
59
59
|
|
|
60
|
-
> **
|
|
60
|
+
> **Os rails rodam em paralelo.** Cada lançamento isola seu trabalho em um worktree do git por spec, então vários rails podem rodar ao mesmo tempo dentro do mesmo projeto sem se atropelar — as mudanças de cada execução voltam como merge ou como draft PR quando ela termina.
|
|
61
61
|
|
|
62
|
-
|
|
62
|
+
Quer tudo andando de uma vez? O botão **Lançar todos** no cabeçalho de Rails inicia todas as pistas prontas de uma só vez, após uma única confirmação que enquadra o custo total (N rails × gasto de IA). Rails vazios, já em execução ou aguardando uma decisão de PR são pulados e reportados em um toast de resumo compacto. O agente integrado tem o mesmo poder via `specrails_rails(launch_all)` — e cria um rail novo quando não existe pista livre.
|
|
63
63
|
|
|
64
|
-
|
|
64
|
+
Só o caminho legado (feature de Loops desativada) volta à antiga fila de um-job-por-vez por projeto, em que rails extras esperam atrás do que está rodando. O paralelismo entre projetos não muda: cada projeto continua totalmente independente.
|
|
65
65
|
|
|
66
66
|
Não há um botão global de concorrência para ajustar. O único limite automático é baseado em orçamento: se você definiu um orçamento diário (do projeto ou da app), a fila se autopausa assim que o gasto do dia atinge o teto.
|
|
67
67
|
|
|
@@ -73,7 +73,7 @@ Encontre todos os jobs em **Jobs**, na barra lateral direita do projeto — uma
|
|
|
73
73
|
- **Filtro por intervalo de datas** — restringe a uma janela de tempo.
|
|
74
74
|
- **Comparar** — escolha dois jobs e veja-os lado a lado.
|
|
75
75
|
|
|
76
|
-
Clique em qualquer cartão para abrir a **vista de detalhe do Job**, onde ficam o log em streaming ao vivo e as métricas ao vivo. Essa é a próxima página: [A vista de detalhe do job](the-job-detail-view).
|
|
76
|
+
Clique em qualquer cartão para abrir a **vista de detalhe do Job**, onde ficam o log em streaming ao vivo e as métricas ao vivo — e onde, nos jobs Claude, um compositor de chat permite **fazer perguntas ao agente em execução ou orientá-lo no meio da execução** sem parar nada. Essa é a próxima página: [A vista de detalhe do job](the-job-detail-view).
|
|
77
77
|
|
|
78
78
|
## Cancelando um job
|
|
79
79
|
|
|
@@ -1,10 +1,10 @@
|
|
|
1
1
|
# A vista de detalhe do job
|
|
2
2
|
|
|
3
|
-
Clique em qualquer cartão de job na página **Jobs** e chega aqui: o cockpit de uma única execução de rail. Foi construída em torno de uma promessa — **os números ao vivo que vê são reais, nunca estimativas.** Esta página percorre as fases, as métricas ao vivo
|
|
3
|
+
Clique em qualquer cartão de job na página **Jobs** e chega aqui: o cockpit de uma única execução de rail. Foi construída em torno de uma promessa — **os números ao vivo que vê são reais, nunca estimativas.** Esta página percorre as fases, as métricas ao vivo, os cartões de ticket — e o compositor que lhe permite **falar com o job em execução**.
|
|
4
4
|
|
|
5
5
|
## O layout
|
|
6
6
|
|
|
7
|
-
Dois painéis ficam por cima do log completo em streaming:
|
|
7
|
+
Dois painéis ficam por cima do log completo em streaming; num job Claude em execução, um compositor de chat fica por baixo:
|
|
8
8
|
|
|
9
9
|
```
|
|
10
10
|
┌─────────────────────────────────────────────┐
|
|
@@ -15,6 +15,8 @@ Dois painéis ficam por cima do log completo em streaming:
|
|
|
15
15
|
│ │
|
|
16
16
|
│ Log em streaming (auto-scroll · pesquisa) │
|
|
17
17
|
│ │
|
|
18
|
+
├─────────────────────────────────────────────┤
|
|
19
|
+
│ Compositor (envie uma mensagem ao job · …)│
|
|
18
20
|
└─────────────────────────────────────────────┘
|
|
19
21
|
```
|
|
20
22
|
|
|
@@ -71,6 +73,29 @@ Por baixo dos painéis fica o log completo da execução, transmitido em tempo r
|
|
|
71
73
|
|
|
72
74
|
Esta é a verdade crua do que a IA está a fazer — cada chamada de ferramenta, cada edição de ficheiro, cada execução de teste.
|
|
73
75
|
|
|
76
|
+
## Execuções de loop: o explorador de passos
|
|
77
|
+
|
|
78
|
+
Quando o job é uma **execução de loop** (ver [O Loop Builder](the-loop-builder)), o log plano dá lugar a um **explorador de passos** que espelha a forma real do loop:
|
|
79
|
+
|
|
80
|
+
- **A faixa de visão geral** no topo é o mapa ao vivo do loop — um chip por nó (Passo de IA, Shell, Decisor do Loop…), na ordem em que o grafo flui. Os chips vão acendendo à medida que a execução avança: esmaecidos enquanto esperam, pulsando enquanto correm, e depois um visto ou uma cruz. O chip de um Decisor mostra ainda o veredicto pelo qual encaminhou — voltar ao início ou seguir em frente — e um contador de iterações (`Iteração 3/10`) mantém a conta à direita. Clique em qualquer chip para saltar direto ao passo mais recente daquele nó.
|
|
81
|
+
- **Uma caixa recolhível por passo.** Cada passagem por um nó vira a sua própria secção, com o número do passo, o nome, um selo de iteração, a duração ao terminar — e o seu próprio botão de copiar, para levar exatamente a saída de um passo. (O copiar da barra de ferramentas continua a levar o log inteiro.) Tudo o que foi impresso antes do primeiro passo — o banner de arranque, o aviso de worktree — fica arrumado numa secção de **Preparação**.
|
|
82
|
+
- **O modo de acompanhamento** vem ligado por defeito: o passo em execução permanece aberto e com auto-scroll enquanto os anteriores se recolhem. No momento em que sobe o scroll ou abre um passo antigo, o acompanhamento pausa para poder ler — uma pílula flutuante **Retomar acompanhamento** devolve-o ao direto. **Expandir tudo / Recolher tudo** vivem na barra de ferramentas, e escrever na pesquisa procura em todos os passos ao mesmo tempo.
|
|
83
|
+
- **Os passos interrompidos também são honestos.** Um passo que nunca chegou a reportar o seu desfecho — a execução foi cancelada ou a app fechou a meio do passo — é marcado como **Interrompido** com uma borda tracejada, em vez de fingir que terminou.
|
|
84
|
+
|
|
85
|
+
Tudo o resto nesta página funciona exatamente igual nas execuções de loop — as métricas ao vivo, os cartões de ticket, o compositor. Os jobs que não são de loop mantêm o log em streaming clássico acima.
|
|
86
|
+
|
|
87
|
+
## Fale com o job em execução
|
|
88
|
+
|
|
89
|
+
Todo job Claude corre por omissão como uma **sessão ao vivo**, por isso um compositor de chat fica ao fundo desta página — e do modal de job no modo missão. Use-o para fazer uma pergunta ao agente em execução («porque é que aquele teste falhou?») ou para o orientar a meio da execução («salta o refactor, concentra-te no fix»).
|
|
90
|
+
|
|
91
|
+
Algumas coisas que vale a pena saber:
|
|
92
|
+
|
|
93
|
+
- **As mensagens entram em fila, não interrompem.** Envie enquanto o agente está a transmitir e a sua mensagem espera a vez — corre como o prompt seguinte, e o job continua a seguir o seu plano. Um pequeno contador mostra quantas mensagens estão em fila.
|
|
94
|
+
- **A linha de totais é real.** O compositor mostra um resumo ao vivo `N turnos · $X`, somado a partir do uso real de cada turno concluído — coerente com a promessa desta página de nunca adivinhar.
|
|
95
|
+
- **Duas formas de uma sessão terminar.** A maioria dos jobs **termina sozinha**: assim que um turno acaba sem mensagens em fila, a sessão assenta e o job conclui — as suas mensagens são orientação opcional, nunca uma obrigação. Uma ação discreta **Concluir agora** termina-a mais cedo com tudo o que foi produzido até então. Os jobs **Freestyle** são a exceção: ficam à espera entre turnos até que clique em **Finalize** — é esse o seu desenho, uma sessão de ida e volta que fecha quando terminar.
|
|
96
|
+
- **Nas execuções de loop, as mensagens vão para o passo ativo.** Num loop embutido ou personalizado, a sua mensagem chega ao **passo de IA que está a correr nesse momento**. Entre passos (enquanto o Loop Decider pensa, ou um comando de shell corre) o compositor mostra um breve estado *«À espera do próximo passo…»* — o texto rascunhado mantém-se, e o envio reativa-se quando o próximo passo de IA arranca. **Assentar este passo** termina o passo atual mais cedo e deixa o loop avançar com o que ele produziu.
|
|
97
|
+
- **Só Claude, por agora.** Os jobs Codex e Gemini correm numa só passagem exatamente como antes — não aparece compositor. (Os operadores do servidor podem desligar a funcionalidade inteira com `SPECRAILS_INTERACTIVE_JOBS=false`.)
|
|
98
|
+
|
|
74
99
|
## Exportação de diagnóstico
|
|
75
100
|
|
|
76
101
|
Se a [telemetria](../settings/customizing) estava ativada para o job, aparece um botão **Exportar diagnóstico** no cabeçalho. Descarrega um ZIP que contém:
|
|
@@ -40,17 +40,21 @@ Onda 3: #7 (docs sobre tudo) ← espera por #4 e #5
|
|
|
40
40
|
|
|
41
41
|
Dentro do job, as specs de cada onda são implementadas antes de a onda seguinte começar. Não configura isto à mão — o orquestrador deriva as ondas a partir das próprias specs. Veja-o desenrolar-se na [vista de detalhe do job](the-job-detail-view): o log em streaming narra em que spec o batch está, e o cabeçalho de tickets mostra todas as specs que o job tocou.
|
|
42
42
|
|
|
43
|
-
## Isolamento por worktree
|
|
43
|
+
## Isolamento por worktree e como o trabalho é entregue
|
|
44
44
|
|
|
45
|
-
Quando várias specs são implementadas numa só execução, o pipeline mantém cada unidade de trabalho isolada para que alterações concorrentes ou sequenciais não pisem os ficheiros umas das outras.
|
|
45
|
+
Quando várias specs são implementadas numa só execução, o pipeline mantém cada unidade de trabalho isolada para que alterações concorrentes ou sequenciais não pisem os ficheiros umas das outras. A implementação de cada spec corre no seu próprio **git worktree** limpo — um checkout separado que partilha o histórico do seu repositório mas nunca toca na sua árvore de trabalho enquanto a IA trabalha.
|
|
46
|
+
|
|
47
|
+
Quando a execução termina, **nada é enviado e ainda não é aberto nenhum pull request**. O trabalho fica commitado em segurança nos seus branches isolados, as specs passam a um novo estado **Em revisão**, e o specrails **pergunta-lhe primeiro**: no rail aparece uma barra de decisão persistente com **Criar PR** — um pull request em rascunho a partir do branch de integração designado do seu projeto (defina-o em **Settings → Integration branch**; por omissão é o branch por defeito do seu repositório), combinado através de todas as specs do rail — e **Descartar**. O specrails **nunca faz merge, e nunca faz commit diretamente no seu branch de integração** — é você quem decide se sequer existe um PR, e um humano é responsável pelo merge. É a passagem de testemunho segura: o specrails produz o pull request apenas quando você o autoriza, e os seus engenheiros revêem-no e fazem merge no GitHub da forma como já o fazem.
|
|
46
48
|
|
|
47
49
|
Na prática isto significa:
|
|
48
50
|
|
|
49
51
|
- Cada spec recebe um ponto de partida limpo para implementar, em vez de herdar as edições em curso da spec anterior a meio do processo.
|
|
50
|
-
-
|
|
51
|
-
-
|
|
52
|
+
- A sua árvore de trabalho nunca é modificada enquanto a execução decorre — nada é aplicado até você o autorizar.
|
|
53
|
+
- Quando a execução termina, as specs mostram um selo **Em revisão** e o rail faz-lhe a pergunta: **Criar PR** para abrir o pull request em rascunho combinado, ou **Descartar** para limpar os branches e devolver as specs ao backlog. Se lançou o rail a partir do chat do agente, a mesma pergunta aparece como um cartão nessa conversa — responda em qualquer um dos dois lugares: ambos ficam sincronizados.
|
|
54
|
+
- Depois de criado, **Abrir PR** mostra o rascunho, **Publicar** abre-o à revisão e entrega-o à revisão normal da sua equipa no GitHub, e **Verificar merge** passa as specs a Concluído assim que a sua equipa o tiver mergeado.
|
|
55
|
+
- Se os branches isolados não puderem ser combinados de forma limpa ao criar o PR, o specrails para em segurança e deixa os branches para um humano — nunca força um merge partido sobre a sua base. Pode tentar de novo ou descartar a partir da mesma barra.
|
|
52
56
|
|
|
53
|
-
|
|
57
|
+
> Criar o PR precisa do GitHub CLI (`gh`) autenticado e de um remote configurado. Sem eles, o specrails mantém na mesma o trabalho commitado num branch a partir do qual pode abrir um pull request por si mesmo — nada se perde, e a barra de decisão permite tentar de novo. Para voltar ao comportamento anterior (integrar localmente em vez de perguntar), defina `SPECRAILS_RAIL_DELIVER_PR=0`.
|
|
54
58
|
|
|
55
59
|
## Multi-feature entre projetos
|
|
56
60
|
|
|
@@ -80,7 +80,7 @@ Para rodar um loop personalizado:
|
|
|
80
80
|
2. No cabeçalho do rail, abra o **seletor de Loop** e escolha o seu loop publicado.
|
|
81
81
|
3. Aperte **▶ Play**.
|
|
82
82
|
|
|
83
|
-
A execução transmite ao vivo na vista **Jobs
|
|
83
|
+
A execução transmite ao vivo na vista **Jobs** com as mesmas métricas e o mesmo rastreamento de custo de qualquer job de rail — e o seu log ganha um **explorador de passos** dedicado: um mapa ao vivo do seu grafo com uma caixa recolhível por passo, seguindo o passo em execução à medida que o loop avança (ver [A vista de detalhe do job](the-job-detail-view)). No Claude, cada **Passo de IA** é também uma sessão ao vivo: envie mensagens a ele pelo compositor do detalhe do job para orientá-lo no meio do passo (entre passos o compositor espera brevemente, e **Assentar este passo** faz o loop avançar com o que o passo produziu). Um loop que para porque atingiu seu teto de iterações ou de custo é reportado com esse resultado, em vez de um simples sucesso.
|
|
84
84
|
|
|
85
85
|
> **Atenção enquanto um loop roda.** Você não pode editar nem apagar um loop enquanto uma de suas execuções está rodando — pare a execução primeiro.
|
|
86
86
|
|
|
@@ -13,7 +13,7 @@ O quadro tem dois modos de visualização, alternados a partir de um botão na b
|
|
|
13
13
|
- **Vista de post-its** (a predefinida) — mosaicos em forma de cartão com resumos curtos.
|
|
14
14
|
- **Vista de lista** — linhas compactas de uma só linha.
|
|
15
15
|
|
|
16
|
-
|
|
16
|
+
O **seletor de estados** da barra de ferramentas mostra cada estado como um chip próprio com contagem em direto — mais dois grupos inteligentes: **Ativas** (a predefinição — tudo o que ainda está em movimento: rascunhos, por fazer, em curso e em revisão) e **Todos** (tudo, com Concluído fixado no fundo). A sua escolha é lembrada por projeto e espelhada no URL, pelo que um refresh ou um link partilhado restaura a vista exata. Em projetos ligados ao Jira aparece ainda um menu de **estado Jira**, que lista os estados *reais* do fluxo de trabalho do quadro (os nomes tal e qual, p. ex. "Code Review", cada um com contagem em direto) agrupados sob o estado a que mapeiam — combina-se com os chips de estado. Também pode filtrar por **etiqueta**, e ordenar por **Predefinida**, **Ticket #** ou **Prioridade** (cada uma com um seletor ascendente/descendente).
|
|
17
17
|
|
|
18
18
|
## Estados
|
|
19
19
|
|
|
@@ -24,7 +24,8 @@ Uma spec percorre um pequeno conjunto de estados. O quadro dá a cada um uma pis
|
|
|
24
24
|
| **Rascunho** | Uma ideia em curso guardada a partir de uma conversa do modo Explore. Ainda não está pronta para implementar — pode voltar e continuar a dar-lhe forma. Mostra uma etiqueta `Draft`. |
|
|
25
25
|
| **Por fazer** | Pronta para ser executada. É aqui que uma spec terminada aterra quando a cria. |
|
|
26
26
|
| **Em curso** | O pipeline está a trabalhar nela neste momento (um ponto azul pulsante). |
|
|
27
|
-
| **
|
|
27
|
+
| **Em revisão** | Implementada — cada execução terminada estaciona aqui as suas specs para a sua aprovação: faça merge da PR em rascunho ou mova-as você mesmo (uma etiqueta âmbar). |
|
|
28
|
+
| **Concluído** | Aprovada — a PR foi integrada, ou moveu-a você mesmo para aqui (um visto verde). |
|
|
28
29
|
| **Cancelado** | Abandonada (um X vermelho). |
|
|
29
30
|
|
|
30
31
|
Os rascunhos vivem no mesmo grupo ativo que as specs Por fazer — não há uma coluna separada para eles — mas têm um contorno subtilmente colorido e uma etiqueta `Draft` para serem fáceis de identificar. Veja [Rascunhos e o Contract Layer](drafts-and-contract-layer.md) para a história completa sobre rascunhos.
|
|
@@ -37,6 +37,12 @@
|
|
|
37
37
|
|
|
38
38
|
你还可以在全局设置的 *Code section* 区域里选择**摘要语言**(英语或西班牙语)。
|
|
39
39
|
|
|
40
|
+
## 构建故事
|
|
41
|
+
|
|
42
|
+
代码查看器下方是**构建故事**——一条按时间排列的时间线,记录着构建当前文件的每一个 spec 和每一个任务。每个章节是一张卡片:哪个 spec 介入了(附其当前状态)、什么时候、文件是被创建、修改还是删除,以及改动的规模(新增和删除的行数)。点击卡片即可打开该 spec 的详情。基于 loop 的 rail 也会记录它们触碰的文件,因此在隔离 worktree 中完成的工作会像普通流水线任务一样出现在故事里。
|
|
43
|
+
|
|
44
|
+
对任何章节你都可以请求一段通俗易懂的解释:按下**解释此更改**,应用会用一到三句话描述这个具体改动为该文件带来了什么——没有代码,没有术语。解释与文件摘要共用同一个每月预算;在生成解释之前,卡片会退回到它所知道的真实事实:改动类型、spec 和日期。更喜欢原始数据?**故事 / 日志**切换器可以换回经典的改动历史列表,并支持按需查看 diff。同样的面板也出现在代理模式的 **Files** 视图中。
|
|
45
|
+
|
|
40
46
|
## 把代码连回 spec
|
|
41
47
|
|
|
42
48
|
来源关联是双向的。在 Code 浏览器里,点击文件上的工单标记会打开那个工单的详情。而反过来,**工单详情**视图里有一个 *此工单改动的文件* 区段——在那里点击一个文件,你就会直接跳进 Code 浏览器并打开它。它把"这是我们写的 spec"和"这是从中产出的代码"这个闭环给接上了。
|
|
@@ -7,7 +7,7 @@
|
|
|
7
7
|
Specrails 充当 Jira 和你项目之间的**同步层**。核心思路是:你本地的规格存储仍然是流水线读取的那个权威来源,而 Specrails 负责让它和 Jira 保持一致。
|
|
8
8
|
|
|
9
9
|
- 当你启动一条 rail 时,Specrails 会把关联的 Jira 事务移动到 **In Progress**。
|
|
10
|
-
- 当一个任务结束时,Specrails
|
|
10
|
+
- 当一个任务结束时,Specrails 会转移该事务的状态:成功时移到你映射的**评审**状态,只有当你确认这份工作后才会到达 **Done**(合并草稿 PR 会发布一条 "PR merged" 评论);失败时退回 **To Do**,并附上包含任务 id、成本和时长的完成评论。
|
|
11
11
|
- Specrails 会定期**轮询** Jira,把任何人在看板上做的改动取回来,反映到你的规格里。
|
|
12
12
|
|
|
13
13
|
所有的回写都会经过一个持久化、防崩溃的发件箱(outbox),所以 Jira 一时的小故障绝不会让任务出错——那次更新只是会重试而已。
|
|
@@ -53,9 +53,14 @@ Agent Chat 通过内嵌的 **Specrails MCP 服务器**来驱动应用,因此
|
|
|
53
53
|
|
|
54
54
|
## 贴心细节
|
|
55
55
|
|
|
56
|
+
- **在对话中打造超级规格。** 让智能体和你一起*打磨*规格,而不是一次性生成:它会先阅读真实代码,简短地向你提问,并在对话中以实时卡片展示不断演进的草稿。你确认后它会创建规格,并默认在后台用 **Contract Layer**(精确的文件路径、数据形状、不变量)加以充实,让负责实现的智能体不必即兴发挥。说"不要 contract layer"即可跳过充实步骤。
|
|
57
|
+
- **点击它提到的内容。** 在固定到某个项目的任务中,智能体回复里的规格编号(`#12`)和 job/run 的 id 都是可点击的标签——点规格会打开看板的详情弹窗,点 job id 会打开实时的任务视图。如果引用已不存在,会看到一条低调的"未找到"提示。
|
|
58
|
+
- **实现卡片始终可见。** 当智能体为你实现规格时,一张实时卡片会跟踪这项工作——只要它还需要你做决定(创建 PR、发布、重试、丢弃),它就会**固定在消息框正上方**,无论对话滚动到哪里;它在历史记录中原来的位置会改为显示一条「已固定在上方」的细提示。多张活动卡片会以小标签的形式堆叠(点击即可把它换到前面),点击箭头可把卡片最小化成一条细栏。一旦 PR 发布——或工作被合并或丢弃——卡片就会回到对话历史中原来的位置。
|
|
56
59
|
- **提示词历史。** 在输入框为空时,按 **↑**/**↓** 浏览你之前问过的内容(滚动时以淡化样式显示);开始输入即可编辑,或按回车发送。
|
|
60
|
+
- **编辑队列。** 智能体忙碌时又发了消息?只要有消息在排队,**↑**/**↓** 就会改为在*这些消息*之间移动:输入框显示选中的那条,你可就地编辑,按**回车即保存回队列**(Esc 取消;未发送的草稿会原样回来)。
|
|
57
61
|
- **最小化,而不丢失。** 点击 ✕ 把面板收回气泡——对话仍在继续运行。重新打开时你会落在最新一条消息上;无需重新输入任何内容。
|
|
58
62
|
- **新建对话。** **+** 按钮开启一段全新的线程;历史记录存在于整个应用层面,凌驾于任何单个项目之上。
|
|
63
|
+
- **切换任务。** 项目选择器旁的任务选择器按从新到旧列出你的对话——跳动的圆点标记代理仍在工作的对话,小徽章显示排队消息的数量。列表超过八条时会出现搜索框;每行的垃圾桶图标在快速的行内确认后删除任务——即使是正在运行的任务(会先警告,然后停止代理)。
|
|
59
64
|
|
|
60
65
|
## 一些需要知道的事
|
|
61
66
|
|
|
@@ -18,7 +18,7 @@ SpecsBoard (左) Rails (右)
|
|
|
18
18
|
|
|
19
19
|
rail 是一条**执行通道**。你从 SpecsBoard 上拖一张 spec 卡片放到某条 rail 上,然后按下 **▶ Play**。这条 rail 就会启动流水线,从头到尾把这个 spec 做完——就在你项目的工作目录里,改文件、跑测试,样样都来。
|
|
20
20
|
|
|
21
|
-
你可以同时拥有好几条 rail
|
|
21
|
+
你可以同时拥有好几条 rail,把工作组织成一条条命名的通道(一条放你眼下专注的功能,另一条排在它后面候着)。rail 是**动态的**:Rails 头部的 **+ 添加** 按钮可以新建一条通道(每个项目最多 12 条),空闲且为空的通道可以删除。每条 rail 都由服务器托管,所以你的通道集合在刷新后依然保留,移动端 companion 和内置代理都能看到——当所有通道都在忙时,代理甚至能自己创建一条 rail。关于多 rail 和批量运行的更多内容,请看 [批量实现与多功能](batch-implement-and-multi-feature)。
|
|
22
22
|
|
|
23
23
|
## 在某个 spec 上启动一条 rail
|
|
24
24
|
|
|
@@ -49,7 +49,7 @@ rail 是一条**执行通道**。你从 SpecsBoard 上拖一张 spec 卡片放
|
|
|
49
49
|
| **Batch** | `/specrails:batch-implement` | 一个任务,按依赖感知的批次(wave)依次处理 rail 上的各个 spec。最适合一组相关的 spec。 |
|
|
50
50
|
| **Freestyle** | Freestyle | Claude 自主实现每个 spec,**绕过**流水线。每个 spec 一个独立任务。仅限 Claude。 |
|
|
51
51
|
|
|
52
|
-
Freestyle 是个特例:它跳过 Agent 链条,把原始 spec 直接交给 Claude,让它用自己的原生工具去做。因为它比较"放飞",所以按下 Play 会先弹出一个确认框,而且有一个按 rail 单独的模型选择器,让你在 Haiku / Sonnet / Opus 之间挑选。只有当 rail 的引擎是 Claude 时它才会出现。
|
|
52
|
+
Freestyle 是个特例:它跳过 Agent 链条,把原始 spec 直接交给 Claude,让它用自己的原生工具去做。因为它比较"放飞",所以按下 Play 会先弹出一个确认框,而且有一个按 rail 单独的模型选择器,让你在 Haiku / Sonnet / Opus 之间挑选。只有当 rail 的引擎是 Claude 时它才会出现。Freestyle 运行还是唯一会**一直开着等你**的任务:在任务详情的输入框里和它聊天,满意了就点击 **Finalize**(其他所有任务都会自己收尾)。
|
|
53
53
|
|
|
54
54
|
除了这些内置 loop,你还可以**搭建自己的 loop**——重复一个 verify → fix → verify 的循环直到目标达成、在 AI 步骤之间串联 shell 命令,等等。这些自定义 loop 会出现在同一个 Loop 选择器里。这就是下一个大点子:[Loop Builder](the-loop-builder)。
|
|
55
55
|
|
|
@@ -57,11 +57,11 @@ Freestyle 是个特例:它跳过 Agent 链条,把原始 spec 直接交给 Cl
|
|
|
57
57
|
|
|
58
58
|
每次你按下 Play,这次 rail 的运行就成了一个**任务**。最该记牢的一条规则是:
|
|
59
59
|
|
|
60
|
-
>
|
|
60
|
+
> **rail 是并行运行的。** 每次启动都会把工作隔离到每个 spec 独立的 git worktree 中,所以同一个项目里的多条 rail 可以同时运行、互不干扰——每次运行结束后,改动会以 merge 或 draft PR 的形式回归。
|
|
61
61
|
|
|
62
|
-
|
|
62
|
+
想让所有工作一起开跑?Rails 头部的 **全部启动** 按钮会一次性启动所有就绪的通道,只需一次确认,确认框会说明总成本(N 条 rail × AI 花费)。空的、已在运行的或等待 PR 决定的 rail 会被跳过,并在一个紧凑的汇总 toast 中报告。内置代理通过 `specrails_rails(launch_all)` 拥有同样的能力——而且当没有空闲通道时,它会自己创建一条新 rail。
|
|
63
63
|
|
|
64
|
-
|
|
64
|
+
只有传统路径(关闭 Loops 功能时)才会退回到旧的"每个项目一次一个任务"队列,此时多余的 rail 会排在正在运行的那条后面。跨项目的并行不变:每个项目仍然完全独立。
|
|
65
65
|
|
|
66
66
|
没有什么全局并发旋钮可调。唯一的自动节流是基于预算的:如果你设了每日预算(项目级或应用级),当当天的花费触到上限时,队列会自动暂停。
|
|
67
67
|
|
|
@@ -73,7 +73,7 @@ Freestyle 是个特例:它跳过 Agent 链条,把原始 spec 直接交给 Cl
|
|
|
73
73
|
- **日期范围筛选**——收窄到某个时间窗口。
|
|
74
74
|
- **对比**——选两个任务并排查看。
|
|
75
75
|
|
|
76
|
-
|
|
76
|
+
点击任意一张卡片,就能打开**任务详情视图**,实时流式日志和实时指标都在那里——而且在 Claude 任务上,一个聊天输入框让你**向运行中的 Agent 提问,或在运行途中给它指方向**,什么都不用停。这就是下一页的内容:[任务详情视图](the-job-detail-view)。
|
|
77
77
|
|
|
78
78
|
## 取消一个任务
|
|
79
79
|
|
|
@@ -1,10 +1,10 @@
|
|
|
1
1
|
# 任务详情视图
|
|
2
2
|
|
|
3
|
-
在 **Jobs** 页面点击任意一张任务卡片,你就来到了这里:观察单次 rail 运行的"驾驶舱"。它围绕一个承诺打造——**你看到的实时数字都是真实的,绝不是猜出来的。**
|
|
3
|
+
在 **Jobs** 页面点击任意一张任务卡片,你就来到了这里:观察单次 rail 运行的"驾驶舱"。它围绕一个承诺打造——**你看到的实时数字都是真实的,绝不是猜出来的。** 本页会带你逐一了解各个阶段、实时指标、工单卡片——以及那个让你**和运行中的任务对话**的输入框。
|
|
4
4
|
|
|
5
5
|
## 布局
|
|
6
6
|
|
|
7
|
-
|
|
7
|
+
完整的流式日志上方坐着两个面板;正在运行的 Claude 任务下方还有一个聊天输入框:
|
|
8
8
|
|
|
9
9
|
```
|
|
10
10
|
┌─────────────────────────────────────────────┐
|
|
@@ -15,6 +15,8 @@
|
|
|
15
15
|
│ │
|
|
16
16
|
│ Streaming log (auto-scroll · search · …) │
|
|
17
17
|
│ │
|
|
18
|
+
├─────────────────────────────────────────────┤
|
|
19
|
+
│ Composer (给任务发一条消息 · …) │
|
|
18
20
|
└─────────────────────────────────────────────┘
|
|
19
21
|
```
|
|
20
22
|
|
|
@@ -71,6 +73,29 @@ Architect ──► Developer ──► Reviewer ──► Ship
|
|
|
71
73
|
|
|
72
74
|
这就是 AI 正在做什么的原始真相——每一次工具调用、每一次文件编辑、每一次测试运行。
|
|
73
75
|
|
|
76
|
+
## Loop 运行:步骤浏览器
|
|
77
|
+
|
|
78
|
+
当任务是一次 **loop 运行**(见 [Loop Builder](the-loop-builder))时,扁平的日志会让位给一个**步骤浏览器**,它映射出 loop 的真实结构:
|
|
79
|
+
|
|
80
|
+
- 顶部的**总览条**是 loop 的实时地图——每个节点一个芯片(AI 步骤、Shell、循环决策器……),按图的流向排列。芯片随运行进度逐一点亮:等待时暗淡,运行时闪动,结束后打上对勾或叉号。决策器的芯片还会显示它实际采用的裁决——回到循环还是继续前进——右侧的迭代计数器(`迭代 3/10`)负责记数。点击任何芯片即可直接跳到该节点最近的一步。
|
|
81
|
+
- **每个步骤一个可折叠的盒子。** 对某个节点的每一次执行都会成为独立的一节,带有步骤编号、名称、迭代徽章、完成后的耗时——还有它自己的复制按钮,让你恰好拿走这一步的输出。(工具栏上的复制仍然拿走整份日志。)在第一步之前打印的内容——运行横幅、worktree 提示——会收进一个**准备**小节。
|
|
82
|
+
- **跟随模式**默认开启:正在运行的步骤保持展开并自动滚动,之前的步骤则折叠让路。一旦你向上滚动或打开旧步骤,跟随会暂停以便阅读——浮动的**恢复跟随**胶囊把你带回实时画面。**全部展开 / 全部折叠**在工具栏里,而在搜索框输入会同时搜索所有步骤。
|
|
83
|
+
- **中断的步骤同样诚实。** 一个从未来得及报告结果的步骤——运行被取消,或应用在步骤中途退出——会以虚线边框标记为**已中断**,而不是假装它完成了。
|
|
84
|
+
|
|
85
|
+
这个页面的其他一切在 loop 运行中都完全一样——实时指标、工单卡片、输入框。非 loop 任务仍保留上面经典的流式日志。
|
|
86
|
+
|
|
87
|
+
## 和运行中的任务对话
|
|
88
|
+
|
|
89
|
+
每个 Claude 任务默认都以**实时会话**的方式运行,所以本页底部——以及任务模式下的任务弹窗底部——都有一个聊天输入框。用它向运行中的 Agent 提问("那个测试为什么挂了?"),或者在运行途中给它指方向("跳过重构,专心修 bug")。
|
|
90
|
+
|
|
91
|
+
几件值得知道的事:
|
|
92
|
+
|
|
93
|
+
- **消息会排队,不会打断。** 在 Agent 流式输出时发送,你的消息会等着轮到自己——作为下一个 prompt 执行,任务继续按它的计划推进。一个小计数器会显示有多少条消息在排队。
|
|
94
|
+
- **总计行是真实的。** 输入框会显示一条实时的 `N 轮 · $X` 摘要,由每个已完成轮次的真实用量累加而来——和本页"绝不猜数字"的承诺一致。
|
|
95
|
+
- **会话有两种结束方式。** 大多数任务**自己收尾**:一旦某轮结束且没有排队的消息,会话就自行落定、任务完成——你的消息是可选的引导,从来不是义务。一个低调的**立即收尾**操作可以提前结束它,保留到目前为止产出的一切。**Freestyle** 任务是例外:它们在轮次之间待命,直到你点击 **Finalize**——这正是它的设计,一场由你来关闭的往返会话。
|
|
96
|
+
- **loop 运行中,消息会送到活跃的步骤。** 在内置或自定义 loop 上,你的消息会到达**此刻正在运行的 AI 步骤**。步骤之间(Loop Decider 思考时,或 shell 命令运行时)输入框会短暂显示*"等待下一步……"*状态——你草拟的文字会保留,下一个 AI 步骤启动时发送会重新可用。**结算此步骤**可以提前结束当前步骤,让 loop 带着它的产出继续前进。
|
|
97
|
+
- **目前仅限 Claude。** Codex 和 Gemini 任务和以前一样一次性运行——不会出现输入框。(服务器运维可以用 `SPECRAILS_INTERACTIVE_JOBS=false` 关掉整个功能。)
|
|
98
|
+
|
|
74
99
|
## 诊断导出
|
|
75
100
|
|
|
76
101
|
如果该任务启用了[遥测](../settings/customizing),头部会出现一个**导出诊断**按钮。它会下载一个 ZIP,里面包含:
|
|
@@ -40,17 +40,21 @@ Wave 3: #7 (docs across all) ← waits for #4 and #5
|
|
|
40
40
|
|
|
41
41
|
在这个任务内部,每个批次的 spec 都会在下一个批次开始之前实现完。你不需要手动配置这些——编排器会从 spec 本身推导出批次。在[任务详情视图](the-job-detail-view)里看着它一步步展开:流式日志会讲述这一批正进行到哪个 spec,而工单头部会显示这个任务触及的每一个 spec。
|
|
42
42
|
|
|
43
|
-
## Worktree
|
|
43
|
+
## Worktree 隔离,以及工作是如何交付的
|
|
44
44
|
|
|
45
|
-
当多个 spec
|
|
45
|
+
当多个 spec 在一次运行中被实现时,流水线会让每个工作单元保持隔离,这样并发或顺序的改动就不会把彼此的文件搞乱。每个 spec 的实现都跑在它自己那块干净的 **git worktree** 里——这是一个独立的检出,它共享你仓库的历史,但在 AI 干活期间绝不会碰你的工作树。
|
|
46
|
+
|
|
47
|
+
当运行结束时,**什么都不会被推送,也还没有任何 pull request 被创建**。工作安全地留在它们各自的隔离分支上,spec 进入一个新的 **On review(审查中)** 状态,然后 specrails **先来问你**:轨道上会出现一条常驻的决策栏,提供 **Create PR**——从你为项目指定的集成分支(在 **Settings → Integration branch** 里设置它;它默认取你仓库的默认分支)发起一个 draft pull request,把轨道上所有 spec 的工作合并在一起——以及 **Discard**。specrails **绝不合并,也绝不直接向你的集成分支提交**——PR 要不要存在由你决定,而合并这一步由人来掌控。这是一次安全的交接:只有你点头,specrails 才产出 pull request,你的工程师则像他们一贯做的那样,在 GitHub 里审查并合并它。
|
|
46
48
|
|
|
47
49
|
落到实处就是:
|
|
48
50
|
|
|
49
|
-
- 每个 spec
|
|
50
|
-
-
|
|
51
|
-
-
|
|
51
|
+
- 每个 spec 都得到一块干净的画布去实现,而不是半路接手上一个 spec 尚在进行中的编辑。
|
|
52
|
+
- 在运行进行期间,你的工作树绝不会被改动——在你点头之前,什么都不会落地。
|
|
53
|
+
- 运行完成后,spec 卡片会带上 **On review** 徽章,轨道向你提出那个问题:**Create PR** 打开合并后的 draft pull request,或 **Discard** 清理这些分支并把 spec 送回 backlog。如果这条轨道是从智能体聊天里启动的,同样的问题会以卡片的形式出现在那段对话里——在任何一处作答,两边都保持同步。
|
|
54
|
+
- 创建之后,**Open PR** 查看这个草稿,**发布** 把它开放给团队评审、交给你团队日常的 GitHub 审查流程,**Check merge** 则在你的团队完成合并后,把 spec 翻转为 Done。
|
|
55
|
+
- 如果在创建 PR 时这些隔离的分支没法干净地合并到一起,specrails 会安全地停下来,把这些分支留给人来处理——它绝不会把一次破碎的合并硬塞到你的基线上。你可以在同一条决策栏上重试或丢弃。
|
|
52
56
|
|
|
53
|
-
|
|
57
|
+
> 创建 PR 需要 GitHub CLI(`gh`)已完成认证,并配置好远端。若没有这些,specrails 依然会把工作保留在一个已提交的分支上,你可以自己从它发起 pull request——不会丢失任何东西,而且决策栏允许你重试。若要回退到旧行为(在本地整合而不是先询问),设置 `SPECRAILS_RAIL_DELIVER_PR=0`。
|
|
54
58
|
|
|
55
59
|
## 跨项目的多功能
|
|
56
60
|
|
|
@@ -80,7 +80,7 @@ builder 会帮你在 loop 真正跑起来之前就把它弄对:
|
|
|
80
80
|
2. 在 rail 头部打开 **Loop 选择器**,挑你那个已发布的 loop。
|
|
81
81
|
3. 按下 **▶ Play**。
|
|
82
82
|
|
|
83
|
-
这次运行会在 **Jobs**
|
|
83
|
+
这次运行会在 **Jobs** 视图里实时流式呈现,指标与成本追踪和任何 rail 任务一样——而它的日志则拥有一个专属的**步骤浏览器**:一张图的实时地图,每个步骤一个可折叠的盒子,并随 loop 推进跟随正在运行的步骤(见[任务详情视图](the-job-detail-view))。在 Claude 上,每个 **AI 步骤**同样是一场实时会话:从任务详情的输入框给它发消息,在步骤进行中给它指方向(步骤之间输入框会短暂等待,**结算此步骤**则让 loop 带着该步骤的产出继续前进)。一个因为撞到迭代上限或成本上限而停下的 loop,会以那个结果来上报,而不是报成一个干脆的成功。
|
|
84
84
|
|
|
85
85
|
> **loop 运行时请留意。** 当某个 loop 的某次运行正在执行时,你没法编辑或删除这个 loop——先把那次运行停掉。
|
|
86
86
|
|
|
@@ -13,7 +13,7 @@
|
|
|
13
13
|
- **便签视图**(默认)——卡片样式的方块,附带简短摘要。
|
|
14
14
|
- **列表视图**——紧凑的单行行式布局。
|
|
15
15
|
|
|
16
|
-
|
|
16
|
+
工具栏上的 **状态选择器** 把每种状态都显示为带实时计数的独立筛选片,另加两个智能分组:**活跃**(默认视图——一切仍在推进中的内容:草稿、待办、进行中和评审中)和 **全部**(所有内容,完成的固定在底部)。你的选择会按项目记住并同步到 URL,刷新或分享链接都能还原完全相同的视图。在连接了 Jira 的项目上还会出现一个 **Jira 状态** 下拉菜单,列出看板*真实*的工作流状态(原始名称,例如 "Code Review",每个都带实时计数),按其映射到的状态分组——它与状态筛选片叠加生效。你还可以按 **标签** 筛选,并按 **默认**、**工单 #** 或 **优先级** 排序(每一种都带有升序/降序切换)。
|
|
17
17
|
|
|
18
18
|
## 状态
|
|
19
19
|
|
|
@@ -24,7 +24,8 @@
|
|
|
24
24
|
| **草稿** | 从一次 Explore 对话中保存下来的、仍在打磨中的想法。还没准备好实现——你随时可以回来继续雕琢。会显示一个 `Draft` 标签。 |
|
|
25
25
|
| **待办** | 可以开工了。一份完成的 spec 创建后就落在这个状态。 |
|
|
26
26
|
| **进行中** | 流水线正在处理它(一个跳动的蓝点)。 |
|
|
27
|
-
|
|
|
27
|
+
| **评审中** | 已实现——每次运行结束后,spec 都会停在这里等你确认:合并草稿 PR,或自己把它移走(一个琥珀色标签)。 |
|
|
28
|
+
| **完成** | 已通过——PR 已合并,或你自己把它移到了这里(一个绿色对勾)。 |
|
|
28
29
|
| **已取消** | 已放弃(一个红色 X)。 |
|
|
29
30
|
|
|
30
31
|
草稿和待办的 spec 共处于同一个活跃区域里——并没有单独的列——但它们带有一圈淡淡的着色边框和一个 `Draft` 标签,所以很容易辨认。关于草稿的完整介绍,请参阅 [草稿与 Contract Layer](drafts-and-contract-layer.md)。
|
package/docs/internals/README.md
CHANGED
|
@@ -15,6 +15,11 @@ If you're a user looking for **how do I do X?** docs, head back to the [user gui
|
|
|
15
15
|
| [openspec-workflow.md](openspec-workflow.md) | `opsx:*` change lifecycle — used by the app itself for structured change management |
|
|
16
16
|
| [adding-a-provider.md](adding-a-provider.md) | How to add a new AI CLI: one adapter file plus one entry in the registry |
|
|
17
17
|
| [profiles.md](profiles.md) | Agent profiles quick start: open the Agents section, pick a profile per rail at launch, author custom agents in Agent Studio. For the true file-format and snapshotting internals, read `server/profile-manager.ts` and the profile-manager section of `CLAUDE.md` |
|
|
18
|
+
| [safe-pr-review-flow.md](safe-pr-review-flow.md) | The ask-first PR delivery: the `rail_pr_deliveries` row, decision state machine, the two synced decision surfaces (rail row + agent-chat card), the `on_review` ticket status and its Jira mapping |
|
|
19
|
+
| [interactive-jobs.md](interactive-jobs.md) | Interactive-by-default jobs: the persistent-stdin session model, `finalize` vs `auto` settle modes, loop-step turn routing, accounting reconciliation, kill-switch matrix |
|
|
20
|
+
| [loop-step-log-explorer.md](loop-step-log-explorer.md) | The step-grouped log surface for loop runs: the `loop_graph` / `loop_step` / `loop_step_end` event contract and seq guarantees, grouping + status model (interrupted rule, legacy fallback), follow mode, perf notes |
|
|
21
|
+
| [gemini-mcp-registration.md](gemini-mcp-registration.md) | How MCP servers actually reach gemini-cli (`.gemini/settings.json` + trust env, FQN tool prefix) and the deferred `.mcp.json` gap on non-agent-chat surfaces |
|
|
22
|
+
| [browser-capture-performance.md](browser-capture-performance.md) | Embedded-browser fluidity: the CDP screencast → WS → canvas pipeline, the latency levers (non-blocking navigation, input coalescing, latest-frame-wins drawing, frame conflation), tuning knobs, and the OAuth popup design |
|
|
18
23
|
|
|
19
24
|
**See also:** the app supports multiple AI CLIs as first-class, interchangeable engines — Claude Code, Codex CLI, and Gemini CLI. See [`../codex.md`](../codex.md) and [`../gemini.md`](../gemini.md) for the per-provider detail. Gemini is **enabled by default** (selectable whenever the `gemini` CLI is on `PATH`); the emergency rollback is `SPECRAILS_GEMINI_BETA=0` (only the exact string `0` disables it). Codex parallels this with `SPECRAILS_CODEX_BETA=0`.
|
|
20
25
|
|
|
@@ -250,9 +250,21 @@ app-level `PluginManager` already threads `providerId` through every
|
|
|
250
250
|
relevant method.
|
|
251
251
|
|
|
252
252
|
For `mcpRegistration === 'project-json'` providers, the existing
|
|
253
|
-
`.mcp.json` surgical-merge path applies —
|
|
254
|
-
|
|
255
|
-
|
|
253
|
+
`.mcp.json` surgical-merge path applies — **but only if your CLI actually
|
|
254
|
+
reads claude-style `.mcp.json`**. `project-json` really names that one
|
|
255
|
+
mechanism, and Gemini is the proof it isn't universal: gemini-cli has
|
|
256
|
+
never read `.mcp.json` — its only MCP surface is `mcpServers` in
|
|
257
|
+
`settings.json` (user scope `~/.gemini/`, project scope
|
|
258
|
+
`<cwd>/.gemini/`), and an untrusted cwd suppresses MCP entirely (headless
|
|
259
|
+
runs exit 55 with `FatalUntrustedWorkspaceError`; the app injects
|
|
260
|
+
`GEMINI_CLI_TRUST_WORKSPACE=true` per spawn). The desktop agent chat
|
|
261
|
+
registers its MCP for gemini via `<agent-cwd>/.gemini/settings.json` +
|
|
262
|
+
that trust env (`prepareAgentMcp` in `server/agent-mcp-config.ts`);
|
|
263
|
+
the plugin `.mcp.json` merge path still runs for gemini rails but the
|
|
264
|
+
server silently never loads there — a known deferred gap. Full facts +
|
|
265
|
+
the gap table: [gemini-mcp-registration.md](gemini-mcp-registration.md).
|
|
266
|
+
If your provider has its own config surface, mirror the gemini branch of
|
|
267
|
+
`prepareAgentMcp` rather than assuming `.mcp.json` is enough.
|
|
256
268
|
|
|
257
269
|
### 6. (If the binary needs a spawn-env quirk) add it to cli-prompt.ts
|
|
258
270
|
|
|
@@ -191,15 +191,15 @@ Example — queue a command on a specific provider:
|
|
|
191
191
|
| `GET` | `/jobs` | Job list (`?limit=&offset=&status=`) |
|
|
192
192
|
| `GET` | `/jobs/export` | CSV/JSON export |
|
|
193
193
|
| `GET` | `/jobs/compare` | Compare metrics between two jobs |
|
|
194
|
-
| `GET` | `/jobs/:id` | One job. Returns `{ job, events, phaseDefinitions }`; `job` is annotated with `hasTelemetry
|
|
194
|
+
| `GET` | `/jobs/:id` | One job. Returns `{ job, events, phaseDefinitions }`; `job` is annotated with `hasTelemetry`, `tickets[]` (resolved from the command, powers the ticket header), `interactiveSettleMode` (`'finalize'` \| `'auto'` \| `null`) and `interactiveAcceptingTurns` (whether a resident session accepts turns right now — a between-steps loop run reports `'auto'`/`false` so the composer can phrase the waiting state) |
|
|
195
195
|
| `DELETE` | `/jobs/:id` | Cancel a running or queued job |
|
|
196
196
|
| `DELETE` | `/jobs` | Purge completed jobs (optional `{ from, to }` window) |
|
|
197
197
|
| `PATCH` | `/jobs/:id/priority` | Re-rank a queued job |
|
|
198
|
-
| `POST` | `/jobs/:id/messages` | Send one more user turn to a running **interactive**
|
|
199
|
-
| `POST` | `/jobs/:id/finalize` | Finalize a running interactive job (SIGTERM the resident child; final totals +
|
|
198
|
+
| `POST` | `/jobs/:id/messages` | Send one more user turn to a running **interactive** job (queued behind the active turn). Body `{ text }`. Manager-agnostic: QueueManager is tried first, then the loop engine's active ai-step session. `202` accepted, `400` missing text, `403` interactive jobs disabled, `409` no active interactive session (unknown / non-interactive / finalized / a loop run between steps) |
|
|
199
|
+
| `POST` | `/jobs/:id/finalize` | Finalize a running interactive job (SIGTERM the resident child; final totals + terminal status are stamped when it closes). For a loop run this settles the **current step** and the loop advances. `202` scheduled, `403` interactive jobs disabled, `409` not an active interactive session |
|
|
200
200
|
| `GET` | `/jobs/:jobId/diagnostic` | Stream a diagnostic ZIP (telemetry + profile + plugins snapshots) |
|
|
201
201
|
|
|
202
|
-
The two interactive endpoints back the in-job chat
|
|
202
|
+
The two interactive endpoints back the in-job chat that is **on by default for every Claude job** — QueueManager jobs (implement / batch / Freestyle / custom commands) and the loop engine's claude ai-steps alike. Two settle modes: Freestyle/ultracode jobs idle until an explicit finalize (`'finalize'`); everything else settles itself on quiescence (`'auto'` — a turn result with nothing queued), where finalize acts as "wrap up now" / "settle this step". Providers without persistent stdin (Codex, Gemini) run one-shot as before and 409 here. Both endpoints 403 when the server has `SPECRAILS_INTERACTIVE_JOBS=false`. As-built detail: [interactive-jobs.md](interactive-jobs.md).
|
|
203
203
|
|
|
204
204
|
Example — fetch one job:
|
|
205
205
|
|
|
@@ -435,7 +435,7 @@ A non-developer-friendly file tree + Monaco viewer with plain-language AI summar
|
|
|
435
435
|
| `PUT` | `/:railIndex/profile` | Set the rail's default profile |
|
|
436
436
|
| `PUT` | `/:railIndex/engine` | Set the rail's AI engine override. Body `{ aiEngine }` (string — one of the project's providers — or `null` to clear) |
|
|
437
437
|
| `PUT` | `/:railIndex/name` | Set the rail's display name. Body `{ name }` (string or `null` to clear back to the default label); 400 if longer than 60 characters |
|
|
438
|
-
| `POST` | `/:railIndex/launch` | Launch the rail. Body `{ mode?, profileName?, aiEngine?, model?, interactive? }`. `mode` is `implement` / `batch-implement` / `ultracode`; `model` (haiku/sonnet/opus) applies to ultracode only
|
|
438
|
+
| `POST` | `/:railIndex/launch` | Launch the rail. Body `{ mode?, loopId?, profileName?, aiEngine?, model?, reasoning_effort?, originConversationId?, originSurface?, interactive? }`. `mode` is `implement` / `batch-implement` / `ultracode` / `loop`; a factory `loopId` (`factory:implement` etc.) maps to its legacy mode, and a **bare legacy mode with no `loopId`** (MCP / mobile / direct REST) derives the matching factory loop when Loops are enabled, so every launch door gets the same isolation + ask-first PR flow as the dashboard. `model` (haiku/sonnet/opus/fable) applies to ultracode only. The in-job chat is **on by default for every Claude job** — the legacy `interactive` param is accepted and **ignored** (wire compat; the spawn-time gate decides). Returns `202 { jobId, railIndex, mode }`; **`503`** when the Claude or Codex CLI binary is not found (a missing Gemini/other binary surfaces as `500`) |
|
|
439
439
|
| `POST` | `/:railIndex/stop` | Stop the rail's running job (cancels every job the rail registered) |
|
|
440
440
|
|
|
441
441
|
---
|
|
@@ -582,6 +582,7 @@ Every project-scoped message includes a `projectId` field. App-level messages ha
|
|
|
582
582
|
| `job.turn_user` | project | Interactive job: a user prompt was accepted (echoed so the in-job chat can render the bubble immediately; `queued` is true when a turn is already streaming) |
|
|
583
583
|
| `job.turn_done` | project | Interactive job: a turn finished streaming, carrying the running sum of real token/cost totals |
|
|
584
584
|
| `job.finalized` | project | Interactive job finalized (or crashed): final authoritative totals + terminal status |
|
|
585
|
+
| `job.interactive` | project | Loop runs: the accepting-turns signal (`acceptingTurns: true` when an ai-step's resident session goes live, `false` when it settles) — flips the composer between live and the between-steps waiting state without polling |
|
|
585
586
|
|
|
586
587
|
### Budget & cost
|
|
587
588
|
|
|
@@ -0,0 +1,93 @@
|
|
|
1
|
+
# Embedded browser: performance + popup support
|
|
2
|
+
|
|
3
|
+
The embedded browser backs two surfaces: **Add Spec → From a website** (`BrowserCaptureModal`) and the read-only **WebView** for opening links / the Agent-Mode Browser tool (`WebViewModal`, `AgentBrowserCapture`). Both ride the same session machinery. This doc maps the pipeline, the fluidity levers applied (benchmark: Cursor's embedded browser), the tuning knobs, and the OAuth popup design.
|
|
4
|
+
|
|
5
|
+
## Pipeline map
|
|
6
|
+
|
|
7
|
+
```
|
|
8
|
+
Chromium (headless, persistent shared context — browser-context-pool.ts)
|
|
9
|
+
│ CDP Page.startScreencast (JPEG frames) Playwright input API
|
|
10
|
+
▼ ▲
|
|
11
|
+
PlaywrightPageHandle (server/browser-playwright.ts) │
|
|
12
|
+
│ ScreencastFrame (raw JPEG Buffer) │ dispatchInput
|
|
13
|
+
▼ │
|
|
14
|
+
BrowserCaptureManager (server/browser-capture-manager.ts)
|
|
15
|
+
│ binary WS frames (dedicated /ws/browser/:id) │ JSON control {type:'input'|'probe'}
|
|
16
|
+
▼ │
|
|
17
|
+
useBrowserCaptureSession (client) ───────────────────┘
|
|
18
|
+
│ createImageBitmap → canvas 2d drawImage
|
|
19
|
+
▼
|
|
20
|
+
<canvas> in BrowserCaptureModal / WebViewModal
|
|
21
|
+
```
|
|
22
|
+
|
|
23
|
+
- REST (`project-router-terminals.ts`, `/browser/sessions*`): create / navigate / capture / clipboard / element / popup-view / kill.
|
|
24
|
+
- Session create opens one page in the app-wide shared persistent context (global cookies/logins).
|
|
25
|
+
|
|
26
|
+
## Bottlenecks found (as-was)
|
|
27
|
+
|
|
28
|
+
1. **`create()` awaited the initial `page.goto(…, waitUntil: 'domcontentloaded')`** — the POST (and the modal spinner) blocked up to 30s on a slow site before the first frame could ever be shown.
|
|
29
|
+
2. **Unthrottled wheel forwarding.** Every trackpad wheel event (60–120 Hz on macOS) crossed WS → manager → Playwright as `mouse.move` **then** `mouse.wheel` — two sequentially-awaited CDP commands per tick, flooding the page's input queue. This was the single biggest scroll-lag source. (`WebViewModal` also forwarded every raw `pointermove`, unthrottled.)
|
|
30
|
+
3. **Client frame path dropped the *newest* frame.** While one decode was in flight, incoming frames were discarded — so under load the canvas kept showing the *older* frame and lagged reality.
|
|
31
|
+
4. **Screencast ack after fan-out.** `Page.screencastFrameAck` was sent after the frame handler ran; Chromium throttles on unacked frames, so ack latency directly limited fps.
|
|
32
|
+
5. **No backpressure handling.** A slow client's WS send-buffer queued unlimited stale frames — latency grew unboundedly instead of frames being dropped.
|
|
33
|
+
6. **Pop-ups were silently ignored.** `window.open` / `target=_blank` / OAuth login windows opened invisible pages — an Okta-style login was impossible.
|
|
34
|
+
|
|
35
|
+
## Changes applied
|
|
36
|
+
|
|
37
|
+
### Server
|
|
38
|
+
|
|
39
|
+
| Lever | Where | Expected win |
|
|
40
|
+
|---|---|---|
|
|
41
|
+
| **Non-blocking initial navigation** — `create()` returns as soon as the page exists; `goto` completes in the background and lands via the `nav` WS broadcast. The client attaches + screencasts immediately, so the page paints progressively. | `browser-capture-manager.ts` `runInitialNavigation` | Removes 1–30 s of perceived cold-open latency; the biggest UX win. |
|
|
42
|
+
| **Ack-first screencast** — `screencastFrameAck` fires (fire-and-forget) *before* the handler/fan-out, overlapping Chromium's next capture with delivery. | `browser-playwright.ts` `startScreencast` | Higher fps ceiling, lower frame age. |
|
|
43
|
+
| **Wheel fast-path** — skip the redundant `mouse.move` when the cursor hasn't moved (tracked via `lastMouse`), and dispatch move+wheel back-to-back (`Promise.all`) so a concurrent wheel can't interleave between them. | `browser-playwright.ts` `dispatchInput` | ~2× fewer CDP commands per wheel; ordering hazard removed. |
|
|
44
|
+
| **Frame conflation for slow consumers** — skip a frame for any WS client whose `bufferedAmount` exceeds 1 MB (frames are independent JPEGs; `lastFrame` still updates). | `browser-capture-manager.ts` fan-out | Latency stays bounded under backpressure — staleness, not fps, is what reads as "sluggish". |
|
|
45
|
+
| **Centralised screencast params** — `screencastParams()`: JPEG, `everyNthFrame: 1`, guard caps 3840×2400 (viewport already ≤ display size, so this is a guard, not a downscaler). | `browser-playwright.ts` | Tunable quality knob (below); pathological-viewport guard. |
|
|
46
|
+
| **Live URL bar** — `onNavigated` (main-frame `framenavigated`) broadcasts `nav` on in-page link clicks/redirects. | manager + playwright handle | URL bar no longer goes stale after clicking links. |
|
|
47
|
+
|
|
48
|
+
### Client
|
|
49
|
+
|
|
50
|
+
| Lever | Where | Expected win |
|
|
51
|
+
|---|---|---|
|
|
52
|
+
| **Pointer/wheel coalescing** — `createPointerInputCoalescer`: ≤1 `move` (newest-wins) + ≤1 `wheel` (deltas summed, latest position) per animation frame; `flush()` runs synchronously before every mouse down/up, preceded by an exact `move` to the click point. | `lib/browser-capture.ts`, used by both modals | 2–5× fewer input messages during scroll; click precision *improved* (down/up now always preceded by an exact-position move — the server dispatches clicks at the current cursor position). |
|
|
53
|
+
| **Latest-frame-wins decode+draw pipeline** — `createFramePipeline`: only the newest undecoded frame is kept (intermediates dropped), decode via `createImageBitmap(Blob)` (off-main-thread), paints coalesced on rAF drawing only the newest bitmap. | `lib/browser-frame-pipeline.ts`, wired in `useBrowserCaptureSession` | Under load the canvas shows the *freshest* frame instead of falling behind; drops are counted, not felt. |
|
|
54
|
+
| **Dev perf probe** — `localStorage['specrails-desktop:browser-capture-debug'] = '1'` → `console.table` every 2 s: `fpsReceived`, `fpsDrawn`, `droppedStale`, `droppedUndrawn`, `avgDecodeMs`, `avgDrawMs`. | `browser-frame-pipeline.ts` reporter | Cheap before/after measurement on real pages. |
|
|
55
|
+
|
|
56
|
+
Select-mode hover-probe throttling (rAF + 40 ms) is untouched — element-picker precision is unchanged.
|
|
57
|
+
|
|
58
|
+
## Popup support (OAuth login windows)
|
|
59
|
+
|
|
60
|
+
Pop-ups now work end-to-end — the design:
|
|
61
|
+
|
|
62
|
+
- **Adoption.** `PlaywrightPageHandle.onPopup` (Playwright `page.on('popup')`) hands every popup to the manager, which registers it on the session's `popups[]` stack. The popup lives in the **same browser context** natively, so cookies and the `window.opener`/`postMessage` relationship survive — exactly what completes an OAuth popup flow. Popups can themselves open popups (chained IdP windows): latest wins.
|
|
63
|
+
- **Routing split.** *Interactive* traffic (mouse/wheel/keys, clipboard — pasting credentials) targets the **viewed** page (top popup while `popupView`, else root). *Capture-ish* traffic (region capture, breakpoints, hover probe, URL-bar navigation, lastUrl persistence) **always targets the root page** — a popup is never the spec's subject. `resize` fans to root + all popups so coordinate mapping never diverges.
|
|
64
|
+
- **Screencast switch.** `applyScreencast` reconciles which page the CDP screencast runs on (`screencastPage`) against the active page on the same serialized per-session op chain; opening/closing/toggling a popup stops the cast on the old page and starts it on the new one (CDP emits a frame immediately on start, so the switch paints at once).
|
|
65
|
+
- **Lifecycle.** Popup `close` (the typical OAuth self-close) auto-returns to the opener — or to the next popup down. Session `kill`/`shutdown` closes all popups. Viewport is inherited at adoption.
|
|
66
|
+
- **Client.** WS `{type:'popup', count, active, url}` broadcasts (re-sent to late attachers, refreshed as the popup walks its redirect chain) drive a slim bar: *"Login window — <origin>"* + back-to-page while active; a *"Show login window"* chip while parked on the root; `+N` hint when stacked. Select mode is disabled (and force-exited) while a popup is viewed. The toggle is `POST /browser/sessions/:id/popup-view {target:'root'|'popup'}`.
|
|
67
|
+
|
|
68
|
+
## Tuning knobs
|
|
69
|
+
|
|
70
|
+
| Knob | Default | Effect |
|
|
71
|
+
|---|---|---|
|
|
72
|
+
| `SPECRAILS_BROWSER_SCREENCAST_QUALITY` (server env) | `70` | JPEG quality 1–100. Lower → smaller frames/higher fps; higher → crisper. |
|
|
73
|
+
| `localStorage['specrails-desktop:browser-capture-debug'] = '1'` (client) | off | Per-2s frame-pipeline stats in the console. |
|
|
74
|
+
| `MAX_CLIENT_BUFFERED_BYTES` (`browser-capture-manager.ts`) | 1 MB | WS backpressure threshold before frames are conflated per client. |
|
|
75
|
+
|
|
76
|
+
## Deferred / non-goals
|
|
77
|
+
|
|
78
|
+
- **DPR-aware streaming** (frames at `devicePixelRatio ×` for retina crispness) — costs 4× pixels; quality knob covers most of it. Revisit if crispness complaints appear.
|
|
79
|
+
- **Context prewarm on Add-Spec-modal open** — would shave the first-ever Chromium launch (~0.5–1 s); needs a hook outside the browser-capture surface. The shared context already persists across sessions, so only the first open pays it.
|
|
80
|
+
- **Input round-trip probe** — needs a server echo; the frame probe covers the visible symptom.
|
|
81
|
+
|
|
82
|
+
## Verification
|
|
83
|
+
|
|
84
|
+
Unit coverage: `server/browser-capture-manager.test.ts` (deferred nav, conflation, full popup lifecycle), `server/browser-playwright.test.ts` (`screencastParams`), `server/project-router.browser.test.ts` (popup-view route), `client/src/lib/browser-frame-pipeline.test.ts` (latest-wins/drop/dispose/stats), `client/src/lib/browser-capture.test.ts` (coalescer, popup helpers).
|
|
85
|
+
|
|
86
|
+
Manual QA feel-check list:
|
|
87
|
+
|
|
88
|
+
1. **Scroll fluidity** — open a long page (e.g. a docs site), trackpad-scroll fast: motion should track your fingers with no rubber-banding or seconds-later catch-up.
|
|
89
|
+
2. **Typing latency** — click a search box, type quickly: characters should appear with terminal-like latency.
|
|
90
|
+
3. **Cold open** — "From a website" on a slow site: the modal should show the page *painting* immediately, not a 10 s spinner.
|
|
91
|
+
4. **Picker precision** — select mode: hover highlight follows exactly, clicked element == captured element, breadcrumb ↑/↓ unchanged.
|
|
92
|
+
5. **Okta-style OAuth popup** — click a "Sign in with …" button: the login window takes over the canvas with the "Login window — <origin>" bar; complete the login (typing + ⌘V paste land in the popup); on the popup's self-close you're back on the opener **logged in**. "Back to page" / "Show login window" toggles views mid-flow.
|
|
93
|
+
6. **Perf numbers** — set the debug flag, repeat (1): `fpsDrawn` should sit near `fpsReceived` with `droppedUndrawn` low; during heavy load drops rise while the image stays *current*.
|