Upgrade build tooling and add PHPCS integration

[lihsaa591]

Summary

Fixes the broken build toolchain and adds WordPress Coding Standards (PHPCS) tooling for the Accelerate theme.

Changes

Area	Change	Why
package.json	grunt 0.4.5 → ^1.6.3	Years-out-of-date pin; kept in step with the pro theme and current npm/Node
package.json	grunt-contrib-compress ~1.2.0 → ^2.0.0, grunt-contrib-jshint ~1.0.0 → ^3.2.0	Kept in step with the grunt 1.x upgrade; each verified by running its task before/after
package.json	grunt-wp-i18n ~0.5.4 → ^1.0.4	Old version's bundled makepot.php calls the removed PHP 8 function create_function(), fatal-erroring grunt makepot
package.json	engines.node/engines.npm >=0.8.0/>=1.1.0 → >=18.0.0/>=9.0.0	2014-era values, no longer meaningful
Gruntfile.js	compress task now excludes package-lock.json, vendor/, composer.json, composer.lock, phpcs.xml.dist	These were being (or would be) archived straight into the release zip
Gruntfile.js	makepot task now sets potComments explicitly	grunt-wp-i18n@1.0.4's default comment template leaks a literal <!=...=!> placeholder into the .pot header when not overridden — an upstream bug
.npmrc (new)	omit=optional	Without it, npm install silently skips all devDependencies (where the whole Grunt toolchain lives) whenever the shell has NODE_ENV=production set — grunt never gets installed
.gitignore	Added /vendor/	Composer's dev dependencies shouldn't be tracked
composer.json, phpcs.xml.dist (new)	WordPress + PHPCompatibility ruleset, testVersion 7.4-, composer phpcs / composer phpcbf scripts	No coding-standards tooling existed in the repo
.github/workflows/phpcs.yml (new)	Runs PHPCS on PR, scoped to changed PHP files only	~1767 pre-existing errors/286 warnings across untouched legacy files — full-repo linting would block on unrelated debt. Cleanup is a separate follow-up
languages/accelerate.pot	Regenerated via npm run build on the fixed toolchain	Output of the now-working build, not a manual edit

QA / Test steps

Toolchain (no WordPress needed):

1. git clone this branch fresh, cd into it.
2. Run npm install with no flags.
   • Expected: completes with no error, and node_modules/.bin/grunt exists.
3. Run npm run build.
   • Expected: makepot and compress both run and finish with Done., exit code 0. No create_function() PHP fatal error.
4. Open languages/accelerate.pot and check the first 2 lines.
   • Expected: # Copyright (C) <year> ThemeGrill / # This file is distributed under the GNU General Public License, version 3 (GPLv3). — plain text, no <!= or =!> characters.
5. Run unzip -l dist/accelerate.zip | tail -5.
   • Expected: file count matches the theme's actual file set (120 at time of writing) — no vendor/, composer.json, composer.lock, or phpcs.xml.dist entries.
6. Run composer install && composer phpcs.
   • Expected: PHPCS runs against the new phpcs.xml.dist ruleset (will report the pre-existing backlog — that's expected and out of scope for this PR).

Theme behavior in WordPress (manual — do this before merging):

1. Take dist/accelerate.zip from step 3 above (or activate the theme directory directly) and activate Accelerate on a WordPress install.
2. Visit the homepage, a blog archive, and a single post — confirm layout, fonts, and icons render as before. No theme PHP, template, or JS source was touched by this PR.
3. If translations are in use, confirm Loco Translate (or similar) can still read languages/accelerate.pot without errors.

Changelog entry

Fix - Updated build tooling; npm install and grunt makepot no longer fail on modern Node/PHP.

🤖 Generated with Claude Code

[Copilot]

Copilot review overview

🟡 Changes recommended

Resolve the Node 18 dependency incompatibility, ensure npm installs devDependencies in production mode, and handle deleted PHP paths in CI.

Get a fresh assessment by requesting another Copilot review.

Review effort: Lite
Findings: 1 · 1

Open (2)

• Align Node engine requirement with locked glob dependency · New
• Ensure devDependencies install in production-mode npm builds · New

What changed in this PR

Upgrades build tooling and adds Composer/PHPCS validation and CI for the theme.

Changes:

• Updates Grunt dependencies, packaging, and POT generation.
• Adds Composer-based WordPress coding standards tooling.
• Adds changed-PHP-file PHPCS checks in GitHub Actions.
• Refreshes npm/Composer lockfiles and generated translations.

File	Summary
phpcs.xml.dist	Defines coding standards configuration.
package.json	Updates build dependencies and Node requirements.
package-lock.json	Locks upgraded npm dependencies.
languages/​accelerate.pot	Regenerated translation catalog.
Gruntfile.js	Fixes POT metadata and archive exclusions.
composer.lock	Locks Composer tooling dependencies.
composer.json	Adds PHPCS tooling and scripts.
.npmrc	Configures npm installation behavior.
.gitignore	Ignores Composer vendor files.
.github/​workflows/​phpcs.yml	Adds changed-file PHPCS CI.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[lihsaa591]

@tg-autopilot review

[Copilot]

Copilot review overview

🔵 Needs a closer look

Resolve the lockfile engine mismatch and make CI path handling safe.

Review effort: Lite
Findings: None

Resolved since last review (2)

• Align Node engine requirement with locked glob dependency
• Ensure devDependencies install in production-mode npm builds