chore(governance): merge-Gate im Run-Ledger auf den Tatsachenstand bringen

[DYAI2025]

Eine Zeile im Run-Ledger, plus die Begründung, was nicht angefasst wurde.

Der Befund

Der Ledger führte merge als PENDING, obwohl PR #78 gemergt ist (1f41354, CI grün am exakten Head b52fcd0, Run 32412284034). Das war die letzte Stelle, an der GitHub und Run-Ledger auseinanderliefen — die Zielvorgabe verlangt beide als reconciled.

Was bewusst NICHT geändert wurde

deploy und production-verification bleiben PENDING. Das ist der zutreffende Wert: sie haben nicht stattgefunden. Ein Statuswert BLOCKED wäre eine Erfindung — der Ledger kennt in seiner ganzen Historie genau zwei Werte, und im Repo liest ihn kein Skript, also könnte ein dritter einen Konsumenten brechen, den ich nicht sehe. Der Grund für das Ausbleiben gehört in Prosa und steht in docs/plans/2026-08-20-sprint-6-staging-blocker.md.

Das Sechs-Schlüssel-Schema. Kein zusätzliches blocker-Feld, aus demselben Grund.

Zum artifact_hash

Die drei alten Einträge (merge, deploy, production-verification) trugen 0705ee2c…. Dieser Wert ist heute nicht reproduzierbar — keine Datei im Baum hasht darauf, die Quelldatei hat sich seither geändert.

Ihn abzuschreiben hätte eine Herkunft behauptet, die ich nicht prüfen kann. Der neue Eintrag hasht stattdessen die Plandatei docs/plans/2026-08-18-eyt-140-planungswerkbank.md — dieselbe Konvention, die die Implementierungs-Gates m6/m7/m9 bereits verwenden (af5e61df…, gegengeprüft).

Nachgeprüft nach dem Nachtrag

Schluesselmenge:  artifact_hash at feature gate repo status   (sechs, unveraendert)
Statuswerte:      CLEARED, PENDING                            (unveraendert)
merge:            PENDING → CLEARED
deploy:           PENDING  (unveraendert, zutreffend)
production-verification: PENDING  (unveraendert, zutreffend)

🤖 Generated with Claude Code

Summary by Sourcery

Reconcile the run ledger’s merge status with the verified merged state without changing unexecuted deployment stages.

Bug Fixes:

• Reconcile the run ledger with the merged GitHub state by marking the merge gate as CLEARED and recording a verifiable artifact hash.

Chores:

• Leave deploy and production-verification pending because those stages did not run, while preserving the existing six-key schema and status values.

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

This PR updates a single run-ledger entry to correctly reflect that PR #78 has been merged, keeps deploy and production-verification as PENDING for explicit business reasons, and adjusts the artifact_hash to use a verifiable plan document consistent with existing feature gate conventions.

File-Level Changes

Change	Details	Files
Correct the run-ledger record for sprint 6 so merge is reconciled with GitHub and artifact hashing follows the established plan-document convention while deploy-related gates remain pending.	Update the merge gate status from PENDING to CLEARED to match the merged state of PR feat(EYT-140): Planungswerkbank und Wochennavigation — Slice 1, Draft für CI-Evidenz #78 and the corresponding CI run. Leave deploy and production-verification gate statuses as PENDING to accurately represent that they never occurred, avoiding introduction of new status values or fields. Change the artifact_hash for the new merge ledger entry to reference the current plan document that can be reproduced and matches other implementation gates, instead of reusing a non-reproducible historical hash.	docs/context/easytree-sprint-6-core-journey.run-ledger.jsonl

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey - I've reviewed your changes and they look great!

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}