waymark-cli 0.2.0__tar.gz → 0.4.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 (213) hide show
  1. {waymark_cli-0.2.0 → waymark_cli-0.4.0}/CHANGELOG.md +123 -2
  2. {waymark_cli-0.2.0 → waymark_cli-0.4.0}/PKG-INFO +28 -16
  3. {waymark_cli-0.2.0 → waymark_cli-0.4.0}/README.md +27 -15
  4. {waymark_cli-0.2.0 → waymark_cli-0.4.0}/docs/architecture.md +21 -7
  5. {waymark_cli-0.2.0 → waymark_cli-0.4.0}/docs/cli.md +70 -9
  6. {waymark_cli-0.2.0 → waymark_cli-0.4.0}/docs/concepts.md +60 -11
  7. {waymark_cli-0.2.0 → waymark_cli-0.4.0}/docs/getting-started.md +43 -27
  8. {waymark_cli-0.2.0 → waymark_cli-0.4.0}/docs/json.md +402 -4
  9. {waymark_cli-0.2.0 → waymark_cli-0.4.0}/docs/multi-repo.md +0 -6
  10. {waymark_cli-0.2.0 → waymark_cli-0.4.0}/docs/record.md +139 -16
  11. {waymark_cli-0.2.0 → waymark_cli-0.4.0}/docs/skills.md +45 -51
  12. {waymark_cli-0.2.0 → waymark_cli-0.4.0}/docs/smoke-test.md +28 -6
  13. {waymark_cli-0.2.0 → waymark_cli-0.4.0}/pyproject.toml +3 -1
  14. {waymark_cli-0.2.0 → waymark_cli-0.4.0}/src/waymark/__init__.py +1 -1
  15. {waymark_cli-0.2.0 → waymark_cli-0.4.0}/src/waymark/adapters/__init__.py +10 -0
  16. {waymark_cli-0.2.0 → waymark_cli-0.4.0}/src/waymark/adapters/claude_code.py +6 -1
  17. {waymark_cli-0.2.0 → waymark_cli-0.4.0}/src/waymark/assets/__init__.py +0 -1
  18. {waymark_cli-0.2.0 → waymark_cli-0.4.0}/src/waymark/assets/agents/wm-implementer.md +1 -1
  19. {waymark_cli-0.2.0 → waymark_cli-0.4.0}/src/waymark/assets/agents/wm-reviewer.md +3 -2
  20. {waymark_cli-0.2.0 → waymark_cli-0.4.0}/src/waymark/assets/skills/wm-apply/SKILL.md +6 -4
  21. {waymark_cli-0.2.0 → waymark_cli-0.4.0}/src/waymark/assets/skills/wm-archive/SKILL.md +2 -2
  22. {waymark_cli-0.2.0 → waymark_cli-0.4.0}/src/waymark/assets/skills/wm-explore/SKILL.md +6 -7
  23. {waymark_cli-0.2.0 → waymark_cli-0.4.0}/src/waymark/assets/skills/wm-kickoff/SKILL.md +1 -1
  24. {waymark_cli-0.2.0 → waymark_cli-0.4.0}/src/waymark/assets/skills/wm-onboard/SKILL.md +3 -3
  25. {waymark_cli-0.2.0 → waymark_cli-0.4.0}/src/waymark/assets/skills/wm-pr/SKILL.md +3 -3
  26. waymark_cli-0.4.0/src/waymark/assets/skills/wm-propose/SKILL.md +97 -0
  27. {waymark_cli-0.2.0 → waymark_cli-0.4.0}/src/waymark/assets/skills/wm-update/SKILL.md +1 -1
  28. {waymark_cli-0.2.0 → waymark_cli-0.4.0}/src/waymark/cli.py +144 -10
  29. {waymark_cli-0.2.0 → waymark_cli-0.4.0}/src/waymark/hooks/decide.py +17 -10
  30. waymark_cli-0.4.0/src/waymark/record/artifacts/__init__.py +1 -0
  31. {waymark_cli-0.2.0/src/waymark/record → waymark_cli-0.4.0/src/waymark/record/artifacts}/changes.py +9 -31
  32. {waymark_cli-0.2.0/src/waymark/record → waymark_cli-0.4.0/src/waymark/record/artifacts}/charter.py +9 -52
  33. {waymark_cli-0.2.0/src/waymark/record → waymark_cli-0.4.0/src/waymark/record/artifacts}/config.py +11 -2
  34. {waymark_cli-0.2.0/src/waymark/record → waymark_cli-0.4.0/src/waymark/record/artifacts}/deltas.py +68 -21
  35. {waymark_cli-0.2.0/src/waymark/record → waymark_cli-0.4.0/src/waymark/record/artifacts}/design.py +3 -3
  36. {waymark_cli-0.2.0/src/waymark/record → waymark_cli-0.4.0/src/waymark/record/artifacts}/explorations.py +3 -3
  37. waymark_cli-0.4.0/src/waymark/record/artifacts/milestones.py +204 -0
  38. {waymark_cli-0.2.0/src/waymark/record → waymark_cli-0.4.0/src/waymark/record/artifacts}/proposal.py +27 -16
  39. waymark_cli-0.4.0/src/waymark/record/artifacts/resources.py +197 -0
  40. {waymark_cli-0.2.0/src/waymark/record → waymark_cli-0.4.0/src/waymark/record/artifacts}/specs.py +24 -5
  41. {waymark_cli-0.2.0/src/waymark/record → waymark_cli-0.4.0/src/waymark/record/artifacts}/tasks.py +24 -40
  42. waymark_cli-0.4.0/src/waymark/record/evidence/__init__.py +1 -0
  43. {waymark_cli-0.2.0/src/waymark/record → waymark_cli-0.4.0/src/waymark/record/evidence}/agents.py +1 -1
  44. {waymark_cli-0.2.0/src/waymark/record → waymark_cli-0.4.0/src/waymark/record/evidence}/evidence.py +39 -6
  45. {waymark_cli-0.2.0/src/waymark/record → waymark_cli-0.4.0/src/waymark/record/evidence}/fingerprint.py +5 -5
  46. {waymark_cli-0.2.0/src/waymark/record → waymark_cli-0.4.0/src/waymark/record/evidence}/records.py +170 -17
  47. waymark_cli-0.4.0/src/waymark/record/machine/__init__.py +1 -0
  48. {waymark_cli-0.2.0/src/waymark/record → waymark_cli-0.4.0/src/waymark/record/machine}/atlas.py +7 -14
  49. waymark_cli-0.4.0/src/waymark/record/machine/branches.py +83 -0
  50. {waymark_cli-0.2.0/src/waymark/record → waymark_cli-0.4.0/src/waymark/record/machine}/files.py +12 -2
  51. {waymark_cli-0.2.0/src/waymark/record → waymark_cli-0.4.0/src/waymark/record/machine}/git.py +48 -0
  52. {waymark_cli-0.2.0/src/waymark/record → waymark_cli-0.4.0/src/waymark/record/machine}/pointer.py +17 -28
  53. {waymark_cli-0.2.0/src/waymark/record → waymark_cli-0.4.0/src/waymark/record/machine}/project.py +15 -23
  54. {waymark_cli-0.2.0/src/waymark/record → waymark_cli-0.4.0/src/waymark/record/machine}/registry.py +2 -2
  55. waymark_cli-0.4.0/src/waymark/record/markdown/__init__.py +1 -0
  56. {waymark_cli-0.2.0/src/waymark/record → waymark_cli-0.4.0/src/waymark/record/markdown}/links.py +2 -2
  57. {waymark_cli-0.2.0/src/waymark/record → waymark_cli-0.4.0/src/waymark/record/markdown}/outline.py +4 -7
  58. {waymark_cli-0.2.0 → waymark_cli-0.4.0}/src/waymark/record/record.py +40 -37
  59. {waymark_cli-0.2.0 → waymark_cli-0.4.0}/src/waymark/record/state.py +87 -21
  60. waymark_cli-0.4.0/src/waymark/record/writing/__init__.py +1 -0
  61. {waymark_cli-0.2.0/src/waymark/record → waymark_cli-0.4.0/src/waymark/record/writing}/edits.py +3 -10
  62. {waymark_cli-0.2.0/src/waymark/record → waymark_cli-0.4.0/src/waymark/record/writing}/ignore.py +1 -1
  63. {waymark_cli-0.2.0/src/waymark/record → waymark_cli-0.4.0/src/waymark/record/writing}/layout.py +2 -2
  64. {waymark_cli-0.2.0/src/waymark/record → waymark_cli-0.4.0/src/waymark/record/writing}/moves.py +4 -4
  65. {waymark_cli-0.2.0/src/waymark/record → waymark_cli-0.4.0/src/waymark/record/writing}/store.py +26 -2
  66. {waymark_cli-0.2.0/src/waymark/record → waymark_cli-0.4.0/src/waymark/record/writing}/templates/charter.md +5 -18
  67. {waymark_cli-0.2.0/src/waymark/record → waymark_cli-0.4.0/src/waymark/record/writing}/templates/config.toml +1 -1
  68. {waymark_cli-0.2.0/src/waymark/record → waymark_cli-0.4.0/src/waymark/record/writing}/templates/delta.md +9 -0
  69. waymark_cli-0.4.0/src/waymark/record/writing/templates/resource.md +48 -0
  70. {waymark_cli-0.2.0/src/waymark/record → waymark_cli-0.4.0/src/waymark/record/writing}/templates.py +2 -1
  71. {waymark_cli-0.2.0 → waymark_cli-0.4.0}/src/waymark/services/atlas.py +15 -26
  72. waymark_cli-0.4.0/src/waymark/services/check.py +291 -0
  73. {waymark_cli-0.2.0 → waymark_cli-0.4.0}/src/waymark/services/ci.py +3 -3
  74. {waymark_cli-0.2.0 → waymark_cli-0.4.0}/src/waymark/services/common.py +8 -11
  75. {waymark_cli-0.2.0 → waymark_cli-0.4.0}/src/waymark/services/context.py +92 -17
  76. {waymark_cli-0.2.0 → waymark_cli-0.4.0}/src/waymark/services/doctor.py +21 -33
  77. {waymark_cli-0.2.0 → waymark_cli-0.4.0}/src/waymark/services/fix.py +11 -11
  78. {waymark_cli-0.2.0 → waymark_cli-0.4.0}/src/waymark/services/instructions.py +45 -9
  79. {waymark_cli-0.2.0 → waymark_cli-0.4.0}/src/waymark/services/integration.py +62 -20
  80. {waymark_cli-0.2.0 → waymark_cli-0.4.0}/src/waymark/services/lifecycle.py +81 -27
  81. {waymark_cli-0.2.0 → waymark_cli-0.4.0}/src/waymark/services/pr.py +16 -8
  82. {waymark_cli-0.2.0 → waymark_cli-0.4.0}/src/waymark/services/references.py +4 -4
  83. waymark_cli-0.4.0/src/waymark/services/roadmap.py +191 -0
  84. {waymark_cli-0.2.0 → waymark_cli-0.4.0}/src/waymark/services/setup.py +127 -41
  85. waymark_cli-0.4.0/src/waymark/views/init_flow.py +128 -0
  86. {waymark_cli-0.2.0 → waymark_cli-0.4.0}/src/waymark/views/payloads.py +69 -16
  87. waymark_cli-0.4.0/src/waymark/views/prompts.py +229 -0
  88. {waymark_cli-0.2.0 → waymark_cli-0.4.0}/src/waymark/views/render.py +228 -96
  89. {waymark_cli-0.2.0 → waymark_cli-0.4.0}/src/waymark/views/schemas.py +55 -1
  90. waymark_cli-0.4.0/src/waymark/views/style.py +186 -0
  91. waymark_cli-0.4.0/src/waymark/views/terminal.py +256 -0
  92. waymark_cli-0.4.0/src/waymark/views/welcome.py +205 -0
  93. {waymark_cli-0.2.0 → waymark_cli-0.4.0}/tests/adapters/snapshots/wm-implementer.md +1 -1
  94. {waymark_cli-0.2.0 → waymark_cli-0.4.0}/tests/adapters/snapshots/wm-reviewer.md +3 -2
  95. {waymark_cli-0.2.0 → waymark_cli-0.4.0}/tests/adapters/test_claude_code.py +6 -3
  96. {waymark_cli-0.2.0 → waymark_cli-0.4.0}/tests/adapters/test_integration.py +157 -22
  97. {waymark_cli-0.2.0 → waymark_cli-0.4.0}/tests/hooks/test_commands.py +1 -0
  98. {waymark_cli-0.2.0 → waymark_cli-0.4.0}/tests/hooks/test_decide.py +126 -5
  99. waymark_cli-0.4.0/tests/record/artifacts/__init__.py +0 -0
  100. {waymark_cli-0.2.0/tests/record → waymark_cli-0.4.0/tests/record/artifacts}/test_config.py +4 -4
  101. {waymark_cli-0.2.0/tests/record → waymark_cli-0.4.0/tests/record/artifacts}/test_deltas.py +67 -2
  102. waymark_cli-0.4.0/tests/record/artifacts/test_resources.py +114 -0
  103. {waymark_cli-0.2.0/tests/record → waymark_cli-0.4.0/tests/record/artifacts}/test_specs.py +1 -1
  104. {waymark_cli-0.2.0/tests/record → waymark_cli-0.4.0/tests/record/artifacts}/test_tasks.py +4 -11
  105. waymark_cli-0.4.0/tests/record/evidence/__init__.py +0 -0
  106. {waymark_cli-0.2.0/tests/record → waymark_cli-0.4.0/tests/record/evidence}/test_agents.py +1 -1
  107. {waymark_cli-0.2.0/tests/record → waymark_cli-0.4.0/tests/record/evidence}/test_commits.py +1 -1
  108. {waymark_cli-0.2.0/tests/record → waymark_cli-0.4.0/tests/record/evidence}/test_evidence.py +34 -2
  109. {waymark_cli-0.2.0/tests/record → waymark_cli-0.4.0/tests/record/evidence}/test_fingerprint.py +2 -2
  110. {waymark_cli-0.2.0/tests/record → waymark_cli-0.4.0/tests/record/evidence}/test_records.py +92 -5
  111. waymark_cli-0.4.0/tests/record/machine/__init__.py +0 -0
  112. {waymark_cli-0.2.0/tests/record → waymark_cli-0.4.0/tests/record/machine}/test_atlas.py +6 -77
  113. waymark_cli-0.4.0/tests/record/machine/test_branches.py +156 -0
  114. {waymark_cli-0.2.0/tests/record → waymark_cli-0.4.0/tests/record/machine}/test_git.py +17 -1
  115. {waymark_cli-0.2.0/tests/record → waymark_cli-0.4.0/tests/record/machine}/test_project.py +8 -11
  116. {waymark_cli-0.2.0/tests/record → waymark_cli-0.4.0/tests/record/machine}/test_registry.py +1 -1
  117. waymark_cli-0.4.0/tests/record/markdown/__init__.py +0 -0
  118. {waymark_cli-0.2.0/tests/record → waymark_cli-0.4.0/tests/record/markdown}/test_links.py +1 -1
  119. {waymark_cli-0.2.0 → waymark_cli-0.4.0}/tests/record/test_artifacts.py +66 -19
  120. {waymark_cli-0.2.0 → waymark_cli-0.4.0}/tests/record/test_authored_formats.py +60 -7
  121. {waymark_cli-0.2.0 → waymark_cli-0.4.0}/tests/record/test_platforms.py +2 -2
  122. {waymark_cli-0.2.0 → waymark_cli-0.4.0}/tests/record/test_state.py +0 -10
  123. waymark_cli-0.2.0/tests/record/test_tasks_format2.py → waymark_cli-0.4.0/tests/record/test_tasks_records.py +12 -26
  124. waymark_cli-0.4.0/tests/record/writing/__init__.py +0 -0
  125. {waymark_cli-0.2.0/tests/record → waymark_cli-0.4.0/tests/record/writing}/test_ignore.py +1 -1
  126. {waymark_cli-0.2.0/tests/record → waymark_cli-0.4.0/tests/record/writing}/test_layout.py +1 -1
  127. {waymark_cli-0.2.0/tests/record → waymark_cli-0.4.0/tests/record/writing}/test_store.py +24 -3
  128. {waymark_cli-0.2.0 → waymark_cli-0.4.0}/tests/services/test_agent_interface.py +332 -17
  129. {waymark_cli-0.2.0 → waymark_cli-0.4.0}/tests/services/test_archive.py +37 -0
  130. {waymark_cli-0.2.0 → waymark_cli-0.4.0}/tests/services/test_atlas.py +20 -46
  131. {waymark_cli-0.2.0 → waymark_cli-0.4.0}/tests/services/test_check.py +170 -21
  132. {waymark_cli-0.2.0 → waymark_cli-0.4.0}/tests/services/test_ci_and_pr.py +40 -5
  133. {waymark_cli-0.2.0 → waymark_cli-0.4.0}/tests/services/test_doctor.py +25 -52
  134. {waymark_cli-0.2.0 → waymark_cli-0.4.0}/tests/services/test_fix.py +5 -4
  135. {waymark_cli-0.2.0 → waymark_cli-0.4.0}/tests/services/test_lifecycle.py +7 -4
  136. waymark_cli-0.2.0/tests/services/test_lifecycle_format2.py → waymark_cli-0.4.0/tests/services/test_lifecycle_records.py +104 -8
  137. {waymark_cli-0.2.0 → waymark_cli-0.4.0}/tests/services/test_milestones.py +12 -5
  138. waymark_cli-0.4.0/tests/services/test_review_added_items.py +121 -0
  139. waymark_cli-0.4.0/tests/services/test_roadmap.py +127 -0
  140. {waymark_cli-0.2.0 → waymark_cli-0.4.0}/tests/services/test_setup.py +248 -30
  141. {waymark_cli-0.2.0 → waymark_cli-0.4.0}/tests/support.py +7 -12
  142. {waymark_cli-0.2.0 → waymark_cli-0.4.0}/tests/test_atlas_cli.py +9 -11
  143. waymark_cli-0.4.0/tests/test_cli.py +525 -0
  144. {waymark_cli-0.2.0 → waymark_cli-0.4.0}/tests/test_docs.py +1 -0
  145. {waymark_cli-0.2.0 → waymark_cli-0.4.0}/tests/test_install_skills.py +2 -2
  146. {waymark_cli-0.2.0 → waymark_cli-0.4.0}/tests/test_lifecycle_cli.py +3 -3
  147. {waymark_cli-0.2.0 → waymark_cli-0.4.0}/tests/test_skills.py +38 -3
  148. waymark_cli-0.4.0/tests/test_views_cli.py +404 -0
  149. waymark_cli-0.4.0/tests/views/test_prompts.py +149 -0
  150. waymark_cli-0.4.0/tests/views/test_style.py +155 -0
  151. waymark_cli-0.4.0/tests/views/test_terminal.py +161 -0
  152. {waymark_cli-0.2.0 → waymark_cli-0.4.0}/tests/views/test_views.py +92 -4
  153. waymark_cli-0.4.0/tests/views/test_welcome.py +156 -0
  154. {waymark_cli-0.2.0 → waymark_cli-0.4.0}/tools/docs.py +17 -2
  155. {waymark_cli-0.2.0 → waymark_cli-0.4.0}/tools/skills/waymark-check-docs/SKILL.md +1 -1
  156. {waymark_cli-0.2.0 → waymark_cli-0.4.0}/tools/skills/waymark-release/SKILL.md +10 -4
  157. waymark_cli-0.2.0/src/waymark/assets/skills/wm-fix/SKILL.md +0 -60
  158. waymark_cli-0.2.0/src/waymark/assets/skills/wm-propose/SKILL.md +0 -80
  159. waymark_cli-0.2.0/src/waymark/record/milestones.py +0 -105
  160. waymark_cli-0.2.0/src/waymark/services/check.py +0 -148
  161. waymark_cli-0.2.0/src/waymark/services/migrations.py +0 -99
  162. waymark_cli-0.2.0/src/waymark/views/style.py +0 -102
  163. waymark_cli-0.2.0/tests/services/test_migrations.py +0 -122
  164. waymark_cli-0.2.0/tests/test_cli.py +0 -229
  165. waymark_cli-0.2.0/tests/test_views_cli.py +0 -142
  166. waymark_cli-0.2.0/tests/views/test_style.py +0 -73
  167. waymark_cli-0.2.0/tools/skills/waymark-draft-docs/SKILL.md +0 -36
  168. {waymark_cli-0.2.0 → waymark_cli-0.4.0}/.gitignore +0 -0
  169. {waymark_cli-0.2.0 → waymark_cli-0.4.0}/LICENSE +0 -0
  170. {waymark_cli-0.2.0 → waymark_cli-0.4.0}/docs/assets/banner-dark.svg +0 -0
  171. {waymark_cli-0.2.0 → waymark_cli-0.4.0}/docs/assets/banner-light.svg +0 -0
  172. {waymark_cli-0.2.0 → waymark_cli-0.4.0}/docs/assets/trail-dark.svg +0 -0
  173. {waymark_cli-0.2.0 → waymark_cli-0.4.0}/docs/assets/trail-light.svg +0 -0
  174. {waymark_cli-0.2.0 → waymark_cli-0.4.0}/src/waymark/__main__.py +0 -0
  175. {waymark_cli-0.2.0 → waymark_cli-0.4.0}/src/waymark/hooks/__init__.py +0 -0
  176. {waymark_cli-0.2.0 → waymark_cli-0.4.0}/src/waymark/hooks/commands.py +0 -0
  177. {waymark_cli-0.2.0 → waymark_cli-0.4.0}/src/waymark/hooks/events.py +0 -0
  178. {waymark_cli-0.2.0 → waymark_cli-0.4.0}/src/waymark/py.typed +0 -0
  179. {waymark_cli-0.2.0 → waymark_cli-0.4.0}/src/waymark/record/__init__.py +0 -0
  180. {waymark_cli-0.2.0/src/waymark/record → waymark_cli-0.4.0/src/waymark/record/evidence}/commits.py +0 -0
  181. {waymark_cli-0.2.0/src/waymark/record → waymark_cli-0.4.0/src/waymark/record/markdown}/problems.py +0 -0
  182. {waymark_cli-0.2.0/src/waymark/record → waymark_cli-0.4.0/src/waymark/record/markdown}/text.py +0 -0
  183. {waymark_cli-0.2.0 → waymark_cli-0.4.0}/src/waymark/record/names.py +0 -0
  184. {waymark_cli-0.2.0 → waymark_cli-0.4.0}/src/waymark/record/terms.py +0 -0
  185. {waymark_cli-0.2.0/src/waymark/record → waymark_cli-0.4.0/src/waymark/record/writing}/templates/ci-workflow.yml +0 -0
  186. {waymark_cli-0.2.0/src/waymark/record → waymark_cli-0.4.0/src/waymark/record/writing}/templates/config-atlas.toml +0 -0
  187. {waymark_cli-0.2.0/src/waymark/record → waymark_cli-0.4.0/src/waymark/record/writing}/templates/design.md +0 -0
  188. {waymark_cli-0.2.0/src/waymark/record → waymark_cli-0.4.0/src/waymark/record/writing}/templates/exploration.md +0 -0
  189. {waymark_cli-0.2.0/src/waymark/record → waymark_cli-0.4.0/src/waymark/record/writing}/templates/milestone.md +0 -0
  190. {waymark_cli-0.2.0/src/waymark/record → waymark_cli-0.4.0/src/waymark/record/writing}/templates/proposal.md +0 -0
  191. {waymark_cli-0.2.0/src/waymark/record → waymark_cli-0.4.0/src/waymark/record/writing}/templates/tasks.md +0 -0
  192. {waymark_cli-0.2.0 → waymark_cli-0.4.0}/src/waymark/services/__init__.py +0 -0
  193. {waymark_cli-0.2.0 → waymark_cli-0.4.0}/src/waymark/services/guidance.py +0 -0
  194. {waymark_cli-0.2.0 → waymark_cli-0.4.0}/src/waymark/views/__init__.py +0 -0
  195. {waymark_cli-0.2.0 → waymark_cli-0.4.0}/tests/__init__.py +0 -0
  196. {waymark_cli-0.2.0 → waymark_cli-0.4.0}/tests/adapters/__init__.py +0 -0
  197. {waymark_cli-0.2.0 → waymark_cli-0.4.0}/tests/adapters/snapshots/settings.json +0 -0
  198. {waymark_cli-0.2.0 → waymark_cli-0.4.0}/tests/conftest.py +0 -0
  199. {waymark_cli-0.2.0 → waymark_cli-0.4.0}/tests/hooks/__init__.py +0 -0
  200. {waymark_cli-0.2.0 → waymark_cli-0.4.0}/tests/hooks/test_repo_limits.py +0 -0
  201. {waymark_cli-0.2.0 → waymark_cli-0.4.0}/tests/record/__init__.py +0 -0
  202. {waymark_cli-0.2.0/tests/record → waymark_cli-0.4.0/tests/record/markdown}/test_text.py +0 -0
  203. {waymark_cli-0.2.0 → waymark_cli-0.4.0}/tests/record/test_names.py +0 -0
  204. {waymark_cli-0.2.0 → waymark_cli-0.4.0}/tests/services/__init__.py +0 -0
  205. {waymark_cli-0.2.0 → waymark_cli-0.4.0}/tests/test_agent_cli.py +0 -0
  206. {waymark_cli-0.2.0 → waymark_cli-0.4.0}/tests/test_constraints.py +0 -0
  207. {waymark_cli-0.2.0 → waymark_cli-0.4.0}/tests/views/__init__.py +0 -0
  208. {waymark_cli-0.2.0 → waymark_cli-0.4.0}/tests/views/test_branches.py +0 -0
  209. {waymark_cli-0.2.0 → waymark_cli-0.4.0}/tests/views/validator.py +0 -0
  210. {waymark_cli-0.2.0 → waymark_cli-0.4.0}/tools/__init__.py +0 -0
  211. {waymark_cli-0.2.0 → waymark_cli-0.4.0}/tools/install_skills.py +0 -0
  212. {waymark_cli-0.2.0 → waymark_cli-0.4.0}/tools/release.py +0 -0
  213. {waymark_cli-0.2.0 → waymark_cli-0.4.0}/tools/skills/waymark-write-docs/SKILL.md +0 -0
@@ -1,7 +1,128 @@
1
1
  # Changelog
2
2
 
3
- All notable changes to Waymark, one entry per release. A release that changes
4
- the record's format says whether `wm update` migrates an older record.
3
+ All notable changes to Waymark, one entry per release.
4
+
5
+ ## [0.4.0] - 2026-11-18
6
+
7
+ A first impression worth the name: `wm init` welcomes you and asks what to set
8
+ up, and every terminal view has one palette, tree lines and wrapped prose.
9
+ Review findings name their places relative to the project. The record format is
10
+ unchanged.
11
+
12
+ - **Behavior change: `wm init` asks on a terminal.** With both its input and its
13
+ output a terminal, and none of `--atlas`, `--tool` or the new `--yes`, it opens
14
+ with a welcome screen: the Waymark star, which grows in and twinkles, the
15
+ tagline, what it sets up, and the skills to run next. It then asks whether the
16
+ repository is a project or an atlas (and the atlas's name), which agent tools
17
+ to set up, with the ones it finds already selected, and whether to add the CI
18
+ workflow. Esc or Ctrl+C cancels and writes nothing. Where the terminal can't
19
+ read single keys, the questions come as numbered choices. In a clone, it shows
20
+ the welcome screen and asks nothing.
21
+ - **Behavior change: `wm check` groups its findings by file.** Each file's path
22
+ is on a line of its own, with its findings under it as
23
+ ` <severity>: <line>: <code>: <message>`, instead of one
24
+ `<severity>: <path>:<line>: <code>: <message>` line per finding. A script that
25
+ reads the text output should read `wm check --json`, which is unchanged.
26
+ - **`wm init --yes`** asks nothing. So do `--atlas` and `--tool`, and so does
27
+ `wm init` when its input or output isn't a terminal, as when an agent runs it:
28
+ it does what it did before.
29
+ - **A new look in the terminal.** The views use one palette of the 16 standard
30
+ colors, by role: cyan for section rules and commands, green for done, yellow for
31
+ what needs you and for warnings, red for errors, dim for dates and records, bold
32
+ for names. `wm status` colors each change's phase and progress bar and marks each
33
+ milestone's roadmap lines `◆` archived and `◇` open. `wm show` draws a change's
34
+ items as a tree and marks a milestone's roadmap. `wm doctor` lines its checks up
35
+ in one column. Each glyph has an ASCII stand-in for consoles that can't show it.
36
+ - **Prose wraps on a terminal.** `wm show`, `wm inbox`, `wm check` and
37
+ `wm doctor` wrap their prose to the terminal's width, from 60 to 100 columns.
38
+ Output that isn't going to a terminal is not wrapped, so agents read whole lines.
39
+ - **`FORCE_COLOR`.** Set to any value but empty or `0`, it turns color on when the
40
+ output isn't a terminal. `NO_COLOR` still turns color off, and wins. JSON output
41
+ never carries color.
42
+ - **Finding places are relative to the project.** `wm review` and `wm verdict`
43
+ write an absolute path in a finding's place relative to the project, with
44
+ forward slashes, or as `<repo>/<path>` for a code repo in an atlas, and refuse
45
+ any other absolute path. Before, a reviewer's absolute path went into the
46
+ record as given, home folder included.
47
+
48
+ Smoke test: passed on 2026-11-18 with Claude Code 2.1.327 on Windows.
49
+
50
+ ## [0.3.0] - 2026-11-18
51
+
52
+ Context beyond the code: resources, a spec's Background and one list of project
53
+ rules give every fact an agent needs one place. Milestones link their changes and
54
+ keep a log, changes have branches and bases, and the record format resets to 1.
55
+
56
+ - **Behavior change: record format 1, with no migration.** `wm` reads and writes
57
+ only format 1, and this release's record is format 1. A record in any other
58
+ format, including the format 3 that 0.2.0 writes, is refused with one reason:
59
+ install the `wm` version that wrote it. `wm update` migrates nothing. It
60
+ regenerates the files `wm` owns and adds missing `.gitkeep` files. `wm check`
61
+ no longer reports older layouts on their own; such a line fails the check
62
+ that applies to it. `.waymark/atlas.toml` is no longer read as an atlas
63
+ pointer, and `wm doctor` no longer looks for `.waymark/hooks/`.
64
+ - **Behavior change: `wm-fix` is gone; `/wm-propose` does work of any size.**
65
+ It reads the specs and the code and picks the path itself: tiny, built after
66
+ your yes; short, a change with no design; or full, a change with a design,
67
+ with any open question blocking acceptance. `wm init` and `wm update` remove
68
+ the `wm-*` skill folders `wm` no longer ships, and print `removed:` for each.
69
+ - **Record folders stay in git.** `wm init` writes an empty `.gitkeep` into
70
+ `specs/`, `changes/`, `changes/archive/`, `explorations/`, `milestones/` and
71
+ `milestones/archive/`, and `wm update` adds any that are missing.
72
+ - **Behavior change: an item added after a review is reviewed on its own.**
73
+ `(review)` and `(self-review)` records now name the items they cover, as
74
+ `covers <item>...`; a record without it covers every item. Once an item added
75
+ after a passing review is ticked, the next step is a review of the items no
76
+ passing review covers, and the reviewer's pack holds only those. `wm archive`
77
+ refuses a change with such an item unless you override it with a reason.
78
+ `wm show` and the JSON payloads give what each review covers.
79
+ - **A change names its milestone.** A proposal may have a `- Milestone: <name>`
80
+ line. For an active change, `wm check` reports an error when that line and the
81
+ milestones' roadmaps disagree, including a roadmap that links a change whose
82
+ proposal has no such line. `wm new change <name> --milestone <milestone>`
83
+ writes the line and links the change from the roadmap. The implement and
84
+ review context packs carry the milestone's Goal and Non-goals, in a new
85
+ `milestone` field.
86
+ - **A milestone keeps a log, and its roadmap changes only through `wm`.**
87
+ `wm roadmap add`, `wm roadmap drop --reason` and `wm roadmap move --after|--first`
88
+ change the roadmap, and each writes a record in a `## Log` at the end of
89
+ `milestone.md`, as do `wm new change --milestone` and `wm archive`. An agent's
90
+ hand edit to a roadmap line or the Log is refused.
91
+ - **Behavior change: `wm close` needs every roadmap line archived.** A planned
92
+ line that was never proposed now keeps a milestone open, until it is proposed
93
+ or dropped with `wm roadmap drop`.
94
+ - **Each change has a branch and a base.** A proposal may say which change it
95
+ comes after, in an `- After: <change>` line written by
96
+ `wm new change <name> --after <change>`. `wm instructions`, `wm pr` and
97
+ `wm status` show each change's branch and base, `wm pr`'s JSON has a `base` for
98
+ the pull request to target, and `wm check` warns when the change it comes after
99
+ has merged. The default branch comes from the `origin` remote's HEAD, or is
100
+ `main`. The skills open a plan pull request for a new milestone and create
101
+ each change's branch from its base.
102
+ - **Resources.** A new kind of note, `waymark/resources/<name>.md`, holds the
103
+ facts about one thing outside the repo: its kind, the specs it serves, its
104
+ status, the day it was verified, and six sections. `wm new resource <name>
105
+ <kind>`, `wm ls resources` and `wm show <name> --kind resource` work with them,
106
+ and `wm check` holds them to their layout. The explore context pack gains a
107
+ `resources` index, and the implement and review packs a `resources` field with
108
+ the resources serving the change's specs. An implementer may edit resources,
109
+ and `wm init` and `wm update` keep `resources/` in git.
110
+ - **A spec may have a Background.** A `## Background` section, between Purpose
111
+ and Requirements, holds the facts about the spec's area that aren't
112
+ requirements. A delta's `## Background` replaces the spec's whole at archive or
113
+ sync. `wm check` reports an empty one. The implement and review packs gain a
114
+ `backgrounds` field with the Background of each spec the change has a delta
115
+ for, the delta's when it has one. The delta template and the specs step's
116
+ guidance say where a fact goes.
117
+ - **Behavior change: the charter's Rules are one numbered list.** `## Rules`
118
+ holds `1. <rule>` lines, like Goals and Constraints, and every agent gets the
119
+ whole list at every step: `wm instructions` and every `wm context` pack show
120
+ it under "Project rules", and `rules` in their JSON holds all of it. A step
121
+ heading or a bullet under Rules is a `numbered-list-format` error, and the
122
+ `unknown-step` problem is gone. A charter with step headings must be rewritten
123
+ by hand. `wm init` writes Rules without step headings.
124
+
125
+ Smoke test: passed on 2026-11-18 with Claude Code 2.1.327 on Windows.
5
126
 
6
127
  ## [0.2.0] - 2026-11-16
7
128
 
@@ -1,6 +1,6 @@
1
1
  Metadata-Version: 2.5
2
2
  Name: waymark-cli
3
- Version: 0.2.0
3
+ Version: 0.4.0
4
4
  Summary: Spec-driven development for developers who stay in charge of their project while agents write the code.
5
5
  Project-URL: Repository, https://github.com/noahnkr/waymark
6
6
  Project-URL: Documentation, https://github.com/noahnkr/waymark/tree/main/docs
@@ -61,23 +61,25 @@ command-line tool, `wm`, keeps track of where everything stands.
61
61
 
62
62
  ## How it works
63
63
 
64
- Not every piece of work needs the whole trail. What decides it is whether the
65
- work changes what the specs say, not how big it is:
64
+ Everything starts with `/wm-propose`. A typo fix and a new feature go through
65
+ the same door, but they don't take the same amount of work:
66
66
 
67
- | Path | When | What gets written | Run |
68
- |---|---|---|---|
69
- | **Tiny** | Nothing in the specs changes: a typo, a docs fix, a bug, a refactor | Nothing. You say yes, the agent makes the fix, you review the pull request. | `/wm-fix` |
70
- | **Short** | A small change that doesn't need a design | A short plan: what's changing and why, the spec edits, and a task list. | `/wm-propose` |
71
- | **Full** | A change that needs a design | The same plan plus a design, with every decision agreed before work starts. | `/wm-propose` |
67
+ | Path | When | What gets written |
68
+ |---|---|---|
69
+ | **Tiny** | The specs don't change: a typo, a docs fix, a bug, a refactor | Nothing. You say yes, the agent fixes it, you review the pull request. |
70
+ | **Short** | The specs change, but there's nothing to design | A short plan: what's changing and why, the spec edits, and a task list. |
71
+ | **Full** | The specs change and there are decisions to make | The same plan plus a design, and you agree every decision before anything gets built. |
72
72
 
73
- Here's what happens along the way:
73
+ Here's how a change goes:
74
74
 
75
75
  - **Explore**, if you're not sure yet. `/wm-explore` talks the idea through with
76
76
  you, using what the specs already say, and writes nothing unless you ask. It
77
77
  can save your thinking for later, or turn it into a change or a milestone.
78
- - **Propose.** `/wm-propose` asks you whatever the plan needs, then writes it:
79
- why the change is wanted, the edits to the specs, a design if it needs one,
80
- and a task list where every task says how you'll know it's done.
78
+ - **Propose.** `/wm-propose` looks at your specs and code to see what the work
79
+ involves. If it's tiny, it tells you in one line what it'll change and does it
80
+ once you say yes. Otherwise it asks what it needs to know, then writes the
81
+ plan: why, the spec edits, a design if there is one, and a task list where
82
+ every task says how you'll know it's done.
81
83
  - **Accept.** You read a short summary and run `wm accept`. Nothing is built
82
84
  before that.
83
85
  - **Apply.** `/wm-apply` builds the tasks one at a time and commits each one.
@@ -140,8 +142,7 @@ You work through skills, as slash commands in Claude Code:
140
142
  | `/wm-kickoff` | Write the project's charter with you, once per project |
141
143
  | `/wm-onboard` | Take a first change all the way through, explaining each step |
142
144
  | `/wm-explore` | Think a fuzzy idea through, without writing anything |
143
- | `/wm-fix` | Make a small fix that changes nothing in the specs |
144
- | `/wm-propose` | Write the plan for a change |
145
+ | `/wm-propose` | Do any piece of work: a small fix after your yes, or the plan for a change |
145
146
  | `/wm-update` | Revise a plan, settle a decision, or fill a gap |
146
147
  | `/wm-apply` | Build an approved change, then check it |
147
148
  | `/wm-archive` | Finish a change and update the specs |
@@ -198,14 +199,25 @@ waymark/
198
199
  charter.md what the project is, its goals and its rules
199
200
  config.toml settings, and the pinned wm version
200
201
  changes/
202
+ .gitkeep
201
203
  archive/
204
+ .gitkeep
202
205
  2026-01-15-add-dark-mode/
203
206
  design.md how it's built, and the decisions
204
207
  proposal.md why, what changes, and the outcome
205
208
  tasks.md the tasks, and what wm recorded
206
209
  specs/
207
210
  appearance.md the change to the spec
211
+ explorations/
212
+ .gitkeep
213
+ milestones/
214
+ .gitkeep
215
+ archive/
216
+ .gitkeep
217
+ resources/
218
+ .gitkeep
208
219
  specs/
220
+ .gitkeep
209
221
  appearance.md the living spec, now with dark mode
210
222
  ```
211
223
 
@@ -335,7 +347,7 @@ setting until the person picks one.
335
347
  ## Log
336
348
 
337
349
  - (accepted) 2026-01-15 fingerprint 01204aef70272f6b items 1.1 1.2 1.3 by Alex Example
338
- - (self-review) 2026-01-15 by Alex Example: every criterion holds, and both scenarios have a test
350
+ - (self-review) 2026-01-15 covers 1.1 1.2 1.3 by Alex Example: every criterion holds, and both scenarios have a test
339
351
  ```
340
352
 
341
353
  </details>
@@ -476,7 +488,7 @@ is caught once both are in the same branch, not before.
476
488
  - **[Architecture](docs/architecture.md)**: how `wm` is built, and how to add an agent tool
477
489
  - **[Smoke test](docs/smoke-test.md)**: the manual walk-through before a release
478
490
 
479
- Works with Claude Code. Version last verified: **2.1.326**, on Windows.
491
+ Works with Claude Code. Version last verified: **2.1.327**, on Windows.
480
492
 
481
493
  ## License
482
494
 
@@ -32,23 +32,25 @@ command-line tool, `wm`, keeps track of where everything stands.
32
32
 
33
33
  ## How it works
34
34
 
35
- Not every piece of work needs the whole trail. What decides it is whether the
36
- work changes what the specs say, not how big it is:
35
+ Everything starts with `/wm-propose`. A typo fix and a new feature go through
36
+ the same door, but they don't take the same amount of work:
37
37
 
38
- | Path | When | What gets written | Run |
39
- |---|---|---|---|
40
- | **Tiny** | Nothing in the specs changes: a typo, a docs fix, a bug, a refactor | Nothing. You say yes, the agent makes the fix, you review the pull request. | `/wm-fix` |
41
- | **Short** | A small change that doesn't need a design | A short plan: what's changing and why, the spec edits, and a task list. | `/wm-propose` |
42
- | **Full** | A change that needs a design | The same plan plus a design, with every decision agreed before work starts. | `/wm-propose` |
38
+ | Path | When | What gets written |
39
+ |---|---|---|
40
+ | **Tiny** | The specs don't change: a typo, a docs fix, a bug, a refactor | Nothing. You say yes, the agent fixes it, you review the pull request. |
41
+ | **Short** | The specs change, but there's nothing to design | A short plan: what's changing and why, the spec edits, and a task list. |
42
+ | **Full** | The specs change and there are decisions to make | The same plan plus a design, and you agree every decision before anything gets built. |
43
43
 
44
- Here's what happens along the way:
44
+ Here's how a change goes:
45
45
 
46
46
  - **Explore**, if you're not sure yet. `/wm-explore` talks the idea through with
47
47
  you, using what the specs already say, and writes nothing unless you ask. It
48
48
  can save your thinking for later, or turn it into a change or a milestone.
49
- - **Propose.** `/wm-propose` asks you whatever the plan needs, then writes it:
50
- why the change is wanted, the edits to the specs, a design if it needs one,
51
- and a task list where every task says how you'll know it's done.
49
+ - **Propose.** `/wm-propose` looks at your specs and code to see what the work
50
+ involves. If it's tiny, it tells you in one line what it'll change and does it
51
+ once you say yes. Otherwise it asks what it needs to know, then writes the
52
+ plan: why, the spec edits, a design if there is one, and a task list where
53
+ every task says how you'll know it's done.
52
54
  - **Accept.** You read a short summary and run `wm accept`. Nothing is built
53
55
  before that.
54
56
  - **Apply.** `/wm-apply` builds the tasks one at a time and commits each one.
@@ -111,8 +113,7 @@ You work through skills, as slash commands in Claude Code:
111
113
  | `/wm-kickoff` | Write the project's charter with you, once per project |
112
114
  | `/wm-onboard` | Take a first change all the way through, explaining each step |
113
115
  | `/wm-explore` | Think a fuzzy idea through, without writing anything |
114
- | `/wm-fix` | Make a small fix that changes nothing in the specs |
115
- | `/wm-propose` | Write the plan for a change |
116
+ | `/wm-propose` | Do any piece of work: a small fix after your yes, or the plan for a change |
116
117
  | `/wm-update` | Revise a plan, settle a decision, or fill a gap |
117
118
  | `/wm-apply` | Build an approved change, then check it |
118
119
  | `/wm-archive` | Finish a change and update the specs |
@@ -169,14 +170,25 @@ waymark/
169
170
  charter.md what the project is, its goals and its rules
170
171
  config.toml settings, and the pinned wm version
171
172
  changes/
173
+ .gitkeep
172
174
  archive/
175
+ .gitkeep
173
176
  2026-01-15-add-dark-mode/
174
177
  design.md how it's built, and the decisions
175
178
  proposal.md why, what changes, and the outcome
176
179
  tasks.md the tasks, and what wm recorded
177
180
  specs/
178
181
  appearance.md the change to the spec
182
+ explorations/
183
+ .gitkeep
184
+ milestones/
185
+ .gitkeep
186
+ archive/
187
+ .gitkeep
188
+ resources/
189
+ .gitkeep
179
190
  specs/
191
+ .gitkeep
180
192
  appearance.md the living spec, now with dark mode
181
193
  ```
182
194
 
@@ -306,7 +318,7 @@ setting until the person picks one.
306
318
  ## Log
307
319
 
308
320
  - (accepted) 2026-01-15 fingerprint 01204aef70272f6b items 1.1 1.2 1.3 by Alex Example
309
- - (self-review) 2026-01-15 by Alex Example: every criterion holds, and both scenarios have a test
321
+ - (self-review) 2026-01-15 covers 1.1 1.2 1.3 by Alex Example: every criterion holds, and both scenarios have a test
310
322
  ```
311
323
 
312
324
  </details>
@@ -447,7 +459,7 @@ is caught once both are in the same branch, not before.
447
459
  - **[Architecture](docs/architecture.md)**: how `wm` is built, and how to add an agent tool
448
460
  - **[Smoke test](docs/smoke-test.md)**: the manual walk-through before a release
449
461
 
450
- Works with Claude Code. Version last verified: **2.1.326**, on Windows.
462
+ Works with Claude Code. Version last verified: **2.1.327**, on Windows.
451
463
 
452
464
  ## License
453
465
 
@@ -52,12 +52,20 @@ adapter for another agent tool, and how to work on the code.
52
52
 
53
53
  | Folder under `src/waymark/` | Holds |
54
54
  |---|---|
55
- | `record/` | The only code that reads or writes the record's files: parsers, the record lines (`records.py`, the one place each record's shape is defined), the standard layout (`layout.py`), state derivation, delta merging, the acceptance fingerprint, the transactional writer, templates, the registry, git queries. |
55
+ | `record/` | The only code that reads or writes the record's files. At its top: loading the whole record (`record.py`), state derivation (`state.py`), the fixed vocabulary (`terms.py`) and names (`names.py`). The rest is in five packages, below. |
56
56
  | `services/` | What the commands do, and every gate. A refused command raises `Refusal` with what is wrong and what to do next. |
57
57
  | `views/` | Payloads, their JSON schemas, and the text and JSON renderers. One payload feeds both renderings. |
58
58
  | `hooks/` | Tool-neutral hook decisions on six neutral events. |
59
59
  | `adapters/` | One adapter per agent tool. Only code here may name a tool. |
60
60
  | `assets/` | The skills and agent definitions, written once and tool-neutral. |
61
+
62
+ | Package under `record/` | Holds |
63
+ |---|---|
64
+ | `markdown/` | Markdown as `wm` reads it: lines, fences, sections, outlines, links, and the problems found while reading. |
65
+ | `artifacts/` | One module per authored file: changes, the charter, the settings, deltas and their merging, designs, explorations, milestones, proposals, resources, specs and task lists. |
66
+ | `evidence/` | The lines only `wm` writes and the gates they feed: the record lines (`records.py`, the one place each record's shape is defined), gate evidence, the acceptance fingerprint, the per-agent marker and the commit-message check. |
67
+ | `writing/` | Writing the record: the transactional writer, the edits `wm` owns, the standard layout (`layout.py`), folder moves, the `.gitignore` block, and the templates. |
68
+ | `machine/` | This machine and its repository: git queries, reading files, finding the project, atlases, code repo pointers, the registry, and branches. |
61
69
  | `cli.py` | Parses arguments, calls a service, prints. |
62
70
 
63
71
  Three tests in `tests/test_constraints.py` hold the boundaries: the standard
@@ -83,7 +91,7 @@ Claude Code runs `wm hook claude-code <Event>` with its JSON on standard input.
83
91
  planner edit any code repo, and an implementer only the repo an accepted
84
92
  change's item being built names (`editable_repos`). An agent's ending is
85
93
  recorded once: a per-agent marker in the clone's git folder
86
- (`record/agents.py`) lets the stop after a recorded handback through without
94
+ (`record/evidence/agents.py`) lets the stop after a recorded handback through without
87
95
  asking for the ending again.
88
96
  3. **The adapter translates the decision back** into the tool's reply format.
89
97
 
@@ -145,9 +153,8 @@ uv run --no-sync python -m tools.install_skills
145
153
 
146
154
  | Skill | For |
147
155
  |---|---|
148
- | `waymark-draft-docs` | Planning and drafting a new or rewritten docs page with the maintainer |
149
156
  | `waymark-write-docs` | The house style and fact rules for any docs edit |
150
- | `waymark-check-docs` | Checking docs against the code, on request |
157
+ | `waymark-check-docs` | Checking docs against the code, on request or when a release offers it |
151
158
  | `waymark-release` | Cutting a release, from audit to tag |
152
159
 
153
160
  CI runs the tests on Windows, macOS and Linux, each on Python 3.11 and the newest
@@ -173,13 +180,20 @@ scoped by component (`record`, `services`, `views`, `hooks`, `adapter-claude`,
173
180
 
174
181
  ## Releasing
175
182
 
183
+ Each change with a User-visible line adds it to `CHANGELOG.md` under
184
+ `## [Unreleased]`, in the item that updates its docs.
185
+
176
186
  The maintainer releases, with the `waymark-release` skill. Before each release, the
177
187
  [smoke-test checklist](smoke-test.md) is run by hand, and its result goes into the
178
188
  changelog's entry. The skill:
179
189
 
180
- 1. sets the version in `src/waymark/__init__.py` and the pin in `waymark/config.toml`,
181
- and writes and dates the entry in `CHANGELOG.md`, on a release branch;
182
- 2. opens the pull request; after it is merged, pushes a tag `v<version>` on `main`.
190
+ 1. checks `## [Unreleased]` against the changes archived since the last tag, and
191
+ lists the review findings they left open, for the maintainer to fix, plan or drop;
192
+ 2. sets the version in `src/waymark/__init__.py` and the pin in `waymark/config.toml`,
193
+ and turns `## [Unreleased]` into the dated entry in `CHANGELOG.md`, on a release
194
+ branch;
195
+ 3. offers `waymark-check-docs` on the docs pages changed since the last tag;
196
+ 4. opens the pull request; after it is merged, pushes a tag `v<version>` on `main`.
183
197
 
184
198
  The release workflow checks that the tag, the version, the changelog entry and the
185
199
  smoke-test record agree, runs the tests, builds, publishes to PyPI through trusted
@@ -2,24 +2,34 @@
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.2.0. Read commands take `--json`; their payloads are described in the [JSON schema reference](json.md).
5
+ Every command of `wm` 0.4.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
 
9
+ ## Environment
10
+
11
+ - `NO_COLOR`: set to any value, even empty, and the text output carries no color. It wins over `FORCE_COLOR`.
12
+ - `FORCE_COLOR`: set to any value but empty or `0`, and the text output carries color even when it isn't going to a terminal.
13
+ - `TERM=dumb`: no color on a terminal.
14
+ - JSON output never carries color.
15
+ - On a terminal, prose in `wm show`, `wm inbox`, `wm check` and `wm doctor` wraps to the terminal's width, from 60 to 100 columns. Output that isn't going to a terminal is never wrapped.
16
+ - When the output's encoding can't show the glyphs, they're drawn in ASCII.
17
+
9
18
  ## wm init
10
19
 
11
20
  Create the record, or set up this machine in a clone that has one.
12
21
 
13
22
  ```
14
- wm init [--atlas NAME] [--tool NAME]
23
+ wm init [--atlas NAME] [--tool NAME] [--yes]
15
24
  ```
16
25
 
17
26
  - `--atlas`: make this repository an atlas: a record that several code repos share
18
27
  - `--tool`: an agent tool to set up; repeatable (default: claude-code)
28
+ - `--yes`: ask nothing, even on a terminal: a project with every agent tool, and no CI
19
29
 
20
30
  ## wm update
21
31
 
22
- Migrate the record to this version and regenerate the files Waymark owns.
32
+ Regenerate the files Waymark owns, and add any missing record folders.
23
33
 
24
34
  ```
25
35
  wm update
@@ -108,16 +118,19 @@ wm hook <tool> <event>
108
118
 
109
119
  ## wm new
110
120
 
111
- Create a change, milestone or exploration from the built-in template.
121
+ Create a change, milestone, exploration or resource from the built-in template.
112
122
 
113
123
  ```
114
- wm new <change|milestone|exploration> <name> [--short] [--owner NAME]
124
+ wm new <change|milestone|exploration|resource> <name> [resource-kind] [--short] [--owner NAME] [--milestone MILESTONE] [--after CHANGE]
115
125
  ```
116
126
 
117
- - `kind`: one of `change`, `milestone`, `exploration`
127
+ - `kind`: one of `change`, `milestone`, `exploration`, `resource`
118
128
  - `name`: a kebab-case name, for example add-search-limit
129
+ - `resource_kind`: for a resource only: service, platform, account, database, dataset or document
119
130
  - `--short`: put a change on the short path
120
131
  - `--owner`: a change's owner (default: your git name)
132
+ - `--milestone`: the milestone a change belongs to; links it from the milestone's roadmap
133
+ - `--after`: the change this one comes after; its unmerged branch is this one's base
121
134
 
122
135
  ## wm accept
123
136
 
@@ -268,6 +281,54 @@ wm close <milestone>
268
281
 
269
282
  - `milestone`: the milestone's name
270
283
 
284
+ ## wm roadmap
285
+
286
+ Change a milestone's roadmap: add, drop or move a change's line, with a record.
287
+
288
+ ```
289
+ wm roadmap <command>
290
+ ```
291
+
292
+ ## wm roadmap add
293
+
294
+ Add a planned line for a change at the end of a milestone's roadmap.
295
+
296
+ ```
297
+ wm roadmap add <milestone> <change> <description> [--by NAME]
298
+ ```
299
+
300
+ - `milestone`: the milestone's name
301
+ - `change`: the change's name, for example add-search-limit
302
+ - `description`: what the change delivers toward the goal
303
+ - `--by`: who the record names as its writer (default: your git name)
304
+
305
+ ## wm roadmap drop
306
+
307
+ Take a change's line off a milestone's roadmap, with the reason.
308
+
309
+ ```
310
+ wm roadmap drop <milestone> <change> --reason REASON [--by NAME]
311
+ ```
312
+
313
+ - `milestone`: the milestone's name
314
+ - `change`: the change's name
315
+ - `--reason`: why the change is dropped (required)
316
+ - `--by`: who the record names as its writer (default: your git name)
317
+
318
+ ## wm roadmap move
319
+
320
+ Move a change's line on a milestone's roadmap.
321
+
322
+ ```
323
+ wm roadmap move <milestone> <change> [--after CHANGE] [--first] [--by NAME]
324
+ ```
325
+
326
+ - `milestone`: the milestone's name
327
+ - `change`: the change's name
328
+ - `--after`: put it right after this change's line
329
+ - `--first`: put it at the top of the roadmap
330
+ - `--by`: who the record names as its writer (default: your git name)
331
+
271
332
  ## wm status
272
333
 
273
334
  Show where things stand: changes, milestones, what needs you.
@@ -298,7 +359,7 @@ wm show [--json] <name> [--kind KIND] [--from ATLAS]
298
359
 
299
360
  - `--json`: print the view as JSON, with its schema version
300
361
  - `name`: its name; an archived change also by its dated folder name
301
- - `--kind`: which kind, if the name is shared; one of `change`, `spec`, `milestone`, `exploration`
362
+ - `--kind`: which kind, if the name is shared; one of `change`, `spec`, `milestone`, `exploration`, `resource`
302
363
  - `--from`: read a spec from an atlas this project references
303
364
 
304
365
  ## wm ls
@@ -306,11 +367,11 @@ wm show [--json] <name> [--kind KIND] [--from ATLAS]
306
367
  List changes, specs, milestones or explorations.
307
368
 
308
369
  ```
309
- wm ls [--json] <changes|specs|milestones|explorations> [--archived] [--from ATLAS]
370
+ wm ls [--json] <changes|specs|milestones|explorations|resources> [--archived] [--from ATLAS]
310
371
  ```
311
372
 
312
373
  - `--json`: print the view as JSON, with its schema version
313
- - `kind`: one of `changes`, `specs`, `milestones`, `explorations`
374
+ - `kind`: one of `changes`, `specs`, `milestones`, `explorations`, `resources`
314
375
  - `--archived`: include archived changes or milestones
315
376
  - `--from`: list the specs of an atlas this project references
316
377