mi/werkator
1
0
Fork 0
Code Issues Pull Requests 1 Actions Packages Projects Releases Wiki Activity

Point the legacy references at the history

Browse Source 
`legacy/gitTally` was removed from the tree with the rename, but the
README still described it as a reference kept in the repository, and the
plan told an executing session to read parts of it — including step 14,
which is open.

The README section is gone; `docs/plan/README.md`, step 14 and the
legacy analysis now say where the script actually is
(`git show 7f55068^:legacy/gitTally`). Executed steps and ADR 0004 keep
their wording: they record what was true when they ran.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
mhoennig
2026-08-31 07:23:56 +02:00
co-authored by Claude Opus 5
parent 3c65819954
commit 56fd39f1ad
4 changed files with 6 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
-5
View File
@@ -8,11 +8,6 @@ Lightweight, declarative and highly opinionated software build system (CI/CD).
- [docs/bootstrapping.md](docs/bootstrapping.md) — initializing a repository with `init`
- [docs/deployment.md](docs/deployment.md) — running Werkator as a systemd service behind a reverse proxy
## Legacy Script
`legacy/werkator` (bash) is **deprecated** and kept only as a behavioral reference for the rewrite.
Do not use it for new installations.
## Developer Setup
Source `.envrc` to add `tools/` to your `PATH`, or install [direnv](#direnv) to have this done automatically on `cd`:
docs/plan/00-legacy-analysis.md
+2 -1
View File
@@ -1,6 +1,7 @@
# Legacy Werkator Analysis
Condensed analysis of `legacy/werkator` (bash, ~6000 lines) as input for the rewrite.
Condensed analysis of the legacy bash script (~6000 lines) as input for the rewrite.
The script was removed from the tree with the rename to Werkator; its last state is `git show 7f55068^:legacy/gitTally`.
Line numbers refer to the legacy script at the time of analysis (version 0.7.8).
## What the Legacy System Does
docs/plan/14-build-phase-timing-and-overhead.md
+1 -1
View File
@@ -1,7 +1,7 @@
# Step 14: Build-Phase Timing and Orchestration Overhead
Prerequisites: steps 04 (build executor), 05 (artifact store), 07 (API), 08 (web UI), 11 (Docker runtime).
Read `README.md` first; read the referenced `legacy/werkator` functions only where this step points at them.
Read `README.md` first; read the referenced legacy functions only where this step points at them — the script lives in the history now, see `README.md`.
## Goal
docs/plan/README.md
+3 -2
View File
@@ -1,6 +1,6 @@
# Werkator Rewrite Plan
This directory contains the step-by-step plan for rewriting `legacy/werkator` (bash) as the Kotlin/Spring application in this repository.
This directory contains the step-by-step plan for rewriting the legacy bash script as the Kotlin/Spring application in this repository.
Each step file is self-contained and sized for one focused Claude Code session.
## How to Execute a Step
@@ -9,7 +9,8 @@ Start a fresh Claude Code session and prompt, for example: "Execute docs/plan/01
The executing session should:
1. Read this file, `00-legacy-analysis.md`, and the step file.
2. Read the referenced parts of `legacy/werkator` only if the step file says so.
2. Read the referenced parts of the legacy bash script only if the step file says so.
It was removed from the tree with the rename to Werkator; its last state is `git show 7f55068^:legacy/gitTally`, and `00-legacy-analysis.md` condenses it.
3. Implement with tests, following `CLAUDE.md` conventions.
4. Run `./gradlew ktlintFormat` and then `./gradlew build` until green.
5. Update the step's checkbox below and note deviations inside the step file.