the signals and their derived score are provisional and subject to change.
validate manually before sharing.
b8738b4e72b10505989856ee329c0ecdd89fceb2none
# Testing
## Framework
Tests use a minimal SRFI-269 implementation in `(tests support)`. Three
primitives — `is`, `test`, `suite` — build first-class test entities and
deliver them to a pluggable runner. Definition is separated from execution.
## Running tests
All tests (via Automake):
make check
Single file:
./pre-inst-env guile tests/test-router.scm
## Writing tests
```scheme
(use-modules (tests support)
(safsaf router)) ; module under test
(define-suite router-# CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
## Project Overview
Safsaf is a web framework for Guile Scheme, built on Guile Fibers
using the Guile Knots web server.
## Environment Setup
The project uses `direnv` with Guix. The `.envrc` runs `use guix -D -f guix-dev.scm`, which pulls in all dependencies: `guile-knots`, `guile-webutils`, `guile-lib`, `guile-json-4`, `guile-squee`, `guile-sqlite3`, `guile-gcrypt`.
Run `direnv allow` to# Documentation
## What is here, and what is generated
- `index.texi` — the manual's frame: title, top node, chapter includes,
appendices, indices. Only changes when a chapter is added or removed.
- `guidance.texi` — the hand-written Guidance chapter. This is normally
the only file here to edit.
- `dependencies.texi` — the hand-written Dependencies chapter, after the
API chapter: which modules of the libraries Safsaf is built on an
application imports itself, and what the rest are used fornone