| name | harness-update |
| description | Refresh an adopted target repository from the latest Harness Starter Kit reference. Use when the user asks for /harness update or wants source tracking and selective harness updates. |
| argument-hint | [target details] |
Harness Update
Refresh a target repository's harness from a confirmed kit source.
Steps
- Read
../../references/package-contract.md.
- Read
../../references/update-workflow.md.
- If
./harness-starter-kit/commands/harness-update.md exists in the target,
prefer that canonical workflow.
- Inspect target status before editing.
- Refresh or inspect the local kit reference without destructive operations.
- Classify candidates as safe, patch carefully, reference only, manual
review, or deferred.
- Apply only target-specific, non-conflicting updates.
- Update source tracking only when the current kit source is known.
- Run checks and produce the Harness Update Report.
Boundaries
- Never blindly overwrite target files.
- Never delete, replace, or re-clone a dirty target-local kit reference.
- Keep source tracking separate from patches to pre-existing dirty files.
