werkregie/doc/prs/2026-10-14-PR#77-demo-author.md

PR#77: The Demo Shows the Author Session of Its Stuck Pull Request

WARNING: This document describes only the change applied in this PR. It may already be outdated once the next PR is merged. Historic PR documentation is not maintained along with new PRs; treat it as a snapshot.

Related Links

• werkregie PR#74, which shows the author session of a stuck agent pull request.

Problem

Since werkregie PR#74, "Du bist dran" shows the session that last worked on the branch of a stuck pull request. The public demo on werkregie.javagil.de does not show it, since its pull request in conflict has no author session. PR#74 left Demo.kt unchanged, because Demo.snapshot is above a Mutation-CRAP of 15.

Non-Goals

• No change of the real dashboard.

Specification

Feature: the demo shows the author session of its stuck pull request

Scenario#77.01: the demo's pull request in conflict has an author session

… so that a visitor sees what "Du bist dran" offers for a stuck pull request.

• Given the demo without the access token
• When the visitor opens "Du bist dran"
• Then the pull request in conflict shows its author session and the message for it

Verified by

• DemoTest "the demo's pull request in conflict shows its author session and the message for it"

Solution

• The demo's pull request #215 in conflict gets an author session, as the relay of the laptop would report it, attached by Authors.attach as on the real dashboard; it has no link, since its session exists in no Claude Desktop.
• Demo.snapshot (complexity 20) is split into items, sources, loads and costs, each at most 4.
• DemoTest checks the snapshot: its items and sources, the author session, the load charts and the costs.
• Version 0.48.0.

Open Questions

None.

Additional Changes

• The plan sets #orch.author to deployed: Werkator deploys the server after the merge, and the relay of think runs 0.47.0 since 2026-10-14.