chore(deps): update dependency @harperfast/integration-testing to v1

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
@harperfast/integration-testing	^0.7.0 → ^1.0.0

---

Release Notes

HarperFast/integration-testing (@​harperfast/integration-testing)

v1.0.0

Compare Source

⚠ BREAKING CHANGES

• a call that passes the node where the context belongs now throws
  a TypeError instead of being silently accepted. Any suite doing that today passes
  while leaking a Harper instance, and will go red on upgrade — the point of the
  change, but it is a visible behavior change, so it is released as a major rather
  than slipped into a patch. Consumers on a ^0.7.x range opt in deliberately.

Bug Fixes

• reject a Harper node where a test context is expected (#​31) (8854fc8)

---

Configuration

📅 Schedule: (in timezone America/New_York)

• Branch creation
  • "before 9am on Monday"
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[dawsontoth]

Approving. This is a major bump, so I ran the suite that actually exercises the dependency rather than just the unit test.

npm ci                    exit 0
npm run format:check      exit 0  (prettier)
npm test                  1 test passed  (tsc build + node --test)
npm run test:integration  11 tests / 3 suites, 11 passed, 0 failed

The integration run is the load-bearing one — it drives @harperfast/integration-testing@1.0.0 end to end and all three suites pass:

• harper dev: server-renders with HMR over HTTP, and falls through to Harper resources (3 tests)
• harper dev (SPA): serves the app shell for navigations and falls through for everything else (4 tests)
• harper run: builds and server-renders the production output (no HMR) (4 tests)

The v1.0.0 breaking change doesn't apply to us. The only breaking change in 0.7.1...1.0.0 is #31: passing a Harper node where a test context is expected now throws a TypeError instead of being silently accepted (which previously leaked a Harper instance). Our suite passes 11/11, so nothing here was relying on the old silent-accept behavior. That was released as a major precisely so consumers on ^0.7.x opt in deliberately — this is that opt-in, and it's clean.

Diff is one line (^0.7.0 → ^1.0.0) plus the lockfile. All 7 CI checks green, including Integration (Node 22/24/26).

Local env: macOS, Node 24.19.0, npm 11.17.0, isolated HOME with the 127.0.0.x loopback aliases the harness binds to.