Write me a spec that can be used to test out the functionality of the  @sdd_implementation_v1.md  or any general SDD implementation. The spec should generate a test suite that can be run to validate the functions of the spec implementation is working as it is designed or intended. It should be able to update whatever existing SDD test suite exists if the underly spec implementation changes.

MIT License Copyright (c) 2026 David Carver and NineWorlds

Formalize "Tribal Knowledge" into "Golden Standards" through a heuristic-based discovery process. This plan identifies architectural "Gravity Wells," documents anti-patterns, and maps cross-module protocols to ensure consistency and formalize project intelligence in a language/framework-agnostic manner.

• Current State: The project has implementation-defined standards that may be implicitly understood but lack formal documentation in AI system prompts.
• Constraints: This plan is language and framework agnostic. The executing agent must determine the specific tech stack through probing and adapt its discovery methodology accordingly.
• SDD Memory: All findings, surprising dependencies, and architectural debt must be logged in prompts/plans/context_discovery/memory/.

• No Directory Creation Tool: Use your Write tool to create a placeholder .gitkeep file in the target path.
• No Delete/Move Tools:
  1. Write the new file to the destination.
  2. Add the old file path to the "Cleanup & Manual Actions" section of the task spec for human action.

• No Direct Shell: Do not assume shell access (bash/zsh).

Status: PROPOSED
Version: 2.1.0
Target: Standardized AI Workflow (Universal LLM/Agent Compatibility)

• Scope: This protocol applies to all AI-assisted development (features, refactors, migrations).
• Summary: To eliminate "Vibe Coding" and ensure consistency, this plan implements a Spec-First Protocol. Agents must generate a Phased GSD (Goal, Steps, Deliverables) document before writing any production code for complex tasks.
• Context & Memory: v2.0 introduces persistent context management. Each plan resides in its own directory, with a dedicated memory/ sub-folder to record findings, unexpected dependencies, and state changes across execution phases.

On a a linux system, the app.prompts.xml file that contains the saved prompts, is stored in `~/.config/Goggle/AndroidStudioVersion/options/app.prompt.xml'

For MacOSX: Configuration/Settings: ~/Library/Application Support/Google/AndroidStudio

• Plugins: ~/Library/Application Support/Google/AndroidStudio/plugins
• System/Cache Files: ~/Library/Caches/Google/AndroidStudio
• Logs: ~/Library/Logs/Google/AndroidStudio

For Windows: On Windows, the settings are stored within the user's AppData folder:

This guide is only for original Ubuntu out-of-the-box packages. If you have added a custom PPA like pipewire-debian, you might get into conflicts.

Ubuntu 22.04 has PipeWire partially installed and enabled as it's used by browsers (WebRTC) for recoding the screeen under Wayland. We can enable remaining parts and use PipeWire for audio and Bluetooth instead of PulseAudio.

Starting from WirePlumber version 0.4.8 automatic Bluetooth profile switching (e.g. switching from A2DP to HSP/HFP when an application needs microphone access) is supported. Jammy (22.04) repos provide exactly version 0.4.8. So, we're good.

Based on Debian Wiki, but simplified for Ubuntu 22.04.