fix(governance): resolve execution_verified type cluster in lane-worker and execution-gate

[vortsghost2025]

Summary

Fixes the execution_verified TypeScript type cluster in lane-worker.js and execution-gate.js by aligning route record shapes with runtime behavior.

Root Causes

1. Early route objects omitted execution verification metadata (execution_verified, would_verify, ownership_notes, schema_remediation)
2. An unscoped repoRoot reference caused PROCESSING_EXCEPTION in CPS logging
3. Dry-run reference checks performed discovery before the skip return

Changes

• Added missing route record fields in lane-worker.js (_routeRaw, FOREIGN_INSTANCE_ACTIONABLE, STALE_FOREIGN_INSTANCE, PROCESSING_EXCEPTION, and domain/execution failure returns)
• Moved this.dryRun guard before _findReferencedMessage in execution-gate.js
• Updated test-execution-gate.js to use confidence: 8 and from: 'library' with lookup isolation proofs
• Fixed repoRoot → this.repoRoot in CPS logging path

Verification

• node scripts/test-execution-gate.js: 14/14 pass
• npx tsc --noEmit: zero TypeScript errors in affected cluster
• Global TypeScript baseline still has unrelated failures
• No deployment or service restart included
• No live repository was modified

---

CI INFRASTRUCTURE NOTE:
The current red CI result occurs before feature tests because tsconfig.ci.json is absent from master. Signing Integrity passed. Feature validation remains documented by focused local tests pending the separate CI-infrastructure repair.

[coderabbitai]

Important

Draft PR not reviewed

Draft PRs are not automatically reviewed by default.

• Trigger a manual review

To automatically review draft PRs, update your CodeRabbit configuration:

reviews:
  auto_review:
    drafts: true

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}