[ScriptedAlchemy]

Why

Workspace names containing brackets or braces can exclude their own files from language-client synchronization. A literal asterisk can also select sibling folders. Fixes #4408 by separating the workspace URI from glob syntax.

What changed

• Use a typed protocol relative pattern that the pinned language client converts to VS Code's RelativePattern.
• Add a runnable Cursor extension-host regression through the production selector and client converter.
• Regenerate the embedded extension. This also refreshes brace-expansion to the version already recorded in the lockfile.

Scope

• Preserve file-only selection, trusted single-root admission, and the independent native-diagnostic workspace check.
• Leave diagnostic caps and fix(cursor): apply diagnostic caps after excluding non-deliverable producer lanes #4407 unchanged. Windows drive/UNC behavior and the full daemon notification journey remain unverified.

Blast Radius

Only the Cursor extension's document selection changes. Workspace identity stays literal, while the existing client and host own glob matching.

Verification

• Cursor 3.22.7 on macOS, 28 selector cases. Existing construction failed five; the production helper through the client converter passed all 28. Temporary profiles and fixtures inherited HOME; a no-op development extension prevented bridge startup.
• Bazel Node runs passed TypeScript checking and all eight existing tests.
• Bazel Node ran the existing bundle generator and its byte-for-byte drift check. Both passed.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 61adf7f

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