Repository navigation
Aggregator live Kaneo reader: stop presenting creation time as update time #1197
Description
Part of epic #1184 (PM stack coherence review, 2026-10-26).
Kaneo board dates are wrong: card updatedAt is the task's createdAt. Evidence: live.ts kaneoBoard maps updatedAt: t.createdAt, carrying no updated field into BoardItem. derive.ts deriveToday then sorts/prioritises by that fabricated field, so freshness and priority derivations are quietly computed from creation dates.
Acceptance:
- Board items' updatedAt matches Kaneo's API value in a stub-server test, or is absent.
- Today's priority sort no longer consumes a fabricated date.
- Card age is labelled honestly where no update timestamp exists.
Acceptance criteria
- Board items'
updatedAtmatches Kaneo's API value in a stub-server test, or is absent — never the task'screatedAtpresented as update time. - Today's priority sort no longer consumes a fabricated date.
- Card age is labelled honestly where no update timestamp exists.
Activity
developing-today commentedon Oct 27, 2026
CODE-331
dezren39 commentedon Oct 28, 2026
Intake review
Related: Part of epic #1184. Sibling batch: #1198, #1196, #1195. Related: #1162 (reconciled in-progress list) consumes the same BoardItem dates.
Notes / risks: A fabricated updatedAt silently corrupts every freshness/priority derivation downstream — fixing the mapping at live.ts kaneoBoard is the whole fix; do not patch the sort.
Suggested approach: If Kaneo's API has no updated field, prefer absent + honest age labelling over any substitute timestamp.
Live check: verified still open and unheld this run; a merged-PR search on this run (2026-10-28T10:35:00Z) returned no PR resolving this issue, so it remains live work. Acceptance criteria appended to the body (original text preserved verbatim above it) and labels normalized by the fleet monitor.
dezren39 commentedon Nov 1, 2026
Picked up triage in queue task 2476; checking current main and ownership.
1 remaining item
dezren39 commentedon Nov 1, 2026
Triage verdict: creation-time fallback remains
At current main f00dde6,
pm-stack/aggregator/src/sources/live.ts:181mapsupdatedAt: t.updatedAt ?? t.createdAt. This is narrower than the original report: real update time is now preferred, but missing update times are still presented as creation times. Route a fix covering the missing case, downstream sorting and honest age display, with a stub-server regression test.dezren39 commentedon Nov 1, 2026
Triage complete; follow-up queue task 4905 covers the remaining fallback and regression tests. The issue remains open.
dezren39 commentedon Nov 1, 2026
🤖 Agent note · picked up
fix(aggregator): do not present Kaneo creation time as update time (#…
dezren39 commentedon Nov 1, 2026
🤖 Agent note · done
pm-stack/aggregator/src/sources/live.tsno longer substitutescreatedAtwhen Kaneo omitsupdatedAt; the board item stays undated, so Today/recency sorts treat it as oldest and the done policy keeps it as age-unproven instead of consuming fabricated freshness.queue/4905-1197-kaneo-updated-at· tests: laptopbun test test/kaneo-updated-at-1197.test.ts test/board-done-policy.test.ts— 6 pass, 0 fail (new stub-fetch regression: distinct update time passes through verbatim; missing update time stays absent, never the creation time)