/** * `metadata.updated` bookkeeping. * * The 2.0 metadata shape carries `updated` — "when did this increment last * move". Before this, the only timestamp was `lastActivity`, and it was * touched exclusively by status transitions: a whole session of `task claim` / * `task done` / `task skip` left it frozen at the creation time, so `status` * and any staleness heuristic read as "nothing happened here in days". * * Ledger appends go through {@link touchIncrementUpdated}, which is a raw * read-modify-write of metadata.json (NOT MetadataManager) on purpose: it must * not validate, must not transition, must not fire sync triggers, and must * never make a task command fail. * * @module core/tasks/increment-updated */ /** * Stamp `updated` (and the legacy `lastActivity` mirror) on the increment's * metadata.json. Best-effort: any error is swallowed — losing a timestamp must * never lose a ledger event. * * @param incrementDir - increment folder (the one holding metadata.json) * @param at - ISO timestamp to stamp (defaults to now) * @returns true when metadata.json was rewritten */ export declare function touchIncrementUpdated(incrementDir: string, at?: string): boolean; //# sourceMappingURL=increment-updated.d.ts.map