PersonalBlog

T

implementer 408f33e4e9 test: lock in HOST validation and bind-interface control (E00-S04-T04)

Extend the env-adapter suite to the issue's reworked acceptance criteria:
- static assertions: the adapter resolves HOST via resolveHost (hostname/IP at
  the adapter boundary) and the server passes config.host to server.listen
- deterministic boundary probe: valid HOST forms (IPv4/IPv6/hostname) pass,
  invalid HOST forms throw ConfigStartupError naming host
- boot probes: HOST=127.0.0.1 binds loopback only (no answer on a
  non-loopback interface) with the startup log reflecting the actual bind;
  an invalid HOST exits non-zero naming the field without echoing the raw
  value
- mutation probes: bypassing resolveHost or dropping config.host from
  server.listen both fail
- config-startup-error: update the order-asserion mutation probe for the new
  server.listen(config.port, config.host, ...) signature

2026-08-30 04:42:03 +00:00

.gitea/workflows

test: lock in the env adapter as the single owner of process.env with static scan, mutation and deterministic probes (E00-S04-T04)

2026-08-30 04:17:22 +00:00

apps/server

feat: HOST validated at the adapter boundary and controls the actual bind interface (E00-S04-T04)

2026-08-30 04:41:53 +00:00

docs/development

docs: document the environment adapter in the non-container guide (E00-S04-T04)

2026-08-30 04:17:22 +00:00

extensions/example

feat: add root build/test/typecheck scripts (E00-S01-T05)