Add Java category to the plugins page filter

[jdubois]

Pull Request Checklist

• I have read and followed the CONTRIBUTING.md guidelines.
• I have read and followed the Guidance for submissions involving paid services.
• My contribution adds a new instruction, prompt, agent, skill, workflow, or canvas extension file in the correct directory.
• The file follows the required naming convention.
• The content is clearly structured and follows the example format.
• I have tested my instructions, prompt, agent, skill, workflow, or canvas extension with GitHub Copilot.
• I have run npm start and verified that README.md is up to date (ran npm run build).
• I am targeting the main branch for this pull request.

---

Description

The plugins page category sidebar only shows the 12 most-used tags, so java (3 plugins) never appeared. This pins java in the category list (plugins.astro and PluginsCatalog.tsx) and adds the java keyword to java-modernization-studio, so all Java plugins (java-development, java-mcp-development, openapi-to-application-java-spring-boot, java-modernization-studio) match.

---

Type of Contribution

• New instruction file.
• New prompt file.
• New agent file.
• New plugin.
• New skill file.
• New agentic workflow.
• New canvas extension.
• Update to existing instruction, prompt, agent, plugin, skill, workflow, or canvas extension.
• Other (please specify): website plugins filter

---

Additional Notes

Validation: npm ci OK; npm run build OK; npm run plugin:validate passed (104 plugins); website npm run build (astro) OK, and dist/plugins/index.html contains the java category option.

---

By submitting this pull request, I confirm that my contribution abides by the Code of Conduct and will be licensed under the MIT License.

[github-actions]

🚦 Submission status: 👀 Ready for review

Risk tier: merge-risk:medium — New or substantially changed resource without privileged execution
Required to merge: passing submission-gate checks plus 1 approval from reviewers with write access.

Why this tier

• Changes files outside the low-risk documentation and resource paths

Automated checks

Check	Status	Details
Line endings	✅ Passed	Passed · logs
Spelling	✅ Passed	Passed · logs
Generated README consistency	✅ Passed	Passed · logs
Plugin and extension validation	✅ Passed	Passed · logs
Plugin structure	✅ Passed	Passed · logs
Risk scan	✅ Passed	Passed · logs
Contributor reputation	✅ Passed	Passed · logs
Duplicate resource scan	✅ Passed	Passed · logs
PR quality signal	⏭️ Skipped	Skipped by its workflow · logs
Canvas/plugin smoke test	✅ Passed	Passed · logs

Review

• Approvals: 0/1
• Assigned reviewer: not assigned yet — comment /request-review to ask for one
• Review target date: not set
• Still needed: 1 more approval(s)
• No staffed reviewer pool owns these files yet; any reviewer with write access counts as the domain reviewer.

Commands

Command	Who	What it does
/rerun-checks	PR author, maintainers	Re-runs failed or incomplete checks and re-evaluates this gate
/request-review	PR author, maintainers	Asks the review rotation to assign a reviewer (adds needs-reviewer)

_{Updated for 15360df · gate run · This comment is maintained automatically — see submission gate docs.}

[github-actions]

🔒 PR Risk Scan Results

Scanned 3 changed file(s).

Severity	Count
🔴 High	0
🟠 Medium	0
ℹ️ Info	0

✅ No matching risk patterns were detected in changed files.

This is an automated soft-gate report. Findings indicate review targets and do not block merge by themselves.

[github-actions]

🧩 Canvas smoke test

✅ Passed · 0 error(s), 1 warning(s)

Check	Result
Syntax, imports, file safety	✅
Preview image (≥ 400×160 PNG)	✅
Plugin manifests	✅
Materialize	✅
Install (Copilot CLI)	✅

Plugin java-modernization-studio v1.0.2

Field	Value
Description	Drive the GitHub Copilot App Modernization for Java workflow from an interactive canvas: environment readiness, repo assessment, prioritized plan and progress, validation gates, and one-click predefined-task runs grounded in the repo's real artifacts.
Author	Ayan Gupta — https://github.com/ayangupt
License	—
Keywords	app-modernization, assessment-dashboard, azure-migration, java, java-modernization, legacy-java, modernization-cockpit, validation-gates
Extensions	java-modernization-studio
Materialize	✅
Install	✅

Changed plugin files

• plugins/java-modernization-studio/plugin.json

Extension java-modernization-studio

Field	Value
Registered by	java-modernization-studio
Package	java-modernization-studio 1.0.0
Preview	2480×1896, 275.6 KB
Modules	9 (8 reachable from extension.mjs)
Files	13

Permissions and capabilities (static analysis of modules reachable from extension.mjs)

• Spawns processes (node:child_process)
• File system access (node:fs)
• Network sockets / local server (node:http, node:net, ...)
• Host information (node:os)
• Outbound HTTP requests (fetch)
• Reads environment variables (process.env)

Warnings

• test/cockpit.test.mjs: import "node:test" is not a Node.js builtin, host-provided package, or declared dependency (module is not reachable from extension.mjs)

---

Static checks compile modules without executing them. Minimum preview size is configurable with CANVAS_PREVIEW_MIN_WIDTH/CANVAS_PREVIEW_MIN_HEIGHT. Workflow run

[Copilot]

🟢 Approval recommended

The focused filter and metadata changes fit the existing catalog design, with no blocking issues remaining.

0 open findings

What changed in this PR

Makes Java plugins easier to discover through the plugins page category filter.

Changes:

• Pins Java in the category options.
• Adds the Java keyword to Java Modernization Studio and updates its documentation entry.

File	Description
website/​src/​pages/​plugins.astro	Includes Java in category candidates.
website/​src/​components/​brand/​PluginsCatalog.tsx	Pins Java within the category limit.
plugins/​java-modernization-studio/​plugin.json	Adds the Java keyword.
docs/​README.plugins.md	Reflects the updated keyword.

🧠 Review effort: Max

---

💡 Configure MCP servers for context-aware, tailored reviews. Learn more in the docs.