LCORE-2661: Automatic conversation expiration: the stub

Author: tisnik

docs/design/automatic-conversation-expiration/automatic-conversation-expiration-spike.md

@@ -0,0 +1,17 @@
+# Spike for the Automatic conversation expiration
+
+## Overview
+
+**The problem**: Conversation history can already be manually deleted, but
+customers who operate high-security environments would like some strong
+controls over conversation persistence. Since conversations require some level
+of persistence, they have accepted the idea of conversations having a
+configurable idle timer. If a conversation is idle for a certain amount of
+time, the conversation becomes automatically deleted from any/all persistence
+layers. This requirement was communicated to us (the RHOKP team) by our
+stakeholders.
+
+**The recommendation**: Implement a new runner that identify idle conversations
+and if their time to live (TTL) is longer than defined duration, the
+conversation will be deleted using the same code that is implemented in "delete
+conversation" REST API endpoint.

docs/design/automatic-conversation-expiration/automatic-conversation-expiration.md

@@ -0,0 +1,49 @@
+# Feature design for the Automatic conversation expiration
+
+|               |                                                              |
+|---------------|--------------------------------------------------------------|
+| **Date**      | 2026-06-29                                                   |
+| **Component** | Conversation history database, runners                       |
+| **Authors**   | Pavel Tišnovský                                              |
+| **Feature**   | [LCORE-1475](https://redhat.atlassian.net/browse/LCORE-1475) |
+| **Spike**     | [LCORE-2661](https://redhat.atlassian.net/browse/LCORE-2661) |
+| **Links**     | Spike doc: `docs/automatic-conversation-expiration`          |
+
+<!-- vim-markdown-toc GFM -->
+
+    * [What](#what)
+    * [Why](#why)
+    * [Requirements](#requirements)
+    * [Use Cases](#use-cases)
+    * [Architecture](#architecture)
+        * [Trigger mechanism](#trigger-mechanism)
+        * [Storage / data model changes](#storage--data-model-changes)
+* [References](#references)
+* [Changelog](#changelog)
+
+<!-- vim-markdown-toc -->
+
+## What
+
+## Why
+
+## Requirements
+
+## Use Cases
+
+## Architecture
+
+### Trigger mechanism
+
+### Storage / data model changes
+
+# References
+
+# Changelog
+
+TODO: Record significant changes after initial creation.
+
+| Date       | Change          | Reason          |
+|------------|-----------------|-----------------|
+| 2026-06-29 | Initial version | feature request |
+