fix(micode): normalize epoch seconds vs milliseconds in time.created

[junhoyeo]

Problem

crates/tokscale-core/src/sessions/micode.rs hard-assumed time.created/time.completed are epoch milliseconds (matching OpenCode). Some MiMo Code channels/builds have been observed writing epoch seconds, which made dates land ~1000x in the past (1970-era) and durations ~1000x too small (PR #710).

Fix

Added micode_timestamp_to_ms: a value at/under the 1e12 threshold is treated as seconds and scaled to ms, mirroring the existing timestamp_secs_to_ms helpers in the goose/hermes parsers. The normalized value now feeds:

• the UnifiedMessage timestamp (the date),
• the dedup fingerprint (created_bits/completed_bits),
• the duration calculation (micode_duration_ms normalizes both endpoints),

so all three agree regardless of the input unit. Smallest correct change; no unrelated refactors. ClientId / commit metadata untouched (not a code issue).

Tests (would fail without the fix)

• test_parse_micode_sqlite_normalizes_seconds_and_milliseconds: a ms-valued and a seconds-valued time.created denoting the same instant yield identical timestamp (1_700_000_000_000) and date, plus a millisecond-scale duration (Some(1234)). Without normalization the seconds input formats to 1970 and a ~1ms duration.
• test_parse_micode_sqlite_non_object_path_field: a non-object path (bare string) no longer risks dropping the message; workspace stays None (previously untested, flagged).
• test_parse_micode_sqlite_legacy_fallback_embedded_path_workspace: with no session table the modern JOIN query fails to prepare and the legacy fallback runs; workspace is derived from the embedded path.root (previously untested, flagged).

cargo test -p tokscale-core and cargo clippy -p tokscale-core --tests both pass clean.

Residual concern

A single real MiMo database that mixes seconds and ms across rows is not specifically tested, though each row is normalized independently so mixed units are handled.

🤖 Generated with Claude Code

---

Summary by cubic

Normalize MiMo Code time.created/time.completed to milliseconds to fix 1970-era dates and 1000x-short durations when some channels write epoch seconds. The normalization now powers timestamps, dedup fingerprints, and duration so they stay consistent across mixed inputs.

• Bug Fixes
  • Added micode_timestamp_to_ms to treat values ≤ 1e12 as seconds and scale to ms.
  • Used normalized created_ms/completed_ms for UnifiedMessage timestamp, created_bits/completed_bits, and micode_duration_ms.
  • Tests cover seconds vs ms normalization, defensive parsing of non-object path, and legacy fallback deriving workspace from embedded path.root.

^{Written for commit d6da0cb. Summary will update on new commits.}

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
tokscale	Ignored		Jun 22, 2026 7:25am

[cubic-dev-ai]

No issues found across 1 file

_{Re-trigger cubic}