[limen GEN-4444j99-promptscope-test-coverage-0620] Raise test coverage in 4444J99/promptscope

[4444J99]

Autonomous limen dispatch of task GEN-4444j99-promptscope-test-coverage-0620.

Find the largest source module in 4444J99/promptscope with little or no test coverage and add a focused, PASSING test suite for it. Run the repo's own test command and confirm green. No placeholder tests. [auto-generated 2026-06-20 to keep the stream endless]

Produced in an isolated worktree off origin — review before merge.

[sourcery-ai]

Sorry @4444J99, you have reached your weekly rate limit of 500000 diff characters.

Please try again later or upgrade to continue using Sourcery

[gemini-code-assist]

Code Review

This pull request makes the execution context optional in several API handlers and the metrics helper, introduces a comprehensive frontend integration test suite using Node's vm module, and updates rate-limiting KV keys in tests. The reviewer feedback suggests adding a .catch() block to the fire-and-forget metrics promise to prevent unhandled rejections, aligning the test DOM's getElementById with standard behavior by returning null for non-existent elements, and removing redundant mutations of the host's globalThis.fetch since the fake fetch is already scoped to the VM context.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

[gemini-code-assist]

In the current implementation, getElementById automatically creates and returns a new FakeElement if the requested ID does not exist in the map. This behavior deviates from the standard DOM specification (where document.getElementById returns null for non-existent elements) and can mask bugs in the frontend code (such as typos in element IDs or missing elements in the HTML).

It is highly recommended to return null when the element is not found, and explicitly populate the expected elements in buildDocument.

  getElementById(id: string) {
    return this.elements.get(id) ?? null;
  }

[gemini-code-assist]

To support the standard-compliant getElementById behavior (returning null when an element is not found), we should explicitly instantiate and populate the FakeElement instances in the elements map here instead of relying on the auto-creation side-effect of the old getElementById.

Suggested change

	for (const id of ids) doc.getElementById(id);
	for (const id of ids) doc.elements.set(id, new FakeElement(id));

[gemini-code-assist]

Since mutating the host's globalThis.fetch is redundant (as the fake fetch is scoped to the VM context), we can safely remove the global fetch backup and the afterEach cleanup hook to keep the test suite clean and prevent potential side effects.

[gemini-code-assist]

Overwriting globalThis.fetch on the host global object is redundant and can introduce test interference or flakiness if other tests run concurrently. Since the fake fetch is already passed directly into the VM context (line 306), the code running inside the VM will correctly resolve to this fake fetch without needing to mutate the host's global state.

We should remove this line, along with the originalFetch backup and afterEach cleanup hook (lines 166-170).

[gemini-code-assist]

The writeMetrics promise is executed in a "fire-and-forget" manner. If any of the underlying KV operations fail or if the RATE_KV binding is misconfigured/undefined, the promise will reject. Without a .catch() handler, this rejection will bubble up as an unhandled promise rejection, which can cause issues in the runtime or fail test suites.

Adding a .catch() block ensures that metric-writing failures are safely logged and do not disrupt the main request lifecycle or test execution.

Suggested change

	const writeMetrics = Promise.all([
	addCounts(env, METRIC_ALL_KEY, deltas),
	addCounts(env, metricDayKey(date), deltas, METRIC_TTL_SECONDS),
	recordSince(env, date),
	]).then(() => undefined));
	]).then(() => undefined);
	if (ctx?.waitUntil) ctx.waitUntil(writeMetrics);
	else void writeMetrics;
	const writeMetrics = Promise.all([
	addCounts(env, METRIC_ALL_KEY, deltas),
	addCounts(env, metricDayKey(date), deltas, METRIC_TTL_SECONDS),
	recordSince(env, date),
	]).then(() => undefined)
	.catch(err => {
	console.error('Failed to write metrics:', err);
	});
	if (ctx?.waitUntil) ctx.waitUntil(writeMetrics);
	else void writeMetrics;