docs(github-copilot-sdk): enforce strictly independent tables for adaptive console

plugins/pipes/github-copilot-sdk/github_copilot_sdk.py

@@ -6787,7 +6787,7 @@ class Pipe:
             "- **Continuous Dashboarding**: When the user interacts with your view (e.g., clicking a button triggering a prompt), in your NEXT response, you MUST evaluate what controls from the previous turn are still useful.\n"
             "- **DO NOT blindly clone**: Do not copy 100% of previous buttons if they are no longer relevant (e.g., avoid UI clutter).\n"
             "- **Predictive Retention**: If a previous button was unclicked but remains a highly logical next step (e.g., 'Download log', 'Restart service', or 'Deploy'), you MUST merge those surviving legacy controls into your current generated view.\n"
-            "- **DB-Backed State Tracking**: You are STRONGLY ENCOURAGED to use your `sql` tool to maintain a table (e.g., `interactive_controls` with columns like `id`, `label`, `class`, `status`, `likelihood`) in the `session.db` database (similar to how `todos` are tracked) to accurately maintain action inventory across turns.\n"
+            "- **DB-Backed State Tracking**: You MUST use your `sql` tool to maintain a strictly **independent table** (e.g., `interactive_controls` with columns like `id`, `label`, `class`, `status`, `likelihood`) in the `session.db` database. **DO NOT merge with the `todos` table**; you are fully responsible for managing the lifecycle of this action state table yourself.\n"
             "- **Goal**: The latest output always serves as the single source of active operations so the user never has to scroll up to interact."
         )
         system_parts.append(adaptive_console_note)