[POS][Local Catalog] Repo for incremental sync timestamps

[samiuelson]

POS Incremental Sync Timestamp Storage

Description

Summary

Implemented a repository system for storing and retrieving site-specific incremental sync timestamps for POS products and variations using DataStore preferences.

Changes

• WooPosSyncTimestampRepository: Low-level repository for string timestamp storage with site-specific keys
• WooPosSyncTimestampManager: High-level manager providing Date object API with GMT timezone handling

Key Features

• Site-specific storage: Timestamps are isolated per site using dynamic key generation
• Type-safe API: Date objects for convenience, strings for raw access
• Error handling: Graceful null site handling with logging

Steps to reproduce

Testing information

This code is not used at the moment. Check if CI is green and if the code looks good.

The tests that have been performed

Above

Images/gif

N/A

• I have considered if this change warrants release notes and have added them to RELEASE-NOTES.txt if necessary. Use the "[Internal]" label for non-user-facing changes.

[wpmobilebot]

📲 You can test the changes from this Pull Request in WooCommerce-Wear Android by scanning the QR code below to install the corresponding build.

	App Name	WooCommerce-Wear Android
	Platform	⌚️ Wear OS
	Flavor	Jalapeno
	Build Type	Debug
	Commit	0e9c15e
	Direct Download	woocommerce-wear-prototype-build-pr14511-0e9c15e.apk

[wpmobilebot]

📲 You can test the changes from this Pull Request in WooCommerce Android by scanning the QR code below to install the corresponding build.

	App Name	WooCommerce Android
	Platform	📱 Mobile
	Flavor	Jalapeno
	Build Type	Debug
	Commit	0e9c15e
	Direct Download	woocommerce-prototype-build-pr14511-0e9c15e.apk

[Copilot]

Pull Request Overview

This PR implements a repository system for storing and retrieving site-specific incremental sync timestamps for POS products and variations using DataStore preferences.

• Adds a low-level repository (WooPosSyncTimestampRepository) for string timestamp storage with site-specific keys
• Implements a high-level manager (WooPosSyncTimestampManager) providing Date object API with GMT timezone handling
• Includes comprehensive test coverage for the timestamp manager functionality

Reviewed Changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 2 comments.

File	Description
WooPosSyncTimestampRepository.kt	Low-level repository for storing/retrieving site-specific timestamps using DataStore
WooPosSyncTimestampManager.kt	High-level manager providing Date object API with GMT formatting and parsing
WooPosSyncTimestampManagerTest.kt	Comprehensive unit tests for the timestamp manager functionality

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[codecov-commenter]

Codecov Report

❌ Patch coverage is 39.50617% with 49 lines in your changes missing coverage. Please review.
✅ Project coverage is 37.89%. Comparing base (7f6538d) to head (0e9c15e).

Files with missing lines	Patch %	Lines
...os/util/datastore/WooPosSyncTimestampRepository.kt	0.00%	49 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff            @@
##              trunk   #14511   +/-   ##
=========================================
  Coverage     37.89%   37.89%           
- Complexity     9362     9374   +12     
=========================================
  Files          2024     2026    +2     
  Lines        113785   113866   +81     
  Branches      15092    15107   +15     
=========================================
+ Hits          43121    43152   +31     
- Misses        66698    66747   +49     
- Partials       3966     3967    +1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[malinajirka]

💡 I think storing formatted dates has some drawbacks, the main one is that we can't safely change the format without clearing the storage. I'd suggest storing just timestamps - milliseconds since 1970.

Considering Samuel is AFK, @kidinov could you double check my train of thoughts and share whether you agree with this suggestion before I make the change? Thanks!