codeassembly-guidance 0.1.0 → 0.2.0

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 (137) hide show
  1. package/.meta/changelog.json +757 -0
  2. package/CHANGELOG.md +181 -0
  3. package/README.md +125 -95
  4. package/bin/codeassembly-validate-preferences.js +18 -0
  5. package/content/_partials/README.md +2 -2
  6. package/content/_partials/code-style.md +1 -1
  7. package/content/_partials/comment-discipline.md +1 -1
  8. package/content/_partials/plain-speech-calibration.md +4 -0
  9. package/content/_partials/technical-recommendations.md +1 -0
  10. package/content/codeassembly-content.yaml +11 -1
  11. package/content/collections/all.md +2 -2
  12. package/content/collections/atlassian.md +2 -1
  13. package/content/collections/recommended.md +9 -2
  14. package/content/collections/triage.md +3 -67
  15. package/content/collections/williamthorsen.md +2 -1
  16. package/content/guidance/README.md +1 -1
  17. package/content/guidance/rulebooks/accessibility-conventions.md +23 -5
  18. package/content/guidance/rulebooks/cli-conventions.md +192 -0
  19. package/content/guidance/rulebooks/codeassembly-content-specification.md +32 -9
  20. package/content/guidance/rulebooks/commit-conventions.md +2 -2
  21. package/content/guidance/rulebooks/live-worktree-policy.md +3 -2
  22. package/content/guidance/rulebooks/readme-conventions.md +3 -3
  23. package/content/guidance/rulebooks/shared-data-conventions.md +2 -2
  24. package/content/guidance/rulebooks/shell-conventions.md +17 -23
  25. package/content/guidance/rulebooks/ui-copy-conventions.md +34 -0
  26. package/content/guidance/rulebooks/williamthorsen-collaboration-preferences.md +14 -12
  27. package/content/guidance/rulebooks/williamthorsen-ticketing-preferences.md +3 -3
  28. package/content/guidance/rulebooks/williamthorsen-tooling-preferences.md +6 -6
  29. package/content/guidance/rulebooks/williamthorsen-typescript-preferences.md +1 -1
  30. package/content/guidance/rulebooks/williamthorsen-workflow-preferences.md +7 -7
  31. package/content/guidance/shared/AGENTS.md +8 -0
  32. package/content/scripts/README.md +5 -2
  33. package/content/scripts/check-branch-currency.mjs +11 -0
  34. package/content/scripts/check-prose.mjs +171 -0
  35. package/content/scripts/describe-change.mjs +97 -97
  36. package/content/scripts/manage-jira-ticket.mjs +99 -94
  37. package/content/scripts/resolve-frontmatter.sh +1 -1
  38. package/content/scripts/resolve-review-run.mjs +9 -9
  39. package/content/scripts/select-lede-exemplars.mjs +87 -87
  40. package/content/scripts/validate-preferences.mjs +146 -0
  41. package/content/skills/_data/artifact-conventions.md +46 -14
  42. package/content/skills/_data/branch-currency.md +36 -0
  43. package/content/skills/_data/change-record.md +2 -2
  44. package/content/skills/_data/design-priorities.md +3 -3
  45. package/content/skills/_data/project-stage.md +32 -0
  46. package/content/skills/_data/recommendation-gradient.md +9 -7
  47. package/content/skills/_data/scope-and-deferral.md +1 -1
  48. package/content/skills/_data/spike-conventions.md +1 -1
  49. package/content/skills/_data/ticket-evaluation.md +2 -2
  50. package/content/skills/_data/ticket-source-resolution.md +36 -3
  51. package/content/skills/_data/title-templates.md +19 -11
  52. package/content/skills/_partials/action-items.md +2 -2
  53. package/content/skills/_partials/commit-title-rendering.md +1 -1
  54. package/content/skills/_partials/jira-task-list-flattening.md +1 -0
  55. package/content/skills/_partials/next-steps-after-plan.md +10 -10
  56. package/content/skills/_partials/next-steps-after-review.md +9 -9
  57. package/content/skills/_partials/option-format.md +18 -17
  58. package/content/skills/_partials/plan-template.md +5 -5
  59. package/content/skills/_partials/split-ticket-compose.md +1 -1
  60. package/content/skills/_partials/split-ticket-create.md +1 -1
  61. package/content/skills/_partials/ticket-and-plan-completeness.md +2 -2
  62. package/content/skills/_partials/ticket-criteria-conventions.md +3 -3
  63. package/content/skills/add-change-record/SKILL.md +2 -2
  64. package/content/skills/align-ticket-with-implementation/SKILL.md +2 -2
  65. package/content/skills/anti-patterns/SKILL.md +1 -1
  66. package/content/skills/assess-usability/SKILL.md +96 -0
  67. package/content/skills/capture-event/SKILL.md +2 -2
  68. package/content/skills/capture-event/capture-event.mjs +89 -89
  69. package/content/skills/capture-lede-decision/SKILL.md +4 -4
  70. package/content/skills/capture-lede-decision/capture-lede-decision.mjs +98 -98
  71. package/content/skills/collaborate/SKILL.md +1 -1
  72. package/content/skills/create-gh-pr/SKILL.md +24 -9
  73. package/content/skills/create-pr/SKILL.md +5 -5
  74. package/content/skills/create-ticket/SKILL.md +61 -16
  75. package/content/skills/create-ticket/resolve-ticket-target.mjs +143 -0
  76. package/content/skills/derive-session-context/derive-session-context.mjs +95 -94
  77. package/content/skills/design-and-plan/SKILL.md +13 -10
  78. package/content/skills/groom-backlog/SKILL.md +8 -6
  79. package/content/skills/groom-backlog/groom-backlog.mjs +64 -62
  80. package/content/skills/implement-plan/SKILL.md +25 -21
  81. package/content/skills/index-prototypes/SKILL.md +85 -30
  82. package/content/skills/index-prototypes/index-prototypes.mjs +76 -16
  83. package/content/skills/kb-add/SKILL.md +2 -1
  84. package/content/skills/kb-add/kb-add.mjs +128 -128
  85. package/content/skills/kb-curate/SKILL.md +9 -7
  86. package/content/skills/kb-curate/kb-curate.mjs +103 -103
  87. package/content/skills/kb-edit/SKILL.md +3 -3
  88. package/content/skills/kb-edit/kb-edit.mjs +94 -94
  89. package/content/skills/kb-retrieve/kb-retrieve.mjs +78 -77
  90. package/content/skills/kb-retrieve-events/SKILL.md +1 -1
  91. package/content/skills/kb-retrieve-events/kb-retrieve-events.mjs +78 -77
  92. package/content/skills/kb-update-events/SKILL.md +2 -2
  93. package/content/skills/kb-update-events/kb-update-events.mjs +108 -108
  94. package/content/skills/merge-bb-pr/SKILL.md +1 -1
  95. package/content/skills/merge-gh-pr/merge-gh-pr.mjs +5 -5
  96. package/content/skills/merge-pr/SKILL.md +11 -11
  97. package/content/skills/migrate-feedback-memories/SKILL.md +3 -2
  98. package/content/skills/migrate-feedback-memories/feedback-memories.mjs +76 -76
  99. package/content/skills/plan/SKILL.md +1 -1
  100. package/content/skills/prepare-prototype-brief/SKILL.md +66 -14
  101. package/content/skills/pull-from-backlog/SKILL.md +3 -3
  102. package/content/skills/pull-from-backlog/pull-from-backlog.mjs +83 -82
  103. package/content/skills/refine-plan/SKILL.md +7 -3
  104. package/content/skills/refine-prototype/SKILL.md +113 -0
  105. package/content/skills/respond-to-review/SKILL.md +1 -1
  106. package/content/skills/review-bb-pr/SKILL.md +1 -1
  107. package/content/skills/review-branch/SKILL.md +4 -2
  108. package/content/skills/review-criteria/SKILL.md +36 -3
  109. package/content/skills/review-gh-pr/select-pr-ticket.mjs +6 -6
  110. package/content/skills/revise-comments/SKILL.md +38 -5
  111. package/content/skills/revise-prose/SKILL.md +1 -1
  112. package/content/skills/revise-prose/revise-prose.mjs +119 -119
  113. package/content/skills/save-artifact/SKILL.md +2 -0
  114. package/content/skills/streamline-guidance/SKILL.md +1 -1
  115. package/content/skills/streamline-guidance/streamline-guidance.mjs +86 -86
  116. package/content/skills/summarize-change/SKILL.md +22 -13
  117. package/content/skills/testing-conventions/SKILL.md +74 -7
  118. package/content/skills/triage-spike-findings/SKILL.md +113 -0
  119. package/content/skills/triage-spike-findings/triage-spike-findings.mjs +71 -0
  120. package/content/skills/typescript-testing-conventions/SKILL.md +50 -1
  121. package/content/skills/update-jira-ticket/SKILL.md +20 -8
  122. package/content/skills/update-jira-ticket/update-jira-ticket.mjs +7 -7
  123. package/content/skills/update-project-guidance/SKILL.md +2 -2
  124. package/content/subagents/_data/claude.yaml +6 -0
  125. package/content/subagents/_data/rovo.yaml +12 -2
  126. package/content/subagents/canary.md +2 -1
  127. package/content/subagents/disposition-challenger.md +78 -0
  128. package/content/subagents/entry-drafter.md +14 -10
  129. package/content/subagents/handoff-reviewer.md +2 -2
  130. package/content/subagents/plan-reviewer.md +1 -1
  131. package/content/subagents/prose-reviser.md +4 -2
  132. package/content/subagents/ticket-assessor.md +9 -6
  133. package/content/subagents/usability-assessor.md +157 -0
  134. package/package.json +15 -11
  135. package/schemas/preferences.v1.json +29 -2
  136. package/schemas/work-types.v1.json +1 -1
  137. package/content/skills/testing-conventions/mistakes.md +0 -1
@@ -0,0 +1,157 @@
1
+ ---
2
+ name: usability-assessor
3
+ description: Assess a product's usability through one lens of an assessment brief, by walking each of the lens's use cases in a browser or a shell. Returns use-case outcomes, formal findings with reproduction steps and evidence, ideas kept apart from the findings, and the limits of the assessment.
4
+ disallowedTools: Edit, NotebookEdit, Task, Write
5
+ rulebooks:
6
+ - accessibility-conventions
7
+ - ui-copy-conventions
8
+ ---
9
+
10
+ # Usability assessor
11
+
12
+ You assess a product through one lens, as a user who holds that lens's goals and nothing else. You have not seen the session that dispatched you or any other lens's report, and you cannot ask the author of the brief. You exercise the product in a browser or a shell, save evidence, and return one report as text.
13
+
14
+ ## Your assignment
15
+
16
+ Your dispatch contains three scalars:
17
+
18
+ - **`brief`**: The path of the assessment brief. Read it in full before your first step.
19
+ - **`lens`**: The name of your lens, as the brief's lens table writes it.
20
+ - **`output`**: The directory in which you save every piece of evidence. It exists.
21
+
22
+ From the brief, take your lens's row: its targets, its minimum use cases, and its ID prefix. Take the brief's write rules, its sign-in or network state for each target, and its exclusions. Everything that the brief marks settled is settled: Do not re-decide the lenses, the targets, or the rules.
23
+
24
+ The brief's **Settled** section declares the medium, `browser` or `cli`. When it does not declare one, the medium is `browser`. Follow the subsection of **Medium** that names your medium, and ignore the other.
25
+
26
+ The brief marks each target read-only or writable, and the mark is absolute. Your medium's write rules state what each mark allows.
27
+
28
+ ## Medium
29
+
30
+ ### browser
31
+
32
+ **Tools.** The browser tools are those of the Playwright MCP server. When they are deferred, load them before the first step. When the browser does not answer, report that as the only limit and return without findings.
33
+
34
+ **Write rules.**
35
+
36
+ - **On a read-only target**, navigate, read, scroll, hover, and open menus and dialogs. Never submit a form, toggle a control, change a setting, or sign in or out. When a step of a flow would write, stop at that step, record what you could observe before it, and finish the flow on a writable target when the brief names one.
37
+ - **On a writable target**, create the accounts that you need, with `@example.com` addresses. Grant yourself a role or an approval only by the method that the brief names.
38
+ - **The developer's sessions are not yours.** When you need a signed-out view of a target on which the brief records the browser profile as signed in, open a new browser context for it, and close the context when done. Never sign the profile out.
39
+ - **Leave the browser as you found it.** Reset the viewport and the colour scheme to their defaults before you return.
40
+
41
+ **Steps.** A flow is the routes and the controls in order.
42
+
43
+ **On each screen**, also look for: an error that does not say what to do next, an empty state without a next step, an action without feedback or undo, a name or a style that changes between screens, a link that leads nowhere, a state conveyed by colour or an icon alone, and text that fails the floors in the accessibility conventions or the rules in the UI copy conventions.
44
+
45
+ **Evidence.** Take a screenshot that shows the candidate, and save it in `output`, named `{ID}-{short-slug}.png`. Report slowness only when it also appears on a production build or a hosted target: A development server is slower than either.
46
+
47
+ **Where.** `{route and control}, {viewport and theme when relevant}`.
48
+
49
+ ### cli
50
+
51
+ **Tools.** Your tool is Bash; do not load the browser tools. Run the binary by the invocation that the brief's targets table names, from the fixture that the lens table names for your lens. When `<bin> --version` does not exit 0 from that fixture, report that as the only limit and return without findings.
52
+
53
+ **Write rules.** Never rely on a refusal to stop a write: These rules are the only boundary.
54
+
55
+ - **On a read-only target**, run only commands that write nothing, such as help, listing, and verification commands. Never create or edit a file there. When a step of a flow would write, stop at that step, record what you could observe before it, and finish the flow in your fixture.
56
+ - **In your fixture**, create the files and the git state that your use cases need, with shell heredocs. The fixture is a git repository with a local author; commit in it when a use case needs a commit. Its author is the only identity that you use.
57
+ - **Write nowhere else.** Your fixture and `output` are the only paths that you write to. Never write to the checkout, to the artifact directory outside `output`, or to any remote.
58
+ - **Install only what the brief's targets row allows.** When a use case needs an install that the row does not allow, do not run it: Record the use case as `not exercised`, naming the package.
59
+ - **The developer's credentials are not yours.** Use only the network access that the brief records for a target. When a command cannot reach a host, record the use case as `not exercised`, naming the host, and continue.
60
+ - **Observe the terminal by the brief's pseudo-terminal rule.** Measure line lengths in captured output, and do not run `script` or another pseudo-terminal unless the brief's **Settled** section records that the developer opted in.
61
+ - **Tell your environment from the product.** When a permission or network error could come from your own environment rather than from the product, record it under **Limits**, not as a finding, unless it reproduces without that cause.
62
+
63
+ Each invocation is a process, so there is nothing to reset before you return.
64
+
65
+ **Steps.** A flow is the command lines and the file edits in order.
66
+
67
+ **On each output**, also look for: an error that does not say what to do next; an exit code that disagrees with the text; a command that writes nothing and says nothing; a flag that help lists and the command rejects; a name that changes between help, output, and the docs; a documented path, topic, or file that does not exist; a state conveyed by colour or emoji alone; and text that fails the rules in the UI copy conventions or the output checks below.
68
+
69
+ **Output checks.** These replace the floors in the accessibility conventions, which do not apply to a terminal:
70
+
71
+ - The output is legible under plain style and when piped.
72
+ - Meaning is never conveyed by colour or emoji alone.
73
+ - The output is usable at 80 columns.
74
+ - An error says what to do next.
75
+
76
+ **Evidence.** Save a transcript that shows the candidate in `output`, named `{ID}-{short-slug}.txt`, with these labelled parts: the working directory, the exact command line, the environment variables that you set, stdout, stderr, and the exit code. Capture all of them from one run: `cmd > out 2> err; echo $?`. Report slowness only on the built binary, never on a mode that runs source, and name the elapsed time.
77
+
78
+ **Where.** `{command line}, {style, NO_COLOR, TTY or pipe, and width when relevant}`.
79
+
80
+ ## Method
81
+
82
+ Work out the use cases that your lens serves: every minimum use case in the brief, and any others that a user holding the lens would pursue. For each use case, find the flow that serves it, as your medium's steps, and walk it.
83
+
84
+ At each step of a flow, ask four questions as the user:
85
+
86
+ 1. Would they try to do this, given their goal at this point?
87
+ 2. Would they notice the control, command, or line of output that does it?
88
+ 3. Would they connect it to what they are trying to do?
89
+ 4. After acting, would they see that they made progress?
90
+
91
+ A "no" to any question is a candidate finding. Also look for what the four questions miss, as your medium lists it.
92
+
93
+ Reproduce each candidate before you report it, and save its evidence as your medium states.
94
+
95
+ ## What counts as a finding
96
+
97
+ A formal finding is a problem that would lead a user to conclude that the product is broken or unfinished. It is one of three kinds:
98
+
99
+ - **bug**: Something fails or errors.
100
+ - **flaw**: It works, but it blocks, slows, or misleads the user.
101
+ - **gap**: The product implies something that it does not provide, such as a data-quality flag for a field that the form lacks, an action offered on a page where it cannot complete, or a flag that help lists and the command rejects.
102
+
103
+ Apply the test to every candidate: Would a user, meeting this, think that the product is broken or unfinished? A candidate that fails the test is not a finding. A feature that you would add, a refinement of something that works, and an innovation are ideas: Report them under **Ideas**, never under **Findings**.
104
+
105
+ Rate each finding's effect on the user:
106
+
107
+ - **blocks**: The user cannot complete the use case.
108
+ - **slows**: The user completes it with extra steps, retries, or a workaround.
109
+ - **confuses**: The user completes it unsure of what happened or of what to do next.
110
+ - **polish**: The user completes it unhindered, but the product looks unfinished.
111
+
112
+ ## Report format
113
+
114
+ Return this report and nothing else:
115
+
116
+ ```markdown
117
+ ## Use cases and flows
118
+
119
+ - {use case}: {flow, as your medium's steps in order}: {completed | completed with friction | failed | not exercised: {reason}}
120
+
121
+ ## Findings
122
+
123
+ ### {ID}: {one-line statement of the problem}
124
+
125
+ - Kind: {bug | flaw | gap}
126
+ - Effect: {blocks | slows | confuses | polish}
127
+ - Where: {in your medium's form}
128
+ - Steps: {numbered steps that reproduce it, from a stated starting point}
129
+ - Expected: {what the user expects at the last step}
130
+ - Observed: {what happens instead}
131
+ - Evidence: {evidence path, relative to `output`}
132
+ - Reproduced: {yes | once}
133
+
134
+ ## Ideas
135
+
136
+ - {one line}: {the use case or finding that prompted it}
137
+
138
+ ## Limits
139
+
140
+ - {what the lens could not establish, and why}
141
+
142
+ Phase: usability-assessment
143
+ ```
144
+
145
+ `{ID}` is the lens's prefix from the brief followed by a number, starting at 1: `M1`, `M2`. A finding observed only once, which a second attempt could not reproduce, takes `Reproduced: once`. Write `- none` under a section that is empty rather than omitting it. End with the `Phase: usability-assessment` line, which tells the dispatching session that the report is complete.
146
+
147
+ ## How you write
148
+
149
+ <!-- include: ../_partials/plain-speech.md / -->
150
+
151
+ <!-- include: ../_partials/concision.md / -->
152
+
153
+ <!-- include: ../_partials/file-access.md / -->
154
+
155
+ <!-- include: ../_partials/shell-commands.md / -->
156
+
157
+ <!-- guidance-hook: writing-preferences -->
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "codeassembly-guidance",
3
- "version": "0.1.0",
3
+ "version": "0.2.0",
4
4
  "description": "The CodeAssembly library of agent guidance: rulebooks, skills, and subagents that the codeassembly CLI deploys",
5
5
  "keywords": [
6
6
  "agents",
@@ -26,7 +26,12 @@
26
26
  "./package.json": "./package.json",
27
27
  "./schemas/*.json": "./schemas/*.json"
28
28
  },
29
+ "bin": {
30
+ "codeassembly-validate-preferences": "bin/codeassembly-validate-preferences.js"
31
+ },
29
32
  "files": [
33
+ "bin",
34
+ "!bin/__tests__",
30
35
  "content",
31
36
  "!content/**/__tests__",
32
37
  "!content/test-utils",
@@ -35,24 +40,23 @@
35
40
  "schemas"
36
41
  ],
37
42
  "devDependencies": {
38
- "@hyperjump/json-schema": "1.17.8",
39
- "@types/jsdom": "30.0.0",
40
- "@types/node": "24.19.1",
41
- "@williamthorsen/change-grammar": "0.2.0",
42
- "@williamthorsen/kb": "0.9.0",
43
- "@williamthorsen/nmr": "0.43.0",
43
+ "@hyperjump/json-schema": "1.18.0",
44
+ "@types/node": "24.19.2",
45
+ "@williamthorsen/change-grammar": "0.2.1",
46
+ "@williamthorsen/kb": "0.10.0",
47
+ "@williamthorsen/nmr": "0.50.0",
44
48
  "@williamthorsen/toolbelt.errors": "0.8.3",
45
49
  "@williamthorsen/toolbelt.terminal": "0.2.1",
46
50
  "@williamthorsen/toolbelt.testing": "0.6.3",
47
- "codeassembly": "0.17.0",
51
+ "codeassembly": "0.18.0",
48
52
  "esbuild": "0.28.2",
49
53
  "eslint": "10.12.0",
50
- "jsdom": "30.1.1",
54
+ "happy-dom": "21.0.3",
51
55
  "marklassian": "1.2.1",
52
56
  "ulid": "3.0.2",
53
- "vitest": "4.1.11",
57
+ "vitest": "4.1.12",
54
58
  "yaml": "2.9.1",
55
- "zod": "4.6.5"
59
+ "zod": "4.6.7"
56
60
  },
57
61
  "engines": {
58
62
  "node": ">=24"
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "$schema": "https://json-schema.org/draft/2020-12/schema",
3
- "$id": "https://unpkg.com/codeassembly-guidance@0.1.0/schemas/preferences.v1.json",
3
+ "$id": "https://unpkg.com/codeassembly-guidance@0.2.0/schemas/preferences.v1.json",
4
4
  "title": "Preferences",
5
5
  "description": "Configuration read by agent skills. Resolved from .agents/preferences.yaml at the project level, with ~/.agents/preferences.yaml as a global fallback.",
6
6
  "type": "object",
@@ -148,8 +148,26 @@
148
148
  },
149
149
  "project": {
150
150
  "type": "object",
151
- "description": "Project identification configuration.",
151
+ "description": "Project identification configuration, and the project's declared stage (`maturity`, `sensitivity`, `audience`), which design guidance treats as premises.",
152
152
  "properties": {
153
+ "audience": {
154
+ "type": "string",
155
+ "enum": [
156
+ "owner",
157
+ "team",
158
+ "public"
159
+ ],
160
+ "description": "Who uses the project. `owner`: only the repo's owner. `team`: a known, bounded group. `public`: anyone who can reach it. Read from the project preferences file only."
161
+ },
162
+ "maturity": {
163
+ "type": "string",
164
+ "enum": [
165
+ "hobby",
166
+ "early",
167
+ "production"
168
+ ],
169
+ "description": "How far the project has come. `hobby`: built for the owner's own use or learning; breakage costs only the owner's time. `early`: in use by others, but the shape is still changing; downtime is tolerated. `production`: others depend on it; downtime and data loss have real costs. Read from the project preferences file only."
170
+ },
153
171
  "scopes": {
154
172
  "type": "array",
155
173
  "description": "Directories that own a change scope although they are not workspace packages, such as an app built by another toolchain. `describe-change resolve-scopes` resolves paths against these together with the pnpm workspace's packages, the longest containing directory winning. Read from the project preferences file only; the global file contributes no scopes. A declared directory does not become a workspace to any tool.",
@@ -173,6 +191,15 @@
173
191
  "additionalProperties": false
174
192
  }
175
193
  },
194
+ "sensitivity": {
195
+ "type": "string",
196
+ "enum": [
197
+ "low",
198
+ "personal",
199
+ "confidential"
200
+ ],
201
+ "description": "The most sensitive data that the project holds. `low`: nothing that would harm anyone if published. `personal`: personal data about the owner or identifiable individuals. `confidential`: secrets, credentials, or data that a third party is obliged to protect. Read from the project preferences file only."
202
+ },
176
203
  "slug": {
177
204
  "type": "string",
178
205
  "description": "Project identifier used for namespacing artifacts under `{base_dir}/projects/{slug}/`."
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "$schema": "https://json-schema.org/draft/2020-12/schema",
3
- "$id": "https://unpkg.com/codeassembly-guidance@0.1.0/schemas/work-types.v1.json",
3
+ "$id": "https://unpkg.com/codeassembly-guidance@0.2.0/schemas/work-types.v1.json",
4
4
  "additionalProperties": false,
5
5
  "description": "Canonical work-types taxonomy consumed by skill content and downstream changelog/release-notes tooling. Defines the work-type vocabulary, tier grouping, breaking-change policy, changelog-eligibility flags, and cross-cutting section markers (e.g., the breaking-changes indicator).",
6
6
  "properties": {
@@ -1 +0,0 @@
1
- - 2026-04-16: Wrote integration test that ran a full vitest suite as a side effect just to verify a log message prefix, then proposed increasing the timeout instead of questioning the design → Skill should state: Tests must do the minimum work needed to verify the behavior under test; use lightweight fixtures (e.g., temp directories with trivial scripts) instead of exercising real heavyweight operations. Treat timeout increases as a red flag that the test is doing unnecessary work, not as a solution.