ci: drive pipeline via make targets + local make ci gate (refs #30)

Add a root Makefile (lint/build/unit/smoke/ci) as the single source of
truth for the checks, and have each Gitea Actions job call the matching
make target so local and CI cannot drift. `make ci` runs the full
pipeline locally — the interim gate while no runner is registered.

The smoke target auto-points DOCKER_HOST at the rootless Podman socket
when present (and DOCKER_HOST is unset), leaving Docker/CI hosts alone.
Document `make ci` and the Podman prerequisites in docs/runbooks/ci.md.

Verified: `make ci` is green locally (lint, build, unit, container smoke).

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

.gitea/ISSUE_TEMPLATE/adr-proposal.md

@@ -1,24 +0,0 @@
----
-name: ADR proposal
-about: Propose a decision that needs recording before coding (CLAUDE.md §14)
-title: "ADR: "
-labels:
-  - type:adr-proposal
----
-
-**Decision to be made:**
-
-**Context / forces:** <!-- what makes this non-obvious; constraints, trade-offs -->
-
-**Options considered:**
-1.
-2.
-
-**Proposed option + why:**
-
-**Consequences:** <!-- what becomes easier/harder; what we commit to -->
-
-**Coupling rules touched (CLAUDE.md §8):** <!-- none, or which and why -->
-
-> On acceptance, the ADR file (`docs/architecture/adr-NNNN-title.md`, Nygard
-> template) lands in the PR that implements the decision.

.gitea/ISSUE_TEMPLATE/bug.md

@@ -1,21 +0,0 @@
----
-name: Bug
-about: Something behaves incorrectly
-title: ""
-labels:
-  - type:bug
----
-
-**What happened:**
-
-**What you expected:**
-
-**Steps to reproduce:**
-1.
-2.
-
-**Environment:** <!-- branch/commit, OS, container engine, anything relevant -->
-
-**Logs / evidence:**
-
-**Suspected area:** <!-- e.g. area:bff, area:acl — add the matching area label -->

.gitea/ISSUE_TEMPLATE/slice.md

@@ -1,31 +0,0 @@
----
-name: Slice (user story)
-about: A backlog slice — independently demoable, encodes the Definition of Done
-title: "S-NN · "
-labels:
-  - type:slice
----
-
-**Outcome:** <!-- one sentence; user-visible if possible -->
-
-**Acceptance:**
-<!-- Gherkin scenarios or testable assertions -->
--
-
-**Touches:** <!-- services and folders -->
-
-**Out of scope:** <!-- explicit non-goals -->
-
-## Definition of Done
-
-- [ ] This linked Gitea issue exists and is on the right milestone.
-- [ ] Failing test written and committed first (`test(scope): … (refs #NN)`).
-- [ ] Implementation makes the test pass (`feat(scope): … (refs #NN)`).
-- [ ] Refactor commit follows if structure improved.
-- [ ] Conventional Commit messages referencing this issue.
-- [ ] All Gitea Actions CI jobs green (or `make ci` green while no runner exists).
-- [ ] `docker compose up` from a fresh clone reaches green health checks within 3 minutes.
-- [ ] Docs touched if behaviour, contracts, or operations changed.
-- [ ] ADR added in `docs/architecture/` if a non-obvious decision was made.
-- [ ] Demo note appended to `docs/demo-script.md` if the slice is user-visible.
-- [ ] This issue closed by the merging PR (`closes #NN`).

.gitea/PULL_REQUEST_TEMPLATE.md

@@ -1,23 +0,0 @@
-<!-- Title: Conventional Commit style, e.g. feat(bff): … (closes #NN) -->
-
-## What & why
-
-<!-- Summary of the change and the slice/bug it addresses. -->
-
-Closes #
-
-## Definition of Done
-
-- [ ] Linked Gitea issue (above).
-- [ ] Failing test committed before the implementation.
-- [ ] Implementation makes the test pass; refactor commit if structure improved.
-- [ ] Conventional Commits referencing the issue (`refs #NN`).
-- [ ] CI green — all Gitea Actions jobs (or `make ci` green while no runner exists).
-- [ ] `docker compose up` from a fresh clone reaches green health checks within 3 minutes.
-- [ ] Docs updated if behaviour, contracts, or operations changed.
-- [ ] ADR added in `docs/architecture/` if a non-obvious decision was made.
-- [ ] Demo note in `docs/demo-script.md` if user-visible.
-
-## Notes for reviewers
-
-<!-- Anything that helps review: trade-offs, follow-ups, known gaps. -->

.gitignore

@@ -22,10 +22,6 @@ node_modules/
 dist/
 .angular/
 
-# Python / MkDocs
-.venv/
-site/
-
 # OS
 .DS_Store
 Thumbs.db

CHANGELOG.md

@@ -1,20 +0,0 @@
-# Changelog
-
-All notable changes to this project. Generated from Conventional Commits by git-cliff.
-
-## Unreleased
-
-### CI
-- Gitea Actions pipeline + runner runbook (refs #30) (#37)
-
-### Chores
-- Add idempotent Gitea backlog seeder
-- Remove bootstrap scripts from main (#35)
-
-### Documentation
-- Split S-00 into sub-slices (refs #1) (#33)
-
-### Features
-- Placeholder BFF + /health endpoint (closes #28) (#34)
-- Containerize BFF + compose-up smoke (closes #29) (#36)
-

Makefile

@@ -19,7 +19,7 @@ export DOCKER_HOST := unix://$(PODMAN_SOCK)
 endif
 endif
 
-.PHONY: ci lint build unit smoke down changelog help
+.PHONY: ci lint build unit smoke down help
 
 ## ci: run the full pipeline — lint, build, unit, smoke (mirrors Gitea Actions)
 ci: lint build unit smoke
@@ -45,10 +45,6 @@ smoke:
 down:
 	docker compose -f $(COMPOSE) down --volumes
 
-## changelog: regenerate CHANGELOG.md from Conventional Commits (git-cliff)
-changelog:
-	git-cliff --output CHANGELOG.md
-
 ## help: list available targets
 help:
 	@grep -E '^## ' $(MAKEFILE_LIST) | sed 's/^## //'

README.md

@@ -41,32 +41,31 @@ For the architecture rationale, see [docs/PRD.md §3](docs/PRD.md) and [docs/arc
 
 **Prerequisites**
 
-- .NET 10 SDK (for `make lint/build/unit`)
+- Docker Engine (or Docker Desktop) with Compose v2
-- A container engine with Compose v2 — Docker, or rootless Podman (see [docs/runbooks/ci.md](docs/runbooks/ci.md) for the Podman + Compose-provider setup)
+- ~8 GB free RAM, ~10 GB free disk
-- `make`, `curl`, `git`
+- Bash or PowerShell
-- ~4 GB free RAM, ~5 GB free disk (grows as services land)
 
-**Clone**
+**Bring the stack up**
 
 ```bash
-git clone git@git.labs.respellion.tech:eho/register-referentie.git
+git clone https://gitea.respellion.local/respellion/register-reference.git
-cd register-referentie
+cd register-reference
+cp .env.example .env          # edit if you change ports
+docker compose -f infra/docker-compose.yml up -d
 ```
 
-**Wired today (Iteration 0):** only the placeholder BFF exists so far. Get to green in under 10 minutes — run the full check gate, or just the running service:
+Health checks should be green within ~3 minutes on a developer machine. If something fails, see [docs/runbooks/local-startup.md](docs/runbooks/local-startup.md).
 
-```bash
+> **Wired today (Iteration 0):** only the placeholder BFF is in `infra/docker-compose.yml` so far. Bring it up and smoke-test its health endpoint:
-make ci          # lint + build + unit + container smoke — the CI gate
+>
-```
+> ```bash
+> docker compose -f infra/docker-compose.yml up -d --build --wait
+> curl http://localhost:8080/health   # -> Healthy
+> ```
+>
+> `--wait` exits non-zero unless the container reports healthy, so this doubles as the compose-up smoke test. The remaining services and the URLs below land in later slices.
 
-```bash
+**Default URLs**
-docker compose -f infra/docker-compose.yml up -d --build --wait
-curl http://localhost:8080/health     # -> Healthy
-```
-
-`--wait` exits non-zero unless the container reports healthy, so it doubles as the compose-up smoke test. The remaining services and the URLs below land in later slices.
-
-**Target service URLs** *(most land in later slices)*
 
 | Service | URL |
 |---|---|
@@ -74,7 +73,7 @@ curl http://localhost:8080/health     # -> Healthy
 | Openbaar register | http://localhost:4201 |
 | Behandel-portal | http://localhost:4202 |
 | Beheer-portal | http://localhost:4203 |
-| BFF | http://localhost:8080 |
+| BFF | http://localhost:5000 |
 | OpenZaak | http://localhost:8000 |
 | Open Notificaties | http://localhost:8001 |
 | Flowable | http://localhost:8080 |
@@ -83,12 +82,10 @@ curl http://localhost:8080/health     # -> Healthy
 
 Test credentials, BSNs, and personas: see [docs/synthetic-data.md](docs/synthetic-data.md).
 
-**Build the docs site**
+**Re-seed synthetic data**
 
 ```bash
-python3 -m venv .venv && .venv/bin/pip install mkdocs-material
+./tools/seed.sh               # or pwsh ./tools/seed.ps1
-.venv/bin/mkdocs serve         # live preview at http://localhost:8000
-.venv/bin/mkdocs build         # static site in ./site
 ```
 
 ---

cliff.toml

@@ -1,45 +0,0 @@
-# git-cliff configuration — generates CHANGELOG.md from Conventional Commits.
-# Run via `make changelog`. See https://git-cliff.org.
-
-[changelog]
-header = """
-# Changelog
-
-All notable changes to this project. Generated from Conventional Commits by git-cliff.\n
-"""
-body = """
-{% if version %}\
-## {{ version }} — {{ timestamp | date(format="%Y-%m-%d") }}
-{% else %}\
-## Unreleased
-{% endif %}\
-{% for group, commits in commits | group_by(attribute="group") %}
-### {{ group | upper_first }}
-{% for commit in commits %}\
-- {{ commit.message | upper_first }}{% if commit.breaking %} **[BREAKING]**{% endif %}
-{% endfor %}\
-{% endfor %}\n
-"""
-trim = true
-
-[git]
-conventional_commits = true
-filter_unconventional = true
-split_commits = false
-protect_breaking_commits = true
-tag_pattern = "v[0-9]*"
-# CalVer tags: YYYY.MM.PATCH
-filter_commits = false
-commit_parsers = [
-  { message = "^feat", group = "Features" },
-  { message = "^fix", group = "Bug Fixes" },
-  { message = "^perf", group = "Performance" },
-  { message = "^refactor", group = "Refactor" },
-  { message = "^docs", group = "Documentation" },
-  { message = "^test", group = "Tests" },
-  { message = "^ci", group = "CI" },
-  { message = "^build", group = "Build" },
-  { message = "^arch", group = "Architecture" },
-  { message = "^chore", group = "Chores" },
-  { message = ".*", group = "Other" },
-]

docs/architecture/adr-0001-loose-coupling.md

@@ -1,58 +0,0 @@
-# ADR-0001: Loose coupling to upstream Common Ground modules
-
-- **Status:** Accepted
-- **Date:** 2026-06-03
-- **Deciders:** Respellion engineering
-- **Template note:** This is the first ADR and doubles as the worked example of
-  the Nygard template. Copy its shape for new ADRs (`adr-NNNN-title.md`).
-
-## Context
-
-This reference application orchestrates several upstream Common Ground modules —
-OpenZaak (ZGW APIs), Open Notificaties (NRC), Objecten/Objecttypen, Flowable,
-Keycloak. Each is an independently developed, independently deployed peer. The
-temptation in a demo is to reach straight into a peer's database or couple to its
-internal schema to move faster. That coupling is exactly what makes Common Ground
-landscapes brittle and un-upgradeable in practice.
-
-We need a stance, recorded up front, on how our services may talk to these peers.
-
-## Decision
-
-**We integrate with upstream modules only through their documented public APIs, and
-we isolate that integration behind explicit anti-corruption boundaries.**
-
-Concretely (mirrors CLAUDE.md §8):
-
-1. The **ACL** is the only code that talks to ZGW APIs; no other service constructs
-   ZGW URLs.
-2. The **Workflow Client** is the only code that talks to Flowable; BPMN models hold
-   no OpenZaak knowledge.
-3. **Portals talk only to the BFF** — never directly to a backend or a peer module.
-4. **No direct database access across services or to any peer.** Each service owns
-   its schema; the Read Projection is a rebuildable derived artefact.
-5. **Idempotency at every event boundary** (the Event Subscriber tolerates duplicate
-   and out-of-order NRC events).
-
-Bending any of these is an ADR-worthy moment (CLAUDE.md §14): stop and open an
-`adr-proposal` issue first.
-
-## Consequences
-
-**Positive**
-
-- Upstream modules can be upgraded or swapped behind their APIs without rippling
-  through our services.
-- Coupling is visible and minimal — anti-corruption code lives in one named place.
-- The architecture teaches the Common Ground pattern by enforcing it.
-
-**Negative / costs**
-
-- More indirection: a translation layer (ACL, Workflow Client) instead of direct
-  calls. Accepted — it's the point.
-- Eventual consistency across aggregates must be designed for, not assumed away.
-
-**Follow-up**
-
-- Each integration slice that touches a boundary references this ADR; new boundary
-  decisions get their own ADR.

docs/gitea-workflow.md

@@ -1,52 +0,0 @@
-# Working with Gitea: issues, milestones, PRs
-
-Gitea is the **system of record** (CLAUDE.md §7). `BACKLOG.md` is a human-readable
-mirror of the active milestone — when they disagree, Gitea wins.
-
-## Issues
-
-- Open issues from the templates in `.gitea/ISSUE_TEMPLATE/`:
-  - **Slice** — a backlog user story (`S-NN · …`), encodes the Definition of Done.
-  - **Bug** — a defect.
-  - **ADR proposal** — a decision to record before coding (CLAUDE.md §14).
-- Every issue gets `type:*` plus the relevant `area:*` label(s), and is assigned to
-  its iteration **milestone** (`Iteration N — …`).
-- Splitting a slice that grew too big: see CLAUDE.md §13 and the "How to split a
-  slice" section of `BACKLOG.md`.
-
-## Branches & commits
-
-- Trunk-based: short-lived branches off `main`, squash-merged. Never push to `main`.
-- Branch name: `<type>/<issue-number>-<slug>`, e.g. `feat/28-bff-health`.
-- Conventional Commits, each referencing its issue: `feat(bff): … (refs #28)`.
-- TDD order: the `test(...)` red commit precedes the `feat(...)` green commit.
-
-## Pull requests
-
-- Open with `tea pr create` (the Gitea CLI) or the web UI; the body uses
-  `.gitea/PULL_REQUEST_TEMPLATE.md` and its DoD checklist.
-- The merging PR closes its issue via `closes #NN` in the squash-commit body.
-  Work that isn't finished (e.g. CI green pending a runner) uses `refs #NN` and the
-  issue stays open.
-- A PR needs a linked issue. Don't open one without it.
-
-## CI gate
-
-Until a self-hosted `respellion-linux` runner is registered, `make ci` is the gate
-(it runs the same checks the workflow does). See [runbooks/ci.md](runbooks/ci.md).
-
-## CLI cheatsheet (`tea`)
-
-```bash
-tea issues list --state open          # backlog
-tea issue create --title "S-NN · …" --labels type:slice,area:bff --milestone "Iteration 1 — Walking Skeleton"
-tea pr create --base main --head <branch> --title "…" --description "… closes #NN"
-tea pr list                           # open PRs
-tea pr merge <n> --style squash       # merge (after review)
-```
-
-## Changelog & releases
-
-`CHANGELOG.md` is generated from commits by `git-cliff` (`make changelog`), refreshed
-on tag. Versioning is **CalVer** `YYYY.MM.PATCH`; releases are published via Gitea
-Releases.

docs/index.md

@@ -1,23 +0,0 @@
-# register-referentie
-
-A reference application demonstrating Respellion's Common Ground architecture
-pattern. Quality and architectural clarity over feature throughput — every commit
-should teach.
-
-## Where to go
-
-- **[Product Requirements](PRD.md)** — what we're building and why.
-- **[ADR-0001: Loose coupling](architecture/adr-0001-loose-coupling.md)** — the
-  non-negotiable integration stance; the template for future ADRs.
-- **[Working in Gitea](gitea-workflow.md)** — issues, milestones, branches, PRs.
-- **[CI runbook](runbooks/ci.md)** — the pipeline and the `make ci` local gate.
-
-## Quickstart
-
-See the repository `README.md`. In short: clone, then either run the checks with
-`make ci`, or bring the BFF up with
-`docker compose -f infra/docker-compose.yml up -d --build --wait` and
-`curl http://localhost:8080/health`.
-
-> This site is built with MkDocs Material (`mkdocs build`). It grows with the
-> backlog; sections appear as their slices land.

mkdocs.yml

@@ -1,41 +0,0 @@
-site_name: register-referentie
-site_description: Reference application for Respellion's Common Ground architecture pattern
-docs_dir: docs
-
-theme:
-  name: material
-  features:
-    - navigation.sections
-    - navigation.top
-    - content.code.copy
-  palette:
-    - scheme: default
-      toggle:
-        icon: material/brightness-7
-        name: Switch to dark mode
-    - scheme: slate
-      toggle:
-        icon: material/brightness-4
-        name: Switch to light mode
-
-nav:
-  - Home: index.md
-  - Product Requirements: PRD.md
-  - Architecture:
-      - "ADR-0001: Loose coupling": architecture/adr-0001-loose-coupling.md
-  - Working in Gitea: gitea-workflow.md
-  - Runbooks:
-      - CI: runbooks/ci.md
-
-markdown_extensions:
-  - admonition
-  - toc:
-      permalink: true
-  - pymdownx.superfences
-
-# Many docs referenced by PRD.md land in later slices; don't fail the build on them.
-validation:
-  nav:
-    omitted_files: warn
-  links:
-    not_found: warn