@cardor/agent-harness-kit 1.8.0 → 1.9.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.
package/LICENSE CHANGED
@@ -32,9 +32,10 @@
32
32
  not limited to compiled object code, generated documentation,
33
33
  and conversions to other media types.
34
34
 
35
- "Work" shall mean the work of authorship made available under
36
- the License, as indicated by a copyright notice that is included in
37
- or attached to the work (an example is provided in the Appendix below).
35
+ "Work" shall mean the work of authorship, whether in Source or
36
+ Object form, made available under the License, as indicated by a
37
+ copyright notice that is included in or attached to the work
38
+ (an example is provided in the Appendix below).
38
39
 
39
40
  "Derivative Works" shall mean any work, whether in Source or Object
40
41
  form, that is based on (or derived from) the Work and for which the
@@ -44,21 +45,23 @@
44
45
  separable from, or merely link (or bind by name) to the interfaces of,
45
46
  the Work and Derivative Works thereof.
46
47
 
47
- "Contribution" shall mean, as submitted to the Licensor for inclusion
48
- in the Work by the copyright owner or by an individual or Legal Entity
49
- authorized to submit on behalf of the copyright owner. For the purposes
50
- of this definition, "submitted" means any form of electronic, verbal,
51
- or written communication sent to the Licensor or its representatives,
52
- including but not limited to communication on electronic mailing lists,
53
- source code control systems, and issue tracking systems that are managed
54
- by, or on behalf of, the Licensor for the purpose of submitting to the
55
- Work, but excluding communication that is conspicuously marked or
56
- otherwise designated in writing by the copyright owner as "Not a
57
- Contribution."
58
-
59
- "Contributor" shall mean Licensor and any Legal Entity on behalf of
60
- whom a Contribution has been received by the Licensor and incorporated
61
- within the Work.
48
+ "Contribution" shall mean any work of authorship, including
49
+ the original version of the Work and any modifications or additions
50
+ to that Work or Derivative Works thereof, that is intentionally
51
+ submitted to Licensor for inclusion in the Work by the copyright owner
52
+ or by an individual or Legal Entity authorized to submit on behalf of
53
+ the copyright owner. For the purposes of this definition, "submitted"
54
+ means any form of electronic, verbal, or written communication sent
55
+ to the Licensor or its representatives, including but not limited to
56
+ communication on electronic mailing lists, source code control systems,
57
+ and issue tracking systems that are managed by, or on behalf of, the
58
+ Licensor for the purpose of discussing and improving the Work, but
59
+ excluding communication that is conspicuously marked or otherwise
60
+ designated in writing by the copyright owner as "Not a Contribution."
61
+
62
+ "Contributor" shall mean Licensor and any individual or Legal Entity
63
+ on behalf of whom a Contribution has been received by Licensor and
64
+ subsequently incorporated within the Work.
62
65
 
63
66
  2. Grant of Copyright License. Subject to the terms and conditions of
64
67
  this License, each Contributor hereby grants to You a perpetual,
@@ -74,22 +77,22 @@
74
77
  use, offer to sell, sell, import, and otherwise transfer the Work,
75
78
  where such license applies only to those patent claims licensable
76
79
  by such Contributor that are necessarily infringed by their
77
- Contribution(s) alone or by the combination of their Contribution(s)
80
+ Contribution(s) alone or by combination of their Contribution(s)
78
81
  with the Work to which such Contribution(s) was submitted. If You
79
- institute patent litigation against any entity (including a cross-claim
80
- or counterclaim in a lawsuit) alleging that the Work or any
81
- Contribution embodied within the Work constitutes direct or contributory
82
- patent infringement, then any patent licenses granted to You under
83
- this License for that Work shall terminate as of the date such
84
- litigation is filed.
82
+ institute patent litigation against any entity (including a
83
+ cross-claim or counterclaim in a lawsuit) alleging that the Work
84
+ or a Contribution incorporated within the Work constitutes direct
85
+ or contributory patent infringement, then any patent licenses
86
+ granted to You under this License for that Work shall terminate
87
+ as of the date such litigation is filed.
85
88
 
86
89
  4. Redistribution. You may reproduce and distribute copies of the
87
90
  Work or Derivative Works thereof in any medium, with or without
88
91
  modifications, and in Source or Object form, provided that You
89
92
  meet the following conditions:
90
93
 
91
- (a) You must give any other recipients of the Work or Derivative
92
- Works a copy of this License; and
94
+ (a) You must give any other recipients of the Work or
95
+ Derivative Works a copy of this License; and
93
96
 
94
97
  (b) You must cause any modified files to carry prominent notices
95
98
  stating that You changed the files; and
@@ -101,24 +104,28 @@
101
104
  the Derivative Works; and
102
105
 
103
106
  (d) If the Work includes a "NOTICE" text file as part of its
104
- distribution, You must include a readable copy of the
105
- attribution notices contained within such NOTICE file, in
106
- at least one of the following places: within a NOTICE text
107
- file distributed as part of the Derivative Works; within
108
- the Source form or documentation, if provided along with the
109
- Derivative Works; or, within a display generated by the
110
- Derivative Works, if and wherever such third-party notices
111
- normally appear. The contents of the NOTICE file are for
112
- informational purposes only and do not modify the License.
113
- You may add Your own attribution notices within Derivative
114
- Works that You distribute, alongside or in addition to the
115
- NOTICE text from the Work, provided that such additional
116
- attribution notices cannot be construed as modifying the License.
117
-
118
- You may add Your own license statement for Your modifications and
119
- may provide additional grant of rights to use, copy, modify, merge,
120
- publish, distribute, sublicense, and/or sell copies of the Work,
121
- and to permit persons to whom the Work is furnished to do so.
107
+ distribution, then any Derivative Works that You distribute must
108
+ include a readable copy of the attribution notices contained
109
+ within such NOTICE file, excluding those notices that do not
110
+ pertain to any part of the Derivative Works, in at least one
111
+ of the following places: within a NOTICE text file distributed
112
+ as part of the Derivative Works; within the Source form or
113
+ documentation, if provided along with the Derivative Works; or,
114
+ within a display generated by the Derivative Works, if and
115
+ wherever such third-party notices normally appear. The contents
116
+ of the NOTICE file are for informational purposes only and
117
+ do not modify the License. You may add Your own attribution
118
+ notices within Derivative Works that You distribute, alongside
119
+ or as an addendum to the NOTICE text from the Work, provided
120
+ that such additional attribution notices cannot be construed
121
+ as modifying the License.
122
+
123
+ You may add Your own copyright statement to Your modifications and
124
+ may provide additional or different license terms and conditions
125
+ for use, reproduction, or distribution of Your modifications, or
126
+ for any such Derivative Works as a whole, provided Your use,
127
+ reproduction, and distribution of the Work otherwise complies with
128
+ the conditions stated in this License.
122
129
 
123
130
  5. Submission of Contributions. Unless You explicitly state otherwise,
124
131
  any Contribution intentionally submitted for inclusion in the Work
@@ -137,10 +144,10 @@
137
144
  agreed to in writing, Licensor provides the Work (and each
138
145
  Contributor provides its Contributions) on an "AS IS" BASIS,
139
146
  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
140
- implied, including, without limitation, any conditions of TITLE,
141
- NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR
142
- PURPOSE. You are solely responsible for determining the
143
- appropriateness of using or reproducing the Work and assume any
147
+ implied, including, without limitation, any warranties or conditions
148
+ of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
149
+ PARTICULAR PURPOSE. You are solely responsible for determining the
150
+ appropriateness of using or redistributing the Work and assume any
144
151
  risks associated with Your exercise of permissions under this License.
145
152
 
146
153
  8. Limitation of Liability. In no event and under no legal theory,
@@ -148,23 +155,38 @@
148
155
  unless required by applicable law (such as deliberate and grossly
149
156
  negligent acts) or agreed to in writing, shall any Contributor be
150
157
  liable to You for damages, including any direct, indirect, special,
151
- incidental, or exemplary damages of any character arising as a
158
+ incidental, or consequential damages of any character arising as a
152
159
  result of this License or out of the use or inability to use the
153
- Work (even if such Contributor has been advised of the possibility
154
- of such damages).
160
+ Work (including but not limited to damages for loss of goodwill,
161
+ work stoppage, computer failure or malfunction, or any and all
162
+ other commercial damages or losses), even if such Contributor
163
+ has been advised of the possibility of such damages.
155
164
 
156
165
  9. Accepting Warranty or Additional Liability. While redistributing
157
166
  the Work or Derivative Works thereof, You may choose to offer,
158
167
  and charge a fee for, acceptance of support, warranty, indemnity,
159
168
  or other liability obligations and/or rights consistent with this
160
- License. However, in accepting such obligations, You may offer only
161
- conditions consistent with this License and indemnify each other
162
- Contributor for any liability incurred by such Contributor as a
163
- result of your offering any such warranty or additional liability.
169
+ License. However, in accepting such obligations, You may act only
170
+ on Your own behalf and on Your sole responsibility, not on behalf
171
+ of any other Contributor, and only if You agree to indemnify,
172
+ defend, and hold each Contributor harmless for any liability
173
+ incurred by, or claims asserted against, such Contributor by reason
174
+ of your accepting any such warranty or additional liability.
164
175
 
165
176
  END OF TERMS AND CONDITIONS
166
177
 
167
- Copyright 2026 enmanuelmag
178
+ APPENDIX: How to apply the Apache License to your work.
179
+
180
+ To apply the Apache License to your work, attach the following
181
+ boilerplate notice, with the fields enclosed by brackets "[]"
182
+ replaced with your own identifying information. (Don't include
183
+ the brackets!) The text should be enclosed in the appropriate
184
+ comment syntax for the file format. We also recommend that a
185
+ file or class name and description of purpose be included on the
186
+ same "printed page" as the copyright notice for easier
187
+ identification within third-party archives.
188
+
189
+ Copyright 2026 Franklin Enmanuel Magallanes Pinargote
168
190
 
169
191
  Licensed under the Apache License, Version 2.0 (the "License");
170
192
  you may not use this file except in compliance with the License.
@@ -176,4 +198,4 @@
176
198
  distributed under the License is distributed on an "AS IS" BASIS,
177
199
  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
178
200
  See the License for the specific language governing permissions and
179
- limitations under the License.
201
+ limitations under the License.
package/README.md CHANGED
@@ -115,7 +115,7 @@ Everything is stored locally in a SQLite database (`.harness/harness.db`). No cl
115
115
  - **Markdown fallback** — `current.md` is always regenerated so agents can understand the session state even without the MCP server.
116
116
  - **Docs search** — agents can call `docs.search(query)` to find relevant content in your project's docs folder before writing code.
117
117
  - **Multi-database support** — SQLite by default (zero native deps, uses `node:sqlite` on Node ≥ 22 or `bun:sqlite` on Bun). Switch to PostgreSQL or MySQL with a single config line — same schema, same MCP tools, same workflow.
118
- - **Incremental scaffold** — `ahk init` and `ahk build` never overwrite files you've customized. Agent definitions you've edited are preserved.
118
+ - **Incremental scaffold** — `ahk init` preserves files you've already customized (agent definitions you've edited are kept). `ahk build` always regenerates agent files from the latest templates so they stay up to date.
119
119
  - **Global installation** — `ahk init` can scaffold the harness into your home directory (`~/.claude` or `~/.config/opencode`) to share it across all projects.
120
120
  - **Input validation** — CLI prompts validate all inputs (name length, path format, task title, etc.) and retry with the error message instead of silently accepting bad values.
121
121
 
@@ -154,6 +154,11 @@ ahk init
154
154
 
155
155
  Interactive scaffold. Asks for your project name, description, AI provider, docs path, task adapter, and an optional first task. Creates all harness files in the current directory.
156
156
 
157
+ For Claude Code and Codex CLI (not OpenCode), you'll also be asked whether to personalize the model per agent (lead/explorer/consultant/builder/reviewer):
158
+
159
+ - Claude Code: pick from `inherit` (default), `haiku`, `sonnet`, `opus`, `fable` per agent.
160
+ - Codex CLI: free-text model name per agent — Codex does not validate this value; leaving it blank or under 3 characters means no override is written to that agent's TOML file.
161
+
157
162
  ```bash
158
163
  ahk init
159
164
 
@@ -240,7 +245,7 @@ Reports three categories:
240
245
 
241
246
  - **lib version** — compares installed version against the latest on npm. Shows `[✓]` if up to date, `[!]` if an update is available, or `[~]` if the registry could not be reached.
242
247
  - **agent files** — reads each agent file on disk and compares against what `ahk build` would generate. Reports `[!]` with the file name if outdated.
243
- - **harness skills** — checks that `ahk-ask`, `ahk-consultant`, and `ahk-triage` skills exist and match the bundled source. Reports `[!]` if missing or outdated.
248
+ - **harness skills** — checks that `ahk-ask`, `ahk-consultant`, `ahk-triage`, and `ahk-review` skills exist and match the bundled source. Reports `[!]` if missing or outdated.
244
249
 
245
250
  Run `ahk build` to fix any reported issues.
246
251
 
@@ -458,10 +463,11 @@ export default defineHarness({
458
463
  provider: 'claude-code', // 'claude-code' | 'opencode' | 'codex-cli'
459
464
 
460
465
  agents: {
461
- lead: { instructionsPath: null },
462
- explorer: { instructionsPath: null, allowedPaths: ['./docs', './src'] },
466
+ lead: { instructionsPath: null, model: 'sonnet' }, // optional per-agent model override
467
+ explorer: { instructionsPath: null, allowedPaths: ['./docs', './src'], model: 'haiku' },
463
468
  builder: { instructionsPath: null, writablePaths: ['./src', './tests'] },
464
469
  reviewer: { instructionsPath: null },
470
+ consultant: { instructionsPath: null, model: 'haiku' },
465
471
  custom: [], // define extra agents here
466
472
  },
467
473
 
@@ -521,7 +527,7 @@ echo "All checks passed."
521
527
 
522
528
  ### Agent definition files
523
529
 
524
- Created once and **never overwritten** by `ahk build` your edits are permanent.
530
+ Created by `ahk init` (which preserves existing files) and **regenerated by `ahk build`** from the latest templates. If you customise an agent file, re-running `ahk build` will overwrite your edits keep customisations in source control.
525
531
 
526
532
  **Claude Code** (`.claude/agents/*.md`) and **OpenCode** (`.opencode/agents/*.md`) use Markdown with YAML frontmatter:
527
533
 
@@ -598,23 +604,23 @@ Good acceptance criteria make the difference — the reviewer agent uses them to
598
604
 
599
605
  The harness exposes these tools via MCP. Agents use them instead of reading files directly.
600
606
 
601
- | Tool | Parameters | Description |
602
- | ------------------------- | ----------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
603
- | `tasks.get` | `status?` | List tasks, optionally filtered by `pending \| in_progress \| done \| blocked` |
604
- | `tasks.claim` | `id, agent` | Atomically claim a pending task. Returns `task_already_claimed` if another agent got it first |
605
- | `tasks.update` | `id, status` | Change task status |
606
- | `tasks.add` | `title, slug?, description?, acceptance?` | Create a new task directly from MCP (agents can queue work on the fly) |
607
- | `tasks.acceptance.update` | `criterionId` | Mark an acceptance criterion as met. Criterion IDs come from `tasks.acceptance_get` |
608
- | `actions.start` | `taskId, agent` | Start a new action, returns `actionId` |
609
- | `actions.write` | `actionId, sectionType, content` | Record a text section: `result \| tools_used \| blockers \| next_steps`. Does **not** populate the Files dashboard — use `actions.record_file` for that |
610
- | `actions.complete` | `actionId, summary` | Close an action with a one-line summary |
611
- | `actions.get` | `taskId` | Full action history for a task (all agents, all sections) |
612
- | `actions.record_file` | `actionId, filePath, operation, notes?` | Register a file touch. The **only** way to populate the Files dashboard. `operation`: `read \| created \| modified \| deleted` |
613
- | `actions.record_tool` | `actionId, toolName, argsJson?, resultSummary?` | Register a tool call. The **only** way to populate the Tools dashboard |
614
- | `docs.search` | `query` | Search the `docsPath` folder for content matching the query |
615
- | `tasks.acceptance_get` | `taskId` | Returns all acceptance criteria for a task with their `id`, `task_id`, `criterion` text, and `met` status. Use the returned `id` values with `tasks.acceptance.update` |
616
- | `deps.snapshot` | _(none)_ | Snapshot current `package.json` dependencies to `.harness/deps-lock.json` |
617
- | `deps.check` | _(none)_ | Compare current `package.json` against `.harness/deps-lock.json`. Returns `{ significant, added, removed, majorBumps, advisory }` |
607
+ | Tool | Parameters | Description |
608
+ | ------------------------- | ----------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
609
+ | `tasks.get` | `status?` | List tasks, optionally filtered by `pending \| in_progress \| done \| blocked` |
610
+ | `tasks.claim` | `id, agent` | Atomically claim a pending task. Returns `task_already_claimed` if another agent got it first |
611
+ | `tasks.update` | `id, status` | Change task status |
612
+ | `tasks.add` | `title, slug?, description?, acceptance?` | Create a new task directly from MCP (agents can queue work on the fly) |
613
+ | `tasks.acceptance.update` | `criterionId` | Mark an acceptance criterion as met. Criterion IDs come from `tasks.acceptance_get` |
614
+ | `actions.start` | `taskId, agent` | Start a new action, returns `actionId` |
615
+ | `actions.write` | `actionId, sectionType, content` | Record a text section: `result \| tools_used \| blockers \| next_steps`. Does **not** populate the Files dashboard — use `actions.record_file` for that |
616
+ | `actions.complete` | `actionId, summary` | Close an action with a one-line summary |
617
+ | `actions.get` | `taskId` | Full action history for a task (all agents, all sections) |
618
+ | `actions.record_file` | `actionId, filePath, operation, notes?` | Register a file touch. The **only** way to populate the Files dashboard. `operation`: `read \| created \| modified \| deleted` |
619
+ | `actions.record_tool` | `actionId, toolName, argsJson?, resultSummary?` | Register a tool call. The **only** way to populate the Tools dashboard |
620
+ | `docs.search` | `query` | Search the `docsPath` folder for content matching the query |
621
+ | `tasks.acceptance_get` | `taskId` | Returns all acceptance criteria for a task with their `id`, `task_id`, `criterion` text, and `met` status. Use the returned `id` values with `tasks.acceptance.update` |
622
+ | `deps.snapshot` | _(none)_ | Snapshot current `package.json` dependencies to `.harness/deps-lock.json` |
623
+ | `deps.check` | _(none)_ | Compare current `package.json` against `.harness/deps-lock.json`. Returns `{ significant, added, removed, majorBumps, advisory }` |
618
624
  | `ahk.doctor` | _(none)_ | Check lib version, agent files, and harness skills sync status. Returns `{ lib: { current, latest, outdated }, agents: { outdated, upToDate }, skills: { missing, outdated, ok } }` |
619
625
 
620
626
  ---