feat(install): add native JetBrains Junie install target

[Fmarzochi]

Mission

Add JetBrains Junie (the coding agent built into IntelliJ IDEA, PyCharm, WebStorm and the rest of the JetBrains family) as a native install target in scripts/lib/install-targets/, so egc install --target junie writes EGC guidelines into Junie's discovery path instead of requiring manual setup.

Why this is worth doing

Junie reads project guidelines from .junie/guidelines.md inside the repository -- a single well-documented context file, which makes this one of the simplest possible adapters and opens EGC to the entire JetBrains user base. Please verify the current path against the official Junie docs before implementing.

Where to look

• scripts/lib/install-targets/trae-project.js -- minimal single-context-file project adapter, closest template
• scripts/lib/install-targets/cursor-project.js -- richer context-file adapter if more structure is needed
• scripts/lib/install-targets/helpers.js -- createInstallTargetAdapter, createFlatSkillPlanOperations
• scripts/lib/install-targets/registry.js -- register the new adapter in the ADAPTERS array
• tests/lib/install-targets.test.js -- mirror the existing adapter test shape

Acceptance criteria

• junie-project.js adapter with the verified .junie/guidelines.md layout
• Registered in registry.js (ADAPTERS array + imports)
• Tests added mirroring existing install-target coverage
• node tests/run-all.js passes locally
• PR description cites the Junie doc page used to verify the path

Not required

• No hook wiring, no Python changes -- scoped entirely to the JS install-target layer

[Om-Beast]

Hi @Fmarzochi! I'd like to work on this issue if it's available.

I'll implement the native Junie install target following the existing install-target architecture, register it in the adapter registry, add the corresponding tests, and verify the .junie/guidelines.md path using the official JetBrains documentation before submitting the PR.

Looking forward to contributing!

[Fmarzochi]

Hi @Om-Beast, welcome! The issue is yours - just assigned it to you. Your plan is exactly right: adapter + registry + tests, verifying the path against the official Junie docs first.

Three practical notes for a smooth first PR:

1. Work from a fork and open the PR against main.
2. Enable the DCO hook once after cloning: git config core.hooksPath .githooks - it signs off your commits automatically (our CI enforces DCO).
3. The CLA bot will ask you to sign on your first PR - it's one click.

node tests/run-all.js runs the full suite locally. If anything in the codebase is unclear, ask here anytime. Looking forward to your PR!

[Fmarzochi]

Shipped in #849 by @Om-Beast. EGC now installs project guidelines natively for JetBrains Junie (.junie/guidelines.md). Thanks!

[Fmarzochi]

Closing the loop here: huge thanks @Om-Beast for delivering this one. JetBrains Junie became EGC's 20th supported tool because you picked this issue up, pushed through every review round with fast and precise fixes, and got it merged in hours. That is exactly the energy this project grows on.

You are more than welcome to stick around: come join our Discord at https://discord.gg/TxppsGb52 and say hi in the introductions channel. The community is small, active and just getting started, and contributors like you are the reason it exists. My door is always open for your next idea, and there is a fresh batch of good first issues waiting if you feel like another round. See you there!