Update dex design doc

[nscuro]

Worth being more elaborate and explicit about the component that forms a big part of v5's architecture backbone.

[Copilot]

Pull request overview

Expands the durable execution engine (“dex”) design documentation to be more explicit about core concepts, the PostgreSQL data model, execution/scheduling behavior, buffering/backpressure, and operational trade-offs in Dependency-Track v5.

Changes:

• Substantially elaborates the durable-execution design doc with new sections (data model, event types, buffering write paths, cache/maintenance, etc.) and updated diagrams.
• Adds additional references and “Further reading” links to support the expanded explanation.
• Updates Vale’s accepted vocabulary to avoid false positives for newly introduced terminology.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 6 comments.

File	Description
docs/concepts/architecture/design/durable-execution.md	Major expansion and clarification of the dex design document, including new diagrams/sections and more explicit semantics.
.vale/styles/config/vocabularies/DependencyTrack/accept.txt	Adds accepted terms used by the updated design doc (e.g., “Heartbeat”, “Vanlightly’s”, “scheduler’s”).

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.