docs: update status log with v0.7.0 sprint

This commit is contained in:
2026-04-04 09:36:42 +02:00
parent 6854e858a4
commit 35c9f8269b

View File

@@ -29,22 +29,32 @@ Three ArcheFlow PDCA cycles in one session, each using ArcheFlow's own orchestra
- Runnable quickstart example (`examples/runnable-quickstart.md`)
- CHANGELOG completed with missing v0.4.0 entry + roadmap version history
### v0.7.0 — Superpowers-Inspired + Strategy Abstraction (8 commits, 485 lines, 20 files)
- Context isolation protocol (attention-filters + all 7 agents)
- Structured status tokens: DONE/DONE_WITH_CONCERNS/NEEDS_CONTEXT/BLOCKED
- Evidence-gated verification: banned phrases, evidence markers, downgrade-to-INFO
- Plan granularity constraint: 2-5 min tasks with file:line + code block + verify
- Strategy abstraction: `pdca` (cyclic) vs `pipeline` (linear) vs `auto` (selected by task)
- README: experimental status + interdisciplinary framing (psychology + process eng + software eng)
- Review fixes: fast→pipeline auto-select, merge guard, evidence check completeness
### Key numbers
| Metric | v0.3 → v0.6 delta |
| Metric | v0.3 → v0.7 delta |
|--------|-------------------|
| Commits this session | 21 |
| Lines added | ~1,277 |
| Files touched | 25+ |
| Commits this session | 29 |
| Lines added | ~1,762 |
| Files touched | 30+ |
| Lib scripts | 8 → 9 (archeflow-rollback.sh) |
| Skills | 24 (all now fleshed out) |
| Review cycles | 3 (Guardian + Skeptic + Sage per round) |
| Review findings fixed | 11 |
| Skills | 24 (all fleshed out, no stubs remain) |
| Review cycles | 4 (v0.4: full, v0.5: full, v0.6: fast, v0.7: Guardian-only) |
| Review findings fixed | 15 |
### What to do next
1. **End-to-end dogfood** — run `af-run` on a real task (not ArcheFlow itself) to test the full PDCA loop
2. **Hook execution runtime** the config documents 6 hook events but no runner yet
3. **Publish** — consider tagging v0.6.0 and announcing on git.xorwell.de
4. **GitHub Action** — automated PR review (roadmap item, low effort)
1. **End-to-end dogfood** — run `af-run` on a real task (not ArcheFlow itself) to test both strategies
2. **Hook execution runtime** — config documents 6 hook events but no runner yet
3. **Pipeline strategy testing** — exercise the `--strategy pipeline` path on a bug fix
4. **Publish** — tag v0.7.0, consider claude.com/plugins marketplace listing
5. **GitHub Action** — automated PR review (roadmap item, low effort)
## 2026-04-03: Major Feature Sprint (v0.1 → v0.3)