haiku-method 3.4.1 → 3.6.0

package/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "haiku",
-  "version": "3.4.1",
+  "version": "3.6.0",
   "description": "H·AI·K·U methodology — universal lifecycle orchestration with hat-based workflows, completion criteria, and automatic context preservation.",
   "author": {
     "name": "GigSmart",

package/CHANGELOG.md

@@ -5,6 +5,20 @@ All notable changes to this project will be documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [3.6.0] - 2026-05-04
+
+### Added
+- Drift detection now shows image diffs side-by-side with text changes, letting you review visual artifact modifications during code review.
+- Agents can record file modifications with attribution using `haiku_record_agent_write`, creating audit trails for generated content.
+
+## [3.5.0] - 2026-05-04
+
+### Added
+- Drift detection alerts you when outputs change unexpectedly, with assessment interface to classify and approve changes
+- Knowledge upload during review lets you inject new files or context without restarting the intent
+- One-click output replacement for invalidated results in the review view
+- Coverage gap acknowledgment to mark sections intentionally out-of-scope
+
 ## [3.4.1] - 2026-05-03
 
 This release contains only internal test coverage improvements with no user-facing changes to report.

package/README.md

@@ -98,6 +98,20 @@ Each stage's gate decides whether work advances:
 
 Mix them per stage. Compound gates like `[external, ask]` let you choose at runtime.
 
+## Kill-switch — disabling drift detection
+
+H·AI·K·U ships a per-stage drift-detection gate that catches out-of-band edits to tracked files between ticks. If it ever misfires (false positives during a noisy refactor, an integration that legitimately rewrites tracked surfaces, load shedding under heavy churn), turn it off in `.haiku/settings.yml`:
+
+```yaml
+drift_detection: false
+```
+
+That single key disables the drift-detection gate for the project. Reconciliation, baseline establishment, and every other gate continue to run normally — only drift-finding emission is silenced. Flip it back to `true` (or remove the key entirely) once the noisy condition clears.
+
+**Verifying the kill-switch is live.** After flipping the flag, call `haiku_baseline_init` against any intent — the response will include a `drift_disabled_warning` key when the kill-switch is active. The flag uses the literal lowercase boolean `false`; `"false"` (string) and `False` (Python-cased) are silently ignored. If `drift_disabled_warning` is absent on the next call, the YAML key is malformed.
+
+For incident playbooks — including how to verify the kill-switch is live, how to roll back a corrupt baseline, and how to clear stuck reconciliation findings — see `.haiku/knowledge/RUNBOOK.md` inside any intent that uses drift detection.
+
 ## Links
 
 - **Method paper** — [haikumethod.ai/papers/haiku-method](https://haikumethod.ai/papers/haiku-method)