Architecture
The Wrapsfer API uses a small Clean Architecture-style layout: four projects under src/ with strictly inward-pointing dependencies, and two test projects under tests/. This page describes the layout that exists today and where future code should live.
Configuration
Every configuration source the Wrapsfer API reads today, every key it understands, and how to override each one without editing files.
Testing
How the Wrapsfer API is tested today, and the commands used to run those tests locally. Two test projects live under tests/:
Development Workflow
How to add a feature to the Wrapsfer API while keeping the existing layer boundaries intact. The flow below mirrors what is already in source for the greeting sample — use it as a template when adding the next thing.
Deployment
What ships with the Wrapsfer API today for running it as a container, and what you need to think about before exposing it beyond local development. The repository includes a Dockerfile and a docker-compose.yml. There is no infrastructure-as-code, no platform-specific deploy manifest, and no CI/CD pipeline. This page describes only what exists.