Merge develop into main (v0.0.3 runtime + panel + AI client updates)

.eslintignore

@@ -0,0 +1,3 @@
+ideas/**
+build/**
+vendor/**

.eslintrc.js

@@ -0,0 +1,30 @@
+const defaultConfig = require( '@wordpress/scripts/config/.eslintrc.js' );
+
+const coreModules = new Set( [
+	...( defaultConfig.settings?.[ 'import/core-modules' ] || [] ),
+	'@wordpress/components',
+	'@wordpress/core-data',
+	'@wordpress/data',
+	'@wordpress/dataviews',
+	'@wordpress/dom-ready',
+	'@wordpress/element',
+	'@wordpress/i18n',
+	'@wordpress/icons',
+] );
+
+module.exports = {
+	...defaultConfig,
+	settings: {
+		...( defaultConfig.settings || {} ),
+		'import/core-modules': [ ...coreModules ],
+	},
+	rules: {
+		...( defaultConfig.rules || {} ),
+		'import/no-unresolved': [
+			'error',
+			{
+				ignore: [ '^@wordpress/' ],
+			},
+		],
+	},
+};

.github/workflows/ci.yml

@@ -3,6 +3,8 @@ name: CI
 on:
   pull_request:
     branches: [develop, main]
+  push:
+    branches: [main]
 
 jobs:
   php:
@@ -21,8 +23,8 @@ jobs:
       - name: Run PHP CodeSniffer
         run: composer lint
 
-  lint-changed-js:
-    name: JS Lint (changed files)
+  lint-js:
+    name: JS Lint (full, conditional)
     runs-on: ubuntu-latest
     steps:
       - uses: actions/checkout@v4
@@ -45,11 +47,31 @@ jobs:
       - name: Install dependencies
         if: steps.changed-js.outputs.js == 'true'
         run: npm ci
-      - name: Lint changed JS files only
+      - name: Run full JS lint
         if: steps.changed-js.outputs.js == 'true'
-        env:
-          BASE_REF: origin/${{ github.base_ref }}
-        run: npm run lint:changed:js
+        run: npm run lint:js
       - name: Skip JS lint (no JS changes)
         if: steps.changed-js.outputs.js != 'true'
         run: echo "No JS changes; skipping JS lint."
+
+  plugin-check:
+    name: WordPress Plugin Check
+    runs-on: ubuntu-latest
+    if: github.ref == 'refs/heads/main' || github.base_ref == 'main'
+    timeout-minutes: 20
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-node@v4
+        with:
+          node-version: '20'
+          cache: npm
+      - name: Install dependencies
+        run: npm ci
+      - uses: shivammathur/setup-php@v2
+        with:
+          php-version: '8.1'
+          tools: composer:v2
+      - name: Install Composer dependencies
+        run: composer install --no-interaction --prefer-dist --no-progress
+      - name: Run dist plugin standards check
+        run: npm run plugin:check

.wp-env.json

@@ -0,0 +1,5 @@
+{
+  "plugins": [
+    "."
+  ]
+}

AGENTS.md

@@ -29,6 +29,19 @@ The plugin includes:
 - **Hooks**: `src/js/admin/hooks/` - Custom hooks (data fetching, state)
 - **Config**: `src/js/admin/config/` - Field definitions, actions, settings
 
+### JavaScript Formatting Rules
+
+Apply these rules consistently to avoid large lint/fix churn:
+
+- Use tabs for indentation in JS/JSX files.
+- Use single quotes for JS strings/imports (unless escaping/template use makes that inappropriate).
+- Let Prettier collapse JSX/expressions to single-line when short; do not force manual multi-line wrapping.
+- Do not manually align tokens/spaces for visual columns; keep standard Prettier spacing.
+- Keep object/array/function formatting Prettier-first; avoid hand-formatted stylistic layouts.
+- Avoid nested ternaries; expand to clear `if`/`else` when logic branches.
+- Keep `ideas/` out of JS lint scope (ignored via `.eslintignore` and changed-file lint script).
+- Before committing JS changes, run `npm run lint:js -- --fix` (or scoped equivalent) and then `npm run lint:js`.
+
 ### REST API Pattern
 
 Located in `includes/class-rest-api.php`:
@@ -172,18 +185,21 @@ All user-facing strings must be translatable.
 
 When writing or refactoring PHPUnit tests:
 
-- Keep production code aligned with real WordPress runtime expectations.
-- Do not add test-only `function_exists()` guards for core WordPress APIs just to satisfy PHPUnit.
-- If a test environment is missing a WordPress function, add a deterministic stub in `tests/Support/WordPressStubs.php`.
+- Never add test-only logic, boot contracts, or test-oriented exceptions/messages to plugin runtime code in `includes/` or `clawpress.php`.
+- Do not introduce production `assert_*` helpers, runtime throws, or `function_exists()` guards solely to make tests pass.
+- If PHPUnit needs a missing WordPress API, add a deterministic stub in `tests/Support/WordPressStubs.php` instead of changing plugin behavior.
 - When a stub needs state, store it in `WordPress_Stubs` and reset it in `WordPress_Stubs::reset()` so tests remain isolated.
 - Keep stubs minimal and behavior-focused: enough for assertions without recreating WordPress internals.
-- If behavior is truly optional in production (version-gated or feature-detected APIs), keep runtime guards and prefer covering both paths in tests.
+- Tests must validate real plugin behavior and observable outcomes, not internal test scaffolding.
+- Prefer exercising registered hooks with `do_action()`/`apply_filters()` and asserting side effects (registered menus/routes, enqueued assets, persisted meta/options, scheduler calls).
+- Avoid low-value tests that only assert stub presence (for example `function_exists()` contract lists) or only test helper assertions without behavior coverage.
+- If behavior is truly optional in production (version-gated or feature-detected APIs), keep runtime guards and cover both paths in tests.
 
 ### Verification Expectations
 
 - Run targeted PHPUnit tests for the changed module first.
 - Run the full PHPUnit suite when shared test support files (like `WordPressStubs.php`) are changed.
-- Prefer assertions that verify integration calls happened (for example submenu registration/removal and metadata checks).
+- Prefer assertions that verify integration calls and state transitions happened (for example submenu registration/removal and metadata checks).
 
 ## Important Notes
 

CONTRIBUTING.md

@@ -60,8 +60,11 @@ npm run lint:css
 npm run lint:php
 npm run lint:php:fix
 npm run lint:changed
+npm run plugin:check
 ```
 
+`npm run plugin:check` builds a distribution zip, starts a disposable local WordPress environment via `wp-env`, installs the official Plugin Check plugin, installs the dist zip under a temporary slug, and runs `wp plugin check` against that packaged artifact.
+
 ## Tests
 
 Run PHP unit tests:

README.md

@@ -1,8 +1,20 @@
-# ClawPress
+=== ClawPress ===
+Contributors: bradvin
+Tags: ai, assistant, admin
+Requires at least: 6.9
+Tested up to: 6.9
+Requires PHP: 8.1
+Stable tag: 0.0.2
+License: GPLv2 or later
+License URI: https://www.gnu.org/licenses/gpl-2.0.html
+
+AI assistant for WordPress admins.
+
+== Description ==
 
 ![ClawPress Logo](img/clawpress-logo-500x500.png)
 
-The AI for WordPress that actually does things
+ClawPress is the AI for WordPress that actually does things.
 
 [Preview in WordPress Playground](https://playground.wordpress.net/?blueprint-url=https://raw.githubusercontent.com/bradvin/clawpress/refs/heads/main/blueprint.json)
 
@@ -19,6 +31,7 @@ npm run build
 make test
 make lint
 make lint-changed
+npm run plugin:check
 ```
 
 ## Key Features
@@ -32,6 +45,7 @@ Current MVP features implemented in this plugin:
 - Offline mode which still allows slash commands to be used.
 - Setup Wizard built into chat to guide users through plugin setup process.
 - Admin settings page to set which provider, model, and other settings to use.
+- Admin abilities settings page to enable which abilities can be used by the agent.
 - Registers WP Abilities to and loads them as tools into the AI client.
 - Creates an action log database table to track actions taken by the AI assistant.
 - Context & system prompt built up using chat history, tools (abilities), agent files & memory.
@@ -102,6 +116,7 @@ Custom endpoints with permission callbacks and parameter validation.
 
 ### Development (npm)
 - `@wordpress/scripts` - Build tooling
+- `@wordpress/env` - Local disposable WordPress environment for plugin checks
 
 ### Development (Composer)
 - `wp-coding-standards/wpcs` - WordPress Coding Standards for PHP_CodeSniffer
@@ -128,25 +143,29 @@ Custom endpoints with permission callbacks and parameter validation.
 
 ## TODO
 
-- Fix context usage info / limit / tooltip.
-- Add current admin screen to context.
-- Persist tool calls to chat history
-- Define actual scope of agent user. (should the user only be used for heartbeat tasks?)
-- Agent skills!
+### Approved
+
+- Add more agent abilities for reading general WordPress content (posts, pages, etc.)
+- Add abilities to read memory files (long and short term).
+- Add abilities for bulk file_reads and bulk memory_reads.
+- Add ability to send emails to administrator using built-in WP mail functions.
 - Chat threads - have multiple conversation threads at once, per user.
-- Improve agent loop for multi-step messages
-- Add heartbeat wizard for setting up useful nightly site health email report.
-- Implement working heartbeat tasks.
-- Use WP_Filesystem to read/write files
-- Add abilities to read memory files (long and short term)
+- Implement a working heartbeat task. Start small and test how it works. Create a built in nightly healthcheck that checks site health and emails admin. Add wizard for setting up useful nightly site health email report.
+- Agent skills! Create abilities to read, create, update, execute a skill. Consider limitations and security.
+
+### Backlog
+
+- Add current site context, when doing direct chat messages. Consider an ability to pull this info, including all active plugins.
+- Improve context usage info / limit / tooltip. (right now its not useful and not accurate. Also need to decide on a suitable max context size - maybe 200K)
+- Define actual scope of agent user. (should the user only be used for heartbeat tasks?)
 - Fix boostrap agent file setup and writing (doesnt always run)
-- /reset command should clear everything (like uninstall + activation)
-- Add more agent abilities for general WordPress content (posts, pages, etc.)
+- /reset command should clear everything (like uninstall + activation). All history will be wiped and Welcome card should show. Even after page refreshes.
 - Consider how browser search and use will work within WordPress.
 - Mulit agent support. (can configure multiple agents)
 - Multi-user support. (each user has their own agents)
 - Channels for agent interaction.
 - Streaming responses.
+- Add ability to read DB, or generate a query to read from the DB. Might need an ability to get DB schema, which can then be used to generate a query. Need to consider destructive queries, or make all queries require confirmation just to be safe.
 
 ## Decision Log
 

bin/lint-changed

@@ -12,6 +12,10 @@ fi
 declare -a JS_FILES=()
 
 while IFS= read -r -d '' file; do
+  if [[ "$file" == ideas/* || "$file" == build/* || "$file" == vendor/* ]]; then
+    continue
+  fi
+
   case "$file" in
     *.js|*.jsx|*.mjs|*.cjs)
       JS_FILES+=("$file")

bin/plugin-check

@@ -0,0 +1,29 @@
+#!/usr/bin/env bash
+set -euo pipefail
+
+SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
+REPO_ROOT="$(cd "$SCRIPT_DIR/.." && pwd)"
+
+cd "$REPO_ROOT"
+
+DIST_SLUG="clawpress-dist-check"
+EXPECTED_SLUG="clawpress"
+DIST_ZIP_PATH="/var/www/html/wp-content/plugins/clawpress/dist/clawpress.zip"
+PLUGIN_CHECK_VERSION="${PLUGIN_CHECK_VERSION:-1.8.0}"
+PLUGIN_CHECK_ENGINE_ZIP_URL="https://downloads.wordpress.org/plugin/plugin-check.${PLUGIN_CHECK_VERSION}.zip"
+PLUGIN_CHECK_BOOTSTRAP_PATH="/var/www/html/wp-content/plugins/clawpress/bin/plugin-check-bootstrap.php"
+
+echo "Building plugin zip for dist plugin check..."
+npm run plugin-zip
+
+echo "Starting wp-env for dist plugin check..."
+npx wp-env start
+
+echo "Installing dist zip into temporary plugin slug..."
+npx wp-env run tests-cli -- bash -lc "set -euo pipefail; rm -rf /tmp/plugin-check-dist /var/www/html/wp-content/plugins/${DIST_SLUG}; mkdir -p /tmp/plugin-check-dist; unzip -q ${DIST_ZIP_PATH} -d /tmp/plugin-check-dist; DIST_SOURCE=\$(find /tmp/plugin-check-dist -mindepth 1 -maxdepth 1 -type d | head -n 1); if [[ -z \"\${DIST_SOURCE}\" ]]; then echo 'Unable to locate extracted plugin directory from dist zip.' >&2; exit 1; fi; cp -R \"\${DIST_SOURCE}\" /var/www/html/wp-content/plugins/${DIST_SLUG};"
+
+echo "Ensuring site plugin-check plugin is not installed..."
+npx wp-env run tests-cli -- bash -lc "set -euo pipefail; if wp plugin is-installed plugin-check >/dev/null 2>&1; then wp plugin deactivate plugin-check --quiet || true; wp plugin delete plugin-check --quiet; fi"
+
+echo "Running standalone Plugin Check engine against dist plugin contents..."
+npx wp-env run tests-cli -- bash -lc "set -euo pipefail; ENGINE_ROOT=/tmp/plugin-check-engine; ENGINE_ZIP=/tmp/plugin-check-engine.zip; rm -rf \"\${ENGINE_ROOT}\" \"\${ENGINE_ZIP}\"; mkdir -p \"\${ENGINE_ROOT}\"; if command -v curl >/dev/null 2>&1; then curl -fsSL \"${PLUGIN_CHECK_ENGINE_ZIP_URL}\" -o \"\${ENGINE_ZIP}\"; else wget -q \"${PLUGIN_CHECK_ENGINE_ZIP_URL}\" -O \"\${ENGINE_ZIP}\"; fi; unzip -q \"\${ENGINE_ZIP}\" -d \"\${ENGINE_ROOT}\"; ENGINE_DIR=\"\${ENGINE_ROOT}/plugin-check\"; if [[ ! -f \"\${ENGINE_DIR}/vendor/autoload.php\" ]]; then echo 'Standalone plugin-check engine autoload.php missing after extraction.' >&2; exit 1; fi; if [[ ! -f \"${PLUGIN_CHECK_BOOTSTRAP_PATH}\" ]]; then echo 'Standalone plugin-check bootstrap file is missing in plugin repo.' >&2; exit 1; fi; WP_PLUGIN_CHECK_ENGINE_DIR=\"\${ENGINE_DIR}\" wp --path=/var/www/html --require=\"${PLUGIN_CHECK_BOOTSTRAP_PATH}\" plugin check \"${DIST_SLUG}\" --slug=\"${EXPECTED_SLUG}\" --ignore-codes=trademarked_term"