{"version":"2.1.242","anchor":"telemetry-for-the-home-directory-seeding-path","canonical_anchor":"telemetry-for-the-home-directory-seeding-path","heading":"Telemetry for the home-directory seeding path","tier":"internal","area":"Telemetry","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242\/e\/telemetry-for-the-home-directory-seeding-path","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242","markdown":"### Telemetry for the home-directory seeding path\n\nThree events track the path that seeds a fresh home directory, only on accounts where it runs.\n\n**What**\n\nThree new events track the path that seeds a fresh home directory: apply, hold and recovery, each recorded only when that path runs, which is limited to the same accounts it is.\n\n**Details**\n\n- `tengu_home_seed_apply` carries outcome, probe, generation, epoch_gt1, duration_ms, applied_before_first_ask, output_style_check and per-file refusal counters such as files_refused_loader_reach and settings_refused.\n- `tengu_home_seed_hold` carries outcome, waited_ms, verdict_wait_ms and first_ask; `tengu_home_seed_recovery` carries outcome, generation, duration_ms and rules_dropped.\n- Outcomes are also reported to health tracking under the component name `ccr_home_seed`.\n\n**Evidence**\n\n`tengu_home_seed_apply`\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 3\/5"}