release-baseline

/release-baseline – Set project state as baseline

Makes a "cut" after a release: project state is documented as given, HANDOVER is archived and summarized, docs are split into Frozen/Active.

Argument: $ARGUMENTS = [Release version, e.g. "v1.0.0"]

Prerequisites

• Gate-P7 Go or explicit user request

Execution

1. Read prep report

Read docs/.baseline-prep.md (created via baseline.sh). If not present or older than 10 min: inform the user that ~/.claude/scripts/baseline.sh [version] [projectdir] should be run first.

2. Create BASELINE.md

Create docs/BASELINE.md:

# Baseline: [Version]

**Release**: [Version]
**Date**: [DD.MM.YYYY]
**Status**: [e.g. MVP completed, all gates P0-P7 passed]

## Project State Summary
[Take HANDOVER summary from prep report. If not available: summarize from HANDOVER.md yourself (max. 10 sentences)]

## Core Architecture
[3-5 sentences from docs/architecture/ARCHITECTURE.md – architecture style, main components, deployment model]

## Tech Stack
[Bullet points from .claude/CLAUDE.md or docs/architecture/TECH_STACK.md]

## Completed Milestones
[Table from docs/planning/PROJECT_PLAN.md – completed milestones only]

## Important Decisions
[Take from .claude/CLAUDE.md "Important Decisions" table]

3. Update project CLAUDE.md

Add a "Baseline" section after "Current Phase" (before "Project goals"):

## Baseline
**Release**: [Version] ([Date])
**Status**: [e.g. MVP completed, all gates P0-P7 passed]

### Frozen Docs (read only when needed)
- docs/discovery/ (P0)
- docs/concept/ (P1)
- docs/validation/ (P2)
- docs/architecture/ (P3)
- docs/planning/PROJECT_PLAN.md (milestones)

### Active Docs (at every session start)
- docs/HANDOVER.md (Handover)
- docs/BASELINE.md (reference)
- docs/planning/BACKLOG.md (current work)
- docs/planning/SPRINT.md (current sprint)

If a Baseline section already exists: update it (version, date, status).

4. Reset HANDOVER.md

Before creating the fresh file, scan the current docs/HANDOVER.md for inbox entries: lines matching commands/cleanup.md §1's marker pattern (grep -c '^- INBOX [|]' docs/HANDOVER.md). baseline.sh already copies the whole file into the archive (see prep report), so this step is not the rescue — it is what keeps an untriaged finding in the triage loop instead of letting it go quiet inside the archive: a release cut is not a triage decision and must not silently drop the finding on the reader's behalf. A blocking guard would not help here either (the file is archived either way, and a guard that holds up a release just gets bypassed) — carry the entries forward instead.