{"version":"2.1.221","anchor":"process-markers-gain-a-second-currently-unused-start-time-fi","canonical_anchor":"process-markers-gain-a-second-currently-unused-start-time-fi","heading":"Process markers gain a second, currently-unused start-time field","tier":"internal","area":"Background Tasks","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.221\/e\/process-markers-gain-a-second-currently-unused-start-time-fi","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.221","markdown":"### Process markers gain a second, currently-unused start-time field\n\nProcess marker files can write an alternate start-time field, but that path is hard-coded off.\n\n**What**\n\nProcess marker writing was routed through a helper that can emit an alternate start-time field, but the switch is off in this build.\n\n**Details**\n\n- covers both the daemon\/PID marker and the fleet gesture record\n- the helper emits either `procStart` or the new `procStartFt`, chosen by a predicate hard-coded to return false here\n- the on-disk shape is therefore unchanged; the reader already understands both fields\n\n**Evidence**\n\n`procStartFt`\n\n- Area: Background Tasks\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Present in the build but not switched on"}