🛡️ Sentinel: [CRITICAL] Fix path traversal in exportGherkin

[seonghobae]

🚨 Severity: CRITICAL
💡 Vulnerability: The exportGherkin command allowed path traversal via the output parameter by naively constructing paths using join, making it possible to write files outside of the project root.
🎯 Impact: This allows arbitrary file overwrite outside the project structure, which could lead to critical system files or configurations being tampered with.
🔧 Fix: Updated exportGherkin to construct an absolute path using path.resolve and correctly verify boundary conditions using path.relative. The code now throws a VspecError with INVALID_ARGUMENT if the relative path escapes the project root or is absolute.
✅ Verification: Covered with a path traversal test within a vitest unit test under tests/gherkin.test.ts, confirming VspecError gets thrown as expected. Run pnpm test and pnpm typecheck to verify overall correctness.

---

PR created automatically by Jules for task 8759389234773059014 started by @seonghobae

[google-labs-jules]

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.

---

For security, I will only act on instructions from the user who triggered this task.

[coderabbitai]

Warning

Review limit reached

@seonghobae, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 47 minutes and 56 seconds. Learn how PR review limits work.

Your organization has run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 8eaa82aa-b4a4-42c5-a13f-9bc6bad0cd41

📥 Commits

Reviewing files that changed from the base of the PR and between f4278ec and 175d378.

📒 Files selected for processing (3)

• .jules/sentinel.md
• src/export/gherkin.ts
• tests/gherkin.test.ts

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch sentinel-path-traversal-gherkin-8759389234773059014

✨ Simplify code

• Create PR with simplified code
• Commit simplified code in branch sentinel-path-traversal-gherkin-8759389234773059014

Warning

Billing warning: we have not been able to collect payment for this subscription for more than 72 hours. Please update the payment method or pay any pending invoices in Billing to avoid service interruption.

---

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