Version 2.2.4 - Add developer preferences memory file and update documentation

.ai-assistant.md

@@ -16,6 +16,7 @@ Detailed workflow documentation is available in the `.ai-workflows/` directory:
 
 - **@.ai-workflows/bug-fixing.md**: Guidelines for identifying and fixing bugs
 - **@.ai-workflows/code-review.md**: Standards for reviewing code changes
+- **@.ai-workflows/dev-prefs-memory.md**: Persistent memory of developer preferences
 - **@.ai-workflows/feature-development.md**: Process for developing new features
 - **@.ai-workflows/folder-structure.md**: Documentation of the plugin's folder structure and naming conventions
 - **@.ai-workflows/local-env-vars.md**: Local development environment paths and URLs
@@ -75,6 +76,16 @@ Before releasing:
 
 Local environment variables and paths are documented in **@.ai-workflows/local-env-vars.md**.
 
+## Developer Preferences
+
+AI assistants should maintain a record of developer preferences in **@.ai-workflows/dev-prefs-memory.md**. When you learn about a new preference through user feedback or conversation:
+
+1. Check if the preference is already documented
+2. If not, add it to the appropriate section in the dev-prefs-memory.md file
+3. Reference these preferences in future interactions
+
+This ensures consistency across coding sessions and reduces the need for developers to repeatedly explain their preferences.
+
 ## Common Tasks
 
 For detailed instructions on common tasks like creating releases, adding features, fixing bugs, and testing previous versions, see **@.ai-workflows/release-process.md**.

.ai-workflows/dev-prefs-memory.md

@@ -0,0 +1,57 @@
+# Developer Preferences Memory
+
+This document serves as a persistent memory for developer preferences established during coding sessions. AI assistants should refer to this document to understand the developer's preferences and update it as new preferences are established.
+
+## Purpose
+
+- Maintain a consistent record of developer preferences across coding sessions
+- Ensure AI assistants can provide assistance that aligns with the developer's preferred coding style and practices
+- Reduce the need for developers to repeatedly explain their preferences
+
+## How to Use This Document
+
+- **AI Assistants**: Review this document before providing assistance. Update it when new preferences are established through user feedback.
+- **Developers**: Reference this document to see what preferences have been recorded. Feel free to edit it directly to add or modify preferences.
+
+## Recorded Preferences
+
+### File and Directory Structure
+
+- Prefer lowercase filenames for consistency across the codebase
+- Use unique folder names following best practices
+- Folder references should be easily identifiable when using @mentions in AI-assisted coding
+- Admin-specific functionality should be in the `admin/lib/` directory
+- Core plugin functionality should be in the `includes/` directory
+
+### Code Style
+
+- Follow WordPress coding standards
+- Use OOP best practices for WordPress plugins
+- Create modular, maintainable, and efficient code structure
+
+### Documentation
+
+- Prefer token-efficient documentation in `.ai-assistant.md` that references `.ai-workflows/` files
+- Document the release workflow in `.ai-assistant.md` and `.ai-workflows/release-process.md`
+- Store environment variable documentation in `.ai-workflows/local-env-vars.md`
+- Maintain consistent documentation across readme.txt, README.md, and CHANGELOG.md
+
+### Asset Organization
+
+- Store banner, icon, and screenshot images in `.wordpress-org/assets/`
+- Store WORDPRESS_ORG files within `/wordpress-org`
+- Organize files in `/assets` into relevant `/admin` folders
+
+### Version Control
+
+- Use standard Git practices for version control and code management
+- When updating plugin versions, create a GitHub tag and trigger GitHub actions
+- Follow a specific release process with proper tagging and GitHub releases
+- Ensure commits are merged to the main branch as Git Updater pulls data from the readme.txt file in the primary branch
+
+### Plugin Development
+
+- Prefer simpler solutions over complex ones for plugins
+- Use a specific formatting style for the CHANGELOG.md file, using #### for section headings
+- When updating plugin versions, remember to update language files (POT/PO)
+- Comment out redundant code during testing

CHANGELOG.md

@@ -1,5 +1,11 @@
 All notable changes to this project should be documented both here and in the main Readme files.
 
+#### [2.2.4] - 2025-04-14
+#### Added
+- Developer preferences memory file for AI assistants
+- Improved AI assistant documentation with instructions for maintaining developer preferences
+- Updated WordPress.org documentation with correct plugin slug and version numbers
+
 #### [2.2.3] - 2025-04-14
 #### Changed
 - Moved admin-specific files to admin/lib directory for better organization

README.md

@@ -234,6 +234,11 @@ For more information on Git Updater integration, see the [Git Updater Required H
 
 ## Changelog
 
+### 2.2.4
+* Added: Developer preferences memory file for AI assistants
+* Improved: AI assistant documentation with instructions for maintaining developer preferences
+* Updated: WordPress.org documentation with correct plugin slug and version numbers
+
 ### 2.2.3
 * Improved: Moved admin-specific files to admin/lib directory for better organization
 * Improved: Updated namespaces to reflect the new file locations

languages/wp-fix-plugin-does-not-exist-notices.pot

@@ -2,7 +2,7 @@
 # This file is distributed under the GPL-2.0+.
 msgid ""
 msgstr ""
-"Project-Id-Version: Fix 'Plugin file does not exist' Notices 2.2.3\n"
+"Project-Id-Version: Fix 'Plugin file does not exist' Notices 2.2.4\n"
 "Report-Msgid-Bugs-To: https://wordpress.org/support/plugin/wp-fix-plugin-does-not-exist-notices\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"

readme.txt

@@ -5,7 +5,7 @@ Tags: plugins, missing plugins, cleanup, error fix, admin tools, plugin file doe
 Requires at least: 5.0
 Tested up to: 6.7.2
 Requires PHP: 7.0
-Stable tag: 2.2.3
+Stable tag: 2.2.4
 License: GPL-2.0+
 License URI: https://www.gnu.org/licenses/gpl-2.0.html
 
@@ -179,6 +179,11 @@ Manually editing the WordPress database is risky and requires technical knowledg
 
 == Changelog ==
 
+= 2.2.4 =
+* Added: Developer preferences memory file for AI assistants
+* Improved: AI assistant documentation with instructions for maintaining developer preferences
+* Updated: WordPress.org documentation with correct plugin slug and version numbers
+
 = 2.2.3 =
 * Improved: Moved admin-specific files to admin/lib directory for better organization
 * Improved: Updated namespaces to reflect the new file locations

wp-fix-plugin-does-not-exist-notices.php

@@ -3,7 +3,7 @@
  * Plugin Name: Fix 'Plugin file does not exist' Notices
  * Plugin URI: https://www.wpallstars.com
  * Description: Adds missing plugins to your plugins list with a "Remove Notice" action link, allowing you to safely clean up invalid plugin references.
- * Version: 2.2.3
+ * Version: 2.2.4
  * Author: Marcus Quinn & The WPALLSTARS Team
  * Author URI: https://www.wpallstars.com
  * License: GPL-2.0+
@@ -35,4 +35,4 @@ if (!defined('WPINC')) {
 require_once plugin_dir_path(__FILE__) . 'includes/plugin.php';
 
 // Initialize the plugin
-new WPALLSTARS\FixPluginDoesNotExistNotices\Plugin(__FILE__, '2.2.3');
+new WPALLSTARS\FixPluginDoesNotExistNotices\Plugin(__FILE__, '2.2.4');