Skip to content

chore(release): v0.1.0 – pilot scope #86

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Fluory merged 3 commits into from
Sep 28, 2026
Merged

chore(release): v0.1.0 – pilot scope #86

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
b88809d
chore(release): v0.1.0 – cut the changelog and install the release skill
Fluory Sep 27, 2026
af9bd7c
Merge remote-tracking branch 'origin/main' into claude/chore-release-…
Fluory Sep 27, 2026
32e483f
Merge remote-tracking branch 'origin/main' into claude/chore-release-…
Fluory Sep 28, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
29 changes: 29 additions & 0 deletions .claude/skills/release/SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,29 @@
---
name: release
description: Prüft die Release-Bereitschaft vor einer Auslieferung. Verwenden bei "Release vorbereiten", "Können wir v1.2.0 ausliefern?" in Projekten mit Releases-Add-on. Ein Release gibt immer ein Mensch frei.
---

# /release – vom Merge zum kontrollierten Release

## Prüft

- Version korrekt (SemVer), Tag geplant?
- CHANGELOG vollständig – nur was Nutzer/Betreiber wissen müssen?
- CI grün auf dem Release-Stand?
- Migrationen geprüft (/database-migration gelaufen)?
- Offene `security`- oder `decision-needed`-Issues?
- Rollback-Weg vorhanden und geprobt?
- Staging-Smoke-Test bestanden?
- Monitoring/Alerts bereit; Monitoring-Check nach Deploy eingeplant?

## Ergebnisformat

```
Version: vX.Y.Z · Status: ready | blocked
Bestanden: … · Offen: … · Freigabe benötigt: Orchestrator (immer)
```

## Grenzen

- Deployt nie selbst; erstellt Tag/Release erst nach dokumentierter menschlicher Freigabe.
- `blocked` wird nie schöngeredet – ein offener Punkt ist ein offener Punkt.
2 changes: 1 addition & 1 deletion AGENTS.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -67,7 +67,7 @@ Stages: this card + issue → PR diff + module + tests → neighbouring interfac

## Skill register (load on demand – not everything up front)

Installed in `.claude/skills/` (core, always): **start-work · finish-work · review-pr · plan-issue**.
Installed in `.claude/skills/` (core, always): **start-work · finish-work · review-pr · plan-issue**; installed on trigger: **release** (v0.1.0).
Others exist as templates in `Entwicklungsplan/templates/skills/` and are installed once their trigger occurs:
`project-start`/`project-plan`/`setup-project` (founding: discovery → plan → setup after approval) · `architecture-decision` · `legacy-audit` · `refactor-module` · `security-review` (from P1) ·
`ai-eval` (AI/RAG) · `database-migration` (DB) · `infra-change` (infra) · `observability`/`incident` (operations) ·
Expand Down
6 changes: 6 additions & 0 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,6 +5,12 @@ This file records what changes **in the product** – process and session state

## [Unreleased]

## [0.1.0] – 2026-09-27

First release: the pilot scope – intake of e-mail and PDF/Excel/Word, AI extraction with sources and
uncertainty, review with corrections, exactly-once ERP export, multi-tenancy, audit trail and the public
showcase with prepared samples.

### Added
- Prepared samples for the showcase (`pnpm seed:samples`): per demo company one synthetic request to review
(with an uncertain and a missing value) and one already approved and exported through the normal path. Their
Expand Down
Loading