enricobuehlerandClaude Fable 5 59ef285f08 process: the PR template asks whether a user-facing fact changed, and the release flow gets a docs-freshness step ...

WP5 of the docs-and-onboarding overhaul, the two riders the RFC attaches to WP2–WP4:

- .gitea/PULL_REQUEST_TEMPLATE.md — one question: did a user-facing fact change, and is the
  docs-site page that owns it updated in this PR (install/repo/port facts in data/platforms.json).
  CI's docs-drift only catches the mechanical half; this is the reminder for the rest.
- docs/releases/README.md step 1 — while the release diff is in front of you, check docs freshness,
  and if platforms.json changed, run `bun run sync-platforms` in punktfunk-website and commit,
  because the download page vendors that file and only refreshes when someone does.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

2026-08-19 21:01:00 +02:00

..

agents

docs(agents): AGENTS.md — where the issues live, what the labels mean, which docs to read first

2026-08-18 21:31:48 +02:00

releases

process: the PR template asks whether a user-facing fact changed, and the release flow gets a docs-freshness step

2026-08-19 21:01:00 +02:00

embedding-the-c-abi.md

feat(core): ABI v25 — punktfunk_set_log_callback, so the Apple client hears the core's log lines

2026-08-19 18:33:59 +02:00