Anchor the Phase 7 due-date fixture to the current month

[DaveHomeAssist]

Clears the Deploy NoteForge failure on main.

Problem

The Phase 7 cross-feature smoke hardcoded @due(2026-08-21) in both the fixture note and its incremental update, then asserted the Calendar overlay lists the updated task:

check('open Calendar reflects the same incrementally updated due task',
  /Phase7 updated task/.test(await page.locator('#calendar-overlay').innerText()));

The Calendar anchors on today and its agenda renders only items inside the visible period, so that assertion could only hold while the wall clock was inside August 2026. It passed in CI on 2026-08-20 and has failed every run since the month rolled over — a time-bomb fixture, not a regression.

Confirmed pre-existing: the identical failure reproduces on becbffa, the base commit before the Build Toward the Whole series, with the other 393 checks passing.

Fix

Compute the due date from the current date — the same idiom the Phase 4 fixture already uses — and thread it through to the update step, so the task always lands inside the period the Calendar renders.

Verification

node test/run-features.mjs — 394/394 pass (previously 393 pass, 1 fail).

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, add credits to your account and enable them for code reviews in your settings.