docs: translate repo content to English

.github/engineering-standards.yml

@@ -1,9 +1,9 @@
-# Engineering-Standards-Status dieses Repos.
-# Single source of truth, gilt host- und agent-übergreifend.
-# Schema: siehe byte5ai/engineering-standards.
+# Engineering-standards status of this repo.
+# Single source of truth, applies across hosts and agents.
+# Schema: see byte5ai/engineering-standards.
 
 status: applied          # applied | exempt
 source: byte5ai/engineering-standards
 decided_on: 2026-06-15
 reviewed_on: 2026-06-15
-reason: "Profil: Code-Repo (TS-Plugin-Bündel, siehe plan.md §4). Heute Docs-only; CI wächst mit Phase 0."
+reason: "Profile: code repo (TS plugin bundle, see plan.md §4). Docs-only today; CI grows with Phase 0."

.github/workflows/ci.yml

@@ -15,8 +15,8 @@ jobs:
         with:
           node-version: "20"
 
-      # Code-Repo-Profil: baut/testet, sobald TS-Pakete existieren (Phase 0).
-      # Bis dahin ist der Job grün und validiert nur, dass das Repo konsistent ist.
+      # Code-repo profile: builds/tests once TS packages exist (Phase 0).
+      # Until then the job is green and only checks that the repo is consistent.
       - name: Build & test
         run: |
           if [ -f package.json ]; then
@@ -25,16 +25,16 @@ jobs:
             npm run build --if-present
             npm test
           else
-            echo "No TS packages yet (Stufe A / Phase 0 bootstrap) — nothing to build."
+            echo "No TS packages yet (Stage A / Phase 0 bootstrap) — nothing to build."
           fi
 
-      # Solange das Repo Docs-getragen ist, halten wir die zentralen Dokumente
-      # wenigstens auf balancierte Markdown-Code-Fences geprüft (deterministisch,
-      # dependency-frei). Verschwindet, wenn der Code-Test-Pfad oben greift.
+      # While the repo is docs-driven, at least keep the core documents checked
+      # for balanced Markdown code fences (deterministic, dependency-free).
+      # Goes away once the code-test path above kicks in.
       - name: Docs sanity (balanced code fences)
         run: |
           status=0
-          for f in plan.md research.md AGENTS.md CONTRIBUTING.md; do
+          for f in plan.md research.md AGENTS.md CONTRIBUTING.md README.md; do
             [ -f "$f" ] || continue
             fences=$(grep -c '^```' "$f" || true)
             if [ $((fences % 2)) -ne 0 ]; then

CONTRIBUTING.md

@@ -1,27 +1,27 @@
 # Contributing to omadia Proof
 
-`byte5ai/omadia-proof` ist das ANP-Proof-Plugin-Bündel für omadia. Kontext: [plan.md](plan.md) (Implementierungsplan, Codex-reviewed) und [research.md](research.md) (verifizierte Faktenbasis A1–A8). Die Arbeit ist als Issues in Milestones gruppiert (Stufe A + Phase 0–5).
+`byte5ai/omadia-proof` is the ANP-Proof plugin bundle for omadia. Context: [plan.md](plan.md) (the Codex-reviewed implementation plan) and [research.md](research.md) (the verified fact base, A1–A8). Work is tracked as issues grouped into milestones (Stage A + Phase 0–5).
 
-## Dev-Setup
+## Dev setup
 
 ```bash
-script/setup   # konfiguriert git-Hooks; installiert Dependencies, sobald Pakete existieren
+script/setup   # configures git hooks; installs dependencies once packages exist
 ```
 
 ## Workflow
 
-Dieses Repo folgt den byte5ai-Engineering-Standards (`.github/engineering-standards.yml`, Details in [AGENTS.md](AGENTS.md)).
+This repo follows the byte5ai engineering standards (`.github/engineering-standards.yml`, details in [AGENTS.md](AGENTS.md)).
 
-- **Nie im Haupt-Klon committen — immer ein Worktree:**
+- **Never commit in the main clone — use a worktree:**
   ```bash
   git worktree add ../omadia-proof-<feature> -b feat/<desc> main
   ```
-  Durchgesetzt durch `.hooks/pre-commit`. Nach Merge aufräumen: `git worktree remove …` + `git branch -D …` (oder `script/prune-worktrees`).
-- **Nie direkt auf `main` pushen.** Feature-Branch + PR; CI (`ci`) muss grün sein.
-- **Conventional Commits:** `feat:`, `fix:`, `docs:`, `chore:`, `refactor:`, `test:`, `release:`.
-- **Branch-Präfixe:** `feat/ fix/ refactor/ docs/ chore/ test/ release/ dev/`.
-- **Keine** `Co-Authored-By:`-Trailer (auch nicht für KI-Agenten). **Nie** `--no-verify`. **Nie** Secrets committen.
+  Enforced by `.hooks/pre-commit`. After merge, clean up: `git worktree remove …` + `git branch -D …` (or `script/prune-worktrees`).
+- **Never push directly to `main`.** Feature branch + PR; CI (`ci`) must be green.
+- **Conventional commits:** `feat:`, `fix:`, `docs:`, `chore:`, `refactor:`, `test:`, `release:`.
+- **Branch prefixes:** `feat/ fix/ refactor/ docs/ chore/ test/ release/ dev/`.
+- **No** `Co-Authored-By:` trailers (including for AI agents). **Never** `--no-verify`. **Never** commit secrets.
 
-## Schema-Backflow (zwingend)
+## Schema backflow (mandatory)
 
-Jede Änderung, die ein ANP-Object-/VC-Schema definiert oder ändert, **MUSS** in derselben Arbeitseinheit einen PR gegen `byte5ai/anp` (Appendix A) eröffnen — siehe [plan.md §1.4](plan.md) und [#2](https://github.com/byte5ai/omadia-proof/issues/2). Der RFC ist kanonisch; bei Divergenz gewinnt die SPEC.
+Any change that defines or alters an ANP object/VC schema **MUST** open a matching PR against `byte5ai/anp` (Appendix A) in the same unit of work — see [plan.md §1.4](plan.md) and [#2](https://github.com/byte5ai/omadia-proof/issues/2). The RFC is canonical; on divergence, the SPEC wins.