bad-code: IntentController sequential guard I/O over-fetch

[flyingrobots]

Impact

Currently, IntentController.ts iterates sequentially through descriptor.precommitGuards and performs individual worldline.getNodeProps(guard.nodeId) lookups. In a highly active graph with complex multi-node transactions, this results in sequential I/O bottlenecks and potential cache thrashing.

Refactoring Path

Implement a batch-fetch pipeline in ProjectionHandle (worldline.getNodesProps([...nodeIds])) to resolve all precommit guard dependencies in a single consolidated read pass before evaluating obstructions.

[coderabbitai]

🔗 Related PRs

#639 - Guard fresh live observer materialization [merged]

---

📝 Issue Planner

_{Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.}

• Create Plan

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!