Is per-experience data available, or only lifetime counters?

[VBasaHU]

Hi, thanks for publishing this — the protocol documentation is very helpful.

I have a question about the scope of the telemetry. From the crate
structure it looks like diagnosis exposes lifetime totals (total puff
count, days used) plus battery voltage. I'm trying to understand whether
anything more granular exists.

Specifically:

1. Does the protocol expose any per-experience / per-session data — a
   count of completed experiences, timestamps, session duration, or
   puffs per session — or are the lifetime totals the only usage figures
   available?

2. If it isn't implemented yet: did you see any indication during reverse
   engineering that such data is stored on the device but not exposed, or
   does it look like it genuinely isn't retrievable over BLE?

3. Is there any real-time state indicator (e.g. "heating active",
   "session in progress") that the device notifies on?

4. A holder-specific question, on ILUMA (M0001): does the charger report
   the holder's heating state while the holder is outside the case? In my
   own testing with a generic BLE tool, the device status and battery
   characteristics stayed unchanged throughout a session and only updated
   once the holder was re-docked. Is that consistent with what you found?

I've only used read/notify operations so far and haven't written to any
characteristic. Not asking you to implement anything — just trying to
understand what the protocol can and can't do.

Thanks!

[VBasaHU]

One more question, if you don't mind: issue #3 references packet captures
in docs/packets/ for the per-model capability audit. I don't see that
directory in the public repo — are those captures published anywhere, or
kept locally?

I ask because if there's a capture of a full consumable session, it would
probably answer the counter-semantics question above directly.