From df75b1d250636621022e880a5dd341ff2e804fb0 Mon Sep 17 00:00:00 2001
From: sechmachine <97589681+sechmachine727@users.noreply.github.com>
Date: Thu, 30 Jul 2026 07:40:27 +0700
Subject: [PATCH] style(openspec): normalize canonical spec eof

---
 openspec/specs/apollo-stream-policy/spec.md        | 1 -
 openspec/specs/audio-fec-resilience/spec.md        | 1 -
 openspec/specs/gateway-heartbeat-telemetry/spec.md | 1 -
 openspec/specs/provider-session-lifecycle/spec.md  | 1 -
 4 files changed, 4 deletions(-)

diff --git a/openspec/specs/apollo-stream-policy/spec.md b/openspec/specs/apollo-stream-policy/spec.md
index 509e899..5aa6e4a 100644
--- a/openspec/specs/apollo-stream-policy/spec.md
+++ b/openspec/specs/apollo-stream-policy/spec.md
@@ -20,4 +20,3 @@ The gateway MUST use the generated Protocol intersection to select only a regist
 #### Scenario: Independent peers negotiate one registered profile
 - **WHEN** a production gateway and independent client advertise overlapping registered H.264 or HEVC profiles
 - **THEN** admission selects the first policy-compatible common profile using shared Protocol behavior
-
diff --git a/openspec/specs/audio-fec-resilience/spec.md b/openspec/specs/audio-fec-resilience/spec.md
index 6c1ed2b..1ea17da 100644
--- a/openspec/specs/audio-fec-resilience/spec.md
+++ b/openspec/specs/audio-fec-resilience/spec.md
@@ -9,4 +9,3 @@ The Apollo audio recovery window SHALL remain bounded and SHALL evict the oldest
 #### Scenario: Newer complete block follows sustained loss
 - **WHEN** more than the bounded number of permanently incomplete audio blocks arrive before a complete newer block
 - **THEN** the oldest stale state is dropped, drop telemetry advances, and the newer encoded payload is relayed unchanged
-
diff --git a/openspec/specs/gateway-heartbeat-telemetry/spec.md b/openspec/specs/gateway-heartbeat-telemetry/spec.md
index ebaee37..3896fd9 100644
--- a/openspec/specs/gateway-heartbeat-telemetry/spec.md
+++ b/openspec/specs/gateway-heartbeat-telemetry/spec.md
@@ -23,4 +23,3 @@ Queue delay SHALL measure provider-queue residence, processing delay SHALL measu
 #### Scenario: Known production waits
 - **WHEN** one provider media unit has controlled enqueue, processing, and pacing intervals and fragments across multiple frames
 - **THEN** each cumulative total reports only its intended interval and exactly one processing sample is retained through authenticated Server persistence
-
diff --git a/openspec/specs/provider-session-lifecycle/spec.md b/openspec/specs/provider-session-lifecycle/spec.md
index 7d80f59..a6d96a9 100644
--- a/openspec/specs/provider-session-lifecycle/spec.md
+++ b/openspec/specs/provider-session-lifecycle/spec.md
@@ -20,4 +20,3 @@ Gateway cleanup MUST preserve `cleanup_pending` when provider input release, tra
 #### Scenario: Terminal cleanup fails
 - **WHEN** a provider terminal event is handled but required cleanup cannot complete
 - **THEN** the session is not reported released or reusable and durable state remains cleanup pending
-