Change folder and Actions test

[mors119]

Summary

Just change folder name.

Type of Change

• feat
• fix
• docs
• refactor
• test
• chore

Summary by CodeRabbit

• Chores
  • Updated CI workflow configuration to ensure correct build paths and caching for the VSCode extension.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 7fdcc3a9-c5f5-45bf-9c0d-c87c47b79669

📥 Commits

Reviewing files that changed from the base of the PR and between 52d6482 and a3f6cd7.

⛔ Files ignored due to path filters (2)

• Cargo.lock is excluded by !**/*.lock
• apps/vscode-extension/package-lock.json is excluded by !**/package-lock.json

📒 Files selected for processing (16)

• .github/workflows/ci.yml
• apps/vscode-extension/.vscode-test.mjs
• apps/vscode-extension/.vscode/extensions.json
• apps/vscode-extension/.vscode/launch.json
• apps/vscode-extension/.vscode/settings.json
• apps/vscode-extension/.vscode/tasks.json
• apps/vscode-extension/.vscodeignore
• apps/vscode-extension/CHANGELOG.md
• apps/vscode-extension/README.md
• apps/vscode-extension/esbuild.js
• apps/vscode-extension/eslint.config.mjs
• apps/vscode-extension/package.json
• apps/vscode-extension/src/extension.ts
• apps/vscode-extension/src/test/extension.test.ts
• apps/vscode-extension/tsconfig.json
• apps/vscode-extension/vsc-extension-quickstart.md

---

📝 Walkthrough

Walkthrough

This PR corrects the VSCode extension CI job configuration. Two related settings were updated to reference the correct application directory: the working directory default and the npm cache dependency path both now point to apps/vscode-extension instead of the incorrect apps/frilvault reference.

Changes

VSCode CI Job Configuration Update

Layer / File(s)	Summary
VSCode job working directory and cache path correction .github/workflows/ci.yml	The vscode job working-directory default and npm cache dependency path are corrected to reference apps/vscode-extension and its package-lock.json instead of the apps/frilvault paths.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

A rabbit hops through workflows with care,
Fixing the path to the right extension there,
From frilvault's maze to vscode so bright,
Two little tweaks make the pipeline right! 🐰✨

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Title check	❓ Inconclusive	The title 'Change folder and Actions test' is vague and doesn't clearly convey the specific change being made to the CI workflow.	Provide a more specific title such as 'Update CI workflow to run VSCode extension commands from correct folder' or 'Fix CI workflow to use vscode-extension instead of frilvault directory'.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

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

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

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