From b65c354ef087bc8d0af3339c32664e50d70d70fe Mon Sep 17 00:00:00 2001
From: Developer 02 <developer02@didaloghe.onmicrosoft.com>
Date: Fri, 16 Jan 2026 01:06:22 +0100
Subject: [PATCH] Add DeleteEndpointProcedure for endpoint deletion

Introduced a new `DeleteEndpointProcedure` record in the
`ReC.Application.Common.Procedures.DeleteProcedure` namespace.

This record implements the `IDeleteProcedure` interface and includes
properties for specifying the start and end GUID/ID range, as well as
a `Force` flag to allow deletion even with dependent data.

Added a `ToObjectProcedure` method to convert the record into a
`DeleteObjectProcedure` with the entity set to "ENDPOINT".
---
 .../DeleteEndpointProcedure.cs                | 30 +++++++++++++++++++
 1 file changed, 30 insertions(+)
 create mode 100644 src/ReC.Application/Common/Procedures/DeleteProcedure/DeleteEndpointProcedure.cs

diff --git a/src/ReC.Application/Common/Procedures/DeleteProcedure/DeleteEndpointProcedure.cs b/src/ReC.Application/Common/Procedures/DeleteProcedure/DeleteEndpointProcedure.cs
new file mode 100644
index 0000000..cf71dce
--- /dev/null
+++ b/src/ReC.Application/Common/Procedures/DeleteProcedure/DeleteEndpointProcedure.cs
@@ -0,0 +1,30 @@
+namespace ReC.Application.Common.Procedures.DeleteProcedure;
+
+public record DeleteEndpointProcedure : IDeleteProcedure
+{
+    /// <summary>
+    /// Start GUID/ID (inclusive)
+    /// </summary>
+    public long Start { get; set; }
+
+    /// <summary>
+    /// End GUID/ID (inclusive). If 0, will be set to Start value.
+    /// </summary>
+    public long End { get; set; }
+
+    /// <summary>
+    /// If true, delete even if dependent ACTION data exists
+    /// </summary>
+    public bool Force { get; set; }
+
+    public DeleteObjectProcedure ToObjectProcedure()
+    {
+        return new DeleteObjectProcedure
+        {
+            Entity = "ENDPOINT",
+            Start = Start,
+            End = End,
+            Force = Force
+        };
+    }
+}