@rpamis/comet 0.4.0-beta.18 → 0.4.0-beta.19

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (241) hide show
  1. package/README.md +18 -3
  2. package/assets/manifest.json +3 -1
  3. package/assets/skills/comet/scripts/comet-archive.mjs +121 -121
  4. package/assets/skills/comet/scripts/comet-entry-runtime.mjs +84 -84
  5. package/assets/skills/comet/scripts/comet-guard.mjs +152 -152
  6. package/assets/skills/comet/scripts/comet-handoff.mjs +123 -123
  7. package/assets/skills/comet/scripts/comet-hook-guard.mjs +75 -75
  8. package/assets/skills/comet/scripts/comet-hook-router.mjs +91 -91
  9. package/assets/skills/comet/scripts/comet-intent.mjs +6 -6
  10. package/assets/skills/comet/scripts/comet-resume-probe.mjs +79 -79
  11. package/assets/skills/comet/scripts/comet-runtime.mjs +169 -169
  12. package/assets/skills/comet/scripts/comet-state.mjs +88 -88
  13. package/assets/skills/comet/scripts/comet-yaml-validate.mjs +97 -97
  14. package/assets/skills/comet-build/SKILL.md +21 -6
  15. package/assets/skills/comet-design/SKILL.md +2 -2
  16. package/assets/skills/comet-native/SKILL.md +7 -7
  17. package/assets/skills/comet-native/reference/artifacts.md +3 -3
  18. package/assets/skills/comet-native/reference/clarification.md +1 -1
  19. package/assets/skills/comet-native/reference/commands.md +3 -3
  20. package/assets/skills/comet-native/scripts/comet-native-archive.mjs +114 -113
  21. package/assets/skills/comet-native/scripts/comet-native-doctor.mjs +123 -123
  22. package/assets/skills/comet-native/scripts/comet-native-hook-guard.mjs +88 -88
  23. package/assets/skills/comet-native/scripts/comet-native-init.mjs +116 -116
  24. package/assets/skills/comet-native/scripts/comet-native-new.mjs +100 -100
  25. package/assets/skills/comet-native/scripts/comet-native-next.mjs +118 -118
  26. package/assets/skills/comet-native/scripts/comet-native-root.mjs +95 -95
  27. package/assets/skills/comet-native/scripts/comet-native-runtime.mjs +145 -144
  28. package/assets/skills/comet-native/scripts/comet-native-select.mjs +101 -101
  29. package/assets/skills/comet-native/scripts/comet-native-show.mjs +83 -83
  30. package/assets/skills/comet-native/scripts/comet-native-spec.mjs +87 -87
  31. package/assets/skills/comet-native/scripts/comet-native-status.mjs +98 -98
  32. package/assets/skills/comet-review/SKILL.md +121 -0
  33. package/assets/skills/comet-review/agents/openai.yaml +5 -0
  34. package/assets/skills-zh/comet-build/SKILL.md +21 -6
  35. package/assets/skills-zh/comet-design/SKILL.md +2 -2
  36. package/assets/skills-zh/comet-native/SKILL.md +7 -7
  37. package/assets/skills-zh/comet-native/reference/artifacts.md +3 -3
  38. package/assets/skills-zh/comet-native/reference/clarification.md +1 -1
  39. package/assets/skills-zh/comet-native/reference/commands.md +3 -3
  40. package/assets/skills-zh/comet-review/SKILL.md +121 -0
  41. package/assets/skills-zh/comet-review/agents/openai.yaml +5 -0
  42. package/dist/app/commands/init.d.ts.map +1 -1
  43. package/dist/app/commands/init.js +5 -9
  44. package/dist/app/commands/init.js.map +1 -1
  45. package/dist/app/commands/update.d.ts.map +1 -1
  46. package/dist/app/commands/update.js +5 -9
  47. package/dist/app/commands/update.js.map +1 -1
  48. package/dist/domains/comet-classic/classic-command-context.d.ts +9 -0
  49. package/dist/domains/comet-classic/classic-command-context.d.ts.map +1 -1
  50. package/dist/domains/comet-classic/classic-command-context.js +10 -0
  51. package/dist/domains/comet-classic/classic-command-context.js.map +1 -1
  52. package/dist/domains/comet-classic/classic-guard.d.ts.map +1 -1
  53. package/dist/domains/comet-classic/classic-guard.js +2 -2
  54. package/dist/domains/comet-classic/classic-guard.js.map +1 -1
  55. package/dist/domains/comet-classic/classic-handoff.d.ts.map +1 -1
  56. package/dist/domains/comet-classic/classic-handoff.js +44 -6
  57. package/dist/domains/comet-classic/classic-handoff.js.map +1 -1
  58. package/dist/domains/comet-classic/classic-hook-guard.d.ts.map +1 -1
  59. package/dist/domains/comet-classic/classic-hook-guard.js +2 -1
  60. package/dist/domains/comet-classic/classic-hook-guard.js.map +1 -1
  61. package/dist/domains/comet-classic/classic-intent-command.d.ts.map +1 -1
  62. package/dist/domains/comet-classic/classic-intent-command.js +2 -1
  63. package/dist/domains/comet-classic/classic-intent-command.js.map +1 -1
  64. package/dist/domains/comet-classic/classic-resume-probe-command.d.ts.map +1 -1
  65. package/dist/domains/comet-classic/classic-resume-probe-command.js +4 -3
  66. package/dist/domains/comet-classic/classic-resume-probe-command.js.map +1 -1
  67. package/dist/domains/comet-classic/classic-runtime-run.d.ts +6 -0
  68. package/dist/domains/comet-classic/classic-runtime-run.d.ts.map +1 -1
  69. package/dist/domains/comet-classic/classic-runtime-run.js +58 -9
  70. package/dist/domains/comet-classic/classic-runtime-run.js.map +1 -1
  71. package/dist/domains/comet-classic/classic-state-command.d.ts.map +1 -1
  72. package/dist/domains/comet-classic/classic-state-command.js +8 -5
  73. package/dist/domains/comet-classic/classic-state-command.js.map +1 -1
  74. package/dist/domains/comet-classic/classic-validate-command.d.ts.map +1 -1
  75. package/dist/domains/comet-classic/classic-validate-command.js +2 -2
  76. package/dist/domains/comet-classic/classic-validate-command.js.map +1 -1
  77. package/dist/domains/comet-classic/classic-workspace-command.d.ts.map +1 -1
  78. package/dist/domains/comet-classic/classic-workspace-command.js +3 -3
  79. package/dist/domains/comet-classic/classic-workspace-command.js.map +1 -1
  80. package/dist/domains/comet-entry/hook-adapter.d.ts.map +1 -1
  81. package/dist/domains/comet-entry/hook-adapter.js +4 -1
  82. package/dist/domains/comet-entry/hook-adapter.js.map +1 -1
  83. package/dist/domains/comet-native/native-archive-command.d.ts.map +1 -1
  84. package/dist/domains/comet-native/native-archive-command.js +2 -0
  85. package/dist/domains/comet-native/native-archive-command.js.map +1 -1
  86. package/dist/domains/comet-native/native-atomic-file.d.ts.map +1 -1
  87. package/dist/domains/comet-native/native-atomic-file.js +17 -10
  88. package/dist/domains/comet-native/native-atomic-file.js.map +1 -1
  89. package/dist/domains/comet-native/native-children.d.ts +18 -2
  90. package/dist/domains/comet-native/native-children.d.ts.map +1 -1
  91. package/dist/domains/comet-native/native-children.js +73 -8
  92. package/dist/domains/comet-native/native-children.js.map +1 -1
  93. package/dist/domains/comet-native/native-cli-help.d.ts.map +1 -1
  94. package/dist/domains/comet-native/native-cli-help.js +10 -4
  95. package/dist/domains/comet-native/native-cli-help.js.map +1 -1
  96. package/dist/domains/comet-native/native-cli-shared.d.ts.map +1 -1
  97. package/dist/domains/comet-native/native-cli-shared.js +18 -5
  98. package/dist/domains/comet-native/native-cli-shared.js.map +1 -1
  99. package/dist/domains/comet-native/native-hook-guard.d.ts.map +1 -1
  100. package/dist/domains/comet-native/native-hook-guard.js +15 -2
  101. package/dist/domains/comet-native/native-hook-guard.js.map +1 -1
  102. package/dist/domains/comet-native/native-next-command.d.ts.map +1 -1
  103. package/dist/domains/comet-native/native-next-command.js +94 -15
  104. package/dist/domains/comet-native/native-next-command.js.map +1 -1
  105. package/dist/domains/comet-native/native-portable-continuation.d.ts +19 -7
  106. package/dist/domains/comet-native/native-portable-continuation.d.ts.map +1 -1
  107. package/dist/domains/comet-native/native-portable-continuation.js +115 -72
  108. package/dist/domains/comet-native/native-portable-continuation.js.map +1 -1
  109. package/dist/domains/comet-native/native-portable-migration-runtime.d.ts.map +1 -1
  110. package/dist/domains/comet-native/native-portable-migration-runtime.js +9 -4
  111. package/dist/domains/comet-native/native-portable-migration-runtime.js.map +1 -1
  112. package/dist/domains/comet-native/native-portable-runtime.d.ts +14 -1
  113. package/dist/domains/comet-native/native-portable-runtime.d.ts.map +1 -1
  114. package/dist/domains/comet-native/native-portable-runtime.js +59 -1
  115. package/dist/domains/comet-native/native-portable-runtime.js.map +1 -1
  116. package/dist/domains/comet-native/native-pull-request-finish.d.ts +35 -0
  117. package/dist/domains/comet-native/native-pull-request-finish.d.ts.map +1 -0
  118. package/dist/domains/comet-native/native-pull-request-finish.js +282 -0
  119. package/dist/domains/comet-native/native-pull-request-finish.js.map +1 -0
  120. package/dist/domains/comet-native/native-status-discovery.d.ts.map +1 -1
  121. package/dist/domains/comet-native/native-status-discovery.js +24 -6
  122. package/dist/domains/comet-native/native-status-discovery.js.map +1 -1
  123. package/dist/domains/comet-native/native-workspace-finish.d.ts +6 -0
  124. package/dist/domains/comet-native/native-workspace-finish.d.ts.map +1 -1
  125. package/dist/domains/comet-native/native-workspace-finish.js +86 -35
  126. package/dist/domains/comet-native/native-workspace-finish.js.map +1 -1
  127. package/dist/domains/dashboard/web/assets/{abnfDiagram-N423BO3Z-B5cFR6hS.js → abnfDiagram-N423BO3Z-BYya6ofk.js} +1 -1
  128. package/dist/domains/dashboard/web/assets/{arc-CVQDtMsu.js → arc-DJbo4TD3.js} +1 -1
  129. package/dist/domains/dashboard/web/assets/{architectureDiagram-T3A2C74G-C0v0kULK.js → architectureDiagram-T3A2C74G-D8uZ2IB-.js} +1 -1
  130. package/dist/domains/dashboard/web/assets/{blockDiagram-VBNYF7ZC-DpHLuxu4.js → blockDiagram-VBNYF7ZC-B16BVj-r.js} +1 -1
  131. package/dist/domains/dashboard/web/assets/{c4Diagram-5PPSVZJV-BHnFxUs1.js → c4Diagram-5PPSVZJV-ayV208_D.js} +1 -1
  132. package/dist/domains/dashboard/web/assets/channel-CEsrvmig.js +1 -0
  133. package/dist/domains/dashboard/web/assets/{chunk-2GRJ4B5K-CGC9gh5n.js → chunk-2GRJ4B5K-Bn5o8p3H.js} +1 -1
  134. package/dist/domains/dashboard/web/assets/{chunk-2Q5K7J3B-l4puLU_O.js → chunk-2Q5K7J3B-BnF1SI6B.js} +1 -1
  135. package/dist/domains/dashboard/web/assets/{chunk-5RXB4S5H-ls9jQHZc.js → chunk-5RXB4S5H-ETnma053.js} +1 -1
  136. package/dist/domains/dashboard/web/assets/{chunk-5VM5RSS4-BVavmTEq.js → chunk-5VM5RSS4-Cuvy639H.js} +1 -1
  137. package/dist/domains/dashboard/web/assets/{chunk-6Q2QTUOP-Dungt2g9.js → chunk-6Q2QTUOP-DOXBzl73.js} +1 -1
  138. package/dist/domains/dashboard/web/assets/{chunk-GF5L2VYU-BidXO_ZP.js → chunk-GF5L2VYU-CfREXlEl.js} +1 -1
  139. package/dist/domains/dashboard/web/assets/{chunk-JWPE2WC7-57L5Up5X.js → chunk-JWPE2WC7-DWIdpYTb.js} +1 -1
  140. package/dist/domains/dashboard/web/assets/{chunk-KBJHAD2P-C5u5vbwr.js → chunk-KBJHAD2P-BnqPcfZB.js} +1 -1
  141. package/dist/domains/dashboard/web/assets/{chunk-RYQCIY6F-CvLz21I2.js → chunk-RYQCIY6F-DdJ00fZz.js} +1 -1
  142. package/dist/domains/dashboard/web/assets/{chunk-XXDRQBXY-D5nJpckG.js → chunk-XXDRQBXY-BVDhdJyW.js} +1 -1
  143. package/dist/domains/dashboard/web/assets/classDiagram-JCYQIIEL-CKFe0hg4.js +1 -0
  144. package/dist/domains/dashboard/web/assets/classDiagram-v2-OCEON4UE-CKFe0hg4.js +1 -0
  145. package/dist/domains/dashboard/web/assets/{cose-bilkent-JH36ORCC-Dp0JAGyE.js → cose-bilkent-JH36ORCC-C-nglwHC.js} +1 -1
  146. package/dist/domains/dashboard/web/assets/{cynefin-VYW2F7L2-EjC54l1g.js → cynefin-VYW2F7L2-C8TMmrbP.js} +1 -1
  147. package/dist/domains/dashboard/web/assets/{cynefinDiagram-MW4NZA55-CpYrW3w3.js → cynefinDiagram-MW4NZA55-C3pnQnjg.js} +1 -1
  148. package/dist/domains/dashboard/web/assets/{dagre-VZM6K2ZE-h5K39rCk.js → dagre-VZM6K2ZE-DY7UWiPI.js} +1 -1
  149. package/dist/domains/dashboard/web/assets/{diagram-7IWD3JNH-CKQj9O4H.js → diagram-7IWD3JNH-voTyDkQ5.js} +1 -1
  150. package/dist/domains/dashboard/web/assets/{diagram-B4RE2ZJO-DXRIYcnW.js → diagram-B4RE2ZJO-B3VkUMck.js} +1 -1
  151. package/dist/domains/dashboard/web/assets/{diagram-LBJQPF4R-wWutQYmv.js → diagram-LBJQPF4R-BdJzPkv8.js} +1 -1
  152. package/dist/domains/dashboard/web/assets/{diagram-Q27KOJAE-EgXLJQYi.js → diagram-Q27KOJAE-Bsq0anZx.js} +1 -1
  153. package/dist/domains/dashboard/web/assets/{diagram-UB23O5K3-CsQRXDQZ.js → diagram-UB23O5K3-CBaKRbcu.js} +1 -1
  154. package/dist/domains/dashboard/web/assets/{ebnfDiagram-BXEA7PRR-gm328Eho.js → ebnfDiagram-BXEA7PRR-Bl9Bm5wa.js} +1 -1
  155. package/dist/domains/dashboard/web/assets/{erDiagram-JOGREHBK-BbbMVUx_.js → erDiagram-JOGREHBK-DjOZzfKI.js} +1 -1
  156. package/dist/domains/dashboard/web/assets/{flowDiagram-UKHOOZJN-1Y7scCns.js → flowDiagram-UKHOOZJN-C21e4siK.js} +1 -1
  157. package/dist/domains/dashboard/web/assets/{ganttDiagram-PKOTCBZU-BAoBqczv.js → ganttDiagram-PKOTCBZU-Bs62uy6-.js} +1 -1
  158. package/dist/domains/dashboard/web/assets/{gitGraphDiagram-DS77QQ5N-CMUAyEzl.js → gitGraphDiagram-DS77QQ5N-DQY_Ba00.js} +1 -1
  159. package/dist/domains/dashboard/web/assets/{index-CCApJ0Yr.js → index-BLv71GRj.js} +1 -1
  160. package/dist/domains/dashboard/web/assets/{index-DWdm_XBi.js → index-Be4r99N4.js} +3 -3
  161. package/dist/domains/dashboard/web/assets/index-ByVYiA6g.css +1 -0
  162. package/dist/domains/dashboard/web/assets/{infoDiagram-6WML65LV-BaCdtYYC.js → infoDiagram-6WML65LV-CNgNNG9l.js} +1 -1
  163. package/dist/domains/dashboard/web/assets/{ishikawaDiagram-WSZJBQD7-DQQlNnjU.js → ishikawaDiagram-WSZJBQD7-D9k1fTO1.js} +1 -1
  164. package/dist/domains/dashboard/web/assets/{journeyDiagram-NVQOT4AX-DW9wUMqn.js → journeyDiagram-NVQOT4AX-CHijUnPl.js} +1 -1
  165. package/dist/domains/dashboard/web/assets/{kanban-definition-27J2QSJJ-C_ITaZ0q.js → kanban-definition-27J2QSJJ-DfWlntDq.js} +1 -1
  166. package/dist/domains/dashboard/web/assets/{linear-DXOo6ZRT.js → linear-o6hemX-z.js} +1 -1
  167. package/dist/domains/dashboard/web/assets/{mermaid.core-ol-0NI97.js → mermaid.core-B1DoOsPD.js} +4 -4
  168. package/dist/domains/dashboard/web/assets/{mindmap-definition-FAOFIHXS-CHF_HOLV.js → mindmap-definition-FAOFIHXS-COMQF9Yy.js} +1 -1
  169. package/dist/domains/dashboard/web/assets/{pegDiagram-VL7TDLO6-wQEvkNF8.js → pegDiagram-VL7TDLO6-C_21n7Ps.js} +1 -1
  170. package/dist/domains/dashboard/web/assets/{pieDiagram-7S7Q4E2Y-C3H3kiIP.js → pieDiagram-7S7Q4E2Y-D3EmoYDY.js} +1 -1
  171. package/dist/domains/dashboard/web/assets/{quadrantDiagram-CIZ2JOQS-S0FdVzJb.js → quadrantDiagram-CIZ2JOQS-C3fGdiMa.js} +1 -1
  172. package/dist/domains/dashboard/web/assets/{railroadDiagram-AXF67PYL-DCDXDaVg.js → railroadDiagram-AXF67PYL-mIsjemD-.js} +1 -1
  173. package/dist/domains/dashboard/web/assets/{requirementDiagram-LRYGKXZP-BW8J4gO_.js → requirementDiagram-LRYGKXZP-D_UMpS5e.js} +1 -1
  174. package/dist/domains/dashboard/web/assets/{sankeyDiagram-W5VNT64P-DQQBmLoy.js → sankeyDiagram-W5VNT64P-D1MwyMF6.js} +1 -1
  175. package/dist/domains/dashboard/web/assets/{sequenceDiagram-SI44F4Z6-2tDcli0Y.js → sequenceDiagram-SI44F4Z6-B8jp1RxX.js} +1 -1
  176. package/dist/domains/dashboard/web/assets/{sizeCapture-X5ZJPWSS-4sEZLBKb.js → sizeCapture-X5ZJPWSS-BKioI1Ql.js} +1 -1
  177. package/dist/domains/dashboard/web/assets/{stateDiagram-OKZ733FA-OgPb8pyR.js → stateDiagram-OKZ733FA-B7l8_CDo.js} +1 -1
  178. package/dist/domains/dashboard/web/assets/stateDiagram-v2-UEYNNEHI-BIxuwbeV.js +1 -0
  179. package/dist/domains/dashboard/web/assets/{swimlanes-SLNWSIFB-DR7lwtxd.js → swimlanes-SLNWSIFB-951PRLYp.js} +2 -2
  180. package/dist/domains/dashboard/web/assets/swimlanesDiagram-ULZ7WXOC-CEo6cGsy.js +8 -0
  181. package/dist/domains/dashboard/web/assets/{timeline-definition-Z64GVDOM-DNIJVlQV.js → timeline-definition-Z64GVDOM-CeyA2KbI.js} +1 -1
  182. package/dist/domains/dashboard/web/assets/{vennDiagram-T6HMQDX7-CClhw4QZ.js → vennDiagram-T6HMQDX7-BHe0TZJV.js} +1 -1
  183. package/dist/domains/dashboard/web/assets/{wardleyDiagram-T6FBY63Y-DzR3aFPS.js → wardleyDiagram-T6FBY63Y-CWqdSzJ-.js} +1 -1
  184. package/dist/domains/dashboard/web/assets/{xychartDiagram-ELKLHX3M-DZhq0ZRj.js → xychartDiagram-ELKLHX3M-DCKiZVPV.js} +1 -1
  185. package/dist/domains/dashboard/web/index.html +2 -2
  186. package/dist/domains/dashboard/workspace.d.ts +3 -0
  187. package/dist/domains/dashboard/workspace.d.ts.map +1 -1
  188. package/dist/domains/dashboard/workspace.js +23 -2
  189. package/dist/domains/dashboard/workspace.js.map +1 -1
  190. package/dist/domains/integrations/openspec.d.ts +1 -1
  191. package/dist/domains/integrations/openspec.d.ts.map +1 -1
  192. package/dist/domains/integrations/openspec.js +43 -84
  193. package/dist/domains/integrations/openspec.js.map +1 -1
  194. package/dist/domains/integrations/superpowers.d.ts +10 -1
  195. package/dist/domains/integrations/superpowers.d.ts.map +1 -1
  196. package/dist/domains/integrations/superpowers.js +73 -4
  197. package/dist/domains/integrations/superpowers.js.map +1 -1
  198. package/dist/domains/skill/platform-inspect.d.ts.map +1 -1
  199. package/dist/domains/skill/platform-inspect.js +3 -3
  200. package/dist/domains/skill/platform-inspect.js.map +1 -1
  201. package/dist/domains/skill/platform-install.d.ts +3 -1
  202. package/dist/domains/skill/platform-install.d.ts.map +1 -1
  203. package/dist/domains/skill/platform-install.js +15 -9
  204. package/dist/domains/skill/platform-install.js.map +1 -1
  205. package/dist/domains/skill/project-instructions.d.ts.map +1 -1
  206. package/dist/domains/skill/project-instructions.js +6 -0
  207. package/dist/domains/skill/project-instructions.js.map +1 -1
  208. package/dist/domains/skill/uninstall.d.ts.map +1 -1
  209. package/dist/domains/skill/uninstall.js +39 -29
  210. package/dist/domains/skill/uninstall.js.map +1 -1
  211. package/dist/domains/workflow-contract/contained-atomic-write.d.ts.map +1 -1
  212. package/dist/domains/workflow-contract/contained-atomic-write.js +18 -10
  213. package/dist/domains/workflow-contract/contained-atomic-write.js.map +1 -1
  214. package/dist/domains/workflow-contract/project-config.d.ts +4 -2
  215. package/dist/domains/workflow-contract/project-config.d.ts.map +1 -1
  216. package/dist/domains/workflow-contract/project-config.js +132 -0
  217. package/dist/domains/workflow-contract/project-config.js.map +1 -1
  218. package/dist/domains/workflow-contract/types.d.ts +9 -0
  219. package/dist/domains/workflow-contract/types.d.ts.map +1 -1
  220. package/dist/platform/fs/strip-bom.d.ts +10 -0
  221. package/dist/platform/fs/strip-bom.d.ts.map +1 -0
  222. package/dist/platform/fs/strip-bom.js +12 -0
  223. package/dist/platform/fs/strip-bom.js.map +1 -0
  224. package/dist/platform/install/platforms.d.ts +11 -0
  225. package/dist/platform/install/platforms.d.ts.map +1 -1
  226. package/dist/platform/install/platforms.js +36 -0
  227. package/dist/platform/install/platforms.js.map +1 -1
  228. package/dist/platform/process/external-command.d.ts +1 -0
  229. package/dist/platform/process/external-command.d.ts.map +1 -1
  230. package/dist/platform/process/external-command.js +2 -1
  231. package/dist/platform/process/external-command.js.map +1 -1
  232. package/eval/local/tests/conftest.py +18 -3
  233. package/eval/local/tests/scaffold/test_conftest_helpers.py +57 -0
  234. package/package.json +11 -26
  235. package/dist/domains/dashboard/web/assets/channel-eM0x3m1G.js +0 -1
  236. package/dist/domains/dashboard/web/assets/classDiagram-JCYQIIEL-CEFhao2K.js +0 -1
  237. package/dist/domains/dashboard/web/assets/classDiagram-v2-OCEON4UE-CEFhao2K.js +0 -1
  238. package/dist/domains/dashboard/web/assets/index-DhhbseFJ.css +0 -1
  239. package/dist/domains/dashboard/web/assets/stateDiagram-v2-UEYNNEHI-CiDNPr4P.js +0 -1
  240. package/dist/domains/dashboard/web/assets/swimlanesDiagram-ULZ7WXOC-DggHFP9q.js +0 -8
  241. package/eval/local/tasks/comet-native-interrupted-transition/environment/.comet/config.yaml +0 -6
@@ -34,17 +34,20 @@ If the `select` / `check` output is `BLOCKED` because `bound_branch` does not ma
34
34
 
35
35
  Create the implementation plan through a subagent, avoiding planning skill occupying main session context. Plan files and execution feedback must use the configured Comet artifact language from `comet state get <name> language`.
36
36
 
37
+ Before dispatching, the main session fixes the full plan path `docs/superpowers/plans/<YYYY-MM-DD>-<change-name>.md` (e.g. `docs/superpowers/plans/2026-08-21-rename-alert.md`) and passes it into the instructions below verbatim.
38
+
37
39
  **Subagent instructions**:
38
40
 
39
41
  You are an implementation planning expert. Create an implementation plan based on the following inputs:
40
42
 
41
- 1. **Immediately execute:** Use the Skill tool to load the Superpowers `writing-plans` skill. Skipping this step is prohibited. After the skill loads, ARGUMENTS must include: `Language: Use the configured Comet artifact language from comet state get <name> language`
43
+ 1. **Immediately execute:** Use the Skill tool to load the Superpowers `writing-plans` skill. Skipping this step is prohibited. After the skill loads, ARGUMENTS must include: `Language: Use the configured Comet artifact language from comet state get <name> language`. If the Skill tool is unavailable or the skill cannot be found, end immediately with a single-line final reply `SKILL_UNAVAILABLE`; do not retry and do not write the plan yourself without the skill
42
44
  2. Read the Design Doc (technical design document under `docs/superpowers/specs/`)
43
45
  3. Read `<classic-change-dir>/tasks.md` (task boundaries)
44
- 4. Follow the skill's guidance to create the plan
46
+ 4. Follow the skill's guidance to create the plan; no user will answer you during the run, so skip steps that ask the user a question (such as the `writing-plans` Execution Handoff at the end) and do not ask the user anything
45
47
 
46
48
  Plan requirements:
47
- - Save to `docs/superpowers/plans/YYYY-MM-DD-<feature>.md`
49
+ - Save to the plan path given in the instructions; do not change the file name
50
+ - Cover only the tasks listed in tasks.md; do not expand scope
48
51
  - Reference design document, break down into executable tasks
49
52
  - **Plan file header must contain associated metadata**:
50
53
 
@@ -62,13 +65,17 @@ base-ref: <git rev-parse HEAD before implementation>
62
65
  git rev-parse HEAD
63
66
  ```
64
67
 
65
- Write the plan to file, then return the file path.
68
+ After writing the plan to file, the last line of your final reply must be exactly:
69
+
70
+ ```
71
+ PLAN_PATH: <relative path of the plan file>
72
+ ```
66
73
 
67
74
  **Execute subagent**: Dispatch the above task to a subagent.
68
75
 
69
76
  After the subagent completes:
70
- - If a valid file path is returned and the file exists, record it as the plan
71
- - If the subagent fails or returns an invalid path, fall back to loading the Superpowers `writing-plans` skill inline in the main session (degraded fallback)
77
+ - Read the `PLAN_PATH:` line at the end of the reply; if the file exists, record it as the plan; if the line is missing, look for an existing valid path in the reply text
78
+ - If the subagent reports `SKILL_UNAVAILABLE`, the dispatch fails, or no valid path can be obtained, fall back to loading the Superpowers `writing-plans` skill inline in the main session (degraded fallback), remember that dispatch is unavailable for this session, and go inline directly on later Step 1 entries
72
79
 
73
80
  ### 2. Update Plan Status and Jointly Confirm Workflow Configuration
74
81
 
@@ -240,6 +247,14 @@ When creating an independent change, must invoke `/comet-open`, not `/opsx:new`
240
247
  - Do not sync to main spec in advance, sync uniformly during archiving
241
248
  - For small-scale incremental direct delta spec edits, note in commit message to facilitate design doc drift assessment during archiving
242
249
 
250
+ **Handoff synchronization**: adding, modifying, or removing a delta spec expires the design handoff pack (`handoff_hash`). During Build you can regenerate it directly without reverting the current phase or step:
251
+
252
+ ```bash
253
+ comet handoff <change-name> design --write
254
+ ```
255
+
256
+ Regeneration rebuilds the handoff from the current OpenSpec artifacts and updates `handoff_hash`; it does not change the `phase` field or the Runtime `currentStep`, so you can continue in the Build phase after refreshing.
257
+
243
258
  ### 5. Context Management
244
259
 
245
260
  Build is the longest phase and may span many tasks. To support resume after context compaction:
@@ -206,7 +206,7 @@ If Spec Patches need to be written back, also edit the corresponding `specs/*/sp
206
206
 
207
207
  ### 3. Update Comet State
208
208
 
209
- First record the design_doc path. If Spec Patches wrote back delta spec (added or modified `specs/*/spec.md`), must regenerate handoff to update hash:
209
+ First record the design_doc path. If Spec Patches wrote back delta spec (added, modified, or removed `specs/*/spec.md`), must regenerate handoff to update hash:
210
210
 
211
211
  ```bash
212
212
  # Record design_doc path
@@ -219,7 +219,7 @@ comet handoff <change-name> design --write
219
219
  comet guard <change-name> design --apply
220
220
  ```
221
221
 
222
- If there are no delta spec changes, skip the handoff regeneration step. The state file updates automatically; no manual editing of other fields needed.
222
+ Adding, modifying, or removing a delta spec changes the handoff hash, so deleting a delta spec also requires regenerating the handoff; otherwise the recorded `handoff_hash` no longer matches the current OpenSpec artifacts and the design guard blocks progress. If there are no delta spec changes, skip the handoff regeneration step. The state file updates automatically; no manual editing of other fields needed.
223
223
 
224
224
  ### 3a. Optional Active Context Compaction
225
225
 
@@ -36,9 +36,9 @@ After confirming the phase, read only the needed reference:
36
36
  - Read the [recovery reference](reference/recovery.md) only when the task cannot continue because of an interrupted process, missing local Runtime state after moving devices, repeated lack of progress, a concurrency conflict, failed legacy migration, or damaged state.
37
37
  ## Shape
38
38
 
39
- First investigate facts that can be determined from the repository, tools, and runtime environment. Independent fact-finding may be delegated to subagents. Follow `native.clarification_mode` and the clarification reference to maintain a decision tree. Ask the user only for choices that change the visible result and cannot be inferred reliably.
39
+ First investigate facts that can be determined from the repository, tools, and runtime environment. Independent fact-finding may be delegated to subagents. Follow `native.clarification_mode` and the clarification reference to maintain a decision tree. Ask the user only for choices that change the visible result and cannot be inferred reliably. When the user directly supplies a file, attachment, link, or local path as a requirements source, enter source-document full-coverage mode: read all accessible content and record its `complete`, `partial`, or `unavailable` status; chunking changes only read order and working-memory management, not the final coverage set; `brief.md` records the complete source requirements and coverage states before asking about ambiguity, omissions, or implicit boundaries; every executable source unit must map to both the complete target Spec and at least one acceptance ID, while background, non-goal, or superseded units retain only their classification, reason, and replacement relationship; mark a corrected old unit `superseded` and point it to its replacement; keep `partial`, `unavailable`, unmapped, or unconfirmed content `[blocking]`. Materials supplied only for debugging, evidence, review, or implementation reference do not trigger this mode automatically; clarify an unclear purpose first. A summary cannot replace the source coverage map.
40
40
 
41
- Immediately synchronize confirmed user-visible decisions and important constraints into Decisions, the brief, and complete target specifications. Keep ordinary implementation choices in the implementation and tests unless they affect visible behavior. Acceptance items must be specific, observable, and non-duplicative. When a large requirement needs decomposition, maintain `children.yaml` at the Supervisor Change root, use `depends_on` for real ordering, and use `covers` to cover Supervisor Change acceptance items. Array order is only stable display order and the priority among equally ready children.
41
+ Immediately synchronize confirmed user-visible decisions and important constraints into Decisions, the brief, and complete target specifications. Keep ordinary implementation choices in the implementation and tests unless they affect visible behavior. Acceptance items must be specific, observable, and non-duplicative. When a large requirement needs decomposition, maintain `children.yaml` at the Supervisor Change root, use `depends_on` for real ordering, and use `covers` to cover the Supervisor Change's readable acceptance index. Array order is only stable display order and the priority among equally ready children. New v2 `children.yaml` files index only brief-derived parent acceptance items; `acceptance_index` stores each ID's source and complete text. Spec-derived fine-grained checks remain in the Runtime's complete acceptance matrix and do not need to be duplicated in the initial child plan. Historical v1 files remain accepted under their original contract.
42
42
 
43
43
  For a large requirement, run one decomposition preflight before the final Shape confirmation: recommend Supervisor Change mode only when workers can independently implement and verify at least two outcomes, acceptance items map completely, and real dependency or parallel value exists; keep a single Native change when the goal is tightly coupled, repeatedly edits one core area, coordination costs exceed independent verification, or the user asks for one change; text length and task count alone must not trigger decomposition.
44
44
  When decomposition is recommended, put the `children.yaml` draft, execution waves, and coverage summary into one Shape confirmation; the user can confirm, adjust, or keep one. Do not create child changes before confirmation; do not create worktrees or dispatch Agents before confirmation.
@@ -58,12 +58,12 @@ For the first implementation, read the current brief, complete target specificat
58
58
 
59
59
  One parent Shape confirmation authorizes strictly derived child changes, so do not ask the user to repeat the same scope. The Skill executes only actions returned by Runtime continuation and rereads `readyChildren` after each child completes; the parent still verifies every acceptance item at the end.
60
60
 
61
- When status contains `children`, the current change is a Supervisor Change: do not run a Supervisor Change Builder; advance only `readyChildren`. Every child is an ordinary Native change and must be created in an independent worktree targeting the Supervisor Change's `workspace.changeBranch`. Children without dependencies may Build and Verify in parallel, but Archive them one at a time with `finish=merge` into the Supervisor Change branch. Commit the Supervisor Change contract baseline first so the integration worktree stays clean. A child is `done` only after its Archive is merged into the Supervisor Change branch; only then create dependents from the updated Supervisor Change HEAD. After every child is `done`, execute the Supervisor Change continuation to enter Verify, where a fresh Verifier checks the Supervisor Change's complete acceptance list on the final integrated branch. If Supervisor Change Verify fails, do not reopen an archived child. Follow `repair-child`, append a uniquely named repair child covering the failed acceptance items to `children.yaml`, reconfirm the Supervisor Change Shape, and continue.
61
+ When status contains `children`, the current change is a Supervisor Change: do not run a Supervisor Change Builder; advance only `readyChildren`. Every child is an ordinary Native change and must be created in an independent worktree targeting the Supervisor Change's `workspace.changeBranch`. Children without dependencies may Build and Verify in parallel, but Archive them one at a time with `finish=merge` into the Supervisor Change branch. Commit the Supervisor Change contract baseline first so the integration worktree stays clean. A child is `done` only after its Archive is merged into the Supervisor Change branch; only then create dependents from the updated Supervisor Change HEAD. After every child is `done`, execute the Supervisor Change continuation to enter Verify, where a fresh Verifier checks the Supervisor Change's complete acceptance list on the final integrated branch. If Supervisor Change Verify fails, do not reopen an archived child. Follow `repair-child`, add the actual failed Spec acceptance text to the v2 `acceptance_index`, append a uniquely named repair child covering those failed acceptance items to `children.yaml`, reconfirm the Supervisor Change Shape, and continue.
62
62
 
63
63
  When requirements change, classify them first:
64
64
 
65
- - The current requirement was implemented incompletely: use `--return-to-build` from Verify or Archive to return to Build.
66
- - User-visible behavior or acceptance criteria changed: return to Shape, update the formal artifacts, and reconfirm.
65
+ - The current requirement was implemented incompletely: use `--revise-implementation` from Verify to keep confirmed requirements and return to Build.
66
+ - User-visible behavior or acceptance criteria changed: use `--revise-requirements` from Verify, update the formal artifacts, and reconfirm Shape.
67
67
  - The request is unrelated to the current requirement: keep it for another change.
68
68
 
69
69
  Apply the same rule when the user explicitly adds to the current scope.
@@ -84,7 +84,7 @@ The Verifier first reads the acceptance items, brief, complete target Specs, act
84
84
 
85
85
  The Verifier remains read-only. If existing checks are insufficient, list the additional checks in the `inputOptions.template` returned by the Runtime. The Runtime executes them and returns the results to the Verifier.
86
86
 
87
- The Verifier must finally mark every acceptance item exactly once as `passed`, `failed`, or `blocked`. For a failed or blocked item, provide a reason that the next Build round can act on directly. If the Verifier cannot be started, execution fails, or external information is missing, follow the command reference and the latest `continuation`.
87
+ The Verifier must finally mark every acceptance item exactly once as `passed`, `failed`, or `blocked`. For a failed or blocked item, provide a reason that the next Build round can act on directly. If the Verifier cannot be started, execution fails, or external information is missing, follow the command reference and the latest `continuation`. When a skill-coordinated Verifier passes and Runtime waits for the user decision, use `--accept-result` to enter Archive only after the user accepts the current result; otherwise use `--revise-implementation` or `--revise-requirements`.
88
88
 
89
89
  Completion criterion: the Runtime has accepted the complete Verifier result and has explicitly entered one of Build, Archive, `await-user`, `blocked`, or `done`.
90
90
 
@@ -101,7 +101,7 @@ Completion criterion: state is `done`, and the user-authorized workspace finish
101
101
  After every command, handle only the latest `continuation`:
102
102
 
103
103
  - `continue`: execute `commandArgs` and fill `inputOptions` from its template.
104
- - `await-user`: wait for the listed user decision.
104
+ - `await-user`: wait for the listed user decision. With `commandAlternatives`, execute the matching complete `commandArgs`, preserve `--expected-state-version` plus `--expected-action`, and reread the latest `continuation` if the alternative is stale. Do not reconstruct an unguarded command.
105
105
  - `blocked`: resolve the listed blocker or recovery action first.
106
106
  - `done`: finish.
107
107
 
@@ -29,7 +29,7 @@ Local Runtime data always lives under the Git-ignored `.comet/runtime/native/`.
29
29
 
30
30
  ## Brief
31
31
 
32
- `brief.md` uses these non-empty level-one headings:
32
+ `brief.md` is Native's durable clarification artifact and uses these non-empty level-one headings:
33
33
 
34
34
  ```text
35
35
  # Outcome
@@ -50,9 +50,9 @@ Use these forms in Open questions only for real unresolved user questions:
50
50
  - [blocking] CONFIRM: <final shared understanding>
51
51
  ```
52
52
 
53
- As soon as a decision is confirmed, write it into Decisions and the complete target specifications, then remove the corresponding blocker. Formal artifacts record conclusions and reasons, not hidden model reasoning.
53
+ As soon as a decision is confirmed, write it into Decisions and the complete target specifications, then remove the corresponding blocker. Formal artifacts record conclusions and reasons, not hidden model reasoning. When the user directly supplies a file, attachment, link, or local path as a requirements source, keep the only source coverage map in `brief.md` at `# Scope` under `## Source coverage`; the complete target Spec does not repeat that source table and instead fully expresses all currently active executable semantics.
54
54
 
55
- Acceptance criteria must be specific, observable, and non-duplicative. Use simple sequential IDs such as `A1`, `A2`, and `A3`. IDs map results only; they are not derived from content and do not identify files. On Shape confirmation, the Runtime saves the full acceptance text and its source. A Supervisor Change's `children.yaml` uses `comet.native.children.v1`; each child contains only `name`, `depends_on`, and `covers`. Names must be unique, dependencies must exist and be acyclic, and every Supervisor Change acceptance ID must be covered. The Runtime confirms it together with the Supervisor Change acceptance; any change returns the Supervisor Change to Shape.
55
+ Acceptance criteria must be specific, observable, and non-duplicative. Use simple sequential IDs such as `A1`, `A2`, and `A3`. IDs map results only; they are not derived from content and do not identify files. On Shape confirmation, the Runtime saves the full acceptance text and its source. For every direct-source unit, the coverage map records the source location, `complete`/`partial`/`unavailable` read status, retained semantics, applicable Spec location and acceptance ID, `covered`/`needs-clarification`/`background`/`non-goal`/`superseded` coverage state, and a reason or replacement relationship. Every currently active executable unit must have both a Spec location and acceptance ID; background, non-goal, and superseded source units do not require a Spec location or acceptance ID. Acceptance criteria cover all currently active executable semantics from the original source; `partial`, `unavailable`, uncovered, or incompletely dual-mapped executable units remain blocked. A new Supervisor Change `children.yaml` uses `comet.native.children.v2`: `acceptance_index` stores the source and complete text for brief-derived parent acceptance IDs, each child still contains only `name`, `depends_on`, and `covers`, and `covers` must cover every ID in the index. Spec-derived acceptance remains in the Runtime's complete acceptance matrix; only repair phases add actual failed Spec IDs with their source and text to the index. Names must be unique, dependencies must exist and be acyclic. Historical `comet.native.children.v1` files remain accepted with their original complete acceptance coverage format; any change returns the Supervisor Change to Shape.
56
56
 
57
57
  ## Complete target specifications
58
58
 
@@ -10,7 +10,7 @@ First separate three kinds of information:
10
10
  - **User decision**: choices that materially change output, default behavior, failure results, scope, or irreversible impact. The user confirms these.
11
11
  - **Implementation choice**: algorithms, structures, and working methods that do not change the visible result. The Agent decides these.
12
12
 
13
- Ask the user only when ambiguity materially changes the visible result and cannot be determined reliably from the request, formal specifications, or project rules. Questions must come from real divergence; the Agent decides ordinary implementation details directly.
13
+ Ask the user only when ambiguity materially changes the visible result and cannot be determined reliably from the request, formal specifications, or project rules. Questions must come from real divergence; the Agent decides ordinary implementation details directly. When the user directly supplies a file, attachment, link, or local path as a requirements source, `brief.md` is the durable clarification artifact: first present the complete source requirements and coverage states in `## Source coverage` under `# Scope`, then ask about ambiguity, omissions, or implicit boundaries in `# Open questions`. Materials supplied only for debugging, evidence, review, or implementation reference do not trigger this mode automatically; clarify an unclear purpose first. Split the source into units by headings, paragraphs, lists, tables, code blocks, examples, constraints, links, and boundaries, recording read and coverage states. Executable source units must enter both the complete target Spec and at least one acceptance ID; background and non-goal units retain only a classification and reason and do not require an acceptance ID. When the user corrects the source, mark the old unit `superseded` and link its replacement. Inaccessible links, unparseable files, partially read sources, or unmapped executable units remain `[blocking]`; chunking does not reduce the final coverage set, and a summary cannot replace the source coverage map.
14
14
 
15
15
  Rewrite ambiguous behavior into comparable “input → output” or “trigger → result” form. Every question should contain:
16
16
 
@@ -13,7 +13,7 @@ comet native <group> <command> --help
13
13
  ## Next action returned by the Runtime
14
14
 
15
15
  - `disposition`: whether to continue, wait for the user, resolve a blocker, or finish.
16
- - `commandArgs`: the complete command arguments the Runtime requires.
16
+ - `commandArgs` / `commandAlternatives`: complete command arguments from the Runtime. Alternatives are complete commands for mutually exclusive user decisions; execute the matching one and do not combine them.
17
17
  - `inputOptions`: fields and a JSON template for this command.
18
18
  - `workspace` / `preparation`: the actual working directory and change-creation result.
19
19
  - `stateVersion` / `loop`: the current state version and acceptance Loop progress.
@@ -21,11 +21,11 @@ comet native <group> <command> --help
21
21
  - `verifierDispatch`: inputs needed to start an independent Verifier.
22
22
  - `workspaceFinishResult` / `recoveryArgs`: the post-Archive workspace result and recovery command.
23
23
 
24
- Angle brackets in a template mark values to fill in. `await-user` means wait for the user's decision before running an advancing command. `localExecution: absent` means only that this machine has no currently running local task; it does not mean the change is damaged.
24
+ Angle brackets in a template mark values to fill in. `await-user` means wait for the user's decision before running an advancing command. If `commandArgs` is `null` and `commandAlternatives` is present, confirm the user's decision, then execute the selected alternative's complete `commandArgs` while preserving `--expected-state-version` and `--expected-action`. If the command fails because the state or action binding is stale, reread the latest `continuation` and continue from the current state; do not construct an unguarded replacement command. `localExecution: absent` means only that this machine has no currently running local task; it does not mean the change is damaged.
25
25
 
26
26
  ## Fill command input
27
27
 
28
- Copy `inputOptions.template` into a temporary system JSON file, replace only the requested values, then execute `continuation.commandArgs`. Delete the temporary file afterward. Preserve the acceptance iteration, Verifier attempt, state version, and task identifiers already present in the template. Fill only the fields exposed by the template.
28
+ Copy `inputOptions.template` into a temporary system JSON file, replace only the requested values, then execute `continuation.commandArgs` or the selected `commandAlternative.commandArgs`. Delete the temporary file afterward. Preserve the acceptance iteration, Verifier attempt, state version, and task identifiers already present in the template. Fill only the fields exposed by the template.
29
29
 
30
30
  - `builder-handoff`: submit the implementation summary for this round, addressed acceptance IDs, development checks the Builder actually ran, and known limitations. Leave acceptance conclusions to the Verifier.
31
31
  - `dispatch-verifier`: list the checks the Runtime should execute for the current candidate. Submit an empty list when no command-based check applies.