fix(rules): close the split-literal gap in no-unrouted-cli-invocation

The regex required a launcher in front of the package name, so a split
literal (`"npx " + "@taskless/cli"`) put the two halves in separate
string_fragment nodes and the rule never saw a match. It now matches the
package name alone, which costs nothing: every string in packages/cli/src/
naming the package is an invocation, and both existing occurrences already
sit inside applyCliInvocation(). Added a split-literal test case, which
fails against the launcher-anchored regex.

Both remaining limitations are documented in the rule's note rather than
left implicit, since this rule is the only enforcement for some sites it
covers: a split placed mid-name still evades any single-fragment rule, and
an aliased import is not recognised as routed, which is a false positive
and therefore the safe direction to fail in.

Reported by review on #209.

Author: theCodeDrift

.taskless/rules/sg/no-unrouted-cli-invocation/.tests/no-unrouted-cli-invocation-20260828-test.yml

@@ -15,6 +15,8 @@ invalid:
     console.log(
       "For humans: run `npx @taskless/cli` (no args) to install or update Taskless,"
     );
+  - |
+    const hint = "npx " + "@taskless/cli" + " init";
   - |
     const README_CONTENT = `## Usage
 

.taskless/rules/sg/no-unrouted-cli-invocation/no-unrouted-cli-invocation.yml

@@ -24,14 +24,31 @@ note: |
   Recipes in `src/agent/*.txt` are out of reach here by being .txt, which is
   correct: they carry a `<taskless-cli>` marker the reading agent fills in (see
   `src/prompts/recipes.ts`) and name no package at all.
+
+  TWO KNOWN LIMITATIONS, since this rule is the only enforcement for some of
+  the sites it covers. Both are syntactic, and neither is reachable by
+  anything in the tree today.
+
+  A SPLIT LITERAL puts the package name in its own fragment: `"npx " +
+  "@taskless/cli"`. That is why the regex below matches the package name
+  alone rather than requiring a launcher in front of it, which costs nothing
+  because every string in `packages/cli/src/` naming the package is an
+  invocation. A split placed mid-name (`"@taskless/" + "cli"`) still evades
+  it, and no single-fragment rule can see that.
+
+  An ALIASED IMPORT (`import { applyCliInvocation as apply }`) is not
+  recognised as routed, because the exemption matches the callee text. That
+  direction is a FALSE POSITIVE: it reports a call that is already safe. Left
+  as-is deliberately, since the failure is loud and the alternative would
+  have the rule resolve imports.
 files:
   - "packages/cli/src/**"
 ignores:
   - "packages/cli/src/util/invocation.ts"
   - "packages/cli/src/util/package-manager.ts"
 rule:
   kind: string_fragment
-  regex: "(npx|pnpm dlx|yarn dlx|bunx) @taskless/cli"
+  regex: "@taskless/cli"
   not:
     inside:
       stopBy: end