werkator

Files

T

mhoennigandClaude Fable 5 7a24ad1d7f Step 23 refined: init takes a YAML fragment in the config schema

Refinement decided 2026-09-01: each side gets its native format — the
wrapper keeps a bash-sourceable transport env file, Werkator takes a
YAML fragment in its own config schema via 'init --apply FILE',
deep-merged idempotently. The env-to-config mapping table disappears
entirely: the fragment IS configuration in the one schema, validated by
the existing binding, documented by the existing reference. The env
file names the fragment (WERKATOR_INIT_CONFIG), keeping one entry point
per instance.

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

2026-09-01 18:32:29 +02:00

adrs

Step 21 session A: close step 17's paperwork

2026-09-01 06:21:29 +02:00

examples

Renaming gitTally to Werkator because there is another git-related tool named gittally (#1 )

2026-08-31 13:32:54 +02:00

plan

Step 23 refined: init takes a YAML fragment in the config schema

2026-09-01 18:32:29 +02:00

prs

PR-doc: step 22 moved to its own branch