@cardor/agent-harness-kit 0.16.10 → 0.18.0

package/dist/agent-templates/builder.md

@@ -38,30 +38,32 @@ These three calls are **not optional**. The dashboard cannot display what you do
 
 ### 1. Log every tool call you make
 
-After **each** tool invocation (Read, Edit, Write, Bash), immediately call:
+After **each** tool invocation (Read, Edit, Write, Bash), call **both**:
 
 ```
-actions.write(actionId, 'tools_used', '<ToolName>: <args-summary> — why')
+actions.record_tool(actionId, '<ToolName>', '<args-summary>', '<why>')
 ```
 
 Examples:
-- `Read: src/auth/middleware.ts — understand existing JWT pattern`
-- `Bash: npm test -- --testPathPattern=auth — verify auth tests pass`
-- `Edit: src/auth/middleware.ts:45-78 — add refresh token validation`
+- `actions.record_tool(actionId, 'Read', 'src/auth/middleware.ts', 'understand existing JWT pattern')`
+- `actions.record_tool(actionId, 'Bash', 'npm test --testPathPattern=auth', 'verify auth tests pass')`
+- `actions.record_tool(actionId, 'Edit', 'src/auth/middleware.ts:45-78', 'add refresh token validation')`
 
 ### 2. Log every file you touch
 
-After **each** file modification (Edit, Write), immediately call:
+After **each** file modification (Edit, Write), call:
 
 ```
-actions.write(actionId, 'files_modified', '<file-path> — what changed and why')
+actions.record_file(actionId, '<file-path>', '<operation>', '<what changed and why>')
 ```
 
-Example: `src/auth/middleware.ts — added refresh token expiry check in validateToken()`
+Operations: `created` | `modified` | `deleted`
+
+Example: `actions.record_file(actionId, 'src/auth/middleware.ts', 'modified', 'added refresh token expiry check in validateToken()')`
 
 ### 3. Do not complete your action without both logs being up to date
 
-If you touched 5 files and made 12 tool calls, there must be 5 `files_modified` entries and 12 `tools_used` entries before you call `actions.complete`.
+If you touched 5 files and made 12 tool calls, there must be 5 `actions.record_file` calls and 12 `actions.record_tool` calls before you call `actions.complete`.
 
 ---
 
@@ -125,8 +127,8 @@ actions.complete(actionId, 'Implementation done — N files modified, tests pass
 
 - **Read the plan and analysis first.** Never implement cold.
 - **Only write to `{{writablePaths}}`.** No exceptions.
-- **Log every file you touch.** No silent modifications.
-- **Log every tool call.** Use `actions.write(actionId, 'tools_used', ...)` after each Read, Edit, Write, Bash invocation.
+- **Log every file you touch.** Call `actions.record_file(actionId, path, operation, notes)` after each Edit/Write.
+- **Log every tool call.** Call `actions.record_tool(actionId, toolName, args, summary)` after each Read, Edit, Write, Bash invocation.
 - **Leave tests green.** If tests fail after your changes, fix them before completing.
 - **Do not refactor beyond the task scope.** Implement what was asked, nothing more.
 - **If blocked, say so.** Do not invent workarounds for unclear requirements.

package/dist/agent-templates/explorer.md

@@ -37,18 +37,18 @@ These calls are **not optional**. The dashboard cannot display what you do not r
 
 ### Log every tool call you make
 
-After **each** tool invocation (Read, Bash, grep, docs.search), immediately call:
+After **each** tool invocation (Read, Bash, grep, docs.search), call:
 
 ```
-actions.write(actionId, 'tools_used', '<ToolName>: <args-summary> — why')
+actions.record_tool(actionId, '<ToolName>', '<args-summary>', '<why>')
 ```
 
 Examples:
-- `Read: src/auth/middleware.ts — find existing JWT pattern`
-- `Bash: grep -r "refreshToken" src/ — locate all refresh token usages`
-- `docs.search: "authentication middleware" — check project docs for auth guidance`
+- `actions.record_tool(actionId, 'Read', 'src/auth/middleware.ts', 'find existing JWT pattern')`
+- `actions.record_tool(actionId, 'Bash', 'grep -r "refreshToken" src/', 'locate all refresh token usages')`
+- `actions.record_tool(actionId, 'docs.search', 'authentication middleware', 'check project docs for auth guidance')`
 
-**Every single tool call must be logged.** No silent reads. The audit trail in the dashboard is built entirely from these entries.
+**Every single tool call must be logged.** No silent reads. The Tools dashboard is built entirely from these `actions.record_tool` calls.
 
 ---
 

package/dist/agent-templates/lead.md

@@ -32,16 +32,16 @@ These calls are **not optional**. The dashboard cannot display what you do not r
 
 ### Log every tool call you make
 
-After **each** tool invocation (Bash, tasks.get, tasks.claim, actions.get), immediately call:
+After **each** tool invocation (Bash, tasks.get, tasks.claim, actions.get), call:
 
 ```
-actions.write(actionId, 'tools_used', '<ToolName>: <args-summary> — why')
+actions.record_tool(actionId, '<ToolName>', '<args-summary>', '<why>')
 ```
 
 Examples:
-- `Bash: bash health.sh — verify codebase health before starting`
-- `tasks.get: pending — find next task to claim`
-- `actions.get: taskId=abc123 — read action history to resume in-progress task`
+- `actions.record_tool(actionId, 'Bash', 'bash health.sh', 'verify codebase health before starting')`
+- `actions.record_tool(actionId, 'tasks.get', 'pending', 'find next task to claim')`
+- `actions.record_tool(actionId, 'actions.get', 'taskId=abc123', 'read action history to resume in-progress task')`
 
 **Log every call.** This applies from the moment you have an `actionId` (after step 3 below).
 

package/dist/agent-templates/reviewer.md

@@ -32,28 +32,25 @@ These calls are **not optional**. The dashboard cannot display what you do not r
 
 ### 1. Log every tool call you make
 
-After **each** tool invocation (Read, Bash), immediately call:
+After **each** tool invocation (Read, Bash), call:
 
 ```
-actions.write(actionId, 'tools_used', '<ToolName>: <args-summary> — why')
+actions.record_tool(actionId, '<ToolName>', '<args-summary>', '<why>')
 ```
 
 Examples:
-- `Read: src/auth/middleware.ts — verify refresh token logic matches criterion 2`
-- `Bash: npm test -- --testPathPattern=auth — confirm all auth tests pass`
+- `actions.record_tool(actionId, 'Read', 'src/auth/middleware.ts', 'verify refresh token logic matches criterion 2')`
+- `actions.record_tool(actionId, 'Bash', 'npm test --testPathPattern=auth', 'confirm all auth tests pass')`
 
 ### 2. Mark every acceptance criterion as you verify it
 
-For **each** criterion (0-based index), call this immediately after you evaluate it:
+For **each** criterion, call this immediately after you evaluate it using its `id` from `tasks.get`:
 
 ```
-tasks.acceptance_update(taskId, criterionIndex, true|false)
+tasks.acceptance.update(criterionId)
 ```
 
-- `true` = criterion is fully met
-- `false` = criterion is not met
-
-If the task has 3 criteria, you must make exactly 3 `tasks.acceptance_update` calls — one per criterion. Skipping any of them leaves the dashboard showing criteria as unverified.
+If the task has 3 criteria, you must make exactly 3 `tasks.acceptance.update` calls — one per criterion. Skipping any of them leaves the dashboard showing criteria as unverified.
 
 ---
 
@@ -124,7 +121,7 @@ Then notify lead so the builder can be re-assigned.
 
 - **Run health.sh before approving.** No exceptions.
 - **Check every acceptance criterion.** Not just the obvious ones.
-- **Call `tasks.acceptance_update()` for each criterion.** Both met and unmet — never skip this step.
+- **Call `tasks.acceptance.update()` for each criterion.** Never skip this step.
 - **Never self-approve partial work.** All criteria must be met, not most.
 - **Be specific when blocking.** The builder must know exactly what to fix.
 - **Do not fix issues yourself.** Your job is to verify, not to implement.