[WIP] Fix route handling for .well-known directory in qwik router

[Copilot]

Plan: Handle .well-known paths by returning 404

• Understand current Qwik City routing implementation
• Add logic to getRouteMatchPathname() to detect and block .well-known paths
• Add unit tests for .well-known path handling
• Run tests to verify the implementation
• Request code review
• Run security checks

Original prompt

---

This section details on the original issue you should resolve

<issue_title>[🐞] v2: handle .well-known/appspecific/com.chrome.devtools.json</issue_title>
<issue_description>### Which component is affected?

Qwik City (routing)

Describe the bug

Handle .well-known/appspecific/com.chrome.devtools.json in qwik router. It can match routes and execute handlers from there.

Reproduction

Steps to reproduce

System Info

-

Additional Information

No response</issue_description>

<agent_instructions>Make sure path handling ignores everything in .well-known and returns 404</agent_instructions>

Comments on the Issue (you are @copilot in this section)

• Fixes [🐞] v2: handle .well-known/appspecific/com.chrome.devtools.json #8130

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 44a947b

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR