feat: slice 1 - the neckbeard framework chain runs end to end

Tracer bullet of the migration design (Gate 4, slice 1): pinned v0.1.1
baseline under docs/sources/upstream/ with provenance note, the
Karpathy block moved verbatim to docs/sources/regelwerk/ (standing
rule mapped onto the sources read-only mechanism), AGENTS.md assembled
from the byte-true upstream sections plus the project section 6
(group rules condensed from the old CLAUDE.md), CLAUDE.md reduced to
the upstream pointer, WORKFLOW.md and all four templates copied,
schema.yaml extended (issue milestone/priority/status columns,
component type, wiki area vision - all flagged in the header),
validate.py and gen_status.py forked with marked extensions,
pruefe_upstream_drift.py added, STATUS.md generated, CI gains the
offline validate job, README directory link defused.

Verified: validate 0 errors 0 warnings (the three pre-existing
directory-link errors are gone), gen_status --check current,
drift check 0 findings, baseline byte-identical to the reference
checkout (10/10 files), four negative tests fire (WIP limit 3x
in-progress, waiting without wartegrund, component slug mismatch,
single-byte drift in WORKFLOW.md). gen_status needs Python >= 3.10
locally (write_text newline) - noted for the design AAR.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This commit is contained in:
Thore Cimbal
2026-08-11 12:00:00 +00:00
co-authored by Claude Fable 5
parent 5e46372ea8
commit e36ed337a7
27 changed files with 2311 additions and 235 deletions
+34
View File
@@ -0,0 +1,34 @@
---
type: aar
status: open # open | harvested
date: YYYY-MM-DD
related: [] # design docs, issues, ADRs involved
---
<!-- Copy to docs/aar/YYYY-MM-DD-slug.md. Delete comments when filling in.
Standalone AARs are for incidents and major deviations only —
normal undertakings get their AAR as Gate 5 inside the design doc. -->
# AAR: Title
## What was planned / expected
## What happened
<!-- Facts and timeline, not blame. -->
## Why the difference
<!-- Root cause. For failures, name the routing class:
intent issue / spec issue / code issue. -->
## Learnings
<!-- What future-you should know. Blunt beats polite. -->
## Actions
<!-- Concrete: wiki pages updated (FAQ, Stolpersteine) with links,
framework issues opened, tests added. When all actions are done,
set status: harvested. The refinement session walks all AARs
still marked open. -->