Summary
Audit the shipped durability claims for agents and flows, then make the public and internal docs agree with implementation.
Why
The roadmap says v6 includes durable flows, checkpoint/resume, and OpenTelemetry run spans, while internal/docs/DURABLE_EXECUTION_DESIGN.md still says the flow step/checkpoint model is a design proposal. That mismatch weakens Go Micro's positioning against Dapr, Temporal, and LangGraph.
Acceptance criteria
- Compare README, ROADMAP, website docs, internal durability docs, and implementation.
- Update stale docs or open follow-up issues for missing implementation.
- Add or identify at least one no-secret verification path for crash/resume/checkpoint behavior.
- Document exact durability semantics: agent memory, agent run checkpoints, flow runs, retries, idempotency, and what is not guaranteed.
Verification
go build ./...go test ./...golangci-lint run ./...- Relevant docs/harness checks affected by the change.
Summary
Audit the shipped durability claims for agents and flows, then make the public and internal docs agree with implementation.
Why
The roadmap says v6 includes durable flows, checkpoint/resume, and OpenTelemetry run spans, while
internal/docs/DURABLE_EXECUTION_DESIGN.mdstill says the flow step/checkpoint model is a design proposal. That mismatch weakens Go Micro's positioning against Dapr, Temporal, and LangGraph.Acceptance criteria
Verification
go build ./...go test ./...golangci-lint run ./...