waymark-cli 0.5.0__tar.gz → 0.6.0__tar.gz

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 (205) hide show
  1. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/CHANGELOG.md +77 -0
  2. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/PKG-INFO +27 -15
  3. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/README.md +26 -14
  4. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/docs/cli.md +50 -27
  5. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/docs/concepts.md +78 -39
  6. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/docs/getting-started.md +22 -15
  7. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/docs/json.md +99 -14
  8. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/docs/record.md +99 -51
  9. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/docs/skills.md +48 -27
  10. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/docs/smoke-test.md +74 -47
  11. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/src/waymark/__init__.py +1 -1
  12. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/src/waymark/assets/agents/wm-implementer.md +6 -5
  13. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/src/waymark/assets/agents/wm-reviewer.md +3 -2
  14. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/src/waymark/assets/skills/wm-apply/SKILL.md +20 -10
  15. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/src/waymark/assets/skills/wm-archive/SKILL.md +1 -1
  16. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/src/waymark/assets/skills/wm-explore/SKILL.md +1 -1
  17. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/src/waymark/assets/skills/wm-onboard/SKILL.md +2 -2
  18. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/src/waymark/assets/skills/wm-propose/SKILL.md +11 -8
  19. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/src/waymark/assets/skills/wm-update/SKILL.md +5 -5
  20. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/src/waymark/cli.py +100 -21
  21. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/src/waymark/hooks/decide.py +32 -4
  22. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/src/waymark/record/artifacts/changes.py +25 -4
  23. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/src/waymark/record/artifacts/milestones.py +16 -2
  24. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/src/waymark/record/artifacts/proposal.py +18 -6
  25. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/src/waymark/record/artifacts/tasks.py +56 -47
  26. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/src/waymark/record/evidence/records.py +166 -25
  27. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/src/waymark/record/state.py +50 -4
  28. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/src/waymark/record/terms.py +8 -0
  29. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/src/waymark/record/writing/edits.py +13 -12
  30. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/src/waymark/record/writing/layout.py +29 -3
  31. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/src/waymark/record/writing/templates/exploration.md +0 -5
  32. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/src/waymark/record/writing/templates/tasks.md +4 -4
  33. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/src/waymark/services/check.py +28 -2
  34. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/src/waymark/services/context.py +22 -9
  35. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/src/waymark/services/fix.py +5 -2
  36. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/src/waymark/services/guidance.py +13 -0
  37. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/src/waymark/services/instructions.py +53 -31
  38. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/src/waymark/services/lifecycle.py +229 -56
  39. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/src/waymark/services/pr.py +1 -0
  40. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/src/waymark/services/roadmap.py +11 -5
  41. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/src/waymark/services/setup.py +16 -2
  42. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/src/waymark/views/payloads.py +3 -2
  43. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/src/waymark/views/render.py +10 -2
  44. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/src/waymark/views/schemas.py +14 -3
  45. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/tests/adapters/snapshots/wm-implementer.md +6 -5
  46. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/tests/adapters/snapshots/wm-reviewer.md +3 -2
  47. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/tests/adapters/test_claude_code.py +7 -7
  48. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/tests/hooks/test_commands.py +1 -0
  49. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/tests/hooks/test_decide.py +114 -34
  50. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/tests/hooks/test_repo_limits.py +1 -1
  51. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/tests/record/artifacts/test_tasks.py +12 -8
  52. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/tests/record/evidence/test_evidence.py +7 -6
  53. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/tests/record/evidence/test_fingerprint.py +15 -12
  54. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/tests/record/evidence/test_records.py +116 -26
  55. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/tests/record/test_artifacts.py +17 -7
  56. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/tests/record/test_authored_formats.py +62 -15
  57. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/tests/record/test_state.py +10 -11
  58. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/tests/record/test_tasks_records.py +80 -11
  59. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/tests/services/test_agent_interface.py +121 -55
  60. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/tests/services/test_archive.py +50 -9
  61. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/tests/services/test_check.py +28 -25
  62. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/tests/services/test_ci_and_pr.py +14 -11
  63. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/tests/services/test_fix.py +32 -4
  64. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/tests/services/test_lifecycle.py +46 -38
  65. waymark_cli-0.6.0/tests/services/test_lifecycle_records.py +834 -0
  66. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/tests/services/test_milestones.py +3 -1
  67. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/tests/services/test_review_added_items.py +17 -17
  68. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/tests/services/test_roadmap.py +1 -1
  69. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/tests/services/test_setup.py +23 -7
  70. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/tests/support.py +7 -1
  71. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/tests/test_lifecycle_cli.py +5 -4
  72. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/tests/test_skills.py +14 -0
  73. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/tests/test_views_cli.py +9 -3
  74. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/tests/views/test_branches.py +1 -1
  75. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/tests/views/test_views.py +61 -27
  76. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/tools/docs.py +2 -1
  77. waymark_cli-0.5.0/tests/services/test_lifecycle_records.py +0 -359
  78. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/.gitignore +0 -0
  79. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/LICENSE +0 -0
  80. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/docs/architecture.md +0 -0
  81. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/docs/assets/banner-dark.svg +0 -0
  82. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/docs/assets/banner-light.svg +0 -0
  83. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/docs/assets/trail-dark.svg +0 -0
  84. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/docs/assets/trail-light.svg +0 -0
  85. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/docs/multi-repo.md +0 -0
  86. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/pyproject.toml +0 -0
  87. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/src/waymark/__main__.py +0 -0
  88. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/src/waymark/adapters/__init__.py +0 -0
  89. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/src/waymark/adapters/claude_code.py +0 -0
  90. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/src/waymark/assets/__init__.py +0 -0
  91. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/src/waymark/assets/skills/wm-kickoff/SKILL.md +0 -0
  92. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/src/waymark/assets/skills/wm-pr/SKILL.md +0 -0
  93. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/src/waymark/hooks/__init__.py +0 -0
  94. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/src/waymark/hooks/commands.py +0 -0
  95. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/src/waymark/hooks/events.py +0 -0
  96. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/src/waymark/py.typed +0 -0
  97. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/src/waymark/record/__init__.py +0 -0
  98. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/src/waymark/record/artifacts/__init__.py +0 -0
  99. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/src/waymark/record/artifacts/charter.py +0 -0
  100. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/src/waymark/record/artifacts/config.py +0 -0
  101. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/src/waymark/record/artifacts/deltas.py +0 -0
  102. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/src/waymark/record/artifacts/design.py +0 -0
  103. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/src/waymark/record/artifacts/explorations.py +0 -0
  104. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/src/waymark/record/artifacts/resources.py +0 -0
  105. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/src/waymark/record/artifacts/specs.py +0 -0
  106. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/src/waymark/record/evidence/__init__.py +0 -0
  107. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/src/waymark/record/evidence/agents.py +0 -0
  108. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/src/waymark/record/evidence/commits.py +0 -0
  109. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/src/waymark/record/evidence/evidence.py +0 -0
  110. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/src/waymark/record/evidence/fingerprint.py +0 -0
  111. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/src/waymark/record/machine/__init__.py +0 -0
  112. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/src/waymark/record/machine/atlas.py +0 -0
  113. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/src/waymark/record/machine/branches.py +0 -0
  114. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/src/waymark/record/machine/files.py +0 -0
  115. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/src/waymark/record/machine/git.py +0 -0
  116. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/src/waymark/record/machine/pointer.py +0 -0
  117. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/src/waymark/record/machine/project.py +0 -0
  118. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/src/waymark/record/machine/registry.py +0 -0
  119. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/src/waymark/record/markdown/__init__.py +0 -0
  120. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/src/waymark/record/markdown/labels.py +0 -0
  121. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/src/waymark/record/markdown/links.py +0 -0
  122. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/src/waymark/record/markdown/outline.py +0 -0
  123. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/src/waymark/record/markdown/problems.py +0 -0
  124. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/src/waymark/record/markdown/text.py +0 -0
  125. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/src/waymark/record/names.py +0 -0
  126. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/src/waymark/record/record.py +0 -0
  127. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/src/waymark/record/writing/__init__.py +0 -0
  128. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/src/waymark/record/writing/ignore.py +0 -0
  129. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/src/waymark/record/writing/moves.py +0 -0
  130. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/src/waymark/record/writing/store.py +0 -0
  131. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/src/waymark/record/writing/templates/charter.md +0 -0
  132. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/src/waymark/record/writing/templates/ci-workflow.yml +0 -0
  133. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/src/waymark/record/writing/templates/config-atlas.toml +0 -0
  134. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/src/waymark/record/writing/templates/config.toml +0 -0
  135. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/src/waymark/record/writing/templates/delta.md +0 -0
  136. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/src/waymark/record/writing/templates/design.md +0 -0
  137. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/src/waymark/record/writing/templates/milestone.md +0 -0
  138. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/src/waymark/record/writing/templates/proposal.md +0 -0
  139. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/src/waymark/record/writing/templates/resource.md +0 -0
  140. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/src/waymark/record/writing/templates.py +0 -0
  141. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/src/waymark/services/__init__.py +0 -0
  142. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/src/waymark/services/atlas.py +0 -0
  143. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/src/waymark/services/ci.py +0 -0
  144. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/src/waymark/services/common.py +0 -0
  145. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/src/waymark/services/doctor.py +0 -0
  146. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/src/waymark/services/integration.py +0 -0
  147. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/src/waymark/services/references.py +0 -0
  148. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/src/waymark/views/__init__.py +0 -0
  149. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/src/waymark/views/init_flow.py +0 -0
  150. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/src/waymark/views/prompts.py +0 -0
  151. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/src/waymark/views/style.py +0 -0
  152. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/src/waymark/views/terminal.py +0 -0
  153. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/src/waymark/views/welcome.py +0 -0
  154. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/tests/__init__.py +0 -0
  155. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/tests/adapters/__init__.py +0 -0
  156. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/tests/adapters/snapshots/settings.json +0 -0
  157. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/tests/adapters/test_integration.py +0 -0
  158. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/tests/conftest.py +0 -0
  159. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/tests/hooks/__init__.py +0 -0
  160. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/tests/record/__init__.py +0 -0
  161. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/tests/record/artifacts/__init__.py +0 -0
  162. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/tests/record/artifacts/test_config.py +0 -0
  163. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/tests/record/artifacts/test_deltas.py +0 -0
  164. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/tests/record/artifacts/test_resources.py +0 -0
  165. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/tests/record/artifacts/test_specs.py +0 -0
  166. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/tests/record/evidence/__init__.py +0 -0
  167. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/tests/record/evidence/test_agents.py +0 -0
  168. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/tests/record/evidence/test_commits.py +0 -0
  169. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/tests/record/machine/__init__.py +0 -0
  170. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/tests/record/machine/test_atlas.py +0 -0
  171. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/tests/record/machine/test_branches.py +0 -0
  172. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/tests/record/machine/test_git.py +0 -0
  173. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/tests/record/machine/test_project.py +0 -0
  174. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/tests/record/machine/test_registry.py +0 -0
  175. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/tests/record/markdown/__init__.py +0 -0
  176. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/tests/record/markdown/test_labels.py +0 -0
  177. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/tests/record/markdown/test_links.py +0 -0
  178. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/tests/record/markdown/test_text.py +0 -0
  179. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/tests/record/test_names.py +0 -0
  180. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/tests/record/test_platforms.py +0 -0
  181. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/tests/record/writing/__init__.py +0 -0
  182. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/tests/record/writing/test_ignore.py +0 -0
  183. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/tests/record/writing/test_layout.py +0 -0
  184. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/tests/record/writing/test_store.py +0 -0
  185. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/tests/services/__init__.py +0 -0
  186. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/tests/services/test_atlas.py +0 -0
  187. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/tests/services/test_doctor.py +0 -0
  188. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/tests/test_agent_cli.py +0 -0
  189. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/tests/test_atlas_cli.py +0 -0
  190. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/tests/test_cli.py +0 -0
  191. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/tests/test_constraints.py +0 -0
  192. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/tests/test_docs.py +0 -0
  193. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/tests/test_install_skills.py +0 -0
  194. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/tests/views/__init__.py +0 -0
  195. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/tests/views/test_prompts.py +0 -0
  196. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/tests/views/test_style.py +0 -0
  197. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/tests/views/test_terminal.py +0 -0
  198. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/tests/views/test_welcome.py +0 -0
  199. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/tests/views/validator.py +0 -0
  200. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/tools/__init__.py +0 -0
  201. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/tools/install_skills.py +0 -0
  202. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/tools/release.py +0 -0
  203. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/tools/skills/waymark-check-docs/SKILL.md +0 -0
  204. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/tools/skills/waymark-release/SKILL.md +0 -0
  205. {waymark_cli-0.5.0 → waymark_cli-0.6.0}/tools/skills/waymark-write-docs/SKILL.md +0 -0
@@ -2,6 +2,83 @@
2
2
 
3
3
  All notable changes to Waymark, one entry per release.
4
4
 
5
+ ## [0.6.0] - 2026-11-20
6
+
7
+ The record says who did what: items name the role that builds them, records name
8
+ who wrote them, ticks, archives and revisions are recorded, and records can be
9
+ lists.
10
+
11
+ - **Behavior change: an item's Build line names a role.** The roles are
12
+ `planner`, `implementer` and `human`. `implementer` replaces `delegate`, which
13
+ `wm check` now reports as unknown: change `- **Build:** delegate` to
14
+ `- **Build:** implementer` in any active change, then accept it again.
15
+ - **Behavior change: records name who wrote them by their kind.** Your acts
16
+ (`(accepted)`, `(override)`, `(resolved)`, `(archived)` and the tick of a `human`
17
+ item) name your git name. What the planner writes names `planner for <your
18
+ name>`, and an agent's ending names `implementer` or `reviewer` (they were
19
+ `wm-implementer` and `wm-reviewer`). `--by` still overrides it, and records
20
+ already written keep their names. An implementer's own `wm note` must say
21
+ `--by implementer`.
22
+ - **Behavior change: accepting again needs a revision.** `wm accept` refuses to
23
+ accept a change a second time until a `(revised)` record, written by the new
24
+ `wm revise`, follows its last acceptance.
25
+ - **Behavior change: a revised item goes back to apply.** When a `(revised)`
26
+ record names a ticked item that nothing reopened or ticked again since,
27
+ `wm instructions` makes its reopen the next step, before any review or archive,
28
+ `wm archive` refuses the change even with `--override`, and `wm check` warns as
29
+ `revised-ticked-item`.
30
+ - **Behavior change: every change has a Review line.** `wm new change` writes
31
+ `- **Review:** <level>` with the project's `default_review` (`self` on the
32
+ short path when the default is `independent`), and `wm check` reports an active
33
+ change without one as `missing-review`. The level is read from the line, so
34
+ changing `default_review` no longer changes the level of a change already
35
+ written.
36
+ - **Items only you can do.** A `- **Build:** human` item, such as filling in a
37
+ form, a manual test or setting up a platform, is handed to you by
38
+ `wm instructions` with its steps, and ticked by the planner after your yes. While
39
+ it waits, the planner blocks it and goes on with the other items. An
40
+ implementer started on one is refused, and the review pack and review guidance
41
+ name the items you did.
42
+ - **New command: `wm revise`.** `wm revise <change> "<why>" --parts <part>,...`
43
+ records why an accepted change was edited. It asks for `wm accept` only when
44
+ the acceptance was withdrawn.
45
+ - **Reopen any ticked item.** `wm reopen <change> <item> --reason "<why>"`
46
+ sends a ticked item back to apply even when no review names it, and the
47
+ `(reopened)` record carries the reason. Once ticked again after a passing
48
+ review, the item gets a review of its own.
49
+ - **New records.** `wm tick` writes `(ticked) <item>` and takes `--by`.
50
+ `wm archive` ends the change's own Log with `(archived)`.
51
+ - **Records as lists.** `wm note`, `wm block`, `wm gap`, `wm resolve`,
52
+ `wm review --self`, `wm verdict` and `wm revise` take a repeatable
53
+ `--detail "<text>"`, written as a sub-bullet under the record, after any
54
+ findings. Implementers and reviewers give details as `DETAIL:` lines before
55
+ their ending. A detail with a finding's shape, such as `warning: <text>`, is
56
+ refused. `wm check` reports a sub-line under a record that takes no details as
57
+ `misplaced-detail`.
58
+ - **Outcome as a list.** `wm archive` takes `--built` and `--differs` more than
59
+ once; several values are written as nested bullets under the label.
60
+ - **Skills ask less of you.** `wm-archive` shows the outcome it will write and
61
+ runs `wm archive` itself once you say yes, instead of asking you to type the
62
+ command. `wm-explore` and `wm-propose` label open questions Q1, Q2, options
63
+ A, B and closing offers 1 to 4, so an answer can't be mistaken for a choice.
64
+ `wm-propose` writes its own bold step names with the colon inside the bold,
65
+ as `wm check` expects of labels.
66
+ - **New explorations have no comment under their Status line.** The other
67
+ sections keep their comments and examples.
68
+ - **`wm check --fix` makes charter glossary entries bold.** An entry written
69
+ `- <term>: <meaning>` or `- **<term>**: <meaning>` becomes
70
+ `- **<term>:** <meaning>`.
71
+ - **JSON:** in `wm show --json`, at `show.change` version 5, each item has
72
+ `build` (`planner`, `implementer`, `human` or null) in place of `delegate`, and
73
+ each record has `details`. At version 4 of the implement and review packs,
74
+ each item carries its `build`, notes are objects with `text` and `details`,
75
+ earlier reviews have `details`, and the review pack has `human_items` and
76
+ `human_note`.
77
+ - **Record format:** unchanged. `wm` reads a 0.5.0 record as it is; only an
78
+ active change with `- **Build:** delegate` or no Review line needs editing.
79
+
80
+ Smoke test: passed on 2026-11-20 with Claude Code 2.1.330 on Windows 10.
81
+
5
82
  ## [0.5.0] - 2026-11-19
6
83
 
7
84
  Explorations get a lifecycle, and the record one style: bold labels, records
@@ -1,6 +1,6 @@
1
1
  Metadata-Version: 2.5
2
2
  Name: waymark-cli
3
- Version: 0.5.0
3
+ Version: 0.6.0
4
4
  Summary: Spec-driven development for coding agents, anchored in living specs.
5
5
  Project-URL: Repository, https://github.com/noahnkr/waymark
6
6
  Project-URL: Documentation, https://github.com/noahnkr/waymark/tree/main/docs
@@ -87,7 +87,7 @@ Here's how a change goes:
87
87
  Then it checks the whole change against the plan. For a risky change, a second
88
88
  agent that never saw the build does the check.
89
89
  - **Archive.** `/wm-archive` folds the spec edits into your specs and notes what
90
- was built. You run the command; it's your second sign-off.
90
+ was built. It runs once you say yes; that's your second sign-off.
91
91
  - **Merge.** `/wm-pr` opens a pull request with the code and the updated specs,
92
92
  once you say yes. You merge it.
93
93
 
@@ -112,8 +112,9 @@ Then, in Claude Code:
112
112
  - **`/wm-kickoff`** interviews you for the project's charter, one section at a time.
113
113
  - **`/wm-onboard`** takes one real, small change on your own code through every step.
114
114
 
115
- The package is `waymark-cli`; the command is `wm`. Commit `waymark/` and
116
- `.gitignore`; the skills, agents and hooks are set up per machine.
115
+ The package is `waymark-cli`; the command is `wm`. Commit `waymark/`,
116
+ `.gitignore`, and `.github/workflows/waymark.yml` if `wm init` added it; the
117
+ skills, agents and hooks are set up per machine.
117
118
 
118
119
  <details>
119
120
  <summary><strong>Setting up a new or existing project, in one repository or several</strong></summary>
@@ -149,10 +150,14 @@ You work through skills, as slash commands in Claude Code:
149
150
  | `/wm-archive` | Finish a change and update the specs |
150
151
  | `/wm-pr` | Open the pull request, once you say yes |
151
152
 
152
- `/wm-apply` can also hand work to two agents of its own: an implementer that
153
- builds one task you marked to hand off, and a reviewer that checks a risky
154
- change. [Skills and agents](docs/skills.md) covers what each one reads, writes
155
- and shows you.
153
+ Each task's `- **Build:**` line names who builds it: `planner` for your
154
+ session, which builds most tasks; `implementer` for a fresh agent that builds it
155
+ from the plan alone; or `human` for work only you can do, such as a manual test
156
+ or setting up a platform, which your session hands to you and ticks after your
157
+ yes ([who builds a task](docs/concepts.md#who-builds-an-item)). `/wm-apply`
158
+ starts the implementer, and a reviewer for a risky change.
159
+ [Skills and agents](docs/skills.md) covers what each one reads, writes and shows
160
+ you.
156
161
 
157
162
  ## See it in action
158
163
 
@@ -218,6 +223,7 @@ waymark/
218
223
  # Add dark mode
219
224
 
220
225
  - **Owner:** Alex Example
226
+ - **Review:** self
221
227
 
222
228
  ## Why
223
229
 
@@ -339,8 +345,12 @@ setting until the person picks one.
339
345
 
340
346
  ## Log
341
347
 
342
- - 2026-01-15 (accepted) fingerprint c6a1ef9b1c432c26 items 1.1, 1.2, 1.3 by Alex Example
343
- - 2026-01-15 (self-review) covers 1.1, 1.2, 1.3 by Alex Example: every criterion holds, and both scenarios have a test
348
+ - 2026-01-15 (accepted) fingerprint f80bacd71e28d538 items 1.1, 1.2, 1.3 by Alex Example
349
+ - 2026-01-15 (ticked) 1.1 by planner for Alex Example
350
+ - 2026-01-15 (ticked) 1.2 by planner for Alex Example
351
+ - 2026-01-15 (ticked) 1.3 by planner for Alex Example
352
+ - 2026-01-15 (self-review) covers 1.1, 1.2, 1.3 by planner for Alex Example: every criterion holds, and both scenarios have a test
353
+ - 2026-01-15 (archived) by Alex Example
344
354
  ```
345
355
 
346
356
  </details>
@@ -387,10 +397,11 @@ that can go in them.
387
397
  from that, the specs and the resources. If something's missing, it asks or
388
398
  writes it down instead of guessing.
389
399
  - **Every change gets checked.** When it's built, the whole change is checked
390
- against the plan, and what the check found stays with the change.
400
+ against the plan at its review level, and what the check found stays with the
401
+ change.
391
402
  - **Pick up anywhere.** Everything lives in files in your repository, so any
392
403
  session on any machine can see where things stand.
393
- - **Light for small work, thorough for big work.** A typo is just a commit. A
404
+ - **Light for small work, thorough for big work.** A typo takes your yes and one commit. A
394
405
  risky change gets a design and a second agent to review it.
395
406
 
396
407
  <details>
@@ -419,7 +430,8 @@ for organizations that need access control or approval chains.
419
430
 
420
431
  - Nothing is built until you accept the change.
421
432
  - A change can't be accepted while a design decision or question is still open.
422
- - A change can't be archived until every task is done and the change has been checked.
433
+ - A change can't be archived until every task is done and the review its level
434
+ asks for is recorded ([the gates](docs/concepts.md#the-gates)).
423
435
  - A check can't pass while it lists a critical problem.
424
436
  - Two changes that edit the same part of a spec are flagged before the second is archived.
425
437
  - `wm check`, run in CI, keeps every file in the record well formed.
@@ -452,7 +464,7 @@ edit the same requirement are caught once both are on the same branch. See
452
464
  never calls a model or goes online.
453
465
  - **Tokens:** most of the work happens in your normal session, which already
454
466
  knows the change. A fresh agent, which has to read the plan from scratch, is
455
- only started for a task you mark to hand off or for checking a risky change.
467
+ only started for an `implementer` task or for checking a risky change.
456
468
  - **Your time:** answering the agent's questions while it writes the plan,
457
469
  approving each change twice, and settling what `wm inbox` lists, such as a
458
470
  gap in the plan or a blocked task.
@@ -479,7 +491,7 @@ edit the same requirement are caught once both are on the same branch. See
479
491
  - **[Architecture](docs/architecture.md)**: how `wm` is built, and how to add an agent tool
480
492
  - **[Smoke test](docs/smoke-test.md)**: the manual walk-through before a release
481
493
 
482
- Works with Claude Code. Version last verified: **2.1.328**, on Windows.
494
+ Works with Claude Code. Version last verified: **2.1.330**, on Windows.
483
495
 
484
496
  ## License
485
497
 
@@ -58,7 +58,7 @@ Here's how a change goes:
58
58
  Then it checks the whole change against the plan. For a risky change, a second
59
59
  agent that never saw the build does the check.
60
60
  - **Archive.** `/wm-archive` folds the spec edits into your specs and notes what
61
- was built. You run the command; it's your second sign-off.
61
+ was built. It runs once you say yes; that's your second sign-off.
62
62
  - **Merge.** `/wm-pr` opens a pull request with the code and the updated specs,
63
63
  once you say yes. You merge it.
64
64
 
@@ -83,8 +83,9 @@ Then, in Claude Code:
83
83
  - **`/wm-kickoff`** interviews you for the project's charter, one section at a time.
84
84
  - **`/wm-onboard`** takes one real, small change on your own code through every step.
85
85
 
86
- The package is `waymark-cli`; the command is `wm`. Commit `waymark/` and
87
- `.gitignore`; the skills, agents and hooks are set up per machine.
86
+ The package is `waymark-cli`; the command is `wm`. Commit `waymark/`,
87
+ `.gitignore`, and `.github/workflows/waymark.yml` if `wm init` added it; the
88
+ skills, agents and hooks are set up per machine.
88
89
 
89
90
  <details>
90
91
  <summary><strong>Setting up a new or existing project, in one repository or several</strong></summary>
@@ -120,10 +121,14 @@ You work through skills, as slash commands in Claude Code:
120
121
  | `/wm-archive` | Finish a change and update the specs |
121
122
  | `/wm-pr` | Open the pull request, once you say yes |
122
123
 
123
- `/wm-apply` can also hand work to two agents of its own: an implementer that
124
- builds one task you marked to hand off, and a reviewer that checks a risky
125
- change. [Skills and agents](docs/skills.md) covers what each one reads, writes
126
- and shows you.
124
+ Each task's `- **Build:**` line names who builds it: `planner` for your
125
+ session, which builds most tasks; `implementer` for a fresh agent that builds it
126
+ from the plan alone; or `human` for work only you can do, such as a manual test
127
+ or setting up a platform, which your session hands to you and ticks after your
128
+ yes ([who builds a task](docs/concepts.md#who-builds-an-item)). `/wm-apply`
129
+ starts the implementer, and a reviewer for a risky change.
130
+ [Skills and agents](docs/skills.md) covers what each one reads, writes and shows
131
+ you.
127
132
 
128
133
  ## See it in action
129
134
 
@@ -189,6 +194,7 @@ waymark/
189
194
  # Add dark mode
190
195
 
191
196
  - **Owner:** Alex Example
197
+ - **Review:** self
192
198
 
193
199
  ## Why
194
200
 
@@ -310,8 +316,12 @@ setting until the person picks one.
310
316
 
311
317
  ## Log
312
318
 
313
- - 2026-01-15 (accepted) fingerprint c6a1ef9b1c432c26 items 1.1, 1.2, 1.3 by Alex Example
314
- - 2026-01-15 (self-review) covers 1.1, 1.2, 1.3 by Alex Example: every criterion holds, and both scenarios have a test
319
+ - 2026-01-15 (accepted) fingerprint f80bacd71e28d538 items 1.1, 1.2, 1.3 by Alex Example
320
+ - 2026-01-15 (ticked) 1.1 by planner for Alex Example
321
+ - 2026-01-15 (ticked) 1.2 by planner for Alex Example
322
+ - 2026-01-15 (ticked) 1.3 by planner for Alex Example
323
+ - 2026-01-15 (self-review) covers 1.1, 1.2, 1.3 by planner for Alex Example: every criterion holds, and both scenarios have a test
324
+ - 2026-01-15 (archived) by Alex Example
315
325
  ```
316
326
 
317
327
  </details>
@@ -358,10 +368,11 @@ that can go in them.
358
368
  from that, the specs and the resources. If something's missing, it asks or
359
369
  writes it down instead of guessing.
360
370
  - **Every change gets checked.** When it's built, the whole change is checked
361
- against the plan, and what the check found stays with the change.
371
+ against the plan at its review level, and what the check found stays with the
372
+ change.
362
373
  - **Pick up anywhere.** Everything lives in files in your repository, so any
363
374
  session on any machine can see where things stand.
364
- - **Light for small work, thorough for big work.** A typo is just a commit. A
375
+ - **Light for small work, thorough for big work.** A typo takes your yes and one commit. A
365
376
  risky change gets a design and a second agent to review it.
366
377
 
367
378
  <details>
@@ -390,7 +401,8 @@ for organizations that need access control or approval chains.
390
401
 
391
402
  - Nothing is built until you accept the change.
392
403
  - A change can't be accepted while a design decision or question is still open.
393
- - A change can't be archived until every task is done and the change has been checked.
404
+ - A change can't be archived until every task is done and the review its level
405
+ asks for is recorded ([the gates](docs/concepts.md#the-gates)).
394
406
  - A check can't pass while it lists a critical problem.
395
407
  - Two changes that edit the same part of a spec are flagged before the second is archived.
396
408
  - `wm check`, run in CI, keeps every file in the record well formed.
@@ -423,7 +435,7 @@ edit the same requirement are caught once both are on the same branch. See
423
435
  never calls a model or goes online.
424
436
  - **Tokens:** most of the work happens in your normal session, which already
425
437
  knows the change. A fresh agent, which has to read the plan from scratch, is
426
- only started for a task you mark to hand off or for checking a risky change.
438
+ only started for an `implementer` task or for checking a risky change.
427
439
  - **Your time:** answering the agent's questions while it writes the plan,
428
440
  approving each change twice, and settling what `wm inbox` lists, such as a
429
441
  gap in the plan or a blocked task.
@@ -450,7 +462,7 @@ edit the same requirement are caught once both are on the same branch. See
450
462
  - **[Architecture](docs/architecture.md)**: how `wm` is built, and how to add an agent tool
451
463
  - **[Smoke test](docs/smoke-test.md)**: the manual walk-through before a release
452
464
 
453
- Works with Claude Code. Version last verified: **2.1.328**, on Windows.
465
+ Works with Claude Code. Version last verified: **2.1.330**, on Windows.
454
466
 
455
467
  ## License
456
468
 
@@ -2,7 +2,7 @@
2
2
 
3
3
  <!-- Generated by tools/docs.py from the code. Don't edit it by hand. -->
4
4
 
5
- Every command of `wm` 0.5.0. Read commands take `--json`; their payloads are described in the [JSON schema reference](json.md).
5
+ Every command of `wm` 0.6.0. Read commands take `--json`; their payloads are described in the [JSON schema reference](json.md).
6
6
 
7
7
  Exit codes: `0` success; `1` refused, or problems found; `2` usage error.
8
8
 
@@ -121,7 +121,7 @@ wm hook <tool> <event>
121
121
  Create a change, milestone, exploration or resource from the built-in template.
122
122
 
123
123
  ```
124
- wm new <change|milestone|exploration|resource> <name> [resource-kind] [--short] [--owner NAME] [--milestone MILESTONE] [--after CHANGE] [--from EXPLORATION]
124
+ wm new <change|milestone|exploration|resource> <name> [resource-kind] [--short] [--owner NAME] [--milestone MILESTONE] [--after CHANGE] [--from EXPLORATION] [--by NAME]
125
125
  ```
126
126
 
127
127
  - `kind`: one of `change`, `milestone`, `exploration`, `resource`
@@ -132,6 +132,7 @@ wm new <change|milestone|exploration|resource> <name> [resource-kind] [--short]
132
132
  - `--milestone`: the milestone a change belongs to; links it from the milestone's roadmap
133
133
  - `--after`: the change this one comes after; its unmerged branch is this one's base
134
134
  - `--from`: the exploration a change or milestone comes from; its status then leads to it
135
+ - `--by`: who the (proposed) record in a change's milestone names as its writer (default: "planner for <your git name>")
135
136
 
136
137
  ## wm accept
137
138
 
@@ -142,77 +143,96 @@ wm accept <change> [--by NAME]
142
143
  ```
143
144
 
144
145
  - `change`: the change's name
145
- - `--by`: who the record names as its writer (default: your git name)
146
+ - `--by`: who the record names as its writer (default: your git name for your own acts, "planner for <your git name>" for what the planner writes)
146
147
 
147
148
  ## wm tick
148
149
 
149
150
  Tick an item: it has been applied.
150
151
 
151
152
  ```
152
- wm tick <change> <item>
153
+ wm tick <change> <item> [--by NAME]
153
154
  ```
154
155
 
155
156
  - `change`: the change's name
156
157
  - `item`: the item's number, for example 1.2
158
+ - `--by`: who the record names as its writer (default: your git name for your own acts, "planner for <your git name>" for what the planner writes)
157
159
 
158
160
  ## wm block
159
161
 
160
162
  Record that an item is blocked.
161
163
 
162
164
  ```
163
- wm block <change> <item> <reason> [--by NAME]
165
+ wm block <change> <item> <reason> [--by NAME] [--detail TEXT]
164
166
  ```
165
167
 
166
168
  - `change`: the change's name
167
169
  - `item`: the item's number, for example 1.2
168
170
  - `reason`: why it is blocked
169
- - `--by`: who the record names as its writer (default: your git name)
171
+ - `--by`: who the record names as its writer (default: your git name for your own acts, "planner for <your git name>" for what the planner writes)
172
+ - `--detail`: a point written as a sub-bullet under the record, in the order given; repeatable
170
173
 
171
174
  ## wm gap
172
175
 
173
176
  Record a spec gap: the record wasn't enough to build an item.
174
177
 
175
178
  ```
176
- wm gap <change> <item> <note> [--by NAME]
179
+ wm gap <change> <item> <note> [--by NAME] [--detail TEXT]
177
180
  ```
178
181
 
179
182
  - `change`: the change's name
180
183
  - `item`: the item's number, for example 1.2
181
184
  - `note`: what is missing from the record
182
- - `--by`: who the record names as its writer (default: your git name)
185
+ - `--by`: who the record names as its writer (default: your git name for your own acts, "planner for <your git name>" for what the planner writes)
186
+ - `--detail`: a point written as a sub-bullet under the record, in the order given; repeatable
183
187
 
184
188
  ## wm note
185
189
 
186
190
  Write a note about an item still to be finished, such as a partial result, in the change's Log.
187
191
 
188
192
  ```
189
- wm note <change> <item> <text> [--by NAME]
193
+ wm note <change> <item> <text> [--by NAME] [--detail TEXT]
190
194
  ```
191
195
 
192
196
  - `change`: the change's name
193
197
  - `item`: the item's number, for example 1.2
194
198
  - `text`: the note
195
- - `--by`: who the record names as its writer (default: your git name)
199
+ - `--by`: who the record names as its writer (default: your git name for your own acts, "planner for <your git name>" for what the planner writes)
200
+ - `--detail`: a point written as a sub-bullet under the record, in the order given; repeatable
201
+
202
+ ## wm revise
203
+
204
+ Record why an accepted change was edited, before the human accepts it again.
205
+
206
+ ```
207
+ wm revise <change> <why> [--parts PARTS] [--by NAME] [--detail TEXT]
208
+ ```
209
+
210
+ - `change`: the change's name
211
+ - `why`: what the edit changed, and why
212
+ - `--parts`: the parts it changed, separated by commas: item numbers, "proposal", "design" or "specs/<area>"
213
+ - `--by`: who the record names as its writer (default: your git name for your own acts, "planner for <your git name>" for what the planner writes)
214
+ - `--detail`: a point written as a sub-bullet under the record, in the order given; repeatable
196
215
 
197
216
  ## wm review
198
217
 
199
218
  Record a self-review of a change, once every item is ticked.
200
219
 
201
220
  ```
202
- wm review <change> --self SUMMARY [--finding FINDING] [--by NAME]
221
+ wm review <change> --self SUMMARY [--finding FINDING] [--by NAME] [--detail TEXT]
203
222
  ```
204
223
 
205
224
  - `change`: the change's name
206
225
  - `--self`: what the review checked and found (required)
207
226
  - `--finding`: a finding, written <critical|warning|suggestion>: <place>: <text>; repeatable
208
- - `--by`: who the record names as its writer (default: your git name)
227
+ - `--by`: who the record names as its writer (default: your git name for your own acts, "planner for <your git name>" for what the planner writes)
228
+ - `--detail`: a point written as a sub-bullet under the record, in the order given; repeatable
209
229
 
210
230
  ## wm verdict
211
231
 
212
232
  Record a reviewer's verdict on a change.
213
233
 
214
234
  ```
215
- wm verdict <change> <pass|changes|spec-gap> <reasons> [--items ITEM] [--finding FINDING] [--by NAME]
235
+ wm verdict <change> <pass|changes|spec-gap> <reasons> [--items ITEM] [--finding FINDING] [--by NAME] [--detail TEXT]
216
236
  ```
217
237
 
218
238
  - `change`: the change's name
@@ -220,32 +240,35 @@ wm verdict <change> <pass|changes|spec-gap> <reasons> [--items ITEM] [--finding
220
240
  - `reasons`: the reviewer's reasons
221
241
  - `--items`: the items to rebuild; a "changes" verdict names at least one
222
242
  - `--finding`: a finding, written <critical|warning|suggestion>: <place>: <text>; repeatable
223
- - `--by`: who the record names as its writer (default: your git name)
243
+ - `--by`: who the record names as its writer (default: your git name for your own acts, "planner for <your git name>" for what the planner writes)
244
+ - `--detail`: a point written as a sub-bullet under the record, in the order given; repeatable
224
245
 
225
246
  ## wm reopen
226
247
 
227
- Reopen an item that a review of its change named to rebuild.
248
+ Reopen an item that a review of its change named to rebuild, or any ticked item given a reason.
228
249
 
229
250
  ```
230
- wm reopen <change> <item> [--by NAME]
251
+ wm reopen <change> <item> [--reason TEXT] [--by NAME]
231
252
  ```
232
253
 
233
254
  - `change`: the change's name
234
255
  - `item`: the item's number, for example 1.2
235
- - `--by`: who the record names as its writer (default: your git name)
256
+ - `--reason`: why the item goes back to apply; needed when no review names it
257
+ - `--by`: who the record names as its writer (default: your git name for your own acts, "planner for <your git name>" for what the planner writes)
236
258
 
237
259
  ## wm resolve
238
260
 
239
261
  Record what was decided about an item or a change's review that went to the human, and free it.
240
262
 
241
263
  ```
242
- wm resolve <change> <item> <decision> [--by NAME]
264
+ wm resolve <change> <item> <decision> [--by NAME] [--detail TEXT]
243
265
  ```
244
266
 
245
267
  - `change`: the change's name
246
268
  - `item`: the item's number, or "review" for the change's review
247
269
  - `decision`: what was decided
248
- - `--by`: who the record names as its writer (default: your git name)
270
+ - `--by`: who the record names as its writer (default: your git name for your own acts, "planner for <your git name>" for what the planner writes)
271
+ - `--detail`: a point written as a sub-bullet under the record, in the order given; repeatable
249
272
 
250
273
  ## wm sync
251
274
 
@@ -256,21 +279,21 @@ wm sync <change> [--by NAME]
256
279
  ```
257
280
 
258
281
  - `change`: the change's name
259
- - `--by`: who the record names as its writer (default: your git name)
282
+ - `--by`: who the record names as its writer (default: your git name for your own acts, "planner for <your git name>" for what the planner writes)
260
283
 
261
284
  ## wm archive
262
285
 
263
- Archive an applied change. For the human to run.
286
+ Archive an applied change, once the human says yes.
264
287
 
265
288
  ```
266
289
  wm archive <change> [--built TEXT] [--differs TEXT] [--override REASON] [--by NAME]
267
290
  ```
268
291
 
269
292
  - `change`: the change's name
270
- - `--built`: what was built, for the outcome
271
- - `--differs`: how it differs from the proposal; none when left out
293
+ - `--built`: what was built, for the outcome; repeatable, for a list
294
+ - `--differs`: how it differs from the proposal, none when left out; repeatable, for a list
272
295
  - `--override`: archive although review records are missing; the reason is recorded
273
- - `--by`: who the record names as its writer (default: your git name)
296
+ - `--by`: who the record names as its writer (default: your git name for your own acts, "planner for <your git name>" for what the planner writes)
274
297
 
275
298
  ## wm close
276
299
 
@@ -301,7 +324,7 @@ wm roadmap add <milestone> <change> <description> [--by NAME]
301
324
  - `milestone`: the milestone's name
302
325
  - `change`: the change's name, for example add-search-limit
303
326
  - `description`: what the change delivers toward the goal
304
- - `--by`: who the record names as its writer (default: your git name)
327
+ - `--by`: who the record names as its writer (default: your git name for your own acts, "planner for <your git name>" for what the planner writes)
305
328
 
306
329
  ## wm roadmap drop
307
330
 
@@ -314,7 +337,7 @@ wm roadmap drop <milestone> <change> --reason REASON [--by NAME]
314
337
  - `milestone`: the milestone's name
315
338
  - `change`: the change's name
316
339
  - `--reason`: why the change is dropped (required)
317
- - `--by`: who the record names as its writer (default: your git name)
340
+ - `--by`: who the record names as its writer (default: your git name for your own acts, "planner for <your git name>" for what the planner writes)
318
341
 
319
342
  ## wm roadmap move
320
343
 
@@ -328,7 +351,7 @@ wm roadmap move <milestone> <change> [--after CHANGE] [--first] [--by NAME]
328
351
  - `change`: the change's name
329
352
  - `--after`: put it right after this change's line
330
353
  - `--first`: put it at the top of the roadmap
331
- - `--by`: who the record names as its writer (default: your git name)
354
+ - `--by`: who the record names as its writer (default: your git name for your own acts, "planner for <your git name>" for what the planner writes)
332
355
 
333
356
  ## wm exploration
334
357