AP1.1: Method Registry — product_milestone_driven + Methode wählbar
Deploy Development / deploy (push) Successful in 45s
Test Suite / pytest-backend (push) Successful in 1m23s
Test Suite / lint-backend (push) Successful in 2s
Test Suite / compose-smoke (push) Has been skipped
Test Suite / k6 /api/health Baseline (push) Successful in 18s
Test Suite / playwright-smoke (push) Successful in 12s

Zweite Built-in-Methode mit meilensteinorientierter NextAction-Strategie, API und UI-Auswahl pro Vorhaben; AP0.10d Validation-Vorlagen.

Co-authored-by: Cursor <cursoragent@cursor.com>
This commit is contained in:
LarsandCursor committed 2026-07-05 17:24:17 +02:00
1 parent 95feba6204
commit fc956d4ceb
27 files changed
+684 -15

No files matched your search

@@ -51,8 +51,8 @@ Die Reihenfolge „Inventar → mehr UI → irgendwann Core“ hat **lose Steuer
AP0.10b Steering UI Minimum ✓ erledigt
Scope Lock aktiv ← keine neuen Heuristiken / kein AP0.10c
AP1.0 Steering Foundation Skeleton ← NÄCHSTES Code-Paket
AP0.10d MVP Validation (5 Vorhaben) ← parallel / unmittelbar nach AP1.0
AP1.1 Method Registry + 2. Methode
AP0.10d MVP Validation (Vorlage bereit) ← Product Owner ausfüllen
AP1.1 Method Registry + product_milestone ✓ erledigt
AP1.2 Signals konsolidieren; operating_phase entfernen
AP1.3 operating_transitions → Hook Orchestrator
AP0.10c Initiative Flow UI ← erst nach AP1.2 (lifecycle-aware)