docs: update CHANGELOG and version for v0.5.0

.archeflow/config.yaml

@@ -1,7 +1,7 @@
 # ArcheFlow Configuration
 # Copy to your project's .archeflow/config.yaml and customize
 
-version: "0.3.0"
+version: "0.5.0"
 
 # Budget
 costs:

.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "archeflow",
   "description": "Multi-agent orchestration with Jungian archetypes. PDCA quality cycles, shadow detection, git worktree isolation. Zero dependencies — works with any Claude Code session.",
-  "version": "0.3.0",
+  "version": "0.5.0",
   "author": {
     "name": "Chris Nennemann"
   },

CHANGELOG.md

@@ -2,6 +2,16 @@
 
 All notable changes to ArcheFlow are documented in this file.
 
+## [0.5.0] -- 2026-04-04
+
+### Added
+- Lib script validation at run initialization — fail fast if required scripts or `jq` are missing
+- Hook points documentation with 6 lifecycle events (run-start, phase-complete, agent-complete, pre-merge, post-merge, run-complete) and config template
+- Phase rollback support in `archeflow-rollback.sh` via `--to <phase>` flag
+- Per-workflow model assignment configuration with fallback chain (per-workflow per-archetype > per-workflow default > per-archetype > global default)
+- Cross-run finding regression detection in `archeflow-memory.sh` — compares current findings against previously resolved fixes
+- Check-phase parallel reviewer spawning protocol with Guardian-first sequence, A2 fast-path evaluation, timeout handling, and re-check protocol
+
 ## [0.3.0] -- 2026-04-03
 
 ### Added

README.md

@@ -309,7 +309,7 @@ archetypes: [explorer, creator, maker, guardian, db-specialist]
 
 ```
 archeflow/
-├── .claude-plugin/plugin.json   # Plugin manifest (v0.3.0)
+├── .claude-plugin/plugin.json   # Plugin manifest (v0.5.0)
 ├── agents/                      # 7 archetype personas (behavioral protocols)
 │   ├── explorer.md              #   Plan: research and context mapping
 │   ├── creator.md               #   Plan: solution design and proposals

skills/presence/SKILL.md

@@ -89,12 +89,12 @@ Only show if the user explicitly asks or if `progress.dag_on_complete: true` in
 When ArcheFlow activates at session start (via the `using-archeflow` skill), show ONE line:
 
 ```
-archeflow v0.3.0 · 24 skills · writing domain detected
+archeflow v0.5.0 · 24 skills · writing domain detected
 ```
 
 Or for code projects:
 ```
-archeflow v0.3.0 · 24 skills · code domain
+archeflow v0.5.0 · 24 skills · code domain
 ```
 
 If ArcheFlow decides NOT to activate (simple task, single file):

skills/using-archeflow/SKILL.md

@@ -11,7 +11,7 @@ Multi-agent orchestration using archetypal roles and PDCA quality cycles.
 
 On activation, print ONE line:
 ```
-archeflow v0.3.0 · 25 skills · <domain> domain
+archeflow v0.5.0 · 25 skills · <domain> domain
 ```
 Where `<domain>` is auto-detected: `writing` if `colette.yaml` exists, `research` if paper/thesis files exist, `code` otherwise. Then proceed silently — no further announcement unless `archeflow:run` is invoked.