waymark-cli 0.4.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 (210) hide show
  1. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/CHANGELOG.md +160 -0
  2. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/PKG-INFO +64 -61
  3. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/README.md +62 -59
  4. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/docs/architecture.md +2 -3
  5. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/docs/cli.md +73 -30
  6. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/docs/concepts.md +258 -131
  7. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/docs/getting-started.md +29 -20
  8. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/docs/json.md +135 -20
  9. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/docs/multi-repo.md +13 -9
  10. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/docs/record.md +177 -94
  11. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/docs/skills.md +71 -41
  12. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/docs/smoke-test.md +86 -53
  13. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/pyproject.toml +1 -1
  14. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/src/waymark/__init__.py +1 -1
  15. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/src/waymark/assets/agents/wm-implementer.md +6 -5
  16. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/src/waymark/assets/agents/wm-reviewer.md +4 -3
  17. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/src/waymark/assets/skills/wm-apply/SKILL.md +24 -14
  18. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/src/waymark/assets/skills/wm-archive/SKILL.md +1 -1
  19. waymark_cli-0.6.0/src/waymark/assets/skills/wm-explore/SKILL.md +75 -0
  20. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/src/waymark/assets/skills/wm-onboard/SKILL.md +2 -2
  21. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/src/waymark/assets/skills/wm-propose/SKILL.md +14 -11
  22. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/src/waymark/assets/skills/wm-update/SKILL.md +10 -10
  23. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/src/waymark/cli.py +135 -26
  24. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/src/waymark/hooks/decide.py +52 -6
  25. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/src/waymark/record/artifacts/changes.py +104 -27
  26. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/src/waymark/record/artifacts/charter.py +5 -4
  27. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/src/waymark/record/artifacts/deltas.py +32 -16
  28. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/src/waymark/record/artifacts/design.py +24 -19
  29. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/src/waymark/record/artifacts/explorations.py +63 -25
  30. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/src/waymark/record/artifacts/milestones.py +18 -2
  31. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/src/waymark/record/artifacts/proposal.py +37 -24
  32. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/src/waymark/record/artifacts/resources.py +11 -9
  33. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/src/waymark/record/artifacts/tasks.py +182 -82
  34. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/src/waymark/record/evidence/evidence.py +32 -4
  35. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/src/waymark/record/evidence/fingerprint.py +3 -3
  36. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/src/waymark/record/evidence/records.py +312 -71
  37. waymark_cli-0.6.0/src/waymark/record/markdown/labels.py +193 -0
  38. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/src/waymark/record/markdown/outline.py +11 -11
  39. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/src/waymark/record/record.py +42 -0
  40. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/src/waymark/record/state.py +76 -10
  41. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/src/waymark/record/terms.py +8 -0
  42. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/src/waymark/record/writing/edits.py +25 -24
  43. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/src/waymark/record/writing/layout.py +117 -6
  44. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/src/waymark/record/writing/templates/charter.md +1 -1
  45. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/src/waymark/record/writing/templates/delta.md +3 -3
  46. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/src/waymark/record/writing/templates/design.md +7 -5
  47. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/src/waymark/record/writing/templates/exploration.md +4 -7
  48. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/src/waymark/record/writing/templates/proposal.md +5 -5
  49. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/src/waymark/record/writing/templates/resource.md +4 -4
  50. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/src/waymark/record/writing/templates/tasks.md +9 -7
  51. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/src/waymark/services/check.py +55 -11
  52. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/src/waymark/services/context.py +27 -11
  53. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/src/waymark/services/fix.py +31 -11
  54. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/src/waymark/services/guidance.py +13 -0
  55. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/src/waymark/services/instructions.py +74 -39
  56. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/src/waymark/services/lifecycle.py +357 -62
  57. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/src/waymark/services/pr.py +1 -0
  58. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/src/waymark/services/roadmap.py +15 -6
  59. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/src/waymark/services/setup.py +62 -13
  60. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/src/waymark/views/payloads.py +37 -11
  61. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/src/waymark/views/render.py +29 -19
  62. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/src/waymark/views/schemas.py +17 -3
  63. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/tests/adapters/snapshots/wm-implementer.md +6 -5
  64. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/tests/adapters/snapshots/wm-reviewer.md +4 -3
  65. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/tests/adapters/test_claude_code.py +9 -9
  66. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/tests/adapters/test_integration.py +13 -0
  67. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/tests/hooks/test_commands.py +2 -0
  68. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/tests/hooks/test_decide.py +192 -59
  69. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/tests/hooks/test_repo_limits.py +5 -3
  70. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/tests/record/artifacts/test_deltas.py +6 -6
  71. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/tests/record/artifacts/test_resources.py +4 -4
  72. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/tests/record/artifacts/test_specs.py +1 -1
  73. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/tests/record/artifacts/test_tasks.py +56 -26
  74. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/tests/record/evidence/test_evidence.py +27 -15
  75. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/tests/record/evidence/test_fingerprint.py +33 -27
  76. waymark_cli-0.6.0/tests/record/evidence/test_records.py +485 -0
  77. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/tests/record/machine/test_branches.py +3 -1
  78. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/tests/record/machine/test_project.py +1 -1
  79. waymark_cli-0.6.0/tests/record/markdown/test_labels.py +61 -0
  80. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/tests/record/markdown/test_text.py +7 -1
  81. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/tests/record/test_artifacts.py +34 -26
  82. waymark_cli-0.6.0/tests/record/test_authored_formats.py +600 -0
  83. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/tests/record/test_state.py +149 -115
  84. waymark_cli-0.6.0/tests/record/test_tasks_records.py +374 -0
  85. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/tests/record/writing/test_layout.py +4 -4
  86. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/tests/services/test_agent_interface.py +211 -80
  87. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/tests/services/test_archive.py +171 -25
  88. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/tests/services/test_check.py +229 -24
  89. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/tests/services/test_ci_and_pr.py +25 -17
  90. waymark_cli-0.6.0/tests/services/test_fix.py +239 -0
  91. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/tests/services/test_lifecycle.py +149 -59
  92. waymark_cli-0.6.0/tests/services/test_lifecycle_records.py +834 -0
  93. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/tests/services/test_milestones.py +75 -4
  94. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/tests/services/test_review_added_items.py +22 -20
  95. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/tests/services/test_roadmap.py +6 -6
  96. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/tests/services/test_setup.py +90 -13
  97. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/tests/support.py +45 -16
  98. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/tests/test_cli.py +8 -6
  99. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/tests/test_lifecycle_cli.py +52 -27
  100. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/tests/test_skills.py +60 -2
  101. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/tests/test_views_cli.py +13 -7
  102. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/tests/views/test_branches.py +3 -2
  103. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/tests/views/test_views.py +175 -42
  104. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/tools/docs.py +30 -26
  105. waymark_cli-0.4.0/src/waymark/assets/skills/wm-explore/SKILL.md +0 -57
  106. waymark_cli-0.4.0/tests/record/evidence/test_records.py +0 -279
  107. waymark_cli-0.4.0/tests/record/test_authored_formats.py +0 -340
  108. waymark_cli-0.4.0/tests/record/test_tasks_records.py +0 -154
  109. waymark_cli-0.4.0/tests/services/test_fix.py +0 -91
  110. waymark_cli-0.4.0/tests/services/test_lifecycle_records.py +0 -359
  111. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/.gitignore +0 -0
  112. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/LICENSE +0 -0
  113. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/docs/assets/banner-dark.svg +0 -0
  114. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/docs/assets/banner-light.svg +0 -0
  115. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/docs/assets/trail-dark.svg +0 -0
  116. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/docs/assets/trail-light.svg +0 -0
  117. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/src/waymark/__main__.py +0 -0
  118. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/src/waymark/adapters/__init__.py +0 -0
  119. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/src/waymark/adapters/claude_code.py +0 -0
  120. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/src/waymark/assets/__init__.py +0 -0
  121. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/src/waymark/assets/skills/wm-kickoff/SKILL.md +0 -0
  122. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/src/waymark/assets/skills/wm-pr/SKILL.md +0 -0
  123. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/src/waymark/hooks/__init__.py +0 -0
  124. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/src/waymark/hooks/commands.py +0 -0
  125. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/src/waymark/hooks/events.py +0 -0
  126. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/src/waymark/py.typed +0 -0
  127. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/src/waymark/record/__init__.py +0 -0
  128. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/src/waymark/record/artifacts/__init__.py +0 -0
  129. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/src/waymark/record/artifacts/config.py +0 -0
  130. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/src/waymark/record/artifacts/specs.py +0 -0
  131. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/src/waymark/record/evidence/__init__.py +0 -0
  132. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/src/waymark/record/evidence/agents.py +0 -0
  133. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/src/waymark/record/evidence/commits.py +0 -0
  134. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/src/waymark/record/machine/__init__.py +0 -0
  135. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/src/waymark/record/machine/atlas.py +0 -0
  136. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/src/waymark/record/machine/branches.py +0 -0
  137. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/src/waymark/record/machine/files.py +0 -0
  138. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/src/waymark/record/machine/git.py +0 -0
  139. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/src/waymark/record/machine/pointer.py +0 -0
  140. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/src/waymark/record/machine/project.py +0 -0
  141. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/src/waymark/record/machine/registry.py +0 -0
  142. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/src/waymark/record/markdown/__init__.py +0 -0
  143. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/src/waymark/record/markdown/links.py +0 -0
  144. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/src/waymark/record/markdown/problems.py +0 -0
  145. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/src/waymark/record/markdown/text.py +0 -0
  146. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/src/waymark/record/names.py +0 -0
  147. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/src/waymark/record/writing/__init__.py +0 -0
  148. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/src/waymark/record/writing/ignore.py +0 -0
  149. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/src/waymark/record/writing/moves.py +0 -0
  150. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/src/waymark/record/writing/store.py +0 -0
  151. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/src/waymark/record/writing/templates/ci-workflow.yml +0 -0
  152. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/src/waymark/record/writing/templates/config-atlas.toml +0 -0
  153. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/src/waymark/record/writing/templates/config.toml +0 -0
  154. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/src/waymark/record/writing/templates/milestone.md +0 -0
  155. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/src/waymark/record/writing/templates.py +0 -0
  156. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/src/waymark/services/__init__.py +0 -0
  157. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/src/waymark/services/atlas.py +0 -0
  158. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/src/waymark/services/ci.py +0 -0
  159. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/src/waymark/services/common.py +0 -0
  160. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/src/waymark/services/doctor.py +0 -0
  161. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/src/waymark/services/integration.py +0 -0
  162. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/src/waymark/services/references.py +0 -0
  163. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/src/waymark/views/__init__.py +0 -0
  164. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/src/waymark/views/init_flow.py +0 -0
  165. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/src/waymark/views/prompts.py +0 -0
  166. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/src/waymark/views/style.py +0 -0
  167. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/src/waymark/views/terminal.py +0 -0
  168. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/src/waymark/views/welcome.py +0 -0
  169. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/tests/__init__.py +0 -0
  170. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/tests/adapters/__init__.py +0 -0
  171. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/tests/adapters/snapshots/settings.json +0 -0
  172. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/tests/conftest.py +0 -0
  173. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/tests/hooks/__init__.py +0 -0
  174. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/tests/record/__init__.py +0 -0
  175. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/tests/record/artifacts/__init__.py +0 -0
  176. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/tests/record/artifacts/test_config.py +0 -0
  177. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/tests/record/evidence/__init__.py +0 -0
  178. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/tests/record/evidence/test_agents.py +0 -0
  179. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/tests/record/evidence/test_commits.py +0 -0
  180. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/tests/record/machine/__init__.py +0 -0
  181. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/tests/record/machine/test_atlas.py +0 -0
  182. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/tests/record/machine/test_git.py +0 -0
  183. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/tests/record/machine/test_registry.py +0 -0
  184. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/tests/record/markdown/__init__.py +0 -0
  185. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/tests/record/markdown/test_links.py +0 -0
  186. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/tests/record/test_names.py +0 -0
  187. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/tests/record/test_platforms.py +0 -0
  188. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/tests/record/writing/__init__.py +0 -0
  189. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/tests/record/writing/test_ignore.py +0 -0
  190. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/tests/record/writing/test_store.py +0 -0
  191. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/tests/services/__init__.py +0 -0
  192. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/tests/services/test_atlas.py +0 -0
  193. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/tests/services/test_doctor.py +0 -0
  194. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/tests/test_agent_cli.py +0 -0
  195. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/tests/test_atlas_cli.py +0 -0
  196. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/tests/test_constraints.py +0 -0
  197. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/tests/test_docs.py +0 -0
  198. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/tests/test_install_skills.py +0 -0
  199. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/tests/views/__init__.py +0 -0
  200. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/tests/views/test_prompts.py +0 -0
  201. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/tests/views/test_style.py +0 -0
  202. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/tests/views/test_terminal.py +0 -0
  203. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/tests/views/test_welcome.py +0 -0
  204. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/tests/views/validator.py +0 -0
  205. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/tools/__init__.py +0 -0
  206. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/tools/install_skills.py +0 -0
  207. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/tools/release.py +0 -0
  208. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/tools/skills/waymark-check-docs/SKILL.md +0 -0
  209. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/tools/skills/waymark-release/SKILL.md +0 -0
  210. {waymark_cli-0.4.0 → waymark_cli-0.6.0}/tools/skills/waymark-write-docs/SKILL.md +0 -0
@@ -2,6 +2,166 @@
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
+
82
+ ## [0.5.0] - 2026-11-19
83
+
84
+ Explorations get a lifecycle, and the record one style: bold labels, records
85
+ that start with their date, and every record of a change in its Log.
86
+
87
+ - **Behavior change: `parked` is no longer an exploration status.** An
88
+ exploration is `open`, `led-to <links>` or `dropped`, and `wm check` reports
89
+ `parked` as an unknown status. An open exploration's Conclusion may say what it
90
+ waits for. The record format is unchanged.
91
+ - **Behavior change: labels are bold.** Every label line in the record is
92
+ written `- **<Label>:** <text>`, the colon inside the bold: a proposal's facts,
93
+ Impact and Outcome, an item's lines, a decision's parts, a delta's `From`, `To`,
94
+ `Reason` and `Repos`, an exploration's `Status` and a resource's four lines.
95
+ The charter's glossary is `- **<term>:** <meaning>`. A label written plain, or
96
+ with the colon outside, isn't read; `wm check` reports it as `plain-label`, and
97
+ `wm check --fix` makes it bold.
98
+ - **Behavior change: every task item has a Build line**, `- **Build:** planner`
99
+ or `- **Build:** delegate`, first among its lines. An item's lines come in the
100
+ order Build, Repo, Criteria, Verify, before any record. `wm check` reports a
101
+ missing Build line as `item-incomplete` and lines out of order as `item-order`;
102
+ `wm check --fix` puts the lines in order.
103
+ - **Behavior change: a decision's options are a nested list**, one option per
104
+ bullet, at least two. An `- **Options:**` line with text of its own is reported
105
+ as `decision-options`; options are no longer split on `;` or "or".
106
+ - **Behavior change: records start with their date.** Every record, in a change
107
+ and in a milestone's Log, is written `<date> (<kind>) [<args>] [by <who>]: <text>`.
108
+ Item lists in records are separated by `, `, and a `changes` list that `covers`
109
+ follows ends with `;`, as in `2026-11-20 (review) changes 1.2, 2.2; covers 1.1,
110
+ 1.2, 2.2 by wm-reviewer: <reasons>`. A record in the older shape is reported as
111
+ `malformed-record`; no command migrates one.
112
+ - **Behavior change: a finding's severity is in brackets**, written
113
+ ``- [critical] `<place>`: <text>``.
114
+ - **Behavior change: every record of a change goes in its `## Log`.** `wm block`,
115
+ `wm gap`, `wm note`, `wm reopen`, `wm resolve <change> <item>` and an
116
+ implementer's ending write their record into the Log, naming the item after
117
+ the kind, as in `2026-11-20 (blocked) 1.2 by Ada: the API key is missing`, and
118
+ write nothing under the item. `wm check` reports a record under an item in an
119
+ active change as `misplaced-record`, and a record naming an item the change
120
+ doesn't have as `unknown-item`. `wm show` and the implement context pack still
121
+ show each item's records with the item. Each record in the `wm.show.change`
122
+ JSON has an `item` field, and the Log in `wm show` names it.
123
+ - **Upgrading from 0.4.0.** The record format is unchanged, so `wm update`
124
+ accepts a 0.4.0 record, and archived changes are read as they were written. A
125
+ change still in flight keeps its old shapes, which `wm check` now reports:
126
+ `wm check --fix` makes its labels bold and puts its item lines in order, and
127
+ you add a `- **Build:** planner` line to each item and rewrite its records in
128
+ the new shape, in its `## Log`. Or finish and archive the changes in flight
129
+ before upgrading.
130
+ - **`wm new change --from <exploration>` and `wm new milestone --from
131
+ <exploration>`** set the exploration's status to `led-to` the new change or
132
+ milestone. A second `--from` adds its link after the first.
133
+ - **Explorations are archived with their work.** `wm archive` and `wm close`
134
+ move an exploration to `explorations/archive/YYYY-MM-DD-<name>.md` once
135
+ everything it led to is archived or closed, and re-aim the links to it.
136
+ - **`wm exploration drop <exploration> --reason "<why>"`** ends an open
137
+ exploration that won't be acted on: it writes `dropped` and the reason, and
138
+ moves it to the archive.
139
+ - **Agents can't edit an exploration's status line by hand.** The hooks refuse
140
+ the edit and name `--from` and `wm exploration drop`.
141
+ - **Archived explorations in the views.** `wm show <exploration>` finds an
142
+ archived one by its name or dated name and says when it was archived, and
143
+ `wm ls explorations --archived` lists them. The explore context pack lists
144
+ active explorations only. The `wm.show.exploration` JSON is at version 2, with
145
+ an `archived_on` field, and `wm.context.explore` at version 2; both list
146
+ `dropped` instead of `parked`.
147
+ - **`wm check` reports `exploration-not-archived`** for an active exploration
148
+ whose work is all archived.
149
+ - **`wm init` and `wm update` write `explorations/archive/.gitkeep`.**
150
+ - **`/wm-explore <exploration>` picks a saved exploration back up:** it reads it,
151
+ says what in the record has changed since, and goes on from its Questions and
152
+ Approaches. Its closing offers for a saved exploration are do nothing, update or
153
+ drop it, a proposal, or a milestone, the last two created with `--from`.
154
+ - **`wm show` prints records as they are written.** The Log and each item's
155
+ records read `<date> (<kind>) …`, with item lists separated by commas, and
156
+ findings read ``[<severity>] `<place>`: <text>``. A review written without
157
+ `covers` adds a line saying it covers every item. Each record in the
158
+ `wm.show.change` JSON has a `line` field holding it as written.
159
+ - **The context packs use the record's own shapes.** An item's labels are bold,
160
+ `- **Criteria:**`, and earlier findings are in brackets, so what an agent
161
+ copies from a pack is what `wm check` expects.
162
+
163
+ Smoke test: passed on 2026-11-19 with Claude Code 2.1.328 on Windows.
164
+
5
165
  ## [0.4.0] - 2026-11-18
6
166
 
7
167
  A first impression worth the name: `wm init` welcomes you and asks what to set
@@ -1,7 +1,7 @@
1
1
  Metadata-Version: 2.5
2
2
  Name: waymark-cli
3
- Version: 0.4.0
4
- Summary: Spec-driven development for developers who stay in charge of their project while agents write the code.
3
+ Version: 0.6.0
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
7
7
  Project-URL: Issues, https://github.com/noahnkr/waymark/issues
@@ -42,11 +42,12 @@ Description-Content-Type: text/markdown
42
42
  <a href="LICENSE"><img alt="License: MIT" src="https://img.shields.io/badge/license-MIT-8a9299"></a>
43
43
  </p>
44
44
 
45
- Waymark is spec-driven development for coding agents, built on **living specs**:
46
- plain markdown in your repository that says what your system does today. Every
47
- change starts as a written plan that edits those specs, and nothing is built
48
- until you approve it. Your agent then builds from the plan, the finished change
49
- is checked against it, and the specs are updated when you sign off. A small
45
+ Waymark is spec-driven development for coding agents, anchored in **living
46
+ specs**: plain markdown in your repository that says what your system does
47
+ today. Facts an agent can't get from the code, about the services, platforms and
48
+ accounts your system depends on, are kept as **resources** linked to the specs
49
+ they serve. Each change starts as a written plan that edits the specs, is built
50
+ from that plan, and becomes part of the specs when it's done. A small
50
51
  command-line tool, `wm`, keeps track of where everything stands.
51
52
 
52
53
  ## The trail of a change
@@ -61,8 +62,8 @@ command-line tool, `wm`, keeps track of where everything stands.
61
62
 
62
63
  ## How it works
63
64
 
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:
65
+ Every piece of work takes one of three paths, depending on how much it changes
66
+ the specs:
66
67
 
67
68
  | Path | When | What gets written |
68
69
  |---|---|---|
@@ -86,7 +87,7 @@ Here's how a change goes:
86
87
  Then it checks the whole change against the plan. For a risky change, a second
87
88
  agent that never saw the build does the check.
88
89
  - **Archive.** `/wm-archive` folds the spec edits into your specs and notes what
89
- 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.
90
91
  - **Merge.** `/wm-pr` opens a pull request with the code and the updated specs,
91
92
  once you say yes. You merge it.
92
93
 
@@ -111,8 +112,9 @@ Then, in Claude Code:
111
112
  - **`/wm-kickoff`** interviews you for the project's charter, one section at a time.
112
113
  - **`/wm-onboard`** takes one real, small change on your own code through every step.
113
114
 
114
- The package is `waymark-cli`; the command is `wm`. Commit `waymark/` and
115
- `.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.
116
118
 
117
119
  <details>
118
120
  <summary><strong>Setting up a new or existing project, in one repository or several</strong></summary>
@@ -148,10 +150,14 @@ You work through skills, as slash commands in Claude Code:
148
150
  | `/wm-archive` | Finish a change and update the specs |
149
151
  | `/wm-pr` | Open the pull request, once you say yes |
150
152
 
151
- `/wm-apply` can also hand work to two agents of its own: an implementer that
152
- builds one task you marked to hand off, and a reviewer that checks a risky
153
- change. [Skills and agents](docs/skills.md) covers what each one reads, writes
154
- 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.
155
161
 
156
162
  ## See it in action
157
163
 
@@ -185,9 +191,6 @@ $ wm status
185
191
 
186
192
  > /wm-archive
187
193
 
188
- $ wm archive add-dark-mode --built "A dark theme that follows the device, and a Theme choice in Settings."
189
- Archived "add-dark-mode" as changes/archive/2026-01-15-add-dark-mode. Its deltas are now part of the specs.
190
-
191
194
  > /wm-pr
192
195
  ```
193
196
 
@@ -199,9 +202,7 @@ waymark/
199
202
  charter.md what the project is, its goals and its rules
200
203
  config.toml settings, and the pinned wm version
201
204
  changes/
202
- .gitkeep
203
205
  archive/
204
- .gitkeep
205
206
  2026-01-15-add-dark-mode/
206
207
  design.md how it's built, and the decisions
207
208
  proposal.md why, what changes, and the outcome
@@ -209,15 +210,9 @@ waymark/
209
210
  specs/
210
211
  appearance.md the change to the spec
211
212
  explorations/
212
- .gitkeep
213
213
  milestones/
214
- .gitkeep
215
- archive/
216
- .gitkeep
217
214
  resources/
218
- .gitkeep
219
215
  specs/
220
- .gitkeep
221
216
  appearance.md the living spec, now with dark mode
222
217
  ```
223
218
 
@@ -227,7 +222,8 @@ waymark/
227
222
  ```markdown
228
223
  # Add dark mode
229
224
 
230
- - Owner: Alex Example
225
+ - **Owner:** Alex Example
226
+ - **Review:** self
231
227
 
232
228
  ## Why
233
229
 
@@ -245,14 +241,14 @@ Custom colors, or themes beyond light and dark.
245
241
 
246
242
  ## Impact
247
243
 
248
- - Specs: `appearance` (new)
249
- - User-visible: a dark theme, and a Theme choice in Settings
250
- - Code: the stylesheet and the settings page
244
+ - **Specs:** `appearance` (new)
245
+ - **User-visible:** a dark theme, and a Theme choice in Settings
246
+ - **Code:** the stylesheet and the settings page
251
247
 
252
248
  ## Outcome
253
249
 
254
- - Built: A dark theme that follows the device, and a Theme choice in Settings.
255
- - Differs: none
250
+ - **Built:** A dark theme that follows the device, and a Theme choice in Settings.
251
+ - **Differs:** none
256
252
  ```
257
253
 
258
254
  </details>
@@ -277,13 +273,13 @@ stores light, dark or system.
277
273
 
278
274
  ### Decision: Default theme
279
275
 
280
- - Status: decided
281
- - Decided by: human
282
- - Options:
276
+ - **Status:** decided
277
+ - **Decided by:** human
278
+ - **Options:**
283
279
  - follow the device's setting;
284
280
  - always start light.
285
- - Choice: follow the device's setting.
286
- - Why: people who run their device dark expect apps to match without asking.
281
+ - **Choice:** follow the device's setting.
282
+ - **Why:** people who run their device dark expect apps to match without asking.
287
283
 
288
284
  ## Open questions
289
285
 
@@ -333,21 +329,28 @@ setting until the person picks one.
333
329
  ## 1. Dark mode
334
330
 
335
331
  - [x] 1.1 Move the colors into theme variables
336
- - Criteria: every color in the stylesheet comes from a variable with a light and a dark value
337
- - Verify: a search of the stylesheet finds no colors written out
332
+ - **Build:** planner
333
+ - **Criteria:** every color in the stylesheet comes from a variable with a light and a dark value
334
+ - **Verify:** a search of the stylesheet finds no colors written out
338
335
  - [x] 1.2 Follow the device's setting
339
- - Criteria: with no theme picked, the app matches the device's light or dark mode
340
- - Verify: a test for the scenario "Device set to dark"
336
+ - **Build:** planner
337
+ - **Criteria:** with no theme picked, the app matches the device's light or dark mode
338
+ - **Verify:** a test for the scenario "Device set to dark"
341
339
  - [x] 1.3 Add the Theme choice to Settings
342
- - Criteria:
340
+ - **Build:** planner
341
+ - **Criteria:**
343
342
  - Settings offers light, dark and system
344
343
  - the choice is kept between visits
345
- - Verify: a test for the scenario "Theme picked in Settings"
344
+ - **Verify:** a test for the scenario "Theme picked in Settings"
346
345
 
347
346
  ## Log
348
347
 
349
- - (accepted) 2026-01-15 fingerprint 01204aef70272f6b items 1.1 1.2 1.3 by Alex Example
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
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
351
354
  ```
352
355
 
353
356
  </details>
@@ -380,8 +383,6 @@ setting until the person picks one.
380
383
 
381
384
  </details>
382
385
 
383
- <sub>Real output of this version of <code>wm</code>, generated by <code>tools/docs.py</code>.</sub>
384
-
385
386
  <!-- end of generated evidence -->
386
387
 
387
388
  [The record](docs/record.md) explains each of these files, and everything else
@@ -389,17 +390,18 @@ that can go in them.
389
390
 
390
391
  ## Why Waymark
391
392
 
392
- - **The plan comes before the code.** Each change starts as a short written
393
+ - **The specs stay true.** Each change edits the specs, and its edits become
394
+ part of them when it's done, so they always say what your system does today.
395
+ - **Agents work from what's written.** Each change starts as a short written
393
396
  plan: what's changing, why, and how you'll know it works. Your agent builds
394
- from that. If something's missing, it asks or writes it down instead of
395
- guessing.
396
- - **You sign off twice.** Once on the plan, before anything is built, and once
397
- on the result, before the specs are updated.
397
+ from that, the specs and the resources. If something's missing, it asks or
398
+ writes it down instead of guessing.
398
399
  - **Every change gets checked.** When it's built, the whole change is checked
399
- 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.
400
402
  - **Pick up anywhere.** Everything lives in files in your repository, so any
401
403
  session on any machine can see where things stand.
402
- - **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
403
405
  risky change gets a design and a second agent to review it.
404
406
 
405
407
  <details>
@@ -428,7 +430,8 @@ for organizations that need access control or approval chains.
428
430
 
429
431
  - Nothing is built until you accept the change.
430
432
  - A change can't be accepted while a design decision or question is still open.
431
- - 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)).
432
435
  - A check can't pass while it lists a critical problem.
433
436
  - Two changes that edit the same part of a spec are flagged before the second is archived.
434
437
  - `wm check`, run in CI, keeps every file in the record well formed.
@@ -446,9 +449,9 @@ for organizations that need access control or approval chains.
446
449
  These catch mistakes and shortcuts. They aren't a security boundary against
447
450
  someone set on getting around them.
448
451
 
449
- **Teams:** each change has one owner and its own branch. If two changes edit the
450
- same requirement, the second has to be updated before it can be archived. This
451
- is caught once both are in the same branch, not before.
452
+ **Teams:** each change has one owner and its own branch, and two changes that
453
+ edit the same requirement are caught once both are on the same branch. See
454
+ [Working as a team](docs/concepts.md#working-as-a-team).
452
455
 
453
456
  </details>
454
457
 
@@ -461,7 +464,7 @@ is caught once both are in the same branch, not before.
461
464
  never calls a model or goes online.
462
465
  - **Tokens:** most of the work happens in your normal session, which already
463
466
  knows the change. A fresh agent, which has to read the plan from scratch, is
464
- 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.
465
468
  - **Your time:** answering the agent's questions while it writes the plan,
466
469
  approving each change twice, and settling what `wm inbox` lists, such as a
467
470
  gap in the plan or a blocked task.
@@ -488,7 +491,7 @@ is caught once both are in the same branch, not before.
488
491
  - **[Architecture](docs/architecture.md)**: how `wm` is built, and how to add an agent tool
489
492
  - **[Smoke test](docs/smoke-test.md)**: the manual walk-through before a release
490
493
 
491
- Works with Claude Code. Version last verified: **2.1.327**, on Windows.
494
+ Works with Claude Code. Version last verified: **2.1.330**, on Windows.
492
495
 
493
496
  ## License
494
497