Mark Fields

> Is there some write up that tells us where we were, where we are today, and what else we can do to make things better? My main concern -...

Closing this in favor of #21102. At this time, not planning to dig into the fuzz test failures. But open to feedback that we should prioritize that investigation. It's hard...

@agarwal-navin -- I agree it is risky. Without any type validation to distinguish between encoded v. decoded handles, it's nearly impossible to tell whether all the flips/flops between those states...

(Disabling auto-merge until @connorskees has a chance to respond to @agarwal-navin)

@jatgarg How are you planning to use this information? And any concerns about scale? I guess we're already logging the SummarizerTelemetry event every summary, it's just adding extra info. `O(number...

Also, are you confident in existing test coverage? The actual change here is small, but fundamental (switching from fullPath to the passed in handle).

Not planning to merge this for now, to avoid introducing any risk to RC1. Partner team waiting for this is close to bumping to RC2 and it'll be in the...

End to end demo would be good I agree. Use case is primarily Observability via app telemetry - independence from having to sort out FF logs. And getting more info...

Btw @vladsud your specific code/comments were mostly you tripping over NYI parts. Sorry about that. I've cleaned up that part somewhat, enough to illustrate how it would work.

Fixes [AB#7316](https://dev.azure.com/fluidframework/235294da-091d-4c29-84fc-cdfc3d90890b/_workitems/edit/7316)