Cookie Consent: scaffold package [WOOA7S-1533]

[chihsuan]

🚧 Not ready for review — this is an in-progress draft, part of a 3-PR stack. Please don't review yet; I'll mark it ready and ping when it is.

Why

Part of WOOA7S-1533. Migrating the CIAB shoppers-privacy feature out of next-admin/ciab-next into a new standalone, plugin-agnostic Jetpack monorepo package, following the Premium Analytics extraction philosophy (portable, no CIAB deps, consumable by Jetpack / Woo Pro / standalone).

This is PR 1 of 3 — the package scaffold only. No PHP/JS feature code yet, no consumer wires it up, so nothing is live until a later PR + a consumer call Cookie_Consent::init().

Stack

1. PR1 — scaffold ← this PR (targets trunk)
2. PR2 — frontend Interactivity module (targets PR1)
3. PR3 — PHP backend + module enqueue (targets PR2)

What this PR does

Adds projects/packages/cookie-consent/:

File	What to review
composer.json	jetpack-library, private, runtime require is php >=7.2 only (no jetpack-package deps, for portability); standard extra (autotagger, mirror-repo, textdomain, version-constants, changelogger, branch-alias)
package.json	webpack-module build scripts; dep @wordpress/interactivity; build/lint devDeps only
tools/webpack.config.modules.js	single explicit entry → build/modules/cookie-consent/index.js, ESM script-module output
tsconfig.json / declarations.d.ts / eslint.config.mjs / .phpcs.dir.xml	standard package config; text domain jetpack-cookie-consent
.gitattributes / .gitignore	ship built JS + PHP in mirror, exclude TS source/tooling
README.md / CHANGELOG.md / changelog/	package docs + initial changelog entry

A placeholder src/modules/cookie-consent/index.ts lets the build pass; it's replaced in PR2.

Verification

pnpm --filter @automattic/jetpack-cookie-consent build, eslint --max-warnings=0 src, and tsgo --noEmit all pass.

[github-actions]

Are you an Automattician? Please test your changes on all WordPress.com environments to help mitigate accidental explosions.

• To test on WoA, go to the Plugins menu on a WoA dev site. Click on the "Upload" button and follow the upgrade flow to be able to upload, install, and activate the Jetpack Beta plugin. Once the plugin is active, go to Jetpack > Jetpack Beta, select your plugin (Jetpack or WordPress.com Site Helper), and enable the add/cookie-consent-package branch.
• To test on Simple, run the following command on your sandbox:

bin/jetpack-downloader test jetpack add/cookie-consent-package

bin/jetpack-downloader test jetpack-mu-wpcom-plugin add/cookie-consent-package

Interested in more tips and information?

• In your local development environment, use the jetpack rsync command to sync your changes to a WoA dev blog.
• Read more about our development workflow here: PCYsg-eg0-p2
• Figure out when your changes will be shipped to customers here: PCYsg-eg5-p2

[github-actions]

Thank you for your PR!

When contributing to Jetpack, we have a few suggestions that can help us test and review your patch:

• ✅ Include a description of your PR changes.
  
• ✅ Add a "[Status]" label (In Progress, Needs Review, ...).
  
• 🔴 Add testing instructions.
  
• 🔴 Specify whether this PR includes any changes to data or privacy.
  
• ✅ Add changelog entries to affected projects
  

This comment will be updated as you work on your PR and make changes. If you think that some of those checks are not needed for your PR, please explain why you think so. Thanks for cooperation 🤖

---

🔴 Action required: Please include detailed testing steps, explaining how to test your change, like so:

## Testing instructions:

* Go to '..'
*

---

🔴 Action required: We would recommend that you add a section to the PR description to specify whether this PR includes any changes to data or privacy, like so:

## Does this pull request change what data or activity we track or use?

My PR adds *x* and *y*.

---

Follow this PR Review Process:

1. Ensure all required checks appearing at the bottom of this PR are passing.
2. Make sure to test your changes on all platforms that it applies to. You're responsible for the quality of the code you ship.
3. You can use GitHub's Reviewers functionality to request a review.
4. When it's reviewed and merged, you will be pinged in Slack to deploy the changes to WordPress.com simple once the build is done.

If you have questions about anything, reach out in #jetpack-developers for guidance!

[jp-launch-control]

Code Coverage Summary

This PR did not change code coverage!

That could be good or bad, depending on the situation. Everything covered before, and still is? Great! Nothing was covered before? Not so great. 🤷

Full summary · PHP report · JS report