screen-locker/web/src/api.test.ts
Krzysztof kuhy Rudnicki 8f911585c1 Serve the lock decision, its history and its health at 127.0.0.1:8770
The only status surface was a GTK tray icon, commented out of ~/.config/i3
on 2026-08-21. So when the weekly count went wrong, nothing on the machine
said so for two weeks -- the same silence that let a deleted timer job stop
enforcement for thirteen days in August.

Three read-only endpoints, and a React 19 UI over them:

  /api/status     the decision, the week, and whether today has a workout
  /api/decisions  the recorded trail, newest first
  /api/health     timers armed, disarm marker, log and trail freshness

The Why view is the one that matters: it renders the run of
"weekly_minimum_met 5/5" ticks that hid this week's bug, without anyone
having to reach for journalctl.

/api/status also carries gaming.workout_today, which is the fact
steam-backlog-enforcer will cut the daily budget on. Deliberately just the
fact -- the enforcer owns the hour values, so the two repos cannot come to
disagree about what a workout day is. It is derived from count_day_credits,
the same rule the locker enforces with.

_compliance_state_word moves from status_view (tkinter) into
_status_projection, and the systemd arming check moves from
scripts/check_enforcement_armed.py into screen_locker/_armed_state.py, so
the server can answer "is enforcement armed" without a second copy of the
logic that would be free to disagree with the gate.

web/ mirrors steam-backlog-enforcer/web but tightens it: that config has no
"strict" in any tsconfig, extends only tseslint recommended (no type-aware
rules at all), and gates neither lint nor typecheck in pre-commit. Here all
three run, on strictTypeChecked + stylisticTypeChecked, with
noUncheckedIndexedAccess and exactOptionalPropertyTypes. 44 tests, 100% of
statements, branches, functions and lines.

typescript stays pinned at 6.0.3: 7.0.2 is out, but every published
typescript-eslint -- stable, canary and rc-v8 -- declares
typescript ">=4.8.4 <6.1.0". The fleet allowlist already carries that entry.

The 250-line cap now covers ts/tsx. It was python/shell/dart only, which
would have made web/ exempt from the gate the rest of the repo lives under
-- the same omission that exempted the whole Flutter app until 2026-08-15.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Fcwu78wk17FWMHbbfbyicc
2026-08-29 22:50:19 +02:00

44 lines
1.6 KiB
TypeScript

import { afterEach, describe, expect, it, vi } from 'vitest'
import { fetchDecisions, fetchHealth, fetchStatus } from './api'
function mockFetch(response: Partial<Response>): void {
vi.stubGlobal('fetch', vi.fn().mockResolvedValue(response))
}
afterEach(() => {
vi.unstubAllGlobals()
})
describe('api', () => {
it('returns the parsed body for a 200', async () => {
mockFetch({ ok: true, json: () => Promise.resolve({ total: 1 }) })
await expect(fetchDecisions(5)).resolves.toStrictEqual({ total: 1 })
})
it('passes the limit through in the query string', async () => {
const spy = vi.fn().mockResolvedValue({ ok: true, json: () => Promise.resolve({}) })
vi.stubGlobal('fetch', spy)
await fetchDecisions(42)
expect(spy).toHaveBeenCalledWith('/api/decisions?limit=42')
})
it('throws with the status text on a failure, rather than returning empty', async () => {
mockFetch({ ok: false, status: 500, statusText: 'Internal Server Error' })
await expect(fetchStatus()).rejects.toThrow('API returned 500 Internal Server Error')
})
it('requests the health endpoint', async () => {
const spy = vi.fn().mockResolvedValue({ ok: true, json: () => Promise.resolve({}) })
vi.stubGlobal('fetch', spy)
await fetchHealth()
expect(spy).toHaveBeenCalledWith('/api/health')
})
it('requests the status endpoint', async () => {
const spy = vi.fn().mockResolvedValue({ ok: true, json: () => Promise.resolve({}) })
vi.stubGlobal('fetch', spy)
await fetchStatus()
expect(spy).toHaveBeenCalledWith('/api/status')
})
})