docs(02-01): complete schema extension and core domain types plan
- 02-01-SUMMARY.md with task commits, deviations, and self-check - STATE.md updated to Phase 2 Plan 1 complete - ROADMAP.md progress updated (Phase 1 complete, Phase 2 1/3) - REQUIREMENTS.md: SRCH-01 through SRCH-05, DIAG-01, DIAG-02 marked complete Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
@@ -18,11 +18,11 @@ Requirements for initial release. Each maps to roadmap phases. Tracked as Gitea
|
||||
|
||||
### Transaction Search
|
||||
|
||||
- [ ] **SRCH-01**: User can search transactions by execution status (COMPLETED, FAILED, RUNNING) (#7)
|
||||
- [ ] **SRCH-02**: User can search transactions by date/time range (startTime, endTime) (#8)
|
||||
- [ ] **SRCH-03**: User can search transactions by duration range (min/max milliseconds) (#9)
|
||||
- [ ] **SRCH-04**: User can search transactions by correlationId to find all related executions across instances (#10)
|
||||
- [ ] **SRCH-05**: User can full-text search across message bodies, headers, error messages, and stack traces (#11)
|
||||
- [x] **SRCH-01**: User can search transactions by execution status (COMPLETED, FAILED, RUNNING) (#7)
|
||||
- [x] **SRCH-02**: User can search transactions by date/time range (startTime, endTime) (#8)
|
||||
- [x] **SRCH-03**: User can search transactions by duration range (min/max milliseconds) (#9)
|
||||
- [x] **SRCH-04**: User can search transactions by correlationId to find all related executions across instances (#10)
|
||||
- [x] **SRCH-05**: User can full-text search across message bodies, headers, error messages, and stack traces (#11)
|
||||
- [ ] **SRCH-06**: User can view transaction detail with nested processor execution tree (#12)
|
||||
|
||||
### Agent Management
|
||||
@@ -37,8 +37,8 @@ Requirements for initial release. Each maps to roadmap phases. Tracked as Gitea
|
||||
|
||||
### Route Diagrams
|
||||
|
||||
- [ ] **DIAG-01**: Server stores `RouteGraph` definitions with content-addressable versioning (hash-based dedup) (#20)
|
||||
- [ ] **DIAG-02**: Each transaction links to the `RouteGraph` version that was active at execution time (#21)
|
||||
- [x] **DIAG-01**: Server stores `RouteGraph` definitions with content-addressable versioning (hash-based dedup) (#20)
|
||||
- [x] **DIAG-02**: Each transaction links to the `RouteGraph` version that was active at execution time (#21)
|
||||
- [ ] **DIAG-03**: Server renders route diagrams from stored `RouteGraph` definitions (nodes, edges, EIP patterns) (#22)
|
||||
|
||||
### Security
|
||||
|
||||
Reference in New Issue
Block a user