📋 Add category taxonomy to root package.json

[taras]

Motivation

The category taxonomy (labels, descriptions, display order) for the extensions page is currently hardcoded in the Effection website. Moving it to the effectionx root package.json makes effectionx the single source of truth for both per-package category assignments (keywords) and the taxonomy definition itself.

Approach

Add an effectionx.categories field to the root package.json containing the 8 category definitions with keyword, label, and description. The Effection website will read this field from the cloned repo at runtime.

Companion to thefrontside/effection#1136, which will consume this taxonomy dynamically.

Summary by CodeRabbit

• Chores
  • Added new category configuration metadata to project settings.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: a873430b-3203-4bac-b067-09bde2175f86

📥 Commits

Reviewing files that changed from the base of the PR and between 440fb7f and 04dcc61.

📒 Files selected for processing (1)

• package.json

---

📝 Walkthrough

Walkthrough

A new effectionx configuration object has been added to package.json at the top level. This object contains a categories array with 8 entries, each specifying a keyword, label, and description for different functional areas (testing, io, process, streams, concurrency, reactivity, interop, platform). No existing configurations, dependencies, or scripts were modified.

Changes

Cohort / File(s)	Summary
Package Configuration package.json	Added top-level effectionx configuration object with a categories array containing 8 category entries, each with keyword, label, and description fields.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

🚥 Pre-merge checks | ✅ 4

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately summarizes the main change: adding a category taxonomy to package.json, though the emoji is stylistic noise.
Description check	✅ Passed	The description includes both required sections (Motivation and Approach) with clear explanations of the problem, solution, and related context.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Policy Compliance	✅ Passed	The pull request complies with all applicable policies including No Agent Marketing (Strict), Package.json Metadata, and Version Bump policies.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch feat/root-taxonomy

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}