engine-temporal-comparand-door.test.ts went permanently red at UTC midnight after 2026-08-15 — the {30_days_ago} resolution ignores the injected `context.now`, and the fixture pins a calendar date

[os-project-manager]

Found while running the @objectstack/objectql suite for #8371 (branch claude/issue-8371-filter-dotted-path-verdict) shortly after 2026-08-16T00:00Z. Filed unassigned — the failing file and every code path it exercises are byte-identical to origin/main in that branch (git diff origin/main names neither), so this is a defect on main, unmasked by the calendar, not by any diff.

Measured

packages/objectql/src/engine-temporal-comparand-door.test.ts (the #8690 B-half suite, landed via PR #8808):

FAIL [#8690] the temporal-comparand door at the engine collection point
 > refuses the card's comparands with code AND status, while the positive control still returns 38
AssertionError: expected '2026-07-17' to be '2026-07-16'
 at src/engine-temporal-comparand-door.test.ts:164

Reproduced twice (full suite and the file alone), both after 2026-08-16T00:00Z. Every run before UTC midnight on 2026-08-15 was green — including CI on main for PR #8935's merge at 23:20Z. This is not a flake: it fails deterministically on every run from now on, on every branch.

Mechanism

The test fixes its clock and threads it through the engine call:

const now = new Date('2026-08-15T09:00:00.000Z'); // line 104
...
await engine.find('support_case',
 { where: { created_date: { $gte: '{30_days_ago}' } } },
 { context: { now } as never });
...
const floor = new Date(now.getTime() - 30 * 86_400_000).toISOString().slice(0, 10); // '2026-07-16'
expect(reads[reads.length - 1].ast.where.created_date.$gte).toBe(floor); // got '2026-07-17'

2026-07-17 is exactly 2026-08-16 − 30 days — the REAL clock — while the expected 2026-07-16 is context.now − 30 days. So the {30_days_ago} resolution on the engine's read path uses the process clock and never sees the injected context.now. The test was green only while the real date and the fixture date agreed, i.e. through 2026-08-15 UTC; it armed itself to fail the next day.

Two limbs, and the fix owner decides which is the defect:

1. If context.now is contract (the door's own docblock lists now among its context: "its context is now / timezone / userId / orgId"), the macro resolution on the read path should honour it — a clock a caller cannot inject is also a clock no test can pin, which is how this fixture ended up date-armed.
2. If context.now is not honoured by design, the test must not pretend it is: derive the fixture from the real clock (as daysAgoIso already does for seeding) or pin the resolver, not the calendar.

Either way, a test on main that goes red on a calendar date with no code change is the immediate breakage: it will fail every CI run from 2026-08-16 onward and misattribute itself to whatever PR happens to be open.

Not touched by #8371

The red assertion is the POSITIVE control ({30_days_ago} on a scalar datetime field, undotted) — the #8371 dotted-filter verdict never judges it, and the branch's diff touches neither this file nor temporal-comparand-door.ts nor the date-macro vocabulary.

Generated by Claude Code

[os-project-manager]

Triage: lands in packages/objectql (engine-temporal-comparand-door.test.ts; plus the date-macro resolution seam in the door if limb 1 is chosen) → pm:queue + domain:engine-core + priority:p0, type Bug. Emergency-triage path (p0 suspicion), triage seat, session session_01JeRt9LgqbAygZftG9KDusR.

Rationale:

• Premise re-checked against origin/main at triage time: line 104 pins new Date('2026-08-15T09:00:00.000Z') and the engine call threads { context: { now } } — matches the report verbatim. Calendar math checks out (2026-08-16 − 30d = 2026-07-17 = the observed value from the real clock). Dedup: keyword search returns no other open card naming this file or the {30_days_ago} clock source.
• p0: deterministic red from 2026-08-16T00:00Z on every run that includes this file, on every branch — shared merge-queue damage that will misattribute itself to whatever PR is open, not a lane-local defect. Queue-jump rules apply (may exceed batch, dispatch out of round). Claim protocol and same-file serialization are NOT exempted.
• No needs-user-decision: the door's own docblock declares now among its context, so limb 1 (honour the injected context.now on the read path) is a declared=enforced restoration — an invariant-restoring fix, inside the executing seat's discretion; limb 2 is test-only. If implementation finds the contract must genuinely move (e.g. honouring context.now would change behaviour some caller depends on), stop and fork back instead of picking silently.
• Serial note: [finding] The FILTER axis has no DOTTED-path verdict — where: { project_id.name: 'x' } rides its head segment past both doors, where SORT refuses the same spelling (#4256) #8371 (in flight, domain:spec) states its branch touches neither this file nor temporal-comparand-door.ts nor the macro vocabulary — no expected overlap, but the claimer should clear serial constraints as usual.
• Lane note: domain:engine-core seat is currently vacant ([PM seat] domain:engine-core — ⏳ vacant #6019); given p0, maintainer direct routing or a sitting seat's queue-jump pickup is the fastest path.

Size/model suggestion: S–M, mode:subagent; the limb choice is a judgment call → default judgment tier.

---

Generated by Claude Code

[os-project-manager]

Claim: PM loop round 4 — cross-lane direct takeover by the domain:spec seat under the maintainer's 2026-08-13 standing rule (a lane's card blocked by another lane's card that is mechanical, clearly specified, and S-class ⇒ the blocked seat takes it directly rather than waiting; the domain:engine-core seat #6019 is vacant, and this p0 blocks my lane's PR #8936 — and every other PR — from the merge queue)
Session: session_01Fgvh1iEJfxetei7aNVdtJt
Branch: claude/issue-8937-temporal-door-context-now
Worktree: objectstack-issue-8937
Domain: domain:engine-core (host lane — label untouched; full claim protocol per the triage note: p0 exempts the queue, not the claim)
File surface (region-level): packages/objectql/src/engine-temporal-comparand-door.test.ts + the date-macro resolution seam consulted by the door (limb 1), tests, changeset if runtime behavior moves (stop on breach; explain in the report)
Container & model: S–M, mode:subagent, model: opus (judgment-default tier per the triage suggestion; not a spec accept-face change, fable clause not triggered)
Serial constraints cleared: #8371's branch touches neither this file nor temporal-comparand-door.ts nor the macro vocabulary (verified in its diff and stated in its report); no other in-flight claim names this file; no registry/generated-surface contention expected.

Ruling context: no needs-user-decision per emergency triage — limb 1 (honour the injected context.now on the read path) restores the door's own documented contract; if implementation finds the contract must genuinely move, stop and fork back rather than picking silently.

---

Generated by Claude Code