waymark-cli 0.3.0__tar.gz → 0.5.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 (215) hide show
  1. {waymark_cli-0.3.0 → waymark_cli-0.5.0}/CHANGELOG.md +128 -0
  2. {waymark_cli-0.3.0 → waymark_cli-0.5.0}/PKG-INFO +41 -50
  3. {waymark_cli-0.3.0 → waymark_cli-0.5.0}/README.md +39 -48
  4. {waymark_cli-0.3.0 → waymark_cli-0.5.0}/docs/architecture.md +23 -10
  5. {waymark_cli-0.3.0 → waymark_cli-0.5.0}/docs/cli.md +36 -6
  6. {waymark_cli-0.3.0 → waymark_cli-0.5.0}/docs/concepts.md +199 -111
  7. {waymark_cli-0.3.0 → waymark_cli-0.5.0}/docs/getting-started.md +37 -14
  8. {waymark_cli-0.3.0 → waymark_cli-0.5.0}/docs/json.md +36 -6
  9. {waymark_cli-0.3.0 → waymark_cli-0.5.0}/docs/multi-repo.md +13 -9
  10. {waymark_cli-0.3.0 → waymark_cli-0.5.0}/docs/record.md +106 -65
  11. {waymark_cli-0.3.0 → waymark_cli-0.5.0}/docs/skills.md +28 -19
  12. {waymark_cli-0.3.0 → waymark_cli-0.5.0}/docs/smoke-test.md +34 -14
  13. {waymark_cli-0.3.0 → waymark_cli-0.5.0}/pyproject.toml +1 -1
  14. {waymark_cli-0.3.0 → waymark_cli-0.5.0}/src/waymark/__init__.py +1 -1
  15. {waymark_cli-0.3.0 → waymark_cli-0.5.0}/src/waymark/adapters/__init__.py +8 -0
  16. {waymark_cli-0.3.0 → waymark_cli-0.5.0}/src/waymark/adapters/claude_code.py +4 -0
  17. {waymark_cli-0.3.0 → waymark_cli-0.5.0}/src/waymark/assets/agents/wm-implementer.md +2 -2
  18. {waymark_cli-0.3.0 → waymark_cli-0.5.0}/src/waymark/assets/agents/wm-reviewer.md +2 -2
  19. {waymark_cli-0.3.0 → waymark_cli-0.5.0}/src/waymark/assets/skills/wm-apply/SKILL.md +8 -8
  20. {waymark_cli-0.3.0 → waymark_cli-0.5.0}/src/waymark/assets/skills/wm-archive/SKILL.md +1 -1
  21. waymark_cli-0.5.0/src/waymark/assets/skills/wm-explore/SKILL.md +75 -0
  22. {waymark_cli-0.3.0 → waymark_cli-0.5.0}/src/waymark/assets/skills/wm-onboard/SKILL.md +1 -1
  23. {waymark_cli-0.3.0 → waymark_cli-0.5.0}/src/waymark/assets/skills/wm-propose/SKILL.md +9 -9
  24. {waymark_cli-0.3.0 → waymark_cli-0.5.0}/src/waymark/assets/skills/wm-update/SKILL.md +7 -7
  25. {waymark_cli-0.3.0 → waymark_cli-0.5.0}/src/waymark/cli.py +96 -8
  26. {waymark_cli-0.3.0 → waymark_cli-0.5.0}/src/waymark/hooks/decide.py +27 -9
  27. waymark_cli-0.5.0/src/waymark/record/artifacts/__init__.py +1 -0
  28. {waymark_cli-0.3.0/src/waymark/record → waymark_cli-0.5.0/src/waymark/record/artifacts}/changes.py +90 -34
  29. {waymark_cli-0.3.0/src/waymark/record → waymark_cli-0.5.0/src/waymark/record/artifacts}/charter.py +8 -7
  30. {waymark_cli-0.3.0/src/waymark/record → waymark_cli-0.5.0/src/waymark/record/artifacts}/config.py +1 -1
  31. {waymark_cli-0.3.0/src/waymark/record → waymark_cli-0.5.0/src/waymark/record/artifacts}/deltas.py +41 -25
  32. {waymark_cli-0.3.0/src/waymark/record → waymark_cli-0.5.0/src/waymark/record/artifacts}/design.py +27 -22
  33. waymark_cli-0.5.0/src/waymark/record/artifacts/explorations.py +170 -0
  34. {waymark_cli-0.3.0/src/waymark/record → waymark_cli-0.5.0/src/waymark/record/artifacts}/milestones.py +7 -5
  35. {waymark_cli-0.3.0/src/waymark/record → waymark_cli-0.5.0/src/waymark/record/artifacts}/proposal.py +26 -25
  36. {waymark_cli-0.3.0/src/waymark/record → waymark_cli-0.5.0/src/waymark/record/artifacts}/resources.py +21 -13
  37. {waymark_cli-0.3.0/src/waymark/record → waymark_cli-0.5.0/src/waymark/record/artifacts}/specs.py +3 -3
  38. {waymark_cli-0.3.0/src/waymark/record → waymark_cli-0.5.0/src/waymark/record/artifacts}/tasks.py +142 -51
  39. waymark_cli-0.5.0/src/waymark/record/evidence/__init__.py +1 -0
  40. {waymark_cli-0.3.0/src/waymark/record → waymark_cli-0.5.0/src/waymark/record/evidence}/agents.py +1 -1
  41. {waymark_cli-0.3.0/src/waymark/record → waymark_cli-0.5.0/src/waymark/record/evidence}/evidence.py +37 -9
  42. {waymark_cli-0.3.0/src/waymark/record → waymark_cli-0.5.0/src/waymark/record/evidence}/fingerprint.py +7 -7
  43. {waymark_cli-0.3.0/src/waymark/record → waymark_cli-0.5.0/src/waymark/record/evidence}/records.py +196 -53
  44. waymark_cli-0.5.0/src/waymark/record/machine/__init__.py +1 -0
  45. {waymark_cli-0.3.0/src/waymark/record → waymark_cli-0.5.0/src/waymark/record/machine}/atlas.py +4 -4
  46. {waymark_cli-0.3.0/src/waymark/record → waymark_cli-0.5.0/src/waymark/record/machine}/branches.py +2 -2
  47. {waymark_cli-0.3.0/src/waymark/record → waymark_cli-0.5.0/src/waymark/record/machine}/files.py +2 -2
  48. {waymark_cli-0.3.0/src/waymark/record → waymark_cli-0.5.0/src/waymark/record/machine}/pointer.py +1 -1
  49. {waymark_cli-0.3.0/src/waymark/record → waymark_cli-0.5.0/src/waymark/record/machine}/project.py +4 -4
  50. {waymark_cli-0.3.0/src/waymark/record → waymark_cli-0.5.0/src/waymark/record/machine}/registry.py +2 -2
  51. waymark_cli-0.5.0/src/waymark/record/markdown/__init__.py +1 -0
  52. waymark_cli-0.5.0/src/waymark/record/markdown/labels.py +193 -0
  53. {waymark_cli-0.3.0/src/waymark/record → waymark_cli-0.5.0/src/waymark/record/markdown}/links.py +2 -2
  54. {waymark_cli-0.3.0/src/waymark/record → waymark_cli-0.5.0/src/waymark/record/markdown}/outline.py +13 -13
  55. {waymark_cli-0.3.0 → waymark_cli-0.5.0}/src/waymark/record/record.py +55 -13
  56. {waymark_cli-0.3.0 → waymark_cli-0.5.0}/src/waymark/record/state.py +40 -14
  57. waymark_cli-0.5.0/src/waymark/record/writing/__init__.py +1 -0
  58. {waymark_cli-0.3.0/src/waymark/record → waymark_cli-0.5.0/src/waymark/record/writing}/edits.py +23 -23
  59. {waymark_cli-0.3.0/src/waymark/record → waymark_cli-0.5.0/src/waymark/record/writing}/ignore.py +1 -1
  60. {waymark_cli-0.3.0/src/waymark/record → waymark_cli-0.5.0/src/waymark/record/writing}/layout.py +93 -8
  61. {waymark_cli-0.3.0/src/waymark/record → waymark_cli-0.5.0/src/waymark/record/writing}/moves.py +4 -4
  62. {waymark_cli-0.3.0/src/waymark/record → waymark_cli-0.5.0/src/waymark/record/writing}/store.py +1 -1
  63. {waymark_cli-0.3.0/src/waymark/record → waymark_cli-0.5.0/src/waymark/record/writing}/templates/charter.md +1 -1
  64. {waymark_cli-0.3.0/src/waymark/record → waymark_cli-0.5.0/src/waymark/record/writing}/templates/delta.md +3 -3
  65. {waymark_cli-0.3.0/src/waymark/record → waymark_cli-0.5.0/src/waymark/record/writing}/templates/design.md +7 -5
  66. waymark_cli-0.5.0/src/waymark/record/writing/templates/exploration.md +32 -0
  67. {waymark_cli-0.3.0/src/waymark/record → waymark_cli-0.5.0/src/waymark/record/writing}/templates/proposal.md +5 -5
  68. {waymark_cli-0.3.0/src/waymark/record → waymark_cli-0.5.0/src/waymark/record/writing}/templates/resource.md +4 -4
  69. {waymark_cli-0.3.0/src/waymark/record → waymark_cli-0.5.0/src/waymark/record/writing}/templates/tasks.md +9 -7
  70. {waymark_cli-0.3.0/src/waymark/record → waymark_cli-0.5.0/src/waymark/record/writing}/templates.py +1 -1
  71. {waymark_cli-0.3.0 → waymark_cli-0.5.0}/src/waymark/services/atlas.py +14 -8
  72. {waymark_cli-0.3.0 → waymark_cli-0.5.0}/src/waymark/services/check.py +34 -16
  73. {waymark_cli-0.3.0 → waymark_cli-0.5.0}/src/waymark/services/ci.py +3 -3
  74. {waymark_cli-0.3.0 → waymark_cli-0.5.0}/src/waymark/services/common.py +7 -7
  75. {waymark_cli-0.3.0 → waymark_cli-0.5.0}/src/waymark/services/context.py +13 -10
  76. {waymark_cli-0.3.0 → waymark_cli-0.5.0}/src/waymark/services/doctor.py +17 -6
  77. {waymark_cli-0.3.0 → waymark_cli-0.5.0}/src/waymark/services/fix.py +37 -20
  78. {waymark_cli-0.3.0 → waymark_cli-0.5.0}/src/waymark/services/instructions.py +39 -20
  79. {waymark_cli-0.3.0 → waymark_cli-0.5.0}/src/waymark/services/integration.py +5 -4
  80. {waymark_cli-0.3.0 → waymark_cli-0.5.0}/src/waymark/services/lifecycle.py +179 -31
  81. {waymark_cli-0.3.0 → waymark_cli-0.5.0}/src/waymark/services/pr.py +6 -6
  82. {waymark_cli-0.3.0 → waymark_cli-0.5.0}/src/waymark/services/references.py +4 -4
  83. {waymark_cli-0.3.0 → waymark_cli-0.5.0}/src/waymark/services/roadmap.py +9 -6
  84. {waymark_cli-0.3.0 → waymark_cli-0.5.0}/src/waymark/services/setup.py +94 -32
  85. waymark_cli-0.5.0/src/waymark/views/init_flow.py +128 -0
  86. {waymark_cli-0.3.0 → waymark_cli-0.5.0}/src/waymark/views/payloads.py +46 -21
  87. waymark_cli-0.5.0/src/waymark/views/prompts.py +229 -0
  88. {waymark_cli-0.3.0 → waymark_cli-0.5.0}/src/waymark/views/render.py +152 -99
  89. {waymark_cli-0.3.0 → waymark_cli-0.5.0}/src/waymark/views/schemas.py +4 -1
  90. waymark_cli-0.5.0/src/waymark/views/style.py +186 -0
  91. waymark_cli-0.5.0/src/waymark/views/terminal.py +256 -0
  92. waymark_cli-0.5.0/src/waymark/views/welcome.py +205 -0
  93. {waymark_cli-0.3.0 → waymark_cli-0.5.0}/tests/adapters/snapshots/wm-implementer.md +2 -2
  94. {waymark_cli-0.3.0 → waymark_cli-0.5.0}/tests/adapters/snapshots/wm-reviewer.md +2 -2
  95. {waymark_cli-0.3.0 → waymark_cli-0.5.0}/tests/adapters/test_claude_code.py +4 -4
  96. {waymark_cli-0.3.0 → waymark_cli-0.5.0}/tests/adapters/test_integration.py +14 -1
  97. {waymark_cli-0.3.0 → waymark_cli-0.5.0}/tests/hooks/test_commands.py +1 -0
  98. {waymark_cli-0.3.0 → waymark_cli-0.5.0}/tests/hooks/test_decide.py +90 -37
  99. {waymark_cli-0.3.0 → waymark_cli-0.5.0}/tests/hooks/test_repo_limits.py +4 -2
  100. waymark_cli-0.5.0/tests/record/artifacts/__init__.py +0 -0
  101. {waymark_cli-0.3.0/tests/record → waymark_cli-0.5.0/tests/record/artifacts}/test_config.py +1 -1
  102. {waymark_cli-0.3.0/tests/record → waymark_cli-0.5.0/tests/record/artifacts}/test_deltas.py +8 -8
  103. {waymark_cli-0.3.0/tests/record → waymark_cli-0.5.0/tests/record/artifacts}/test_resources.py +7 -7
  104. {waymark_cli-0.3.0/tests/record → waymark_cli-0.5.0/tests/record/artifacts}/test_specs.py +2 -2
  105. {waymark_cli-0.3.0/tests/record → waymark_cli-0.5.0/tests/record/artifacts}/test_tasks.py +49 -23
  106. waymark_cli-0.5.0/tests/record/evidence/__init__.py +0 -0
  107. {waymark_cli-0.3.0/tests/record → waymark_cli-0.5.0/tests/record/evidence}/test_agents.py +1 -1
  108. {waymark_cli-0.3.0/tests/record → waymark_cli-0.5.0/tests/record/evidence}/test_commits.py +1 -1
  109. {waymark_cli-0.3.0/tests/record → waymark_cli-0.5.0/tests/record/evidence}/test_evidence.py +26 -15
  110. {waymark_cli-0.3.0/tests/record → waymark_cli-0.5.0/tests/record/evidence}/test_fingerprint.py +29 -26
  111. waymark_cli-0.5.0/tests/record/evidence/test_records.py +395 -0
  112. waymark_cli-0.5.0/tests/record/machine/__init__.py +0 -0
  113. {waymark_cli-0.3.0/tests/record → waymark_cli-0.5.0/tests/record/machine}/test_atlas.py +5 -5
  114. {waymark_cli-0.3.0/tests/record → waymark_cli-0.5.0/tests/record/machine}/test_branches.py +5 -3
  115. {waymark_cli-0.3.0/tests/record → waymark_cli-0.5.0/tests/record/machine}/test_git.py +7 -1
  116. {waymark_cli-0.3.0/tests/record → waymark_cli-0.5.0/tests/record/machine}/test_project.py +3 -3
  117. {waymark_cli-0.3.0/tests/record → waymark_cli-0.5.0/tests/record/machine}/test_registry.py +1 -1
  118. waymark_cli-0.5.0/tests/record/markdown/__init__.py +0 -0
  119. waymark_cli-0.5.0/tests/record/markdown/test_labels.py +61 -0
  120. {waymark_cli-0.3.0/tests/record → waymark_cli-0.5.0/tests/record/markdown}/test_links.py +1 -1
  121. {waymark_cli-0.3.0/tests/record → waymark_cli-0.5.0/tests/record/markdown}/test_text.py +7 -1
  122. {waymark_cli-0.3.0 → waymark_cli-0.5.0}/tests/record/test_artifacts.py +27 -29
  123. waymark_cli-0.5.0/tests/record/test_authored_formats.py +553 -0
  124. {waymark_cli-0.3.0 → waymark_cli-0.5.0}/tests/record/test_platforms.py +2 -2
  125. {waymark_cli-0.3.0 → waymark_cli-0.5.0}/tests/record/test_state.py +147 -112
  126. waymark_cli-0.5.0/tests/record/test_tasks_records.py +305 -0
  127. waymark_cli-0.5.0/tests/record/writing/__init__.py +0 -0
  128. {waymark_cli-0.3.0/tests/record → waymark_cli-0.5.0/tests/record/writing}/test_ignore.py +1 -1
  129. {waymark_cli-0.3.0/tests/record → waymark_cli-0.5.0/tests/record/writing}/test_layout.py +5 -5
  130. {waymark_cli-0.3.0/tests/record → waymark_cli-0.5.0/tests/record/writing}/test_store.py +3 -3
  131. {waymark_cli-0.3.0 → waymark_cli-0.5.0}/tests/services/test_agent_interface.py +111 -46
  132. {waymark_cli-0.3.0 → waymark_cli-0.5.0}/tests/services/test_archive.py +121 -16
  133. {waymark_cli-0.3.0 → waymark_cli-0.5.0}/tests/services/test_atlas.py +3 -3
  134. {waymark_cli-0.3.0 → waymark_cli-0.5.0}/tests/services/test_check.py +223 -21
  135. {waymark_cli-0.3.0 → waymark_cli-0.5.0}/tests/services/test_ci_and_pr.py +14 -9
  136. {waymark_cli-0.3.0 → waymark_cli-0.5.0}/tests/services/test_doctor.py +16 -0
  137. waymark_cli-0.5.0/tests/services/test_fix.py +211 -0
  138. {waymark_cli-0.3.0 → waymark_cli-0.5.0}/tests/services/test_lifecycle.py +115 -33
  139. {waymark_cli-0.3.0 → waymark_cli-0.5.0}/tests/services/test_lifecycle_records.py +126 -32
  140. {waymark_cli-0.3.0 → waymark_cli-0.5.0}/tests/services/test_milestones.py +73 -4
  141. {waymark_cli-0.3.0 → waymark_cli-0.5.0}/tests/services/test_review_added_items.py +13 -11
  142. {waymark_cli-0.3.0 → waymark_cli-0.5.0}/tests/services/test_roadmap.py +8 -8
  143. {waymark_cli-0.3.0 → waymark_cli-0.5.0}/tests/services/test_setup.py +132 -22
  144. {waymark_cli-0.3.0 → waymark_cli-0.5.0}/tests/support.py +43 -20
  145. {waymark_cli-0.3.0 → waymark_cli-0.5.0}/tests/test_atlas_cli.py +1 -1
  146. {waymark_cli-0.3.0 → waymark_cli-0.5.0}/tests/test_cli.py +239 -7
  147. {waymark_cli-0.3.0 → waymark_cli-0.5.0}/tests/test_install_skills.py +2 -2
  148. {waymark_cli-0.3.0 → waymark_cli-0.5.0}/tests/test_lifecycle_cli.py +51 -27
  149. {waymark_cli-0.3.0 → waymark_cli-0.5.0}/tests/test_skills.py +46 -2
  150. waymark_cli-0.5.0/tests/test_views_cli.py +404 -0
  151. {waymark_cli-0.3.0 → waymark_cli-0.5.0}/tests/views/test_branches.py +2 -1
  152. waymark_cli-0.5.0/tests/views/test_prompts.py +149 -0
  153. waymark_cli-0.5.0/tests/views/test_style.py +155 -0
  154. waymark_cli-0.5.0/tests/views/test_terminal.py +161 -0
  155. {waymark_cli-0.3.0 → waymark_cli-0.5.0}/tests/views/test_views.py +124 -25
  156. waymark_cli-0.5.0/tests/views/test_welcome.py +156 -0
  157. {waymark_cli-0.3.0 → waymark_cli-0.5.0}/tools/docs.py +44 -27
  158. {waymark_cli-0.3.0 → waymark_cli-0.5.0}/tools/skills/waymark-check-docs/SKILL.md +1 -1
  159. {waymark_cli-0.3.0 → waymark_cli-0.5.0}/tools/skills/waymark-release/SKILL.md +10 -4
  160. waymark_cli-0.3.0/src/waymark/assets/skills/wm-explore/SKILL.md +0 -57
  161. waymark_cli-0.3.0/src/waymark/record/explorations.py +0 -132
  162. waymark_cli-0.3.0/src/waymark/record/templates/exploration.md +0 -30
  163. waymark_cli-0.3.0/src/waymark/views/style.py +0 -102
  164. waymark_cli-0.3.0/tests/record/test_authored_formats.py +0 -340
  165. waymark_cli-0.3.0/tests/record/test_records.py +0 -279
  166. waymark_cli-0.3.0/tests/record/test_tasks_records.py +0 -154
  167. waymark_cli-0.3.0/tests/services/test_fix.py +0 -91
  168. waymark_cli-0.3.0/tests/test_views_cli.py +0 -196
  169. waymark_cli-0.3.0/tests/views/test_style.py +0 -73
  170. waymark_cli-0.3.0/tools/skills/waymark-draft-docs/SKILL.md +0 -36
  171. {waymark_cli-0.3.0 → waymark_cli-0.5.0}/.gitignore +0 -0
  172. {waymark_cli-0.3.0 → waymark_cli-0.5.0}/LICENSE +0 -0
  173. {waymark_cli-0.3.0 → waymark_cli-0.5.0}/docs/assets/banner-dark.svg +0 -0
  174. {waymark_cli-0.3.0 → waymark_cli-0.5.0}/docs/assets/banner-light.svg +0 -0
  175. {waymark_cli-0.3.0 → waymark_cli-0.5.0}/docs/assets/trail-dark.svg +0 -0
  176. {waymark_cli-0.3.0 → waymark_cli-0.5.0}/docs/assets/trail-light.svg +0 -0
  177. {waymark_cli-0.3.0 → waymark_cli-0.5.0}/src/waymark/__main__.py +0 -0
  178. {waymark_cli-0.3.0 → waymark_cli-0.5.0}/src/waymark/assets/__init__.py +0 -0
  179. {waymark_cli-0.3.0 → waymark_cli-0.5.0}/src/waymark/assets/skills/wm-kickoff/SKILL.md +0 -0
  180. {waymark_cli-0.3.0 → waymark_cli-0.5.0}/src/waymark/assets/skills/wm-pr/SKILL.md +0 -0
  181. {waymark_cli-0.3.0 → waymark_cli-0.5.0}/src/waymark/hooks/__init__.py +0 -0
  182. {waymark_cli-0.3.0 → waymark_cli-0.5.0}/src/waymark/hooks/commands.py +0 -0
  183. {waymark_cli-0.3.0 → waymark_cli-0.5.0}/src/waymark/hooks/events.py +0 -0
  184. {waymark_cli-0.3.0 → waymark_cli-0.5.0}/src/waymark/py.typed +0 -0
  185. {waymark_cli-0.3.0 → waymark_cli-0.5.0}/src/waymark/record/__init__.py +0 -0
  186. {waymark_cli-0.3.0/src/waymark/record → waymark_cli-0.5.0/src/waymark/record/evidence}/commits.py +0 -0
  187. {waymark_cli-0.3.0/src/waymark/record → waymark_cli-0.5.0/src/waymark/record/machine}/git.py +0 -0
  188. {waymark_cli-0.3.0/src/waymark/record → waymark_cli-0.5.0/src/waymark/record/markdown}/problems.py +0 -0
  189. {waymark_cli-0.3.0/src/waymark/record → waymark_cli-0.5.0/src/waymark/record/markdown}/text.py +0 -0
  190. {waymark_cli-0.3.0 → waymark_cli-0.5.0}/src/waymark/record/names.py +0 -0
  191. {waymark_cli-0.3.0 → waymark_cli-0.5.0}/src/waymark/record/terms.py +0 -0
  192. {waymark_cli-0.3.0/src/waymark/record → waymark_cli-0.5.0/src/waymark/record/writing}/templates/ci-workflow.yml +0 -0
  193. {waymark_cli-0.3.0/src/waymark/record → waymark_cli-0.5.0/src/waymark/record/writing}/templates/config-atlas.toml +0 -0
  194. {waymark_cli-0.3.0/src/waymark/record → waymark_cli-0.5.0/src/waymark/record/writing}/templates/config.toml +0 -0
  195. {waymark_cli-0.3.0/src/waymark/record → waymark_cli-0.5.0/src/waymark/record/writing}/templates/milestone.md +0 -0
  196. {waymark_cli-0.3.0 → waymark_cli-0.5.0}/src/waymark/services/__init__.py +0 -0
  197. {waymark_cli-0.3.0 → waymark_cli-0.5.0}/src/waymark/services/guidance.py +0 -0
  198. {waymark_cli-0.3.0 → waymark_cli-0.5.0}/src/waymark/views/__init__.py +0 -0
  199. {waymark_cli-0.3.0 → waymark_cli-0.5.0}/tests/__init__.py +0 -0
  200. {waymark_cli-0.3.0 → waymark_cli-0.5.0}/tests/adapters/__init__.py +0 -0
  201. {waymark_cli-0.3.0 → waymark_cli-0.5.0}/tests/adapters/snapshots/settings.json +0 -0
  202. {waymark_cli-0.3.0 → waymark_cli-0.5.0}/tests/conftest.py +0 -0
  203. {waymark_cli-0.3.0 → waymark_cli-0.5.0}/tests/hooks/__init__.py +0 -0
  204. {waymark_cli-0.3.0 → waymark_cli-0.5.0}/tests/record/__init__.py +0 -0
  205. {waymark_cli-0.3.0 → waymark_cli-0.5.0}/tests/record/test_names.py +0 -0
  206. {waymark_cli-0.3.0 → waymark_cli-0.5.0}/tests/services/__init__.py +0 -0
  207. {waymark_cli-0.3.0 → waymark_cli-0.5.0}/tests/test_agent_cli.py +0 -0
  208. {waymark_cli-0.3.0 → waymark_cli-0.5.0}/tests/test_constraints.py +0 -0
  209. {waymark_cli-0.3.0 → waymark_cli-0.5.0}/tests/test_docs.py +0 -0
  210. {waymark_cli-0.3.0 → waymark_cli-0.5.0}/tests/views/__init__.py +0 -0
  211. {waymark_cli-0.3.0 → waymark_cli-0.5.0}/tests/views/validator.py +0 -0
  212. {waymark_cli-0.3.0 → waymark_cli-0.5.0}/tools/__init__.py +0 -0
  213. {waymark_cli-0.3.0 → waymark_cli-0.5.0}/tools/install_skills.py +0 -0
  214. {waymark_cli-0.3.0 → waymark_cli-0.5.0}/tools/release.py +0 -0
  215. {waymark_cli-0.3.0 → waymark_cli-0.5.0}/tools/skills/waymark-write-docs/SKILL.md +0 -0
@@ -2,6 +2,134 @@
2
2
 
3
3
  All notable changes to Waymark, one entry per release.
4
4
 
5
+ ## [0.5.0] - 2026-11-19
6
+
7
+ Explorations get a lifecycle, and the record one style: bold labels, records
8
+ that start with their date, and every record of a change in its Log.
9
+
10
+ - **Behavior change: `parked` is no longer an exploration status.** An
11
+ exploration is `open`, `led-to <links>` or `dropped`, and `wm check` reports
12
+ `parked` as an unknown status. An open exploration's Conclusion may say what it
13
+ waits for. The record format is unchanged.
14
+ - **Behavior change: labels are bold.** Every label line in the record is
15
+ written `- **<Label>:** <text>`, the colon inside the bold: a proposal's facts,
16
+ Impact and Outcome, an item's lines, a decision's parts, a delta's `From`, `To`,
17
+ `Reason` and `Repos`, an exploration's `Status` and a resource's four lines.
18
+ The charter's glossary is `- **<term>:** <meaning>`. A label written plain, or
19
+ with the colon outside, isn't read; `wm check` reports it as `plain-label`, and
20
+ `wm check --fix` makes it bold.
21
+ - **Behavior change: every task item has a Build line**, `- **Build:** planner`
22
+ or `- **Build:** delegate`, first among its lines. An item's lines come in the
23
+ order Build, Repo, Criteria, Verify, before any record. `wm check` reports a
24
+ missing Build line as `item-incomplete` and lines out of order as `item-order`;
25
+ `wm check --fix` puts the lines in order.
26
+ - **Behavior change: a decision's options are a nested list**, one option per
27
+ bullet, at least two. An `- **Options:**` line with text of its own is reported
28
+ as `decision-options`; options are no longer split on `;` or "or".
29
+ - **Behavior change: records start with their date.** Every record, in a change
30
+ and in a milestone's Log, is written `<date> (<kind>) [<args>] [by <who>]: <text>`.
31
+ Item lists in records are separated by `, `, and a `changes` list that `covers`
32
+ follows ends with `;`, as in `2026-11-20 (review) changes 1.2, 2.2; covers 1.1,
33
+ 1.2, 2.2 by wm-reviewer: <reasons>`. A record in the older shape is reported as
34
+ `malformed-record`; no command migrates one.
35
+ - **Behavior change: a finding's severity is in brackets**, written
36
+ ``- [critical] `<place>`: <text>``.
37
+ - **Behavior change: every record of a change goes in its `## Log`.** `wm block`,
38
+ `wm gap`, `wm note`, `wm reopen`, `wm resolve <change> <item>` and an
39
+ implementer's ending write their record into the Log, naming the item after
40
+ the kind, as in `2026-11-20 (blocked) 1.2 by Ada: the API key is missing`, and
41
+ write nothing under the item. `wm check` reports a record under an item in an
42
+ active change as `misplaced-record`, and a record naming an item the change
43
+ doesn't have as `unknown-item`. `wm show` and the implement context pack still
44
+ show each item's records with the item. Each record in the `wm.show.change`
45
+ JSON has an `item` field, and the Log in `wm show` names it.
46
+ - **Upgrading from 0.4.0.** The record format is unchanged, so `wm update`
47
+ accepts a 0.4.0 record, and archived changes are read as they were written. A
48
+ change still in flight keeps its old shapes, which `wm check` now reports:
49
+ `wm check --fix` makes its labels bold and puts its item lines in order, and
50
+ you add a `- **Build:** planner` line to each item and rewrite its records in
51
+ the new shape, in its `## Log`. Or finish and archive the changes in flight
52
+ before upgrading.
53
+ - **`wm new change --from <exploration>` and `wm new milestone --from
54
+ <exploration>`** set the exploration's status to `led-to` the new change or
55
+ milestone. A second `--from` adds its link after the first.
56
+ - **Explorations are archived with their work.** `wm archive` and `wm close`
57
+ move an exploration to `explorations/archive/YYYY-MM-DD-<name>.md` once
58
+ everything it led to is archived or closed, and re-aim the links to it.
59
+ - **`wm exploration drop <exploration> --reason "<why>"`** ends an open
60
+ exploration that won't be acted on: it writes `dropped` and the reason, and
61
+ moves it to the archive.
62
+ - **Agents can't edit an exploration's status line by hand.** The hooks refuse
63
+ the edit and name `--from` and `wm exploration drop`.
64
+ - **Archived explorations in the views.** `wm show <exploration>` finds an
65
+ archived one by its name or dated name and says when it was archived, and
66
+ `wm ls explorations --archived` lists them. The explore context pack lists
67
+ active explorations only. The `wm.show.exploration` JSON is at version 2, with
68
+ an `archived_on` field, and `wm.context.explore` at version 2; both list
69
+ `dropped` instead of `parked`.
70
+ - **`wm check` reports `exploration-not-archived`** for an active exploration
71
+ whose work is all archived.
72
+ - **`wm init` and `wm update` write `explorations/archive/.gitkeep`.**
73
+ - **`/wm-explore <exploration>` picks a saved exploration back up:** it reads it,
74
+ says what in the record has changed since, and goes on from its Questions and
75
+ Approaches. Its closing offers for a saved exploration are do nothing, update or
76
+ drop it, a proposal, or a milestone, the last two created with `--from`.
77
+ - **`wm show` prints records as they are written.** The Log and each item's
78
+ records read `<date> (<kind>) …`, with item lists separated by commas, and
79
+ findings read ``[<severity>] `<place>`: <text>``. A review written without
80
+ `covers` adds a line saying it covers every item. Each record in the
81
+ `wm.show.change` JSON has a `line` field holding it as written.
82
+ - **The context packs use the record's own shapes.** An item's labels are bold,
83
+ `- **Criteria:**`, and earlier findings are in brackets, so what an agent
84
+ copies from a pack is what `wm check` expects.
85
+
86
+ Smoke test: passed on 2026-11-19 with Claude Code 2.1.328 on Windows.
87
+
88
+ ## [0.4.0] - 2026-11-18
89
+
90
+ A first impression worth the name: `wm init` welcomes you and asks what to set
91
+ up, and every terminal view has one palette, tree lines and wrapped prose.
92
+ Review findings name their places relative to the project. The record format is
93
+ unchanged.
94
+
95
+ - **Behavior change: `wm init` asks on a terminal.** With both its input and its
96
+ output a terminal, and none of `--atlas`, `--tool` or the new `--yes`, it opens
97
+ with a welcome screen: the Waymark star, which grows in and twinkles, the
98
+ tagline, what it sets up, and the skills to run next. It then asks whether the
99
+ repository is a project or an atlas (and the atlas's name), which agent tools
100
+ to set up, with the ones it finds already selected, and whether to add the CI
101
+ workflow. Esc or Ctrl+C cancels and writes nothing. Where the terminal can't
102
+ read single keys, the questions come as numbered choices. In a clone, it shows
103
+ the welcome screen and asks nothing.
104
+ - **Behavior change: `wm check` groups its findings by file.** Each file's path
105
+ is on a line of its own, with its findings under it as
106
+ ` <severity>: <line>: <code>: <message>`, instead of one
107
+ `<severity>: <path>:<line>: <code>: <message>` line per finding. A script that
108
+ reads the text output should read `wm check --json`, which is unchanged.
109
+ - **`wm init --yes`** asks nothing. So do `--atlas` and `--tool`, and so does
110
+ `wm init` when its input or output isn't a terminal, as when an agent runs it:
111
+ it does what it did before.
112
+ - **A new look in the terminal.** The views use one palette of the 16 standard
113
+ colors, by role: cyan for section rules and commands, green for done, yellow for
114
+ what needs you and for warnings, red for errors, dim for dates and records, bold
115
+ for names. `wm status` colors each change's phase and progress bar and marks each
116
+ milestone's roadmap lines `◆` archived and `◇` open. `wm show` draws a change's
117
+ items as a tree and marks a milestone's roadmap. `wm doctor` lines its checks up
118
+ in one column. Each glyph has an ASCII stand-in for consoles that can't show it.
119
+ - **Prose wraps on a terminal.** `wm show`, `wm inbox`, `wm check` and
120
+ `wm doctor` wrap their prose to the terminal's width, from 60 to 100 columns.
121
+ Output that isn't going to a terminal is not wrapped, so agents read whole lines.
122
+ - **`FORCE_COLOR`.** Set to any value but empty or `0`, it turns color on when the
123
+ output isn't a terminal. `NO_COLOR` still turns color off, and wins. JSON output
124
+ never carries color.
125
+ - **Finding places are relative to the project.** `wm review` and `wm verdict`
126
+ write an absolute path in a finding's place relative to the project, with
127
+ forward slashes, or as `<repo>/<path>` for a code repo in an atlas, and refuse
128
+ any other absolute path. Before, a reviewer's absolute path went into the
129
+ record as given, home folder included.
130
+
131
+ Smoke test: passed on 2026-11-18 with Claude Code 2.1.327 on Windows.
132
+
5
133
  ## [0.3.0] - 2026-11-18
6
134
 
7
135
  Context beyond the code: resources, a spec's Background and one list of project
@@ -1,7 +1,7 @@
1
1
  Metadata-Version: 2.5
2
2
  Name: waymark-cli
3
- Version: 0.3.0
4
- Summary: Spec-driven development for developers who stay in charge of their project while agents write the code.
3
+ Version: 0.5.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
  |---|---|---|
@@ -185,9 +186,6 @@ $ wm status
185
186
 
186
187
  > /wm-archive
187
188
 
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
189
  > /wm-pr
192
190
  ```
193
191
 
@@ -199,9 +197,7 @@ waymark/
199
197
  charter.md what the project is, its goals and its rules
200
198
  config.toml settings, and the pinned wm version
201
199
  changes/
202
- .gitkeep
203
200
  archive/
204
- .gitkeep
205
201
  2026-01-15-add-dark-mode/
206
202
  design.md how it's built, and the decisions
207
203
  proposal.md why, what changes, and the outcome
@@ -209,15 +205,9 @@ waymark/
209
205
  specs/
210
206
  appearance.md the change to the spec
211
207
  explorations/
212
- .gitkeep
213
208
  milestones/
214
- .gitkeep
215
- archive/
216
- .gitkeep
217
209
  resources/
218
- .gitkeep
219
210
  specs/
220
- .gitkeep
221
211
  appearance.md the living spec, now with dark mode
222
212
  ```
223
213
 
@@ -227,7 +217,7 @@ waymark/
227
217
  ```markdown
228
218
  # Add dark mode
229
219
 
230
- - Owner: Alex Example
220
+ - **Owner:** Alex Example
231
221
 
232
222
  ## Why
233
223
 
@@ -245,14 +235,14 @@ Custom colors, or themes beyond light and dark.
245
235
 
246
236
  ## Impact
247
237
 
248
- - Specs: `appearance` (new)
249
- - User-visible: a dark theme, and a Theme choice in Settings
250
- - Code: the stylesheet and the settings page
238
+ - **Specs:** `appearance` (new)
239
+ - **User-visible:** a dark theme, and a Theme choice in Settings
240
+ - **Code:** the stylesheet and the settings page
251
241
 
252
242
  ## Outcome
253
243
 
254
- - Built: A dark theme that follows the device, and a Theme choice in Settings.
255
- - Differs: none
244
+ - **Built:** A dark theme that follows the device, and a Theme choice in Settings.
245
+ - **Differs:** none
256
246
  ```
257
247
 
258
248
  </details>
@@ -277,13 +267,13 @@ stores light, dark or system.
277
267
 
278
268
  ### Decision: Default theme
279
269
 
280
- - Status: decided
281
- - Decided by: human
282
- - Options:
270
+ - **Status:** decided
271
+ - **Decided by:** human
272
+ - **Options:**
283
273
  - follow the device's setting;
284
274
  - always start light.
285
- - Choice: follow the device's setting.
286
- - Why: people who run their device dark expect apps to match without asking.
275
+ - **Choice:** follow the device's setting.
276
+ - **Why:** people who run their device dark expect apps to match without asking.
287
277
 
288
278
  ## Open questions
289
279
 
@@ -333,21 +323,24 @@ setting until the person picks one.
333
323
  ## 1. Dark mode
334
324
 
335
325
  - [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
326
+ - **Build:** planner
327
+ - **Criteria:** every color in the stylesheet comes from a variable with a light and a dark value
328
+ - **Verify:** a search of the stylesheet finds no colors written out
338
329
  - [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"
330
+ - **Build:** planner
331
+ - **Criteria:** with no theme picked, the app matches the device's light or dark mode
332
+ - **Verify:** a test for the scenario "Device set to dark"
341
333
  - [x] 1.3 Add the Theme choice to Settings
342
- - Criteria:
334
+ - **Build:** planner
335
+ - **Criteria:**
343
336
  - Settings offers light, dark and system
344
337
  - the choice is kept between visits
345
- - Verify: a test for the scenario "Theme picked in Settings"
338
+ - **Verify:** a test for the scenario "Theme picked in Settings"
346
339
 
347
340
  ## Log
348
341
 
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
342
+ - 2026-01-15 (accepted) fingerprint c6a1ef9b1c432c26 items 1.1, 1.2, 1.3 by Alex Example
343
+ - 2026-01-15 (self-review) covers 1.1, 1.2, 1.3 by Alex Example: every criterion holds, and both scenarios have a test
351
344
  ```
352
345
 
353
346
  </details>
@@ -380,8 +373,6 @@ setting until the person picks one.
380
373
 
381
374
  </details>
382
375
 
383
- <sub>Real output of this version of <code>wm</code>, generated by <code>tools/docs.py</code>.</sub>
384
-
385
376
  <!-- end of generated evidence -->
386
377
 
387
378
  [The record](docs/record.md) explains each of these files, and everything else
@@ -389,12 +380,12 @@ that can go in them.
389
380
 
390
381
  ## Why Waymark
391
382
 
392
- - **The plan comes before the code.** Each change starts as a short written
383
+ - **The specs stay true.** Each change edits the specs, and its edits become
384
+ part of them when it's done, so they always say what your system does today.
385
+ - **Agents work from what's written.** Each change starts as a short written
393
386
  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.
387
+ from that, the specs and the resources. If something's missing, it asks or
388
+ writes it down instead of guessing.
398
389
  - **Every change gets checked.** When it's built, the whole change is checked
399
390
  against the plan, and what the check found stays with the change.
400
391
  - **Pick up anywhere.** Everything lives in files in your repository, so any
@@ -446,9 +437,9 @@ for organizations that need access control or approval chains.
446
437
  These catch mistakes and shortcuts. They aren't a security boundary against
447
438
  someone set on getting around them.
448
439
 
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.
440
+ **Teams:** each change has one owner and its own branch, and two changes that
441
+ edit the same requirement are caught once both are on the same branch. See
442
+ [Working as a team](docs/concepts.md#working-as-a-team).
452
443
 
453
444
  </details>
454
445
 
@@ -488,7 +479,7 @@ is caught once both are in the same branch, not before.
488
479
  - **[Architecture](docs/architecture.md)**: how `wm` is built, and how to add an agent tool
489
480
  - **[Smoke test](docs/smoke-test.md)**: the manual walk-through before a release
490
481
 
491
- Works with Claude Code. Version last verified: **2.1.327**, on Windows.
482
+ Works with Claude Code. Version last verified: **2.1.328**, on Windows.
492
483
 
493
484
  ## License
494
485
 
@@ -13,11 +13,12 @@
13
13
  <a href="LICENSE"><img alt="License: MIT" src="https://img.shields.io/badge/license-MIT-8a9299"></a>
14
14
  </p>
15
15
 
16
- Waymark is spec-driven development for coding agents, built on **living specs**:
17
- plain markdown in your repository that says what your system does today. Every
18
- change starts as a written plan that edits those specs, and nothing is built
19
- until you approve it. Your agent then builds from the plan, the finished change
20
- is checked against it, and the specs are updated when you sign off. A small
16
+ Waymark is spec-driven development for coding agents, anchored in **living
17
+ specs**: plain markdown in your repository that says what your system does
18
+ today. Facts an agent can't get from the code, about the services, platforms and
19
+ accounts your system depends on, are kept as **resources** linked to the specs
20
+ they serve. Each change starts as a written plan that edits the specs, is built
21
+ from that plan, and becomes part of the specs when it's done. A small
21
22
  command-line tool, `wm`, keeps track of where everything stands.
22
23
 
23
24
  ## The trail of a change
@@ -32,8 +33,8 @@ command-line tool, `wm`, keeps track of where everything stands.
32
33
 
33
34
  ## How it works
34
35
 
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:
36
+ Every piece of work takes one of three paths, depending on how much it changes
37
+ the specs:
37
38
 
38
39
  | Path | When | What gets written |
39
40
  |---|---|---|
@@ -156,9 +157,6 @@ $ wm status
156
157
 
157
158
  > /wm-archive
158
159
 
159
- $ wm archive add-dark-mode --built "A dark theme that follows the device, and a Theme choice in Settings."
160
- Archived "add-dark-mode" as changes/archive/2026-01-15-add-dark-mode. Its deltas are now part of the specs.
161
-
162
160
  > /wm-pr
163
161
  ```
164
162
 
@@ -170,9 +168,7 @@ waymark/
170
168
  charter.md what the project is, its goals and its rules
171
169
  config.toml settings, and the pinned wm version
172
170
  changes/
173
- .gitkeep
174
171
  archive/
175
- .gitkeep
176
172
  2026-01-15-add-dark-mode/
177
173
  design.md how it's built, and the decisions
178
174
  proposal.md why, what changes, and the outcome
@@ -180,15 +176,9 @@ waymark/
180
176
  specs/
181
177
  appearance.md the change to the spec
182
178
  explorations/
183
- .gitkeep
184
179
  milestones/
185
- .gitkeep
186
- archive/
187
- .gitkeep
188
180
  resources/
189
- .gitkeep
190
181
  specs/
191
- .gitkeep
192
182
  appearance.md the living spec, now with dark mode
193
183
  ```
194
184
 
@@ -198,7 +188,7 @@ waymark/
198
188
  ```markdown
199
189
  # Add dark mode
200
190
 
201
- - Owner: Alex Example
191
+ - **Owner:** Alex Example
202
192
 
203
193
  ## Why
204
194
 
@@ -216,14 +206,14 @@ Custom colors, or themes beyond light and dark.
216
206
 
217
207
  ## Impact
218
208
 
219
- - Specs: `appearance` (new)
220
- - User-visible: a dark theme, and a Theme choice in Settings
221
- - Code: the stylesheet and the settings page
209
+ - **Specs:** `appearance` (new)
210
+ - **User-visible:** a dark theme, and a Theme choice in Settings
211
+ - **Code:** the stylesheet and the settings page
222
212
 
223
213
  ## Outcome
224
214
 
225
- - Built: A dark theme that follows the device, and a Theme choice in Settings.
226
- - Differs: none
215
+ - **Built:** A dark theme that follows the device, and a Theme choice in Settings.
216
+ - **Differs:** none
227
217
  ```
228
218
 
229
219
  </details>
@@ -248,13 +238,13 @@ stores light, dark or system.
248
238
 
249
239
  ### Decision: Default theme
250
240
 
251
- - Status: decided
252
- - Decided by: human
253
- - Options:
241
+ - **Status:** decided
242
+ - **Decided by:** human
243
+ - **Options:**
254
244
  - follow the device's setting;
255
245
  - always start light.
256
- - Choice: follow the device's setting.
257
- - Why: people who run their device dark expect apps to match without asking.
246
+ - **Choice:** follow the device's setting.
247
+ - **Why:** people who run their device dark expect apps to match without asking.
258
248
 
259
249
  ## Open questions
260
250
 
@@ -304,21 +294,24 @@ setting until the person picks one.
304
294
  ## 1. Dark mode
305
295
 
306
296
  - [x] 1.1 Move the colors into theme variables
307
- - Criteria: every color in the stylesheet comes from a variable with a light and a dark value
308
- - Verify: a search of the stylesheet finds no colors written out
297
+ - **Build:** planner
298
+ - **Criteria:** every color in the stylesheet comes from a variable with a light and a dark value
299
+ - **Verify:** a search of the stylesheet finds no colors written out
309
300
  - [x] 1.2 Follow the device's setting
310
- - Criteria: with no theme picked, the app matches the device's light or dark mode
311
- - Verify: a test for the scenario "Device set to dark"
301
+ - **Build:** planner
302
+ - **Criteria:** with no theme picked, the app matches the device's light or dark mode
303
+ - **Verify:** a test for the scenario "Device set to dark"
312
304
  - [x] 1.3 Add the Theme choice to Settings
313
- - Criteria:
305
+ - **Build:** planner
306
+ - **Criteria:**
314
307
  - Settings offers light, dark and system
315
308
  - the choice is kept between visits
316
- - Verify: a test for the scenario "Theme picked in Settings"
309
+ - **Verify:** a test for the scenario "Theme picked in Settings"
317
310
 
318
311
  ## Log
319
312
 
320
- - (accepted) 2026-01-15 fingerprint 01204aef70272f6b items 1.1 1.2 1.3 by Alex Example
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
313
+ - 2026-01-15 (accepted) fingerprint c6a1ef9b1c432c26 items 1.1, 1.2, 1.3 by Alex Example
314
+ - 2026-01-15 (self-review) covers 1.1, 1.2, 1.3 by Alex Example: every criterion holds, and both scenarios have a test
322
315
  ```
323
316
 
324
317
  </details>
@@ -351,8 +344,6 @@ setting until the person picks one.
351
344
 
352
345
  </details>
353
346
 
354
- <sub>Real output of this version of <code>wm</code>, generated by <code>tools/docs.py</code>.</sub>
355
-
356
347
  <!-- end of generated evidence -->
357
348
 
358
349
  [The record](docs/record.md) explains each of these files, and everything else
@@ -360,12 +351,12 @@ that can go in them.
360
351
 
361
352
  ## Why Waymark
362
353
 
363
- - **The plan comes before the code.** Each change starts as a short written
354
+ - **The specs stay true.** Each change edits the specs, and its edits become
355
+ part of them when it's done, so they always say what your system does today.
356
+ - **Agents work from what's written.** Each change starts as a short written
364
357
  plan: what's changing, why, and how you'll know it works. Your agent builds
365
- from that. If something's missing, it asks or writes it down instead of
366
- guessing.
367
- - **You sign off twice.** Once on the plan, before anything is built, and once
368
- on the result, before the specs are updated.
358
+ from that, the specs and the resources. If something's missing, it asks or
359
+ writes it down instead of guessing.
369
360
  - **Every change gets checked.** When it's built, the whole change is checked
370
361
  against the plan, and what the check found stays with the change.
371
362
  - **Pick up anywhere.** Everything lives in files in your repository, so any
@@ -417,9 +408,9 @@ for organizations that need access control or approval chains.
417
408
  These catch mistakes and shortcuts. They aren't a security boundary against
418
409
  someone set on getting around them.
419
410
 
420
- **Teams:** each change has one owner and its own branch. If two changes edit the
421
- same requirement, the second has to be updated before it can be archived. This
422
- is caught once both are in the same branch, not before.
411
+ **Teams:** each change has one owner and its own branch, and two changes that
412
+ edit the same requirement are caught once both are on the same branch. See
413
+ [Working as a team](docs/concepts.md#working-as-a-team).
423
414
 
424
415
  </details>
425
416
 
@@ -459,7 +450,7 @@ is caught once both are in the same branch, not before.
459
450
  - **[Architecture](docs/architecture.md)**: how `wm` is built, and how to add an agent tool
460
451
  - **[Smoke test](docs/smoke-test.md)**: the manual walk-through before a release
461
452
 
462
- Works with Claude Code. Version last verified: **2.1.327**, on Windows.
453
+ Works with Claude Code. Version last verified: **2.1.328**, on Windows.
463
454
 
464
455
  ## License
465
456
 
@@ -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
- | `hooks/` | Tool-neutral hook decisions on six neutral events. |
58
+ | `hooks/` | Tool-neutral hook decisions on seven 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
 
@@ -142,12 +150,10 @@ and again whenever they change:
142
150
  uv run --no-sync python -m tools.install_skills
143
151
  ```
144
152
 
145
-
146
153
  | Skill | For |
147
154
  |---|---|
148
- | `waymark-draft-docs` | Planning and drafting a new or rewritten docs page with the maintainer |
149
155
  | `waymark-write-docs` | The house style and fact rules for any docs edit |
150
- | `waymark-check-docs` | Checking docs against the code, on request |
156
+ | `waymark-check-docs` | Checking docs against the code, on request or when a release offers it |
151
157
  | `waymark-release` | Cutting a release, from audit to tag |
152
158
 
153
159
  CI runs the tests on Windows, macOS and Linux, each on Python 3.11 and the newest
@@ -169,17 +175,24 @@ is committed.
169
175
 
170
176
  **Commits** follow [Conventional Commits](https://www.conventionalcommits.org/),
171
177
  scoped by component (`record`, `services`, `views`, `hooks`, `adapter-claude`,
172
- `cli`, `skills`, `docs`, `ci`, `build`), in American English.
178
+ `cli`, `skills`, `docs`, `ci`, `build`, `release`, `plan`), in American English.
173
179
 
174
180
  ## Releasing
175
181
 
182
+ Each change with a User-visible line adds it to `CHANGELOG.md` under
183
+ `## [Unreleased]`, in the item that updates its docs.
184
+
176
185
  The maintainer releases, with the `waymark-release` skill. Before each release, the
177
186
  [smoke-test checklist](smoke-test.md) is run by hand, and its result goes into the
178
187
  changelog's entry. The skill:
179
188
 
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`.
189
+ 1. checks `## [Unreleased]` against the changes archived since the last tag, and
190
+ lists the review findings they left open, for the maintainer to fix, plan or drop;
191
+ 2. sets the version in `src/waymark/__init__.py` and the pin in `waymark/config.toml`,
192
+ and turns `## [Unreleased]` into the dated entry in `CHANGELOG.md`, on a release
193
+ branch;
194
+ 3. offers `waymark-check-docs` on the docs pages changed since the last tag;
195
+ 4. opens the pull request; after it is merged, pushes a tag `v<version>` on `main`.
183
196
 
184
197
  The release workflow checks that the tag, the version, the changelog entry and the
185
198
  smoke-test record agree, runs the tests, builds, publishes to PyPI through trusted