tengu_init telemetry bug fix: three fields were reading from an unrelated/undefined variable

In the tengu_init telemetry event sent when a Claude Code session starts, three fields were being read from the wrong source. lockfile_family, private_registry_host_class, and os_locked_toolchain had been pulling their values from a variable that didn't match the one the rest of the payload used, so they weren't reflecting the same data as everything else in the event. The code now reads all three fields from the correct, consistent source.