fix: correct prev_ok word-boundary check in find_top_level_keyword

abs_pos == from skipped the boundary check for keywords at the scan start
when from > 0. The second branch (text[..abs_pos].chars().next_back()) already
handles abs_pos == 0 correctly via unwrap_or(true), so drop the short-circuit.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

Author: Benoit Aubuchon

apps/framework-cli/src/framework/core/infra_reality_checker.rs

@@ -220,13 +220,12 @@ fn dicts_ddl_equivalent(actual_ddl: &str, desired_ddl: &str) -> bool {
                     _ if depth == 0 => {
                         for &kw in keywords {
                             if text[abs_pos..].starts_with(kw) {
-                                // Require a word boundary before (start or non-alnum/underscore)
-                                let prev_ok = abs_pos == from
-                                    || text[..abs_pos]
-                                        .chars()
-                                        .next_back()
-                                        .map(|p| !p.is_alphanumeric() && p != '_')
-                                        .unwrap_or(true);
+                                // Require a word boundary before (start of text or non-alnum/underscore)
+                                let prev_ok = text[..abs_pos]
+                                    .chars()
+                                    .next_back()
+                                    .map(|p| !p.is_alphanumeric() && p != '_')
+                                    .unwrap_or(true);
                                 // Require a word boundary after (end or non-alnum/underscore)
                                 let after = abs_pos + kw.len();
                                 let next_ok = text[after..]