@rpamis/comet 0.4.3 → 0.4.4
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 +332 -332
- package/assets/manifest.json +1 -1
- package/assets/skills/comet/scripts/comet-archive.mjs +109 -96
- package/assets/skills/comet/scripts/comet-check.mjs +117 -104
- package/assets/skills/comet/scripts/comet-entry-runtime.mjs +59 -59
- package/assets/skills/comet/scripts/comet-guard.mjs +173 -160
- package/assets/skills/comet/scripts/comet-handoff.mjs +110 -97
- package/assets/skills/comet/scripts/comet-hook-guard.mjs +110 -97
- package/assets/skills/comet/scripts/comet-hook-router.mjs +269 -159
- package/assets/skills/comet/scripts/comet-intent.mjs +31 -31
- package/assets/skills/comet/scripts/comet-resume-probe.mjs +104 -91
- package/assets/skills/comet/scripts/comet-runtime.mjs +272 -259
- package/assets/skills/comet/scripts/comet-state.mjs +204 -191
- package/assets/skills/comet/scripts/comet-yaml-validate.mjs +25 -25
- package/assets/skills/comet-archive/SKILL.md +4 -4
- package/assets/skills/comet-build/SKILL.md +4 -6
- package/assets/skills/comet-classic/SKILL.md +1 -1
- package/assets/skills/comet-classic/reference/scripts.md +9 -1
- package/assets/skills/comet-design/SKILL.md +0 -2
- package/assets/skills/comet-hotfix/SKILL.md +1 -3
- package/assets/skills/comet-native/SKILL.md +8 -7
- package/assets/skills/comet-native/reference/artifacts.md +7 -7
- package/assets/skills/comet-native/reference/clarification.md +4 -4
- package/assets/skills/comet-native/reference/commands.md +15 -13
- package/assets/skills/comet-native/reference/recovery.md +3 -3
- package/assets/skills/comet-native/reference/workspace.md +10 -4
- package/assets/skills/comet-native/scripts/comet-native-archive.mjs +230 -149
- package/assets/skills/comet-native/scripts/comet-native-doctor.mjs +239 -161
- package/assets/skills/comet-native/scripts/comet-native-hook-guard.mjs +232 -122
- package/assets/skills/comet-native/scripts/comet-native-init.mjs +184 -107
- package/assets/skills/comet-native/scripts/comet-native-new.mjs +219 -142
- package/assets/skills/comet-native/scripts/comet-native-next.mjs +239 -161
- package/assets/skills/comet-native/scripts/comet-native-root.mjs +205 -128
- package/assets/skills/comet-native/scripts/comet-native-runtime.mjs +276 -195
- package/assets/skills/comet-native/scripts/comet-native-select.mjs +204 -127
- package/assets/skills/comet-native/scripts/comet-native-show.mjs +202 -125
- package/assets/skills/comet-native/scripts/comet-native-spec.mjs +203 -125
- package/assets/skills/comet-native/scripts/comet-native-status.mjs +200 -123
- package/assets/skills/comet-open/SKILL.md +0 -2
- package/assets/skills/comet-tweak/SKILL.md +1 -1
- package/assets/skills/comet-verify/SKILL.md +0 -2
- package/assets/skills-zh/comet-archive/SKILL.md +4 -4
- package/assets/skills-zh/comet-build/SKILL.md +4 -6
- package/assets/skills-zh/comet-classic/SKILL.md +1 -1
- package/assets/skills-zh/comet-classic/reference/scripts.md +9 -1
- package/assets/skills-zh/comet-design/SKILL.md +0 -2
- package/assets/skills-zh/comet-hotfix/SKILL.md +1 -3
- package/assets/skills-zh/comet-native/SKILL.md +8 -7
- package/assets/skills-zh/comet-native/reference/artifacts.md +7 -7
- package/assets/skills-zh/comet-native/reference/clarification.md +4 -4
- package/assets/skills-zh/comet-native/reference/commands.md +16 -10
- package/assets/skills-zh/comet-native/reference/recovery.md +3 -3
- package/assets/skills-zh/comet-native/reference/workspace.md +10 -4
- package/assets/skills-zh/comet-open/SKILL.md +0 -2
- package/assets/skills-zh/comet-tweak/SKILL.md +1 -1
- package/assets/skills-zh/comet-verify/SKILL.md +0 -2
- package/bin/comet-daemon-router.js +23 -7
- package/bin/fast-runtime-router.js +1 -1
- package/dist/app/commands/daemon-server.d.ts.map +1 -1
- package/dist/app/commands/daemon-server.js +13 -2
- package/dist/app/commands/daemon-server.js.map +1 -1
- package/dist/domains/comet-classic/classic-archive-entry.d.ts +1 -1
- package/dist/domains/comet-classic/classic-archive-entry.d.ts.map +1 -1
- package/dist/domains/comet-classic/classic-archive-entry.js +5 -2
- package/dist/domains/comet-classic/classic-archive-entry.js.map +1 -1
- package/dist/domains/comet-classic/classic-branch-binding.d.ts.map +1 -1
- package/dist/domains/comet-classic/classic-branch-binding.js +5 -4
- package/dist/domains/comet-classic/classic-branch-binding.js.map +1 -1
- package/dist/domains/comet-classic/classic-check-entry.d.ts +1 -1
- package/dist/domains/comet-classic/classic-check-entry.d.ts.map +1 -1
- package/dist/domains/comet-classic/classic-check-entry.js +5 -2
- package/dist/domains/comet-classic/classic-check-entry.js.map +1 -1
- package/dist/domains/comet-classic/classic-check-snapshot.d.ts.map +1 -1
- package/dist/domains/comet-classic/classic-check-snapshot.js +68 -26
- package/dist/domains/comet-classic/classic-check-snapshot.js.map +1 -1
- package/dist/domains/comet-classic/classic-guard-entry.d.ts +1 -1
- package/dist/domains/comet-classic/classic-guard-entry.d.ts.map +1 -1
- package/dist/domains/comet-classic/classic-guard-entry.js +5 -2
- package/dist/domains/comet-classic/classic-guard-entry.js.map +1 -1
- package/dist/domains/comet-classic/classic-handoff-entry.d.ts +1 -1
- package/dist/domains/comet-classic/classic-handoff-entry.d.ts.map +1 -1
- package/dist/domains/comet-classic/classic-handoff-entry.js +5 -2
- package/dist/domains/comet-classic/classic-handoff-entry.js.map +1 -1
- package/dist/domains/comet-classic/classic-resume-probe.d.ts.map +1 -1
- package/dist/domains/comet-classic/classic-resume-probe.js +3 -2
- package/dist/domains/comet-classic/classic-resume-probe.js.map +1 -1
- package/dist/domains/comet-classic/classic-script-entry.d.ts +3 -1
- package/dist/domains/comet-classic/classic-script-entry.d.ts.map +1 -1
- package/dist/domains/comet-classic/classic-script-entry.js +34 -3
- package/dist/domains/comet-classic/classic-script-entry.js.map +1 -1
- package/dist/domains/comet-classic/classic-state-command.d.ts.map +1 -1
- package/dist/domains/comet-classic/classic-state-command.js +3 -2
- package/dist/domains/comet-classic/classic-state-command.js.map +1 -1
- package/dist/domains/comet-classic/classic-state-entry.d.ts +1 -1
- package/dist/domains/comet-classic/classic-state-entry.d.ts.map +1 -1
- package/dist/domains/comet-classic/classic-state-entry.js +5 -2
- package/dist/domains/comet-classic/classic-state-entry.js.map +1 -1
- package/dist/domains/comet-classic/classic-store.d.ts.map +1 -1
- package/dist/domains/comet-classic/classic-store.js +67 -1
- package/dist/domains/comet-classic/classic-store.js.map +1 -1
- package/dist/domains/comet-entry/resume-probe.d.ts.map +1 -1
- package/dist/domains/comet-entry/resume-probe.js +3 -2
- package/dist/domains/comet-entry/resume-probe.js.map +1 -1
- package/dist/domains/comet-native/native-acceptance.d.ts +5 -1
- package/dist/domains/comet-native/native-acceptance.d.ts.map +1 -1
- package/dist/domains/comet-native/native-acceptance.js +13 -2
- package/dist/domains/comet-native/native-acceptance.js.map +1 -1
- package/dist/domains/comet-native/native-archive-command.d.ts.map +1 -1
- package/dist/domains/comet-native/native-archive-command.js +167 -37
- package/dist/domains/comet-native/native-archive-command.js.map +1 -1
- package/dist/domains/comet-native/native-artifact-language.d.ts +3 -1
- package/dist/domains/comet-native/native-artifact-language.d.ts.map +1 -1
- package/dist/domains/comet-native/native-artifact-language.js +4 -11
- package/dist/domains/comet-native/native-artifact-language.js.map +1 -1
- package/dist/domains/comet-native/native-artifacts.d.ts +8 -1
- package/dist/domains/comet-native/native-artifacts.d.ts.map +1 -1
- package/dist/domains/comet-native/native-artifacts.js +14 -2
- package/dist/domains/comet-native/native-artifacts.js.map +1 -1
- package/dist/domains/comet-native/native-builder-acceptance-review.d.ts +16 -0
- package/dist/domains/comet-native/native-builder-acceptance-review.d.ts.map +1 -0
- package/dist/domains/comet-native/native-builder-acceptance-review.js +65 -0
- package/dist/domains/comet-native/native-builder-acceptance-review.js.map +1 -0
- package/dist/domains/comet-native/native-cli-help.d.ts.map +1 -1
- package/dist/domains/comet-native/native-cli-help.js +8 -4
- package/dist/domains/comet-native/native-cli-help.js.map +1 -1
- package/dist/domains/comet-native/native-cli-shared.d.ts +4 -2
- package/dist/domains/comet-native/native-cli-shared.d.ts.map +1 -1
- package/dist/domains/comet-native/native-cli-shared.js +37 -9
- package/dist/domains/comet-native/native-cli-shared.js.map +1 -1
- package/dist/domains/comet-native/native-cli.d.ts +4 -1
- package/dist/domains/comet-native/native-cli.d.ts.map +1 -1
- package/dist/domains/comet-native/native-cli.js +9 -5
- package/dist/domains/comet-native/native-cli.js.map +1 -1
- package/dist/domains/comet-native/native-doctor-command.d.ts.map +1 -1
- package/dist/domains/comet-native/native-doctor-command.js +144 -3
- package/dist/domains/comet-native/native-doctor-command.js.map +1 -1
- package/dist/domains/comet-native/native-git-provenance.d.ts.map +1 -1
- package/dist/domains/comet-native/native-git-provenance.js +3 -2
- package/dist/domains/comet-native/native-git-provenance.js.map +1 -1
- package/dist/domains/comet-native/native-hook-guard.d.ts.map +1 -1
- package/dist/domains/comet-native/native-hook-guard.js +56 -26
- package/dist/domains/comet-native/native-hook-guard.js.map +1 -1
- package/dist/domains/comet-native/native-local-execution.d.ts +1 -0
- package/dist/domains/comet-native/native-local-execution.d.ts.map +1 -1
- package/dist/domains/comet-native/native-local-execution.js +7 -0
- package/dist/domains/comet-native/native-local-execution.js.map +1 -1
- package/dist/domains/comet-native/native-lock.d.ts.map +1 -1
- package/dist/domains/comet-native/native-lock.js +12 -0
- package/dist/domains/comet-native/native-lock.js.map +1 -1
- package/dist/domains/comet-native/native-loop-runtime.d.ts +2 -0
- package/dist/domains/comet-native/native-loop-runtime.d.ts.map +1 -1
- package/dist/domains/comet-native/native-loop-runtime.js +6 -0
- package/dist/domains/comet-native/native-loop-runtime.js.map +1 -1
- package/dist/domains/comet-native/native-next-command.d.ts.map +1 -1
- package/dist/domains/comet-native/native-next-command.js +57 -28
- package/dist/domains/comet-native/native-next-command.js.map +1 -1
- package/dist/domains/comet-native/native-output-language.d.ts.map +1 -1
- package/dist/domains/comet-native/native-output-language.js +7 -0
- package/dist/domains/comet-native/native-output-language.js.map +1 -1
- package/dist/domains/comet-native/native-portable-acceptance.d.ts +2 -0
- package/dist/domains/comet-native/native-portable-acceptance.d.ts.map +1 -1
- package/dist/domains/comet-native/native-portable-acceptance.js +11 -1
- package/dist/domains/comet-native/native-portable-acceptance.js.map +1 -1
- package/dist/domains/comet-native/native-portable-archive.d.ts +1 -0
- package/dist/domains/comet-native/native-portable-archive.d.ts.map +1 -1
- package/dist/domains/comet-native/native-portable-archive.js +3 -0
- package/dist/domains/comet-native/native-portable-archive.js.map +1 -1
- package/dist/domains/comet-native/native-portable-checks.d.ts +14 -4
- package/dist/domains/comet-native/native-portable-checks.d.ts.map +1 -1
- package/dist/domains/comet-native/native-portable-checks.js +159 -60
- package/dist/domains/comet-native/native-portable-checks.js.map +1 -1
- package/dist/domains/comet-native/native-portable-continuation.d.ts +2 -1
- package/dist/domains/comet-native/native-portable-continuation.d.ts.map +1 -1
- package/dist/domains/comet-native/native-portable-continuation.js +121 -39
- package/dist/domains/comet-native/native-portable-continuation.js.map +1 -1
- package/dist/domains/comet-native/native-portable-requirements.d.ts +1 -0
- package/dist/domains/comet-native/native-portable-requirements.d.ts.map +1 -1
- package/dist/domains/comet-native/native-portable-requirements.js +61 -18
- package/dist/domains/comet-native/native-portable-requirements.js.map +1 -1
- package/dist/domains/comet-native/native-portable-shape-coordination.d.ts.map +1 -1
- package/dist/domains/comet-native/native-portable-shape-coordination.js +18 -5
- package/dist/domains/comet-native/native-portable-shape-coordination.js.map +1 -1
- package/dist/domains/comet-native/native-portable-state.d.ts.map +1 -1
- package/dist/domains/comet-native/native-portable-state.js +10 -3
- package/dist/domains/comet-native/native-portable-state.js.map +1 -1
- package/dist/domains/comet-native/native-portable-status.d.ts.map +1 -1
- package/dist/domains/comet-native/native-portable-status.js +10 -4
- package/dist/domains/comet-native/native-portable-status.js.map +1 -1
- package/dist/domains/comet-native/native-portable-types.d.ts +2 -1
- package/dist/domains/comet-native/native-portable-types.d.ts.map +1 -1
- package/dist/domains/comet-native/native-portable-types.js.map +1 -1
- package/dist/domains/comet-native/native-portable-verification.d.ts +3 -0
- package/dist/domains/comet-native/native-portable-verification.d.ts.map +1 -1
- package/dist/domains/comet-native/native-portable-verification.js +28 -35
- package/dist/domains/comet-native/native-portable-verification.js.map +1 -1
- package/dist/domains/comet-native/native-portable-verifier-coordination.d.ts +2 -0
- package/dist/domains/comet-native/native-portable-verifier-coordination.d.ts.map +1 -1
- package/dist/domains/comet-native/native-portable-verifier-coordination.js +9 -0
- package/dist/domains/comet-native/native-portable-verifier-coordination.js.map +1 -1
- package/dist/domains/comet-native/native-runner-input-artifacts.d.ts +9 -0
- package/dist/domains/comet-native/native-runner-input-artifacts.d.ts.map +1 -0
- package/dist/domains/comet-native/native-runner-input-artifacts.js +102 -0
- package/dist/domains/comet-native/native-runner-input-artifacts.js.map +1 -0
- package/dist/domains/comet-native/native-runner-input.d.ts +90 -64
- package/dist/domains/comet-native/native-runner-input.d.ts.map +1 -1
- package/dist/domains/comet-native/native-runner-input.js +107 -22
- package/dist/domains/comet-native/native-runner-input.js.map +1 -1
- package/dist/domains/comet-native/native-script-entry.d.ts.map +1 -1
- package/dist/domains/comet-native/native-script-entry.js +9 -3
- package/dist/domains/comet-native/native-script-entry.js.map +1 -1
- package/dist/domains/comet-native/native-snapshot.d.ts.map +1 -1
- package/dist/domains/comet-native/native-snapshot.js +7 -2
- package/dist/domains/comet-native/native-snapshot.js.map +1 -1
- package/dist/domains/comet-native/native-verification-receipt-runtime.d.ts.map +1 -1
- package/dist/domains/comet-native/native-verification-receipt-runtime.js +5 -4
- package/dist/domains/comet-native/native-verification-receipt-runtime.js.map +1 -1
- package/dist/domains/comet-native/native-workspace-finish.d.ts +26 -0
- package/dist/domains/comet-native/native-workspace-finish.d.ts.map +1 -1
- package/dist/domains/comet-native/native-workspace-finish.js +520 -15
- package/dist/domains/comet-native/native-workspace-finish.js.map +1 -1
- package/dist/domains/dashboard/web/assets/{abnfDiagram-VCTEODGH-qlcciI25.js → abnfDiagram-VCTEODGH-CFEU4PQU.js} +1 -1
- package/dist/domains/dashboard/web/assets/{arc-KVm4k9kp.js → arc-BeYYJor9.js} +1 -1
- package/dist/domains/dashboard/web/assets/architecture-7GRP2DOG-YphM8Wtg.js +1 -0
- package/dist/domains/dashboard/web/assets/{architectureDiagram-5GKGNRK7-C366RdBK.js → architectureDiagram-5GKGNRK7-CqTy4fyH.js} +1 -1
- package/dist/domains/dashboard/web/assets/{blockDiagram-I7D4REHJ-DAuTc2OO.js → blockDiagram-I7D4REHJ-SR_5S4SA.js} +1 -1
- package/dist/domains/dashboard/web/assets/{c4Diagram-7LVT6UL2-CFB0RZmL.js → c4Diagram-7LVT6UL2-DzphG2XS.js} +1 -1
- package/dist/domains/dashboard/web/assets/channel-BkwcGbYR.js +1 -0
- package/dist/domains/dashboard/web/assets/{chunk-4HAMMTFA-DTV6lyGQ.js → chunk-4HAMMTFA-BpthUtIs.js} +1 -1
- package/dist/domains/dashboard/web/assets/{chunk-75Z2AOVW-DgJm4cEX.js → chunk-75Z2AOVW-CxAdhPhG.js} +1 -1
- package/dist/domains/dashboard/web/assets/{chunk-DU6HZSFF-NAtcgGZr.js → chunk-DU6HZSFF-5peVNfxp.js} +1 -1
- package/dist/domains/dashboard/web/assets/{chunk-F27PBJKO-BcFXHZMJ.js → chunk-F27PBJKO-CwG4xi2V.js} +1 -1
- package/dist/domains/dashboard/web/assets/{chunk-GMAD6QVW-wNemar9b.js → chunk-GMAD6QVW-BuFFY783.js} +1 -1
- package/dist/domains/dashboard/web/assets/{chunk-GVQU2GXP-BiVCDO9d.js → chunk-GVQU2GXP-OyUFmjE-.js} +1 -1
- package/dist/domains/dashboard/web/assets/{chunk-IMKFNOWR-D9GDj4b6.js → chunk-IMKFNOWR-DmTme45C.js} +1 -1
- package/dist/domains/dashboard/web/assets/{chunk-L3NEJ4N5-DkPl5vac.js → chunk-L3NEJ4N5-D6BHbKty.js} +1 -1
- package/dist/domains/dashboard/web/assets/{chunk-OSK3NFVY-RbbxGqtJ.js → chunk-OSK3NFVY-CCz1v1Nv.js} +1 -1
- package/dist/domains/dashboard/web/assets/{chunk-P2QGCYS3-B9_X57eT.js → chunk-P2QGCYS3-C1_7kDYS.js} +1 -1
- package/dist/domains/dashboard/web/assets/{chunk-POPQ4Y6H-DE4bOH0D.js → chunk-POPQ4Y6H-buFKlAdG.js} +1 -1
- package/dist/domains/dashboard/web/assets/{chunk-PWAF6VOD-Bo-W1iA1.js → chunk-PWAF6VOD-B_K6Jrsv.js} +1 -1
- package/dist/domains/dashboard/web/assets/{chunk-SHT3W25Y-BhLxs4rZ.js → chunk-SHT3W25Y-CRRLsXmS.js} +1 -1
- package/dist/domains/dashboard/web/assets/{chunk-SVP7TREG-BCXfn8uF.js → chunk-SVP7TREG-Q5zCQTul.js} +1 -1
- package/dist/domains/dashboard/web/assets/{chunk-TICWLB2K-DqSBgE5L.js → chunk-TICWLB2K-Zc5XaO5Z.js} +1 -1
- package/dist/domains/dashboard/web/assets/{chunk-XXDRQBXY-Dbkt1xEZ.js → chunk-XXDRQBXY-BAIB2h_r.js} +1 -1
- package/dist/domains/dashboard/web/assets/classDiagram-ZZMXUADV-DzpQhyL3.js +1 -0
- package/dist/domains/dashboard/web/assets/classDiagram-v2-VYDZK3BY-DzpQhyL3.js +1 -0
- package/dist/domains/dashboard/web/assets/{cose-bilkent-JH36ORCC-DrwNpMyX.js → cose-bilkent-JH36ORCC-C7jkFYhm.js} +1 -1
- package/dist/domains/dashboard/web/assets/{cynefin-OW5HDTMX-BbDlivxs.js → cynefin-OW5HDTMX-4yS-l7kx.js} +1 -1
- package/dist/domains/dashboard/web/assets/{cynefinDiagram-5FMLGOSQ-DmLmRN42.js → cynefinDiagram-5FMLGOSQ-DAkfQ8jW.js} +1 -1
- package/dist/domains/dashboard/web/assets/{dagre-GXQ25YYZ-Cgm5DNgI.js → dagre-GXQ25YYZ-D3b16ruz.js} +1 -1
- package/dist/domains/dashboard/web/assets/{diagram-S7CK7UJ4-Bnht1X2m.js → diagram-S7CK7UJ4-BXZHtdNz.js} +1 -1
- package/dist/domains/dashboard/web/assets/{diagram-UQ7AKVKN-LELTI4PR.js → diagram-UQ7AKVKN-B4nIzofw.js} +1 -1
- package/dist/domains/dashboard/web/assets/{diagram-VSXAHHWV-Do0fZuNG.js → diagram-VSXAHHWV-B6d7KNj1.js} +1 -1
- package/dist/domains/dashboard/web/assets/{diagram-VX7I27RA-B0rZTUwt.js → diagram-VX7I27RA-CHr0Rg8a.js} +1 -1
- package/dist/domains/dashboard/web/assets/{diagram-Z3DM3KII-wn8xCc_j.js → diagram-Z3DM3KII-BO2IxR9N.js} +1 -1
- package/dist/domains/dashboard/web/assets/{dist-CYwDKy2m.js → dist-0wyW4qbm.js} +1 -1
- package/dist/domains/dashboard/web/assets/{ebnfDiagram-PWID7BFC-CMDOpP2T.js → ebnfDiagram-PWID7BFC-CHRK8Hyg.js} +1 -1
- package/dist/domains/dashboard/web/assets/{erDiagram-RLTQ6QDP-C2d43bdq.js → erDiagram-RLTQ6QDP-_HFHzZlc.js} +1 -1
- package/dist/domains/dashboard/web/assets/{es-BzaOcXwu.js → es-kjndkyYX.js} +1 -1
- package/dist/domains/dashboard/web/assets/eventmodeling-NTZA5JFV-CG-cVTEg.js +1 -0
- package/dist/domains/dashboard/web/assets/flowDiagram-HODETNUW-C3RaJz-z.js +1 -0
- package/dist/domains/dashboard/web/assets/{ganttDiagram-EL5Y4UJY-hTH7TzhY.js → ganttDiagram-EL5Y4UJY-CxhSw1PI.js} +1 -1
- package/dist/domains/dashboard/web/assets/{gitGraph-4MIJSDKK-C3CCywb-.js → gitGraph-4MIJSDKK-Cbw-3Dnk.js} +1 -1
- package/dist/domains/dashboard/web/assets/{gitGraphDiagram-WWUBYQGX-DW6jDckj.js → gitGraphDiagram-WWUBYQGX-Cx93hwtL.js} +1 -1
- package/dist/domains/dashboard/web/assets/{index-CTZPz_mx.js → index-CQb8j5OE.js} +3 -3
- package/dist/domains/dashboard/web/assets/{index-CWNqBYyI.css → index-Gaxnq6Jd.css} +1 -1
- package/dist/domains/dashboard/web/assets/{info-A6RAGUB7-Bg3eKis8.js → info-A6RAGUB7--d4EMiIK.js} +1 -1
- package/dist/domains/dashboard/web/assets/{infoDiagram-27XIBGKW-7zk6ytVJ.js → infoDiagram-27XIBGKW-DMkRRNGB.js} +1 -1
- package/dist/domains/dashboard/web/assets/{ishikawaDiagram-5VMMS53U-CGDCTmCQ.js → ishikawaDiagram-5VMMS53U-CjKh_jHT.js} +1 -1
- package/dist/domains/dashboard/web/assets/{journeyDiagram-3NMN7TZE-C8_L_e8a.js → journeyDiagram-3NMN7TZE-CG735M_M.js} +1 -1
- package/dist/domains/dashboard/web/assets/{kanban-definition-UXKFOSKX-D5x6qTgM.js → kanban-definition-UXKFOSKX-CgXFmhFM.js} +1 -1
- package/dist/domains/dashboard/web/assets/{line-DC93oja4.js → line-Bhf8l3gG.js} +1 -1
- package/dist/domains/dashboard/web/assets/{linear-81TNubkB.js → linear-YWT9mnmu.js} +1 -1
- package/dist/domains/dashboard/web/assets/{mermaid-parser.core-D60d8uy9.js → mermaid-parser.core-COzQ1kq0.js} +3 -3
- package/dist/domains/dashboard/web/assets/{mermaid.core-l4Wgjz2Q.js → mermaid.core-Cc1lMpx-.js} +4 -4
- package/dist/domains/dashboard/web/assets/{mindmap-definition-YA3MSWOX-Dfqu1201.js → mindmap-definition-YA3MSWOX-B_VOgUSO.js} +1 -1
- package/dist/domains/dashboard/web/assets/{packet-AYTQ26CC-CsFZBhTs.js → packet-AYTQ26CC-CXbJLNC9.js} +1 -1
- package/dist/domains/dashboard/web/assets/{pegDiagram-XKGWAZYB-myFMaA7n.js → pegDiagram-XKGWAZYB-BuS0hioo.js} +1 -1
- package/dist/domains/dashboard/web/assets/{pie-WAS4IAKB-FMuCTNSk.js → pie-WAS4IAKB-BEaGwdWZ.js} +1 -1
- package/dist/domains/dashboard/web/assets/{pieDiagram-E7YTZNPT-CSR4B4Z1.js → pieDiagram-E7YTZNPT-DDzYv-_9.js} +1 -1
- package/dist/domains/dashboard/web/assets/purify.es-Bvo9QlJ8.js +3 -0
- package/dist/domains/dashboard/web/assets/{quadrantDiagram-AXDQQJYC-BiE4kEeP.js → quadrantDiagram-AXDQQJYC-DExT--Ut.js} +1 -1
- package/dist/domains/dashboard/web/assets/{radar-RG4KPBEZ-BZ-n7JtG.js → radar-RG4KPBEZ-C1JtzGr8.js} +1 -1
- package/dist/domains/dashboard/web/assets/{railroad-74A4TZTK-CWVtRfHu.js → railroad-74A4TZTK-CMpkXATR.js} +1 -1
- package/dist/domains/dashboard/web/assets/railroad-abnf-HS5TGJTU-BM35gYWg.js +1 -0
- package/dist/domains/dashboard/web/assets/railroad-ebnf-LZEXJU2U-CN60GGp0.js +1 -0
- package/dist/domains/dashboard/web/assets/railroad-peg-WCYAUIDC-DRUSW4g7.js +1 -0
- package/dist/domains/dashboard/web/assets/{railroadDiagram-O6MQD6OU-CBj7v1de.js → railroadDiagram-O6MQD6OU-BCE65sLR.js} +1 -1
- package/dist/domains/dashboard/web/assets/{requirementDiagram-BXWQKSXE-DSDgb54n.js → requirementDiagram-BXWQKSXE-CmyX3vGG.js} +1 -1
- package/dist/domains/dashboard/web/assets/{sankeyDiagram-P5KCCOFB-1-oXLUAP.js → sankeyDiagram-P5KCCOFB-BFKrX2dv.js} +1 -1
- package/dist/domains/dashboard/web/assets/{sequenceDiagram-WJ2MYXX4-DAF4nGs_.js → sequenceDiagram-WJ2MYXX4-DqodS9W-.js} +1 -1
- package/dist/domains/dashboard/web/assets/{src-CTWLVUqE.js → src-BVUP3QzK.js} +1 -1
- package/dist/domains/dashboard/web/assets/{stateDiagram-D77RDMKH-DzENBaJT.js → stateDiagram-D77RDMKH-nHai_EZh.js} +1 -1
- package/dist/domains/dashboard/web/assets/stateDiagram-v2-MP3YSRHH-BL6vE1m9.js +1 -0
- package/dist/domains/dashboard/web/assets/{swimlanes-42K2YHIH-CnxFUZJc.js → swimlanes-42K2YHIH-BODBARYN.js} +1 -1
- package/dist/domains/dashboard/web/assets/swimlanesDiagram-VR7AAH4N-XHK_nuTj.js +8 -0
- package/dist/domains/dashboard/web/assets/{timeline-definition-24CTP7MA-KtvPzpZM.js → timeline-definition-24CTP7MA-RVnG8rgK.js} +1 -1
- package/dist/domains/dashboard/web/assets/{treeView-Q6P3EWNA-Bdu3P9iY.js → treeView-Q6P3EWNA-B6lrg3KQ.js} +1 -1
- package/dist/domains/dashboard/web/assets/{treemap-WGGIJYW6-DFnn23JR.js → treemap-WGGIJYW6-CJfMKVf4.js} +1 -1
- package/dist/domains/dashboard/web/assets/{vennDiagram-4TSXK5OY-BjpviP26.js → vennDiagram-4TSXK5OY-CZMWJiN7.js} +1 -1
- package/dist/domains/dashboard/web/assets/{wardley-WFR3VGLG-CEo4a-j4.js → wardley-WFR3VGLG-BoUsbNlx.js} +1 -1
- package/dist/domains/dashboard/web/assets/{wardleyDiagram-VM6X3IG4-Bf54n6im.js → wardleyDiagram-VM6X3IG4-BwBCykVb.js} +1 -1
- package/dist/domains/dashboard/web/assets/{xychartDiagram-S5SC5T6Z-CU-hI0Cm.js → xychartDiagram-S5SC5T6Z-vutnbx57.js} +1 -1
- package/dist/domains/dashboard/web/index.html +2 -2
- package/dist/domains/workflow-contract/hook-target-scope.d.ts.map +1 -1
- package/dist/domains/workflow-contract/hook-target-scope.js +2 -1
- package/dist/domains/workflow-contract/hook-target-scope.js.map +1 -1
- package/dist/platform/paths/git-worktree-cache.d.ts +3 -0
- package/dist/platform/paths/git-worktree-cache.d.ts.map +1 -0
- package/dist/platform/paths/git-worktree-cache.js +109 -0
- package/dist/platform/paths/git-worktree-cache.js.map +1 -0
- package/dist/platform/paths/git-worktree.d.ts +6 -0
- package/dist/platform/paths/git-worktree.d.ts.map +1 -1
- package/dist/platform/paths/git-worktree.js +191 -30
- package/dist/platform/paths/git-worktree.js.map +1 -1
- package/dist/platform/process/comet-daemon.d.ts +3 -0
- package/dist/platform/process/comet-daemon.d.ts.map +1 -1
- package/dist/platform/process/comet-daemon.js +8 -6
- package/dist/platform/process/comet-daemon.js.map +1 -1
- package/dist/platform/process/external-command.d.ts +3 -0
- package/dist/platform/process/external-command.d.ts.map +1 -1
- package/dist/platform/process/external-command.js +69 -2
- package/dist/platform/process/external-command.js.map +1 -1
- package/dist/platform/process/git.d.ts.map +1 -1
- package/dist/platform/process/git.js +3 -4
- package/dist/platform/process/git.js.map +1 -1
- package/dist/platform/process/hook-adapter.d.ts +2 -0
- package/dist/platform/process/hook-adapter.d.ts.map +1 -1
- package/dist/platform/process/hook-adapter.js +32 -3
- package/dist/platform/process/hook-adapter.js.map +1 -1
- package/dist/platform/process/hook-read-cache.d.ts +2 -0
- package/dist/platform/process/hook-read-cache.d.ts.map +1 -1
- package/dist/platform/process/hook-read-cache.js +25 -13
- package/dist/platform/process/hook-read-cache.js.map +1 -1
- package/dist/platform/process/process-identity.d.ts.map +1 -1
- package/dist/platform/process/process-identity.js +18 -51
- package/dist/platform/process/process-identity.js.map +1 -1
- package/dist/platform/process/runtime-metrics.d.ts +10 -1
- package/dist/platform/process/runtime-metrics.d.ts.map +1 -1
- package/dist/platform/process/runtime-metrics.js +37 -2
- package/dist/platform/process/runtime-metrics.js.map +1 -1
- package/dist/platform/process/windows-process-broker.d.ts +1 -0
- package/dist/platform/process/windows-process-broker.d.ts.map +1 -1
- package/dist/platform/process/windows-process-broker.js +70 -11
- package/dist/platform/process/windows-process-broker.js.map +1 -1
- package/dist/platform/process/windows-process-identity.d.ts +6 -0
- package/dist/platform/process/windows-process-identity.d.ts.map +1 -0
- package/dist/platform/process/windows-process-identity.js +190 -0
- package/dist/platform/process/windows-process-identity.js.map +1 -0
- package/package.json +1 -1
- package/dist/domains/dashboard/web/assets/architecture-7GRP2DOG-QeljAKq2.js +0 -1
- package/dist/domains/dashboard/web/assets/channel-_AqwP0KA.js +0 -1
- package/dist/domains/dashboard/web/assets/classDiagram-ZZMXUADV-CRo4aB_7.js +0 -1
- package/dist/domains/dashboard/web/assets/classDiagram-v2-VYDZK3BY-CRo4aB_7.js +0 -1
- package/dist/domains/dashboard/web/assets/eventmodeling-NTZA5JFV-KYANo3DQ.js +0 -1
- package/dist/domains/dashboard/web/assets/flowDiagram-HODETNUW-CSROlLuj.js +0 -1
- package/dist/domains/dashboard/web/assets/purify.es-ChwZkWde.js +0 -3
- package/dist/domains/dashboard/web/assets/railroad-abnf-HS5TGJTU-CkHwwI2i.js +0 -1
- package/dist/domains/dashboard/web/assets/railroad-ebnf-LZEXJU2U-8xzEHL6v.js +0 -1
- package/dist/domains/dashboard/web/assets/railroad-peg-WCYAUIDC-nSHBw0tH.js +0 -1
- package/dist/domains/dashboard/web/assets/stateDiagram-v2-MP3YSRHH-CNw52Fkn.js +0 -1
- package/dist/domains/dashboard/web/assets/swimlanesDiagram-VR7AAH4N-6TRvbqqI.js +0 -8
|
@@ -128,8 +128,6 @@ Do not automatically move an individual batch item from Open to `/comet-design`.
|
|
|
128
128
|
comet state check <name> design --json
|
|
129
129
|
```
|
|
130
130
|
|
|
131
|
-
Combine multiple read-only comet commands (for example `state get`, `state next`, `state artifacts`) into a single shell invocation to reduce process startup overhead.
|
|
132
|
-
|
|
133
131
|
This entry validates the full required closure, actual OpenSpec outputs, and Comet state. Do not repeat a separate status scan. `isComplete` is diagnostic; optional artifacts do not block progress. Query status only after a failed check to locate missing dependencies or diagnose reported path/capability errors.
|
|
134
132
|
|
|
135
133
|
If any split item fails these checks, do not announce batch completion or ask which change to start. Stop further advancement and resume `/comet-open` at that change's first `ready` or `blocked` artifact. If OpenSpec checks pass but Comet state checks fail, repair `.comet.yaml` initialization or phase first, then rerun the batch checks.
|
|
@@ -148,7 +148,7 @@ comet state set <change-name> verify_mode full
|
|
|
148
148
|
|
|
149
149
|
A tweak without delta spec usually meets light conditions (≤ 3 tasks and changed files below the scale threshold). Follow comet-verify's light-verification checklist. If the user wants more review, they can run `comet state set <name> review_mode standard` or `thorough` before verification.
|
|
150
150
|
|
|
151
|
-
After verification
|
|
151
|
+
After verification and its report are complete, `/comet-verify` runs `comet guard <change-name> verify --apply`. Reuse its successful archive state and `agent.continuation`; do not manually set `verify_result: pass` or repeat Guard. If Guard fails, address its reasons without claiming acceptance passed. `/comet-archive` still requires final confirmation before archiving; never run archive automatically.
|
|
152
152
|
|
|
153
153
|
### 4. Archive
|
|
154
154
|
|
|
@@ -27,8 +27,6 @@ comet state select <change-name>
|
|
|
27
27
|
comet state check <change-name> verify --json
|
|
28
28
|
```
|
|
29
29
|
|
|
30
|
-
Combine multiple read-only comet commands (for example `state get`, `state next`, `state artifacts`) into a single shell invocation to reduce process startup overhead.
|
|
31
|
-
|
|
32
30
|
When the previous phase's guard already returned this phase's state, continue from that state and `agent.continuation` without repeating select/check; run the entry checks above only when resuming, after workspace changes, or after external state changes. Continue from the returned layout, configuration, nextAction, task information, and coordination summary. If checks and the integration review remain valid, finish only the missing work instead of rerunning the phase. After context loss, use --recover --details --json when full records are needed. Handle the reported cause of any failure.
|
|
33
31
|
|
|
34
32
|
If select/check returns `BLOCKED` — or a branch-binding `ERROR` — because `bound_branch` differs from the current branch, pause under `comet-classic/reference/decision-point.md`. Offer a single choice: return to the bound branch and rerun entry checks, or, after the user explicitly confirms that the current branch should take over this change, run `comet state rebind <change-name>` and rerun entry checks. Do not switch or rebind branches yourself.
|
|
@@ -28,8 +28,6 @@ comet state select <change-name>
|
|
|
28
28
|
comet state check <name> archive --json
|
|
29
29
|
```
|
|
30
30
|
|
|
31
|
-
多条只读 comet 命令(如 `state get`、`state next`、`state artifacts`)可以合并成一条 shell 调用依次执行,减少进程启动开销。
|
|
32
|
-
|
|
33
31
|
上一阶段 guard 已成功返回本阶段状态信息时,直接使用其中的状态与 `agent.continuation` 继续,不重复 select/check;恢复任务、工作区变化或外部状态变化时,才执行上述入口验证。使用入口返回的 layout、configuration、nextAction 和 delivery 摘要继续。丢失上下文后恢复任务时,按 context-recovery.md 读取所需详情。已有授权仍然有效、交付目标也没有变化时,只继续未完成的动作,不重复询问。失败时,处理返回的具体原因。
|
|
34
32
|
|
|
35
33
|
若上述 `select` / `check` 输出 `BLOCKED` 或分支绑定 `ERROR`,且原因是 `bound_branch` 与当前分支不一致,立即按 `comet-classic/reference/decision-point.md` 暂停,让用户单选:切回绑定分支后重新运行入口验证,或在用户明确确认当前分支应接管该 change 后运行 `comet state rebind <change-name>` 并重新入口验证。不得自行切换分支,不得自行换绑。
|
|
@@ -132,7 +130,7 @@ brainstorming → delta spec → 实施 → 验证 → 主 spec 合并 → desig
|
|
|
132
130
|
- 主 spec 按 delta 语义合并的内容
|
|
133
131
|
- design doc / plan 的归档元数据标注
|
|
134
132
|
|
|
135
|
-
确认 delivery 中的实际授权仍有效,再写入兼容字段并运行最终 archive guard
|
|
133
|
+
确认 delivery 中的实际授权仍有效,再写入兼容字段并运行最终 archive guard(前一条成功后才执行后一条):
|
|
136
134
|
|
|
137
135
|
```bash
|
|
138
136
|
comet state set <change-name> branch_status handled && comet guard <change-name> archive
|
|
@@ -144,10 +142,12 @@ handled 只是兼容旧流程的状态字段,不能表示用户已授权 local
|
|
|
144
142
|
|
|
145
143
|
使用显式 pathspec 暂存核对后的路径,再检查 staged diff;不得使用全仓库暂存,也不得把用户已有改动混入归档提交:
|
|
146
144
|
|
|
145
|
+
提交说明沿用已生效的项目格式、语言和正文要求;已有明确规范时直接准备,无需额外询问。下方消息占位符必须替换为实际说明,不能把示例英文模板当作项目规范。项目 Git Hooks 正常执行;被拒绝时保留暂存内容,修正说明后继续同一次提交。提交调用中断或结果不确定时,先核对实际 Git 记录,不盲目重提,也不绕过 Hook。
|
|
146
|
+
|
|
147
147
|
```bash
|
|
148
148
|
git add -- <逐项核对后的归档路径...>
|
|
149
149
|
git diff --cached --stat
|
|
150
|
-
git commit -m "
|
|
150
|
+
git commit -m "<符合项目规范的归档说明>"
|
|
151
151
|
```
|
|
152
152
|
|
|
153
153
|
提交失败或 staged diff 含无关路径时停止,不得继续分支处理。
|
|
@@ -123,11 +123,11 @@ Build 只做任务或分段审查,Verify 负责唯一最终集成审查:
|
|
|
123
123
|
|
|
124
124
|
已确认范围内、不改变公开行为和验收约束的实现细节调整,只更新实施计划及理由,不重新开启 Open/Design。下面的分级规则仅用于真实规格或范围变化。
|
|
125
125
|
|
|
126
|
-
| 规模 | 触发条件 | 做法
|
|
127
|
-
| ---- | ------------------------------ |
|
|
128
|
-
| 小 | 遗漏验收场景、边界条件 | 直接编辑 delta spec + design.md,追加 tasks.md 任务
|
|
126
|
+
| 规模 | 触发条件 | 做法 |
|
|
127
|
+
| ---- | ------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
|
128
|
+
| 小 | 遗漏验收场景、边界条件 | 直接编辑 delta spec + design.md,追加 tasks.md 任务 |
|
|
129
129
|
| 中 | 接口变更、新增组件、数据流变化 | **按 `comet-classic/reference/decision-point.md` 暂停并等待用户明确确认**,给出「继续按此更新设计」或「调整变更要求」两个选项;未确认不得重开设计。确认后,必须使用 Skill 工具加载 Superpowers `brainstorming` 更新 Design Doc + delta spec |
|
|
130
|
-
| 大 | 全新的功能需求 | **暂停、展示拆分选择并等待用户明确确认**;用户确认后,通过 `/comet-open` 创建独立 change
|
|
130
|
+
| 大 | 全新的功能需求 | **暂停、展示拆分选择并等待用户明确确认**;用户确认后,通过 `/comet-open` 创建独立 change |
|
|
131
131
|
|
|
132
132
|
**范围复核**:新增任务前,先核对原目标、公开行为、验收要求,以及用户已接受的风险。补充原范围内遗漏的实现或验收、调整任务粒度时,直接更新任务并记录依据;任务数量或增长比例本身不触发暂停。只有实际扩大范围、需要重新设计或出现可独立交付的新功能时,才按 `comet-classic/reference/decision-point.md` 暂停,让用户确认继续、调整还是拆分。
|
|
133
133
|
|
|
@@ -191,8 +191,6 @@ Guard 先检查配置、任务和产物,再复用输入与环境相同的 Runt
|
|
|
191
191
|
|
|
192
192
|
**证据录制**:实现完成、相关检查跑绿后,录制 build 证据并立即运行 `comet guard <change-name> build --apply`。Build 阶段只录 build 证据:外部(非 `--local`)verify 检查必须在 guard build --apply **成功之后**再录制——阶段转换会使此前录的外部 verify 证据过期(`crossed a phase boundary`),昂贵的非幂等外部检查会被白跑;`--local` 证据不受此限,可在一条 shell 调用里连续录制。输入未变化时 Runtime 会自动复用已记录的证据,文档编辑后的重跑不会再次执行命令。guard 报告证据失效时会给出确切原因和变化文件清单——只重跑列出的 scope,record-check 遮蔽或 phase 边界的情况按报错信息处理,不要全量重来。提交一律放在 guard 通过之后,勾选 task 用 `comet state task-complete`。
|
|
193
193
|
|
|
194
|
-
多条只读 comet 命令(如 `state get`、`state next`、`status`)合并成一条 shell 调用依次执行,减少每条命令的进程启动开销。
|
|
195
|
-
|
|
196
194
|
退出前运行阶段守卫推进 phase(此步骤与 `auto_transition` 无关):
|
|
197
195
|
|
|
198
196
|
```bash
|
|
@@ -28,7 +28,7 @@ comet state next <name> --json
|
|
|
28
28
|
|
|
29
29
|
## 2. 载入当前阶段
|
|
30
30
|
|
|
31
|
-
|
|
31
|
+
执行同一组任务时,复用本次命令返回的状态信息和已读取的上下文。命令更新状态且响应已提供最新状态与 `agent.continuation` 时,直接继续;只有这些字段缺失、切换工作区、恢复会话时丢失上下文或发现外部变化,才重新查询。根据当前改动的风险选择检查范围,Verify 仍需完成一次覆盖最终实现的集成审查。
|
|
32
32
|
|
|
33
33
|
绑定工作区并取得 phase 后,读取并执行 [任务上下文与产物语言](reference/scripts.md#任务上下文与产物语言),运行 `comet task`。按配置确定产物语言;根据 Context Manifest(上下文清单)中的摘要,只展开当前步骤还缺少的内容。实际使用某条内容后如实记录使用结果,任务结束时保存检查点。
|
|
34
34
|
|
|
@@ -40,6 +40,8 @@ comet classic intent route --stdin
|
|
|
40
40
|
|
|
41
41
|
入口 check --json 会返回 layout、configuration、nextAction、任务摘要、coordination 和 delivery;已经返回的字段不再单独查询。恢复会话时若缺少上下文,先用 --recover 取得恢复摘要;需要全部任务、检查点或证据时才加 --details,具体见 context-recovery.md。
|
|
42
42
|
|
|
43
|
+
只执行当前动作仍缺少的查询。把多条 `comet` 命令放进同一次 shell 调用只减少工具往返,每条 CLI 仍各自启动;要减少重复调用,应复用响应已有字段。存在先后依赖时,上一条成功后再执行下一条,并检查每条退出码;不能用最后一条成功掩盖前面的失败。
|
|
44
|
+
|
|
43
45
|
checkpoint 输入必须包含 schemaVersion:1,以及 taskIds/revision/stage/sessionId/evidence/unresolved/reviewRounds;读取时返回 `{checkpoint, stale}`。Runtime 检查数据后生成 Markdown,JSON 示例见 context-recovery.md。task-complete 会自动同步旧计划中已经建立 comet-task ID 对应关系的任务。需要单独同步时使用 sync-plan;返回 planSync mapping-required 时,只需补齐对应关系,不应重新实施任务。
|
|
44
46
|
|
|
45
47
|
delivery 输入包含 action(local|push|pr)、targetBranch,以及可选的 remote、commit、prUrl,示例见 comet-archive。普通入口和 delivery 读取不会访问网络;只有 `state delivery <change-name> --verify` 会只读核对远端和 PR 状态,并返回 `{delivery, verification}`。记录写入成功不等于交付成功。命令不可用、操作被拒绝或记录不一致时停止,不能手改内部状态来绕过检查。
|
|
@@ -93,7 +95,13 @@ comet check run <change-name> verify --local --incremental -- <program> [args...
|
|
|
93
95
|
{
|
|
94
96
|
"version": 2,
|
|
95
97
|
"commands": [
|
|
96
|
-
{
|
|
98
|
+
{
|
|
99
|
+
"argv": ["pnpm", "build"],
|
|
100
|
+
"cwd": ".",
|
|
101
|
+
"files": ["src/**", "package.json", "tsconfig.json"],
|
|
102
|
+
"outputs": ["dist/**"],
|
|
103
|
+
"git": "all"
|
|
104
|
+
},
|
|
97
105
|
{ "argv": ["vitest", "run"], "cwd": ".", "files": ["src/**", "test/**"] }
|
|
98
106
|
]
|
|
99
107
|
}
|
|
@@ -25,8 +25,6 @@ comet state select <change-name>
|
|
|
25
25
|
comet state check <name> design --json
|
|
26
26
|
```
|
|
27
27
|
|
|
28
|
-
多条只读 comet 命令(如 `state get`、`state next`、`state artifacts`)可以合并成一条 shell 调用依次执行,减少进程启动开销。
|
|
29
|
-
|
|
30
28
|
上一阶段 guard 已成功返回本阶段状态信息时,直接使用其中的状态与 `agent.continuation` 继续,不重复 select/check;恢复任务、工作区变化或外部状态变化时,才执行上述入口验证。验证通过后,使用入口返回的 layout、configuration、nextAction 和协作进度摘要继续,不逐字段查询,也不重复 root show。正常进入本阶段时,只做入口检查;丢失上下文后恢复任务或需要读取详情时,按 context-recovery.md 处理。验证失败时,处理返回的具体原因。
|
|
31
29
|
|
|
32
30
|
**恢复**:先核对现有产物和用户确认记录,只补未完成的步骤。无论正常进入还是恢复任务,都要保留已登记且仍然有效的设计,并读取 `data.designReadiness`、`data.issues` 和 `data.nextAction`。补回缺失文件、纠正文件关联的 change,或更新过期 handoff,不清空 `design_doc`。用户已确认设计后,可以执行返回的 complete-design 动作;该命令会保留已完成的步骤。如果已经进入 Build,则只返回当前阶段的入口信息。
|
|
@@ -66,8 +66,6 @@ comet state select <name>
|
|
|
66
66
|
comet state check <name> open
|
|
67
67
|
```
|
|
68
68
|
|
|
69
|
-
多条只读 comet 命令(如 `state get`、`state next`、`state artifacts`)可以合并成一条 shell 调用依次执行,减少进程启动开销。
|
|
70
|
-
|
|
71
69
|
若上述 `select` / `check` 输出 `BLOCKED` 或分支绑定 `ERROR`,且原因是 `bound_branch` 与当前分支不一致,立即按 `comet-classic/reference/decision-point.md` 暂停,让用户单选:切回绑定分支后重新运行入口验证,或在用户明确确认当前分支应接管该 change 后运行 `comet state rebind <change-name>` 并重新入口验证。不得自行切换分支,不得自行换绑。
|
|
72
70
|
|
|
73
71
|
随后按指引创建精简版产物:
|
|
@@ -155,7 +153,7 @@ comet guard <change-name> build --apply
|
|
|
155
153
|
|
|
156
154
|
无 delta spec 的小范围 hotfix 通常满足轻量验证条件(≤ 3 tasks、改动文件数低于 scale 阈值),按 comet-verify 的轻量验证清单逐项检查;默认 `review_mode: off` 时,不自动安排代码审查。若用户希望增加审查,可在验证前运行 `comet state set <name> review_mode standard` 或 `thorough`。若 hotfix 创建了 delta spec,则根据 comet-verify 的规模评估规则进入完整验证路径。
|
|
157
155
|
|
|
158
|
-
|
|
156
|
+
验证及报告完成后,由 `/comet-verify` 执行 `comet guard <change-name> verify --apply`;复用它成功返回的 archive 状态和 `agent.continuation`,不再手动设置 `verify_result: pass` 或重复运行 Guard。Guard 未通过时按其原因处理,不能宣告验收通过。进入 `/comet-archive` 后仍须完成归档前最终确认,不得自动运行归档脚本。
|
|
159
157
|
|
|
160
158
|
### 5. 归档(预设 archive)
|
|
161
159
|
|
|
@@ -9,6 +9,7 @@ Native 将完整需求、进度和验收结论保存在项目中。Agent 只处
|
|
|
9
9
|
|
|
10
10
|
## 必须遵守的规则
|
|
11
11
|
|
|
12
|
+
- 已确认范围内的实现、文档修复、证据复用和恢复连续推进;只在需要新决定、授权或外部信息时暂停。使用最新 continuation 的命令、模板和任务包,修正输入后沿用当前任务。
|
|
12
13
|
- 以磁盘上的 `.comet/config.yaml`、当前 change、`comet-state.yaml` 和正式文件为准,聊天记忆只作辅助。工作流保存的正式文件中,Agent 只编辑 brief、完整目标 Spec、关联时的 `delta.yaml` 和 `children.yaml`;状态、检查结果、报告、锁和事务由 Runtime 管理。
|
|
13
14
|
- 通过 PATH 中公开的 `comet native` 命令推进,用户不手工执行命令。命令不可用时报告安装不完整并停止;参数以 `comet native <command> --help` 为准。
|
|
14
15
|
- 新建 change 走 CLI 并使用响应路径;拒绝后按信息中的命令或目标修正并重试;自定义 Hook、非 Comet 工作和普通同名文件保持中立。
|
|
@@ -40,11 +41,11 @@ Native 将完整需求、进度和验收结论保存在项目中。Agent 只处
|
|
|
40
41
|
|
|
41
42
|
## Shape
|
|
42
43
|
|
|
43
|
-
Agent 先调查能够查明的事实,只询问会改变用户可见结果、又无法可靠推断的决定。简单问题列出未决项及其依赖关系;多个决定相互影响时才建立决策树。按 `native.clarification_mode` 提问前,先把本轮尚未解决的问题写入 brief。用户确认的结论立即同步到
|
|
44
|
+
Agent 先调查能够查明的事实,只询问会改变用户可见结果、又无法可靠推断的决定。简单问题列出未决项及其依赖关系;多个决定相互影响时才建立决策树。按 `native.clarification_mode` 提问前,先把本轮尚未解决的问题写入 brief。用户确认的结论立即同步到 brief 的相关章节和完整目标规格;未明确回答的部分保持 `[blocking]`。
|
|
44
45
|
|
|
45
46
|
完成标准:需求来源已在用户指定的覆盖边界内完整处理并按用途分类,所有影响结果的决定和假设已处理,没有 `[blocking]`,用户明确确认目标、范围、关键决定、全部验收项和非目标,并且 Runtime 已进入 Build。
|
|
46
47
|
|
|
47
|
-
新建需求或重新确认 Shape 时,Runtime
|
|
48
|
+
新建需求或重新确认 Shape 时,brief 只要求目标、范围、非目标和验收示例四个核心章节;有约束、关键决定、待解决问题或特殊验证要求时再补对应章节。Runtime 同时检查完整目标 Spec 或明确的无产品行为变更理由及正式路径。失败会给出文件和修复动作;补齐后重跑 continuation。后续阶段的旧需求保留进度,回到 Shape 时再检查。
|
|
48
49
|
|
|
49
50
|
## Build ↔ Verify Loop
|
|
50
51
|
|
|
@@ -56,7 +57,7 @@ Builder 提交候选实现后,由 Runtime 执行必要检查,再交给新的
|
|
|
56
57
|
|
|
57
58
|
首次实现前,读取当前 brief、完整目标规格和全部验收项,在已确认的需求范围内修改项目代码和测试。修复时优先处理 Verifier 指出的未通过项、无法验证的原因和失败检查;提交前仍要核对其他已确认行为。`previous_unresolved_ids` 只提示本轮修复重点,下一次正式验收仍覆盖全部验收项。
|
|
58
59
|
|
|
59
|
-
Build、Verify 和 Archive
|
|
60
|
+
Build、Verify 和 Archive 会复查正式文件绑定。新确认的 Shape 按 Markdown 内容绑定,空行和软换行保留确认;正文、结构、代码、链接或验收变化仍须重新确认。Hook 编辑后在下一次实现写入或推进前检查实际内容;旧 Shape 沿用原绑定。文档或报告失效时保留工作并给出修复动作,Hook 未触发也会检查。普通文档默认不作废候选,可用 `native.document_writes: revert` 恢复严格行为;路径范围见[正式产物](reference/artifacts.md#正式产物)。
|
|
60
61
|
|
|
61
62
|
用户 Hook 的共享输出目录可通过 `.comet/config.yaml` 的 `hook.allow_paths` 放行;该配置对 Native 和 Classic 共用,工作流产物目录不在白名单范围。详见[用户 Hook 写入](reference/commands.md#用户-hook-写入)。
|
|
62
63
|
|
|
@@ -74,17 +75,17 @@ Build、Verify 和 Archive 会复查文档绑定。文档漂移或报告过期
|
|
|
74
75
|
|
|
75
76
|
## Verify
|
|
76
77
|
|
|
77
|
-
按 Verify
|
|
78
|
+
按 Verify 协议立即启动新的只读 Verifier,原样传递任务包。派发只代表登记:平台接受启动调用、且 Verifier 回报 `verifier-started` 后,才说明它已运行;启动失败立即按异常流程处理。任务包含验收正文时直接使用,否则按分页读取全部 scopeIds。Verifier 独立判断全部验收项,复用与当前实现、工作区和输入匹配的 Runtime 检查,只补缺失或失效证据;文件和日志正文按需读取。
|
|
78
79
|
|
|
79
|
-
|
|
80
|
+
等待工具超时后,继续等待同一个 Verifier。回执未到且子代理无响应时,先核实启动是否成功;只有平台确认执行失败、超时、任务丢失或结束后无结果时才登记错误。Runtime 接受完整结果后,按最新状态继续。只有用户明确接受结果后才执行 `--accept-result`,仅完成自动检查的结果也须明确接受。隔离工作区可在同一回复中接受结果并选择交付方式,执行带 `--finish` 的备选命令;用户未选择时再询问。
|
|
80
81
|
|
|
81
82
|
完成标准:Runtime 接受每项验收结论并给出下一步;返回 Build 就继续修复,返回等待或阻塞就处理对应条件,不把阶段结束当任务完成。
|
|
82
83
|
|
|
83
84
|
## Archive
|
|
84
85
|
|
|
85
|
-
`continuation` 允许 Archive 时,必须先读[Archive 收尾](reference/workspace.md#archive-收尾)
|
|
86
|
+
`continuation` 允许 Archive 时,必须先读[Archive 收尾](reference/workspace.md#archive-收尾),使用已接受的验收结果,执行最新 continuation。用户明确选择收尾方式后,可执行对应的 `--confirmed --finish` 完整命令,由 Runtime 完成预检和事务内复查;返回 dry-run 时先运行预览,`ready: true` 后执行返回的唯一 confirmed 命令。只处理同一响应列出的阻塞。
|
|
86
87
|
|
|
87
|
-
只提交本 change 的实现和正式产物,保留无关修改。检查 `workspaceFinishResult`,阻塞时按 `recoveryArgs`
|
|
88
|
+
只提交本 change 的实现和正式产物,保留无关修改。检查 `workspaceFinishResult`,阻塞时按 `recoveryArgs` 保留现场并恢复。已有授权足以处理的提交说明和本地阻塞由 Agent 修复后继续,不要求用户再次说“重试”;需要新增授权或外部信息时才询问。
|
|
88
89
|
|
|
89
90
|
完成标准:状态为 `done`,用户授权的工作区收尾为 `completed` 或 `kept`,并按记忆接入协议记录任务完成;其他结果继续处理。
|
|
90
91
|
|
|
@@ -31,25 +31,25 @@ Runtime 的本机数据固定保存在被 Git 忽略的 `.comet/runtime/native/`
|
|
|
31
31
|
|
|
32
32
|
Shape、Build、Verify 和 Archive 会复查正式文件与已确认需求的绑定。目标规格必须位于 `specs/<capability>/spec.md`;`specs/` 下的其他文件不会被当作正式 Spec,Hook 会拒绝并提示正确位置。空文档、只有标题或围栏、以及只含模板占位(如 `TODO`、`<TODO>`、`{{reason}}`)的内容都不能满足完整规格。无产品行为变更豁免也必须写具体理由,注释和占位理由不算。Archive 预检若只报告 `verification.md` 缺失、过期或无效,`continuation` 会直接给出 `comet native doctor <change> --repair`;完成后重新运行 dry-run。
|
|
33
33
|
|
|
34
|
+
Shape、Verify 和 Archive 中的普通文档写入默认保持当前阶段和候选:范围为仓库根目录及 `docs/`、`doc/`、`documentation/`、`.github/` 下的 Markdown/text 和 LICENSE 类文件,且必须位于 Native 产物根目录之外。在 `.comet/config.yaml` 设置 `native.document_writes: revert` 可恢复严格行为。正式需求文件始终按上面的绑定规则检查。
|
|
35
|
+
|
|
34
36
|
`.comet/config.yaml` 决定使用哪种工作流,以及 change 产物保存在哪个目录。使用非默认产物目录并需要跨设备恢复时,应同步该文件;其余 `.comet/*` 只保留在本机。
|
|
35
37
|
|
|
36
38
|
Runtime 返回的 `artifacts` 是当前工作区的唯一位置依据:`briefPath`、`childrenPath`、`specsDir` 和 `statePath` 都位于配置解析出的 `<artifact-root>/comet/changes/<change-name>/`,本机 `runtimeDir` 仍位于项目 `.comet/runtime/native/`。不要用 `.comet/comet/` 或其他目录中的同名文件替代缺失产物;若 Hook 指出路径错误,按拒绝信息给出的正确绝对路径重试原编辑,保留已有内容并先读取合并。
|
|
37
39
|
|
|
38
40
|
### Brief
|
|
39
41
|
|
|
40
|
-
`brief.md` 保存 Native
|
|
42
|
+
`brief.md` 保存 Native 的需求澄清记录,使用以下四个核心一级标题,各节内容不能为空:
|
|
41
43
|
|
|
42
44
|
```text
|
|
43
45
|
# Outcome
|
|
44
46
|
# Scope
|
|
45
47
|
# Non-goals
|
|
46
48
|
# Acceptance examples
|
|
47
|
-
# Constraints and invariants
|
|
48
|
-
# Decisions
|
|
49
|
-
# Open questions
|
|
50
|
-
# Verification expectations
|
|
51
49
|
```
|
|
52
50
|
|
|
51
|
+
有实际约束、关键决定、未决问题或特殊检查要求时,再补 `Constraints and invariants`、`Decisions`、`Open questions` 或 `Verification expectations` 章节。已有章节必须填写真实内容;简单任务无需补写“无”来满足模板。用户决定可记录在相关核心章节;需要追踪多个决定时使用 Decisions。
|
|
52
|
+
|
|
53
53
|
Open questions 中只有真实未解决的用户问题使用:
|
|
54
54
|
|
|
55
55
|
```text
|
|
@@ -57,9 +57,9 @@ Open questions 中只有真实未解决的用户问题使用:
|
|
|
57
57
|
- [blocking] Q1: <Batch 问题>
|
|
58
58
|
```
|
|
59
59
|
|
|
60
|
-
用户确认每个决定后,立即将结论写入
|
|
60
|
+
用户确认每个决定后,立即将结论写入 brief 的相关章节和完整目标规格,再移除对应阻塞项。Runtime 会保存最终 Shape 的确认摘要,并通过 `await-user` 等待用户确认;不在 brief 中另加一条确认问题。正式文件只记录结论和理由,不记录模型的隐藏推理过程。按[源文档完整覆盖](#源文档完整覆盖)记录需求来源与 Spec、验收项的对应关系。
|
|
61
61
|
|
|
62
|
-
验收标准必须具体,结果能够验证,各项互不重复。Runtime 只从 brief 顶层的验收示例和 Spec 中明确以 `Scenario:` 标出的完整场景生成验收项;说明段落、普通列表和单独的 WHEN/THEN 行不能拆成额外验收项。验收 ID 按顺序编号,例如 `A1`、`A2`、`A3`;ID 用于把验收结果对应到验收项,不根据内容计算,也不用于标识文件。Runtime 在 Shape 确认时保存完整验收文字及其来源。
|
|
62
|
+
验收标准必须具体,结果能够验证,各项互不重复。Runtime 只从 brief 顶层的验收示例和 Spec 中明确以 `Scenario:` 标出的完整场景生成验收项;说明段落、普通列表和单独的 WHEN/THEN 行不能拆成额外验收项。验收 ID 按顺序编号,例如 `A1`、`A2`、`A3`;ID 用于把验收结果对应到验收项,不根据内容计算,也不用于标识文件。Runtime 在 Shape 确认时保存完整验收文字及其来源。Spec 场景与 brief 已有验收项对应时,在场景正文单独写 `Acceptance: A1`(中文可用 `验收:A1`),引用当前 brief 的真实 ID,不再生成重复验收项。一个场景只能引用一个 ID;新的行为仍写成独立场景。引用只合并验收身份,完整 Spec 仍绑定确认且必须由 Verifier 核对。
|
|
63
63
|
|
|
64
64
|
新版 `children.yaml` 使用 `comet.native.children.v2`:
|
|
65
65
|
|
|
@@ -62,7 +62,7 @@ Batch 使用文本提问时,保留 `Q1`、`Q2` 编号,每题使用独立的
|
|
|
62
62
|
1. 调查当前问题依赖的事实,只暂停前置条件尚未确定的分支。
|
|
63
63
|
2. 从当前可以提出的问题中选择一个,先在 brief 的 `# Open questions` 保存 `- [blocking] <问题>`。
|
|
64
64
|
3. 一次只提出这一个问题,给出问题、推荐及理由、各选项影响,然后等待回答。
|
|
65
|
-
4. 用户回答后,立即把已确定的决定写入
|
|
65
|
+
4. 用户回答后,立即把已确定的决定写入 brief 的相关章节和完整目标规格,再移除已解决的阻塞项;补充答案写入同一个 change。
|
|
66
66
|
5. 更新问题之间的依赖关系,重新确定下一轮可以提出的问题,再开始下一轮。
|
|
67
67
|
|
|
68
68
|
#### Batch 模式
|
|
@@ -70,7 +70,7 @@ Batch 使用文本提问时,保留 `Q1`、`Q2` 编号,每题使用独立的
|
|
|
70
70
|
1. 列出本轮可以一起提出的全部问题:前置事实和决定已经确定,答案彼此独立。每个独立决定保留为单独问题。
|
|
71
71
|
2. 提问前,在 brief 的 `# Open questions` 为本轮全部问题保存 `- [blocking] Q1: <问题>`、`- [blocking] Q2: <问题>` 等稳定标识;后续轮次不把已有标识改用于其他问题。
|
|
72
72
|
3. 一次提出本轮全部问题,每题分别给出问题、推荐及理由和影响,然后等待回答;不能因为工具限制而分批提出本轮问题。
|
|
73
|
-
4. 用户回答后,逐项更新
|
|
73
|
+
4. 用户回答后,逐项更新 brief 的相关章节和完整目标规格,移除已解决项;部分、模糊或未回答的问题保留原标识及 `[blocking]`。
|
|
74
74
|
5. 更新已回答和未回答问题及其依赖,再确定下一轮需要一起提出的全部问题。
|
|
75
75
|
|
|
76
76
|
两种模式都在当前没有可提问项时,继续调查尚未查明的事实,并检查是否遗漏其他情况。当前列表为空不代表澄清完成;最终确认仍需满足下一节的全部完成条件。
|
|
@@ -103,9 +103,9 @@ Batch 使用文本提问时,保留 `Q1`、`Q2` 编号,每题使用独立的
|
|
|
103
103
|
|
|
104
104
|
用户已经明确要求“多个会话”“独立会话”“跨会话协作”或“Agent Team”时,视为选择 A,不重复询问推进方式。确认前不得创建子 change、worktree、Codex 独立会话、Claude Code Agent Team 或分配任务。
|
|
105
105
|
|
|
106
|
-
当最终 Shape
|
|
106
|
+
当最终 Shape 包含两个或更多 Child 时,在 Decisions 中记录 Supervisor Change 和各 Child,先按 continuation 执行 `prepare-shape-confirmation`,由 Runtime 绑定完整 Shape 和子任务方案。展示保存的完整摘要、拆分方案及 A、B 两种方式后,用户可一次回复明确确认方案并选择推进方式,再执行对应的 `--confirmed` 完整备选命令。不得把普通“确认”视为已选择,也不得把仅选择方式视为确认方案。仍可先选择方式再准备确认;仅先选择方式时,用户仍需再次明确确认完整 Shape。正式产物或子任务变化后重新准备并确认,不沿用旧授权。
|
|
107
107
|
|
|
108
|
-
Runtime
|
|
108
|
+
Runtime 把已选择的推进方式写入 `comet-state.yaml` 的 `coordination_mode`;完整 Shape 与推进方式都得到明确确认后,Runtime 才进入 Build,为 Supervisor Change 创建独立的集成分支和 worktree,并基于集成分支的当前提交,为每个子任务生成包含角色、worktree、基线提交和 `runId` 的任务包。推进方式不写入 `children.yaml`,也不改变 Runtime 的 `readyChildren`、`runId`、验收或集成规则。Skill 只启动 `readyChildren` 中列出的当前可执行子任务;选择 A 时最多同时启动两个不依赖其他子任务的任务,选择 B 时按顺序执行。每个子任务都必须属于 Supervisor Change 已确认的需求范围;出现会改变用户可见结果的新决定时,回到 Supervisor Change 的 Shape。
|
|
109
109
|
|
|
110
110
|
恢复 `/comet-native` 时以 Runtime 已保存的 `coordination_mode` 为准,不重复创建已有子任务或 worktree,也不再询问推进方式。`multi-session` 继续使用多会话协作;独立会话或 Agent Team 不可用时自动改用 subagent;`single-session` 继续由当前会话按顺序推进。原来的 Codex 独立会话或 Claude Code Agent Team 已经不存在时,先重新读取 Runtime 状态;不得根据旧会话或旧团队的状态推断子任务已经完成,也不得自动改为单会话推进。
|
|
111
111
|
|
|
@@ -63,7 +63,7 @@ Native 正式产物只能由 `comet native new <name> --json` 登记后创建。
|
|
|
63
63
|
|
|
64
64
|
首次填写 Runtime 模板或通过 `returnAction` 回传结果前必须读取本节。
|
|
65
65
|
|
|
66
|
-
把 `inputOptions.template` 复制到系统临时 JSON 文件,只替换模板要求填写的内容,然后执行 `continuation.commandArgs` 或所选 `commandAlternative.commandArgs
|
|
66
|
+
把 `inputOptions.template` 复制到系统临时 JSON 文件,只替换模板要求填写的内容,然后执行 `continuation.commandArgs` 或所选 `commandAlternative.commandArgs`。Runtime 接受输入后删除临时文件;输入被拒绝时保留原文件,按错误修正后重提。模板中已有的验收轮次、Verifier 尝试次数、状态版本和任务标识都原样保留;只填写模板公开的字段。
|
|
67
67
|
|
|
68
68
|
`inputOptions` 中同一 `exclusiveGroup` 的选项互斥:选择其中一个,将它的 `template` 作为单个 JSON 对象填入临时文件。字段校验失败时,按 `error.issues` 指出的 JSON 路径、缺失字段和未知字段修正原文件。
|
|
69
69
|
|
|
@@ -79,7 +79,9 @@ Supervisor 子任务在任务包指定的 `projectRoot` 工作。回传结果时
|
|
|
79
79
|
|
|
80
80
|
Builder 的交接摘要必须写明本轮修改、处理的验收项、实际运行和未运行的开发期检查,以及已知限制。前面的复核不能替代正式 Verifier;正式 Verifier 仍须独立检查全部验收项。
|
|
81
81
|
|
|
82
|
-
|
|
82
|
+
交接前逐项核对当前 brief、完整目标 Spec 和所有已确认验收 ID,按 Runtime 模板填写 `acceptance_review`;每个 ID 恰好一项。`id` 沿用模板,`status` 如实填写,`evidence` 列出具体文件位置、检查记录或可复核的观察,`note` 说明实现如何满足该项。只有全部为 `implemented-with-evidence` 且每项证据非空时才提交。`implemented-no-evidence`、`not-implemented`、`known-fail` 对应尚缺证据、尚未实现和已知失败,先据此补齐剩余工作,不把未完成候选交给 Verifier 试探反馈。修复模板会保留未受影响项的上轮证据,受影响项提示补充本轮证据;提交前核对每项证据仍适用,并更新失效内容。预填内容不是新的检查结果。自查不代表独立验收通过。
|
|
83
|
+
|
|
84
|
+
开发期只跑定向检查;最终检查计划填入 `builder-handoff.verification_checks`,不要先运行同一完整计划。Runtime 冻结候选后执行:通过则直接返回 `verifierDispatch` 任务包,立即交给新的只读 Verifier;失败或不可重复检查中断则返回 Build;可重复检查中断只按 `retry-checks` 重试。`runtimeCheckExecution.disposition` 区分执行与复用。
|
|
83
85
|
|
|
84
86
|
`verification_checks` 只放 Runtime 能在当前候选上安全管理的命令。外部服务和一次性操作仍由 Verifier 按原约束判断。`builder-handoff.checks` 只记录开发期检查,不是正式证据。
|
|
85
87
|
|
|
@@ -102,22 +104,22 @@ Builder 的交接摘要必须写明本轮修改、处理的验收项、实际运
|
|
|
102
104
|
- `changeDir`:解析 `briefRef` 和 `specRefs[].ref` 相对路径时使用的基准目录。
|
|
103
105
|
- `supervisorStateRef`:包含子任务验收与集成记录的本机状态文件;普通 change 为 `null`。
|
|
104
106
|
|
|
105
|
-
|
|
107
|
+
原样传递可选的 `recoveryContext`。有 `acceptance` 时直接读取全部正文;否则按 `detailsPageArgs` 和后续分页读完 `scopeIds`,保留 `--project-root`。实际启动的 Verifier 复制 `startupInput` 提交回执。追加检查后,把 Runtime 的检查结果和交接交回当前 Verifier,继续等待。
|
|
106
108
|
|
|
107
109
|
Runtime 要求启动 Verifier(`dispatch-verifier`)时,按以下步骤执行:
|
|
108
110
|
|
|
109
|
-
1.
|
|
111
|
+
1. 最终计划随 handoff 的 `verification_checks` 提交,直接使用返回任务包;未提供计划的旧 handoff 才填写 dispatch 模板。证据绑定未变时 `runtimeCheckExecution.disposition=reused`,否则执行检查;Builder 日志不是 Runtime 证据。
|
|
110
112
|
2. 检查中断后,只有最新 `continuation` 返回 `retry-checks` 时,才重试其中指定的可重复检查。断言失败或不允许重复执行的检查,不能当作环境故障自动重跑。
|
|
111
|
-
3. 读取 `verifierDispatch`
|
|
113
|
+
3. 读取 `verifierDispatch` 的工作区、检查记录、`scopeIds`、`scopeCount`、brief/Spec 引用、复核摘要和检查结果;验收正文按上述规则读取。`builderSummary` 是独立核查后参考的交接摘要。
|
|
112
114
|
4. 立即使用当前平台的原生能力,启动一个新的只读 Verifier subagent,原样传递工作目录、检查记录位置和 `recoveryContext`(如果存在)。启动调用被平台拒绝或返回错误时,立即按 `verifier-execution-error` 处理;只有平台接受了这次启动,派发才算完成。subagent 不可用时,只有用户选择了多会话协作、且平台能管理独立会话,才可以启动与 Builder 分开的独立 Agent 会话。其他情况按命令参考报告 Verifier 不可用,并执行最新 `continuation`。
|
|
113
115
|
|
|
114
116
|
`dispatch-verifier` 只登记本次验收,并返回任务包和 attempt 标识;它不会启动独立服务或进程,也不需要配置服务地址或回调。Verifier 返回结果时,必须原样带回本次任务包中的 `candidateId` 和 `verifierExecutionRef`。Runtime 会拒绝旧实现版本或旧 Verifier 任务的迟到结果。
|
|
115
117
|
|
|
116
|
-
|
|
118
|
+
按 Runtime 根据 `localExecution.verifierStartup` 返回的指引继续:`unconfirmed` 时核实平台是否接受启动,找回原任务;尚未调用启动工具才启动,已接受则继续等待。`confirmed` 表示 Verifier 已回报启动或补充检查,等待同一个 Verifier。回执未到或等待工具超时本身不算执行失败;只有下文异常条件成立才登记错误,不重复派发。
|
|
117
119
|
|
|
118
120
|
### 独立验收与结果
|
|
119
121
|
|
|
120
|
-
Verifier
|
|
122
|
+
Verifier 全程只读,先提交任务包的 `startupInput`(`verifier-started`,重复无副作用)。读取当前 scope 的全部验收文字、brief、完整目标 Spec、实现和 Runtime 检查结果,核对版本、工作区、输入及覆盖范围。只在 `inputOptions.template` 中补充缺失或失效的检查,由 Runtime 执行;独立判断 `scopeIds` 中每项。
|
|
121
123
|
|
|
122
124
|
Verifier 最后再阅读 Builder 交接,将其作为调查线索。Builder 只提供本轮实现的位置、验收项的编号与引用、检查记录位置、已知限制和相关文件位置;日志正文按需读取。
|
|
123
125
|
|
|
@@ -125,6 +127,8 @@ Verifier 最后再阅读 Builder 交接,将其作为调查线索。Builder 只
|
|
|
125
127
|
|
|
126
128
|
通过 `verifier-response` 提交结果时,响应只列出当前 `scopeIds`,每项恰好标记一次为 `passed`、`failed` 或 `blocked`;后两种情况写明原因。已通过且仍报告通过的合法超集会由 Runtime 过滤;不存在或重复的 ID、缺少当前 scope,以及 scope 外的 `failed` 或 `blocked` 仍会被拒绝。
|
|
127
129
|
|
|
130
|
+
结果或检查请求因字段、格式或验收范围被拒绝时,按错误修正原输入,并使用返回的当前 `continuation` 重提;仍在运行的 Verifier 继续使用,不登记 `verifier-execution-error` 或重新派发。候选或执行绑定不匹配时先核对派发身份,旧任务的结果不能改成新任务身份后重提。实际检查执行失败、平台任务失败等情况,仍按对应失败路径处理。
|
|
131
|
+
|
|
128
132
|
提交修复后的实现时,Runtime 会保留仍然有效的检查回执,并让新的正式 Verifier 在一轮内检查全部验收场景。全部通过后,直接等待用户接受验收结果;不会自动清空结果,再追加一轮相同的完整验收。
|
|
129
133
|
|
|
130
134
|
Verifier 无法完成任务时,区分以下情况:
|
|
@@ -141,6 +145,8 @@ Verifier 无法完成任务时,区分以下情况:
|
|
|
141
145
|
|
|
142
146
|
- `retry-checks`:只重试本轮实现中由 Runtime 标记为中断、且允许重复执行的检查。复制最新 `continuation` 的 `check_ids`,不要替换检查命令或待验收的实现。每项检查最多执行三次,成功结果和有效日志会保留。
|
|
143
147
|
|
|
148
|
+
Verifier 明确请求重跑失败检查时,使用当前 `request-checks` 模板提交原检查计划;只有允许重复执行、候选和执行身份仍匹配、且未达到现有限额的检查才能重跑。已通过且仍有效的结果由 Runtime 复用。断言失败不会被当作通过,也不会自动循环重跑;不可重复操作先处理其阻塞条件。
|
|
149
|
+
|
|
144
150
|
完成标准:Runtime 已接受完整的 Verifier 结果,并明确进入 Build、Archive、等待用户(`await-user`)、阻塞(`blocked`)或完成(`done`)中的一种状态。
|
|
145
151
|
|
|
146
152
|
## Supervisor 协作
|
|
@@ -192,7 +198,7 @@ Runtime 可以校验已保存检查记录的内容,以及它对应的实现版
|
|
|
192
198
|
|
|
193
199
|
## 命令输入与异常
|
|
194
200
|
|
|
195
|
-
正常流程直接执行 Runtime 在 `continuation`
|
|
201
|
+
正常流程直接执行 Runtime 在 `continuation` 中给出的命令。恢复时未提交动作输入的 `next --summary` 会返回当前模板并保留阶段,直接填写该模板继续,无需再查询一次 status。本节解释返回字段,并说明如何处理以下情况:命令输入被拒绝、无法启动 Verifier、Verifier 任务执行出错、Verifier 因缺少外部信息无法判断,或 Runtime 要求用户决定是否接受未完成独立验收的结果。`continuation.disposition` 说明现在应继续、等待用户、处理阻塞还是结束。只有用户明确确认后,才执行含 `--confirmed` 的后续命令。CLI 文本先给出用户可读的 `summary`、唯一 `NEXT:` 和可选的 `RELAY TO USER:`;用 `--json` 读取结构化响应,`--verbose` 仅用于排查本机执行状态。
|
|
196
202
|
|
|
197
203
|
命令签名和当前参数始终以 CLI 为准:
|
|
198
204
|
|
|
@@ -204,7 +210,7 @@ comet native <group> <command> --help
|
|
|
204
210
|
|
|
205
211
|
### Runtime 返回的下一步
|
|
206
212
|
|
|
207
|
-
- `disposition`:说明现在应该继续、等待用户、处理阻塞还是结束;`
|
|
213
|
+
- `disposition`:说明现在应该继续、等待用户、处理阻塞还是结束;`requiresUserDecision` 为 true 时转述消息并等待决定;`userCommunication.required` 也可能只是要求通知恢复进展,此时按已有授权继续;
|
|
208
214
|
- `commandArgs` / `commandAlternatives`:Runtime 要求执行的完整命令参数;每个备选操作对应一个互斥的用户决定,选择匹配项执行,不要合并多个备选操作;
|
|
209
215
|
- `inputOptions`:这次命令需要填写的字段和 JSON 模板;
|
|
210
216
|
- `workspace` / `preparation`:实际工作目录和 change 创建结果;
|
|
@@ -213,7 +219,7 @@ comet native <group> <command> --help
|
|
|
213
219
|
- `verifierDispatch`:启动独立 Verifier 所需的工作区与证据位置、当前 `scopeIds`、`scopeCount`、全部验收项数量、正文引用、详情分页参数、复核摘要和检查结果;如果存在 `recoveryContext`,也要把它作为最近一次恢复或用户补充的信息直接传给 Verifier;
|
|
214
220
|
- `workspaceFinishResult` / `recoveryArgs`:归档后的工作区收尾结果和恢复命令。
|
|
215
221
|
|
|
216
|
-
Archive-ready
|
|
222
|
+
Archive-ready 时执行最新 continuation。使用隔离工作区、且尚未选择收尾方式(finish)时,等待用户选择,然后执行对应的 `--confirmed --finish` 完整备选命令,保留状态版本参数;Runtime 记录选择并完成预检和事务内复验。用户在接受结果时已选择 finish 的,沿用该选择,不再询问。需要预览自定义提交说明时可先 dry-run;不要自行补其他参数。dry-run 会同时检查归档内容和 Git 收尾涉及的分支及文件;`ready: false` 时在同一响应中处理 `blockers` 和 `workspaceFinishBlockers[].paths` 的完整路径清单,不要额外运行 `status` 或手工提交 change 的状态/verification 文件。只有 `ready: true` 才执行返回的唯一 `archive --confirmed` 命令。
|
|
217
223
|
|
|
218
224
|
模板中的尖括号表示需要填写的值。`await-user` 表示先等待用户决定,此时不执行推进命令。若 `commandArgs` 为 `null` 且返回了 `commandAlternatives`,先确认用户决定,再执行对应备选操作的完整 `commandArgs`,保留其中的 `--expected-state-version` 和 `--expected-action`。命令因状态过期或动作不匹配失败时,重新读取最新 `continuation`,按当前状态继续;不要自行拼接缺少状态校验参数的命令。`localExecution: absent` 只表示这台机器当前没有正在运行的执行任务,不代表 change 已损坏。
|
|
219
225
|
|
|
@@ -12,7 +12,7 @@
|
|
|
12
12
|
|
|
13
13
|
## 故障恢复
|
|
14
14
|
|
|
15
|
-
|
|
15
|
+
命令已返回具体错误、当前状态和恢复动作时,先按该响应处理。Runner 输入校验失败按[填写命令输入](commands.md#填写命令输入)修正,归档提交或合并失败按[Archive 收尾](workspace.md#archive-收尾)继续,仍在运行的任务保持原标识。没有当前状态、调用中断或现场与响应不一致时,先停止依赖该状态的修改,运行一次 `status --details --json`;状态或恢复记录仍无法解释问题时,再运行只读 `doctor`。只执行 `continuation` 或 `doctor` 明确返回的恢复动作。跨设备状态、本机执行状态、锁和事务始终由 Runtime 管理;无法确定自动恢复是否安全时,保留现场并等待用户决定。
|
|
16
16
|
|
|
17
17
|
仅等待外部输入时,按[等待外部输入与监控](#等待外部输入与监控)处理,独立工作继续。恢复后重新分配 Supervisor 任务前,必须读取[Supervisor 协作](commands.md#supervisor-协作);重新启动 Verifier 前,必须读取[Verify 协议](commands.md#verify-协议),核对当前任务标识、待验收的实现版本和执行状态。
|
|
18
18
|
|
|
@@ -31,8 +31,8 @@ Runtime 出现故障时,先停止修改项目,再重新运行 `status --deta
|
|
|
31
31
|
- Verify(`verify-ready`):重新运行当前实现所需的检查,并启动新的 Verifier;不沿用旧设备上的通过结果。
|
|
32
32
|
- Archive(`archive-ready`):先安全返回 Verify,把验收结果重置为待检查(`pending`),再验收已经同步到新设备的实现。
|
|
33
33
|
- 等待用户或阻塞(`await-user` / `blocked`):恢复原来的阻塞原因、负责处理的人和允许动作,等待对应条件满足后再继续。
|
|
34
|
-
- active 目录中的 `done
|
|
35
|
-
- archive 目录中的 `done
|
|
34
|
+
- active 目录中的 `done`:只按 Runtime 返回的动作完成目录移动与清理;尚有 Git 收尾时,按[Archive 收尾](workspace.md#archive-收尾)继续。
|
|
35
|
+
- archive 目录中的 `done`:先核对公开状态中的工作区收尾结果。所选收尾已完成或保留时只读展示;仍报告未完成或 `blocked` 时,按[Archive 收尾](workspace.md#archive-收尾)继续。
|
|
36
36
|
|
|
37
37
|
旧任务的进程、日志连接和 Agent 会话都视为已经丢失,不能根据残留文件猜测它们是否成功。检查已经结束、但 YAML 尚未记录结果时,只能重跑可以安全重复的检查;可能重复产生外部影响的操作,需要等待用户决定。
|
|
38
38
|
|
|
@@ -32,7 +32,7 @@ Supervisor Change 中由 `readyChildren` 返回的子任务固定使用独立 `w
|
|
|
32
32
|
|
|
33
33
|
## Archive 收尾
|
|
34
34
|
|
|
35
|
-
只有 `continuation` 允许 Archive
|
|
35
|
+
只有 `continuation` 允许 Archive 时才继续。归档直接使用已接受的验收结果。用户接受结果时已经选择了收尾方式的,沿用该选择,不再次询问。使用 `current` 工作区时,不需要选择收尾方式:展示当前分支和目录,说明不会执行 merge、push 或创建 PR,再按最新 `continuation` 继续。
|
|
36
36
|
|
|
37
37
|
使用 `branch` 或 `worktree`、且需要选择收尾方式时,一次展示实际 change 分支、目标分支和目录,用单选题提供以下全部选项。文本提问必须使用下表;结构化提问必须将“方式”作为短标签、“实际影响”作为说明,不得只显示 `merge`、`push`、`pull-request` 或 `keep`。
|
|
38
38
|
|
|
@@ -46,15 +46,21 @@ Supervisor Change 中由 `readyChildren` 返回的子任务固定使用独立 `w
|
|
|
46
46
|
|
|
47
47
|
用户选择 A、B、C 或 D 后,分别按 `keep`、`merge`、`push` 或 `pull-request` 执行 Runtime 返回的完整命令;选择 E 后停止。Archive-ready 时按以下顺序操作:
|
|
48
48
|
|
|
49
|
-
|
|
49
|
+
归档前沿用已生效的项目提交规范,准备归档提交说明;选择本地合并时也准备合并说明。格式、语言和正文要求已有明确规范时直接采用,无需再次询问;存在冲突或缺少必须由用户提供的信息时,只询问缺失内容。通过公开的 `--commit-message <text>` 传入归档说明,`--merge-message <text>` 仅用于 merge。中文和多行正文须作为一个完整参数传入。没有项目约定或用户要求时可沿用默认说明,项目 Git Hooks 始终正常执行。
|
|
50
|
+
|
|
51
|
+
1. 执行最新 continuation。隔离工作区尚未选择 finish 时,等待用户选择后执行对应的 `--confirmed --finish` 完整备选命令,保留状态版本参数;Runtime 一次完成预检和事务内复查。需要预览自定义说明时,执行 `archive --dry-run --finish` 并补入上述消息参数,选择 merge 时同时核对合并说明。除公开消息参数外,保留 Runtime 给出的工作区、确认和串行归档参数,不自行增删。
|
|
50
52
|
2. dry-run 返回 `ready: false` 时,只处理同一响应列出的阻塞。不要先额外运行 `status`、重复 Archive,或手工提交 Native 的状态和 verification 文件。
|
|
51
|
-
3.
|
|
53
|
+
3. dry-run 返回 `ready: true` 后,核对 `commitMessages` 与已准备的说明一致,执行它返回的唯一 `archive --confirmed` 命令,完整保留消息内容;不再重跑相同预览或重新拼接说明。
|
|
52
54
|
4. dry-run 或 confirmed 失败时,只按最新结构化 `continuation` 和 `workspaceFinishResult.recoveryArgs` 继续,不从错误文本猜测下一步。
|
|
53
55
|
|
|
54
56
|
选择 A 表示保留当前分支和目录,同一次归档不得删除该 worktree。其他普通 change 归档后,如果该 change 的 worktree 已没有未提交修改,向用户提供清理选项;Runtime 已清理的无需再次询问。只有用户确认后才执行 `git worktree remove`,存在未提交修改或仍在使用的 worktree 必须保留。
|
|
55
57
|
|
|
56
58
|
Supervisor 最终交付后,Runtime 只自动清理没有未提交修改、且不再使用的子任务 worktree、集成 worktree 及其分支。发现未提交文件、当前进程仍在其中或 Git 步骤未完成时,保留现场并返回阻塞原因,绝不强制删除。
|
|
57
59
|
|
|
58
|
-
只提交属于当前 change 的实现和正式文件,保留其他用户改动。执行 Runtime 返回的 `commandArgs` 后,检查工作区收尾结果 `workspaceFinishResult`。结果为阻塞(`blocked
|
|
60
|
+
只提交属于当前 change 的实现和正式文件,保留其他用户改动。执行 Runtime 返回的 `commandArgs` 后,检查工作区收尾结果 `workspaceFinishResult`。结果为阻塞(`blocked`)时,保留现场,说明原因,并在已有交付授权内修复后执行 `recoveryArgs`,不要求用户再次说“重试”。只有恢复需要新的权限、用户信息或交付方式时才询问;恢复完成前保持交付待完成。
|
|
61
|
+
|
|
62
|
+
项目 Git Hook 拒绝提交或合并说明时,卷宗可能已封存而 Git 收尾尚未完成。按项目规范修正尚未完成步骤的说明,在返回的恢复命令中传入对应消息参数;Runtime 复用已完成的归档提交、Spec 发布和合并。已完成提交的说明不能通过恢复改写,也不绕过 Hook 或重新创建 change。
|
|
63
|
+
|
|
64
|
+
用户或 Agent 已按授权手动完成 Git 收尾时,先运行 `comet native doctor <change-name> --json`,按返回的恢复命令继续。`doctor --repair` 对本地 keep / merge 收尾只在卷宗身份、提交内容和所选收尾条件得到证明后清理记录;push / pull-request 仍通过 Archive 核对远端和平台结果。Doctor 不代替提交、合并或推送。归档目录存在或 portable 状态为 done 不代表工作区交付完成;以公开状态和收尾结果为准。
|
|
59
65
|
|
|
60
66
|
完成标准:状态为 `done`,用户授权的工作区收尾结果为已完成(`completed`)或已保留(`kept`);其他结果按 `continuation` 继续。任务结束时,用启动时保存的原始请求、workflow、change 和同一个 session 调用 `comet task --complete`。不要运行 `printenv COMET_TASK` 或读取其他未声明的环境变量来猜测任务内容。
|
|
@@ -130,8 +130,6 @@ comet classic openspec -- --version
|
|
|
130
130
|
comet state check <name> design --json
|
|
131
131
|
```
|
|
132
132
|
|
|
133
|
-
多条只读 comet 命令(如 `state get`、`state next`、`state artifacts`)可以合并成一条 shell 调用依次执行,减少进程启动开销。
|
|
134
|
-
|
|
135
133
|
该入口已检查 OpenSpec 的全部必需依赖、实际输出和 Comet 状态,不再额外重复查询 status。`isComplete` 仅用于诊断,非必需产物不会阻止流程继续。检查失败时,再查询 status,找出尚未生成的依赖,或处理已报告的路径错误、缺少必需能力等问题。
|
|
136
134
|
|
|
137
135
|
任一拆分项未通过检查时,不能宣告拆分完成,也不能询问用户开始哪个 change。应停止后续推进,从该 change 的第一个 `ready` 或 `blocked` 产物恢复 `/comet-open`。OpenSpec 检查通过、但 Comet state 检查失败时,必须先修复 `.comet.yaml` 初始化或 phase,再重新执行整批检查。
|
|
@@ -148,7 +148,7 @@ comet state set <change-name> verify_mode full
|
|
|
148
148
|
|
|
149
149
|
无 delta spec 的 tweak 通常满足轻量验证条件(≤ 3 tasks、改动文件数低于 scale 阈值),按 comet-verify 的轻量验证清单逐项检查。若用户希望增加审查,可在验证前运行 `comet state set <name> review_mode standard` 或 `thorough`。
|
|
150
150
|
|
|
151
|
-
|
|
151
|
+
验证及报告完成后,由 `/comet-verify` 执行 `comet guard <change-name> verify --apply`;复用它成功返回的 archive 状态和 `agent.continuation`,不再手动设置 `verify_result: pass` 或重复运行 Guard。Guard 未通过时按其原因处理,不能宣告验收通过。进入 `/comet-archive` 后仍须完成归档前最终确认,不得自动运行归档脚本。
|
|
152
152
|
|
|
153
153
|
### 4. 归档(预设 archive)
|
|
154
154
|
|
|
@@ -27,8 +27,6 @@ comet state select <change-name>
|
|
|
27
27
|
comet state check <change-name> verify --json
|
|
28
28
|
```
|
|
29
29
|
|
|
30
|
-
多条只读 comet 命令(如 `state get`、`state next`、`state artifacts`)可以合并成一条 shell 调用依次执行,减少进程启动开销。
|
|
31
|
-
|
|
32
30
|
上一阶段 guard 已成功返回本阶段状态信息时,直接使用其中的状态与 `agent.continuation` 继续,不重复 select/check;恢复任务、工作区变化或外部状态变化时,才执行上述入口验证。根据入口返回的 layout、configuration、nextAction、任务信息和协作进度摘要继续。已有检查结果和集成审查仍然有效时,只补未完成的工作,不重新执行整个阶段。丢失上下文后恢复任务,需要完整记录时,使用 --recover --details --json。验证失败时,处理返回的具体原因。
|
|
33
31
|
|
|
34
32
|
若上述 `select` / `check` 输出 `BLOCKED` 或分支绑定 `ERROR`,且原因是 `bound_branch` 与当前分支不一致,立即按 `comet-classic/reference/decision-point.md` 暂停,让用户单选:切回绑定分支后重新运行入口验证,或在用户明确确认当前分支应接管该 change 后运行 `comet state rebind <change-name>` 并重新入口验证。不得自行切换分支,不得自行换绑。
|
|
@@ -161,18 +161,34 @@ function wait(milliseconds) {
|
|
|
161
161
|
}
|
|
162
162
|
|
|
163
163
|
async function requestWithLaunch(module, options, launch, waitForLaunch = true) {
|
|
164
|
+
const deadline =
|
|
165
|
+
process.platform === 'win32' && launch && waitForLaunch ? performance.now() + 10_000 : null;
|
|
166
|
+
const request = () => {
|
|
167
|
+
if (deadline === null) return module.sendCometDaemonRequest(options);
|
|
168
|
+
const remaining = Math.ceil(deadline - performance.now());
|
|
169
|
+
if (remaining <= 0) throw new Error('Comet daemon startup timed out');
|
|
170
|
+
return module.sendCometDaemonRequest({
|
|
171
|
+
...options,
|
|
172
|
+
timeoutMs: Math.min(options.timeoutMs ?? 5_000, remaining),
|
|
173
|
+
});
|
|
174
|
+
};
|
|
164
175
|
try {
|
|
165
|
-
return await
|
|
176
|
+
return await request();
|
|
166
177
|
} catch {
|
|
167
|
-
if (!launch
|
|
168
|
-
|
|
169
|
-
|
|
178
|
+
if (!launch) return null;
|
|
179
|
+
const started = startServer(module, options.endpoint, options.buildId, options.projectRoot);
|
|
180
|
+
if (!started && (deadline === null || !existsSync(launchLockPath(options.endpoint)))) return null;
|
|
170
181
|
}
|
|
171
182
|
if (!waitForLaunch) return null;
|
|
172
|
-
|
|
173
|
-
|
|
183
|
+
const delays = [20, 40, 80, 160, 320, 640, 1_000];
|
|
184
|
+
// Windows explicit start shares one deadline across backoff and IPC. Reads
|
|
185
|
+
// already returned above; they never wait for the background WMI handoff.
|
|
186
|
+
for (let attempt = 0; deadline !== null || attempt < delays.length; attempt += 1) {
|
|
187
|
+
const remaining = deadline === null ? Infinity : deadline - performance.now();
|
|
188
|
+
if (remaining <= 0) return null;
|
|
189
|
+
await wait(Math.min(delays[attempt] ?? 1_000, remaining));
|
|
174
190
|
try {
|
|
175
|
-
return await
|
|
191
|
+
return await request();
|
|
176
192
|
} catch {
|
|
177
193
|
// The detached server may still be loading the runtime bundle.
|
|
178
194
|
}
|
|
@@ -88,7 +88,7 @@ export async function tryRunFastRuntime(argv = process.argv.slice(2)) {
|
|
|
88
88
|
if (!existsSync(runtimePath)) return false;
|
|
89
89
|
|
|
90
90
|
if (route.classicCommand) {
|
|
91
|
-
const classicRuntimeUrl = assetUrl(
|
|
91
|
+
const classicRuntimeUrl = assetUrl(`assets/skills/comet/scripts/comet-${route.classicCommand}.mjs`);
|
|
92
92
|
if (!existsSync(fileURLToPath(classicRuntimeUrl))) return false;
|
|
93
93
|
const [{ runClassicFacade }, { runClassicCli }] = await Promise.all([
|
|
94
94
|
import(runtimeUrl.href),
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"version":3,"file":"daemon-server.d.ts","sourceRoot":"","sources":["../../../app/commands/daemon-server.ts"],"names":[],"mappings":"
|
|
1
|
+
{"version":3,"file":"daemon-server.d.ts","sourceRoot":"","sources":["../../../app/commands/daemon-server.ts"],"names":[],"mappings":"AAiDA,wBAAsB,oBAAoB,CAAC,IAAI,EAAE,SAAS,MAAM,EAAE,GAAG,OAAO,CAAC,IAAI,CAAC,CAyCjF"}
|