fix(build-x): portable token-boundary regex in hallucination-check.sh

The initial manifest-resolution regex used a complex character class
(['"\[ ] / ['"\] =<>~,]) that parses subtly differently across
grep flavors — under ugrep (the grep on some Linux distros) it
failed to match 'requests' in dependencies = ["requests"] even
though GNU grep / BSD grep both matched it.

Replace with the portable complement-of-name-chars pattern:

  (^|[^a-zA-Z0-9_-])${name}([^a-zA-Z0-9_-]|$)

Applied to both check_python and check_rust. Equivalent in
intent — the package name is a whole token, preceded and followed
by a non-name char (or line boundary). Conservative by design
(prefers false-positive avoidance over false-negative pickup).

Caught by the cycle smoke (block §F1/§F2: 'requests' was being
flagged as unresolved on a fixture where pyproject.toml clearly
declared it). Item F follow-up.

Author: xoai

runtime/multi-agent/scripts/hallucination-check.sh

@@ -132,9 +132,14 @@ check_python() {
     # In-repo module (file or package at the top level).
     if [[ -f "${top}.py" || -d "${top}" ]]; then continue; fi
 
-    # Look in the manifest's dependency lists. Cheap grep is sufficient
-    # for the common case (the spec acknowledges this is conservative).
-    if grep -qE "(^|[\"'\[ ])${top}([\"'\] =<>~,]|\$)" "${manifest}" 2>/dev/null; then
+    # Look in the manifest's dependency lists. Match the package name
+    # as a whole token — preceded and followed by a non-name char (or
+    # line boundary). The negated bracket-expression form is portable
+    # across grep flavors (GNU grep, BSD grep, ugrep) where the
+    # `["'\[ ]`-style classes parse subtly differently. Conservative
+    # by design (spec acknowledges false-positive avoidance over
+    # false-negative pickup).
+    if grep -qE "(^|[^a-zA-Z0-9_-])${top}([^a-zA-Z0-9_-]|\$)" "${manifest}" 2>/dev/null; then
       continue
     fi
 
@@ -222,8 +227,9 @@ check_rust() {
     # `crate`, `self`, `super` are language constructs.
     case "${crate}" in crate|self|super|std|core|alloc) continue ;; esac
 
-    # Look in Cargo.toml dependencies.
-    if grep -qE "(^|[\"'])${crate}([\"' =])" "${manifest}" 2>/dev/null; then
+    # Look in Cargo.toml dependencies — same robust token-boundary
+    # pattern as the Python check.
+    if grep -qE "(^|[^a-zA-Z0-9_-])${crate}([^a-zA-Z0-9_-]|\$)" "${manifest}" 2>/dev/null; then
       continue
     fi