made DanceResponse summarize more shallow to prevent test hangs

[owleyeview]

PR: Make DanceResponse Logging Shallow and Trace-Safe

Summary

This PR updates DanceResponse::summarize() to avoid deep debug traversal of transaction-bound runtime graphs when logging.

After the Phase 1.2 transaction-aware reference refactor, DanceResponse contains tx-bound holon references. Formatting these with {:#?} can traverse:

• HolonReference
• TransactionContextHandle
• Arc<TransactionContext>
• Pools, staged holons, relationships, etc.

With tracing enabled, this caused severe performance degradation and apparent test hangs as the object graph grew.

---

What Changed

• DanceResponse::summarize() now:

  • Avoids formatting full runtime references
  • Avoids traversing TransactionContextHandle
  • Logs only shallow identifiers and counts (e.g. holon IDs, tx_id)

• No changes to runtime behavior or transaction logic

• No changes to wire types or binding behavior

This strictly affects logging behavior.

---

Why This Is Safe

• No functional logic modified
• No change to reference semantics
• No change to transaction provenance
• Only reduces logging surface depth

---

Result

• Tests complete successfully with tracing enabled
• No more trace-level hangs due to debug graph traversal
• Logs remain readable and informative
• Logging cost remains bounded as state grows

[evomimic]

The changes made reduce log output to the point where all tests pass. That's good!

Unfortunately, they also make the logs virtually useless to debug any real issues because they reveal nothing about state... just a stream of events.

What this really illustrates is that we've outgrown our logging strategy and a deeper re-factor is in order.

I'm going to approve this PR for now so we can unblock other development tasks. We can open a separate enhancement for re-factoring logging approach.