fix(environment): restrict epoch normalization to clock fields

Require a time-field token boundary before treating numeric values as epoch clocks, so identifiers such as media format codes remain literal. Clarify recognized field forms and clock offset and precision semantics in the fidelity guide.

Fixes #6551
This commit is contained in:
morluto committed 2026-10-23 18:07:45 +08:00
1 parent 18225b9bd6
commit 65168f77fb
4 files changed
+64 -3

No files matched your search

@@ -166,6 +166,21 @@ describe("compareAnswers", () => {
});
});
describe("clock field names", () => {
it("keeps numeric format identifiers literal and recognizes clock field forms", () => {
expect(
compare({ format: 1196444237 }, { format: 1448695129 }).differences,
).toMatchObject([{ category: "value", pointer: "/format" }]);
expect(
compare({ updated_at: 1760000000 }, { updated_at: 1760000999 })
.differences,
).toEqual([]);
expect(
compare({ createdAt: 1760000000 }, { createdAt: 1760000999 }).differences,
).toEqual([]);
});
});
describe("comparison body coverage", () => {
it("compares a live body over the replay limit by status only and counts it", () => {
const result = compareAnswers(