heinzel-github 0.9.1__tar.gz → 0.9.2__tar.gz

heinzel_github-0.9.2/CHANGELOG.md

@@ -0,0 +1,14 @@
+# Changelog
+
+## 0.9.2
+
+Add a GitHub release feed for draft workflows. It starts at the current release frontier and reads published
+release notes alongside the matching section of the supplied CHANGELOG. It stops without advancing the cursor
+when a release cannot be matched or the bounded GitHub page may hide releases. Requires Heinzel 0.9.16 or newer.
+
+## 0.9.1
+
+Move this plugin to its independent repository project for the Heinzel 0.9.1 plugin contract.
+Own its dependencies, tests and artifacts; consume public contracts without concrete provider dependencies.
+
+Earlier history: the heinzel repository before 0.9.

{heinzel_github-0.9.1 → heinzel_github-0.9.2}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: heinzel-github
-Version: 0.9.1
+Version: 0.9.2
 Summary: Read pull requests and issues from GitHub: the code-host and tracker capabilities.
 Project-URL: Source, https://github.com/helmut-hoffer-von-ankershoffen/heinzel-plugins/tree/main/plugins/heinzel-github
 Project-URL: Changelog, https://github.com/helmut-hoffer-von-ankershoffen/heinzel-plugins/blob/main/plugins/heinzel-github/CHANGELOG.md
@@ -8,16 +8,18 @@ Project-URL: Issues, https://github.com/helmut-hoffer-von-ankershoffen/heinzel-p
 License-Expression: MIT
 License-File: LICENSE
 Requires-Python: >=3.12
-Requires-Dist: heinzel<0.10,>=0.9.1
+Requires-Dist: heinzel<0.10,>=0.9.16
 Description-Content-Type: text/markdown
 
 # heinzel-github
 
 Read pull requests and issues from GitHub, the `code-host` and `tracker` capabilities ([ADR 0028](https://github.com/helmut-hoffer-von-ankershoffen/heinzel/blob/main/docs/adr/0028-integrations-are-capability-adapters.md)): a first-party
-[Heinzelmännchen](https://github.com/helmut-hoffer-von-ankershoffen/heinzel) plugin. It is independently released and installed explicitly:
+[Heinzelmännchen](https://github.com/helmut-hoffer-von-ankershoffen/heinzel) plugin.
+
+Install it with:
 
 ```bash
-hz system plugin add github --confirm             # a compatible plugin release; run it again to upgrade
+hz system plugin add github --confirm
 hz system plugin remove heinzel-github
 ```
 
@@ -134,4 +136,49 @@ returns is cleaned too.
 
 Development and release commands: [repository guide](../../README.md).
 
-Migration provenance: heinzel, before the 0.9 plugin-boundary migration.
+
+<!-- screenshots:start -->
+## Screenshots
+
+<img src="docs/assets/screenshots/workflow-collection.png" alt="Explore the fictional weekly code review in the local workflow collection" width="960">
+
+Explore the fictional weekly code review in the local workflow collection
+
+<img src="docs/assets/screenshots/workflow-context.png" alt="Fictional weekly review declares merged-work and issue inputs; no report was generated" width="960">
+
+Fictional weekly review declares merged-work and issue inputs; no report was generated
+
+<img src="docs/assets/screenshots/merged-work.png" alt="Fictional merged pull requests in the app terminal, using a fixture-only requester and the real adapter" width="960">
+
+Fictional merged pull requests in the app terminal, using a fixture-only requester and the real adapter
+
+<img src="docs/assets/screenshots/issue-changes.png" alt="Fictional issue changes, owners and states in the app terminal, using a fixture-only requester" width="960">
+
+Fictional issue changes, owners and states in the app terminal, using a fixture-only requester
+
+<details>
+<summary>Command line</summary>
+
+<img src="docs/assets/screenshots/merged-cli.png" alt="Read fictional merged work in the shell with a fixture-only requester and the real adapter" width="960">
+
+Read fictional merged work in the shell with a fixture-only requester and the real adapter
+
+<img src="docs/assets/screenshots/issues-json.png" alt="Fictional issue results as JSON for scripts and agents, using a fixture-only requester" width="960">
+
+Fictional issue results as JSON for scripts and agents, using a fixture-only requester
+
+</details>
+
+[Open the screenshot gallery](docs/assets/screenshots/index.html).
+<!-- screenshots:end -->
+
+### Release feed for draft workflows
+
+With Heinzel 0.9.16 or newer, the GitHub plugin installed from a wheel can supply a release feed to a draft workflow. Give the
+workflow an exact HTTPS GitHub blob URL for the Markdown CHANGELOG. The feed reads the same repository's published
+release notes and the matching literal CHANGELOG section. It starts from the current release frontier and returns
+later releases in publication order.
+
+An ambiguous tag, a lost frontier, or a full GitHub page of 100 entries including drafts stops the read without
+advancing the cursor. The feed uses `gh` and holds the selected credential privately for the read. It never stores
+or displays the token. Changing the selected account, configuration, or executable requires a new review.

{heinzel_github-0.9.1 → heinzel_github-0.9.2}/README.md

@@ -1,10 +1,12 @@
 # heinzel-github
 
 Read pull requests and issues from GitHub, the `code-host` and `tracker` capabilities ([ADR 0028](https://github.com/helmut-hoffer-von-ankershoffen/heinzel/blob/main/docs/adr/0028-integrations-are-capability-adapters.md)): a first-party
-[Heinzelmännchen](https://github.com/helmut-hoffer-von-ankershoffen/heinzel) plugin. It is independently released and installed explicitly:
+[Heinzelmännchen](https://github.com/helmut-hoffer-von-ankershoffen/heinzel) plugin.
+
+Install it with:
 
 ```bash
-hz system plugin add github --confirm             # a compatible plugin release; run it again to upgrade
+hz system plugin add github --confirm
 hz system plugin remove heinzel-github
 ```
 
@@ -121,4 +123,49 @@ returns is cleaned too.
 
 Development and release commands: [repository guide](../../README.md).
 
-Migration provenance: heinzel, before the 0.9 plugin-boundary migration.
+
+<!-- screenshots:start -->
+## Screenshots
+
+<img src="docs/assets/screenshots/workflow-collection.png" alt="Explore the fictional weekly code review in the local workflow collection" width="960">
+
+Explore the fictional weekly code review in the local workflow collection
+
+<img src="docs/assets/screenshots/workflow-context.png" alt="Fictional weekly review declares merged-work and issue inputs; no report was generated" width="960">
+
+Fictional weekly review declares merged-work and issue inputs; no report was generated
+
+<img src="docs/assets/screenshots/merged-work.png" alt="Fictional merged pull requests in the app terminal, using a fixture-only requester and the real adapter" width="960">
+
+Fictional merged pull requests in the app terminal, using a fixture-only requester and the real adapter
+
+<img src="docs/assets/screenshots/issue-changes.png" alt="Fictional issue changes, owners and states in the app terminal, using a fixture-only requester" width="960">
+
+Fictional issue changes, owners and states in the app terminal, using a fixture-only requester
+
+<details>
+<summary>Command line</summary>
+
+<img src="docs/assets/screenshots/merged-cli.png" alt="Read fictional merged work in the shell with a fixture-only requester and the real adapter" width="960">
+
+Read fictional merged work in the shell with a fixture-only requester and the real adapter
+
+<img src="docs/assets/screenshots/issues-json.png" alt="Fictional issue results as JSON for scripts and agents, using a fixture-only requester" width="960">
+
+Fictional issue results as JSON for scripts and agents, using a fixture-only requester
+
+</details>
+
+[Open the screenshot gallery](docs/assets/screenshots/index.html).
+<!-- screenshots:end -->
+
+### Release feed for draft workflows
+
+With Heinzel 0.9.16 or newer, the GitHub plugin installed from a wheel can supply a release feed to a draft workflow. Give the
+workflow an exact HTTPS GitHub blob URL for the Markdown CHANGELOG. The feed reads the same repository's published
+release notes and the matching literal CHANGELOG section. It starts from the current release frontier and returns
+later releases in publication order.
+
+An ambiguous tag, a lost frontier, or a full GitHub page of 100 entries including drafts stops the read without
+advancing the cursor. The feed uses `gh` and holds the selected credential privately for the read. It never stores
+or displays the token. Changing the selected account, configuration, or executable requires a new review.

heinzel_github-0.9.2/docs/SCREENSHOTS.md

@@ -0,0 +1,10 @@
+# Screenshot gallery
+
+From the collection root, run `make screenshots NAME=heinzel-github OPEN=1`.
+Review the [contact sheet](assets/screenshots/index.html) before committing.
+The [scene plan](screenshots.toml) describes the real UI and CLI captures.
+`make screenshots-check NAME=heinzel-github` verifies freshness offline.
+
+Captures use a temporary fictional profile without connected accounts. The generated
+[manifest](assets/screenshots/capture.json) records the SDK version and input/image digests.
+See the [author guide](../../../docs/SCREENSHOT_AUTHORING.md) for human and agent commands.

heinzel_github-0.9.2/docs/SCREENSHOT_STORY.md

@@ -0,0 +1,40 @@
+## Audience and outcome
+
+A developer or team lead considering a GitHub connector should see how a local workflow can declare both merged pull requests and updated issues as inputs, and what those reads return. The story should make clear that the example is fictional, the workflow is only declared, and no review report has been generated.
+
+## Scenes
+
+1. **Workflow collection, light:** Find the fictional Weekly code review alongside local workflows. This establishes where the example is discovered.
+2. **Workflow context, dark:** Inspect the same workflow’s distinct detail state: its two capability inputs, repository, and intended output. It is a declaration, not a completed review.
+3. **Merged work, app terminal:** Show the fictional merged pull requests returned by the real adapter through the fixture-only requester.
+4. **Issue changes, app terminal:** Show fictional issue titles, states, and owners; the adapter excludes pull requests from issue results.
+5. **Merged work, CLI:** Show the same useful read in a native terminal, identifying the requester as demonstration-only.
+6. **Issues as JSON, CLI:** Show a different capability and output format for scripts, with fictional data.
+
+The first two are Core feature UI scenes with different purposes; the app-terminal scenes are terminal results within the app, not feature UI. The existing plan already expresses this story and is preserved below. Its routes and rendered results still require capture-time verification.
+
+## Fictional fixtures
+
+`docs/screenshot_fixture.py` creates the local Weekly code review contract in isolated state, binds both capabilities to GitHub, and supplies `DemoGh` responses for `acme/widgets`. Its `showcase.merged` and `showcase.issues` operations use the real adapter with October 2026 fixture responses. The names, repository, accounts, PRs, issues, and links are example data; they are not evidence of a real GitHub connection. The fixture’s fixed window and `browser_time` make the story coherent. Some raw fixture records reuse an API URL or ID despite differing displayed numbers; do not present those raw fields as consistent production records.
+
+## Source-bound UI surface inventory
+
+- `pyproject.toml` declares both `heinzel.modules` and `heinzel.connected_sources` entrypoints as `github = "heinzel_github"`. Their target, `src/heinzel_github/__init__.py`, configures the module, settings, services, skill, two read capability providers, `info` operation, system-info contribution, and offline and live health contributions. The connected-source entrypoint points to that same package; the supplied source does not independently establish a separate connector screen or its exact rendering.
+- `src/heinzel_github/_module.py` declares the GitHub module. `src/heinzel_github/_adapter.py` implements merged pull-request and updated-issue reads. No plugin-specific Page, View, navigation, channel, approval, setup, or footer declaration appears in the supplied plugin source. That absence alone does not rule out Core-rendered UI.
+- `README.md` explicitly describes Core Settings → Connectors, connector list/test, system capability list, system info, and doctor. `src/heinzel_github/__init__.py` and `_service.py` provide the info and health data those generic surfaces may render; exact routes and visual controls are not established by these sources. The live test contacts GitHub when explicitly run, so it is outside this offline fixture story.
+- `docs/screenshot_fixture.py` contributes the fictional workflow and two fixture-only operations. `docs/screenshots.toml` declares `/contracts` and `/contracts/weekly-code-review` for collection and detail captures. These are Core workflow surfaces, not GitHub-owned screens; the provided plan is evidence of the intended detail route, not proof that it currently renders. If capture cannot verify it, do not substitute invented HTML or an assumed route.
+- `src/heinzel_github/__init__.py` conditionally registers `GithubReleaseFeeds` from `src/heinzel_github/_release_feed.py`; `README.md` describes its draft-workflow release-feed use. The supplied fixture does not demonstrate that flow or establish its UI, so no release-feed screenshot is claimed.
+- GitHub and `gh auth login` are external provider tools. The app-terminal and native CLI outputs are terminal surfaces. The `review-pull-request` skill declared in `src/heinzel_github/skills/review-pull-request/SKILL.md` is agent guidance, not an evidenced product screen. The existence of the `info` CLI operation does not prove it is terminal-only.
+
+## Privacy pitfalls
+
+Normal presentation fictionalization is limited to these explicit mappings: verified owning-interpreter paths become `/demo-profile/.venv`, and only the verified whole hostname detail in the genuine Doctor row becomes `demo-host`. These mappings change no SDK health status or remaining detail and establish no privacy acceptance. Unknown identities still fail, and an independent reviewer must inspect every image and transcript. Review account names, paths, hostnames, URLs, environment-derived details, tokens, logs, browser chrome, and unrelated background content; fixture labels alone do not establish privacy. Do not run the live connector test during this offline story.
+
+## Acceptance criteria
+
+- Capture the two genuine Core workflow states in applied light and dark appearances, plus the distinct app-terminal and native CLI results. Verify actual routes, headings, and data during capture; do not treat this source review as a successful capture.
+- The collection and detail must show meaningfully different states. Reject duplicate images, caption-only changes, terminal output represented as feature UI, and forged HTML.
+- Verify the merged results and issue results against the fixture and adapter, including exclusion of the PR-shaped issue; show JSON only if it is the actual CLI output. Clearly label the fixture-only requester and fictional data.
+- Do not imply that the declared workflow ran, that a report exists, or that the fixture proves a live GitHub login or production health.
+- Inspect every image and transcript independently for privacy and truthful presentation before publication. Only the narrowly specified path and Doctor-host mappings are permitted; unknown identities fail review.
+- The TOML below was checked against the requested structure by inspection only. No parser, fixture, application, capture, network call, or source code was executed, so runtime route, theme, and output validation remains outstanding.

heinzel_github-0.9.2/docs/assets/screenshots/capture.json

@@ -0,0 +1,102 @@
+{
+  "format": 1,
+  "plugin": "heinzel-github",
+  "core_version": "0.9.18",
+  "inputs_sha256": "332ffc4a251d426fc1e01dc6295a91357db2114443b33d63d63fe1b6936f9fe9",
+  "images": {
+    "docs/assets/screenshots/workflow-collection.png": "9a2115fd574e4b823feb72bede3c0cc747b9402990a7a3f67294a68767adc474",
+    "docs/assets/screenshots/workflow-context.png": "82139ef90338ac3320a0983c79d6132c24d1888a556182af06adde5fec5f217b",
+    "docs/assets/screenshots/merged-work.png": "8ff2207ebeaaae52e02d3718867d056fa8b2de5410e3ca885598c568ab0af79e",
+    "docs/assets/screenshots/issue-changes.png": "5e5cd61862c5982db2102d6d691e80161462915ff0d985438bb8b2550ee286e0",
+    "docs/assets/screenshots/merged-cli.png": "787d4a4a73a860dbf4b33fd849f9737e0a58e5495e3e94ea1104a0e60bdf7233",
+    "docs/assets/screenshots/issues-json.png": "ba32601ae9d5cbf3c0925b64388c8786141602e603d5343e8e03efd6365d52bd"
+  },
+  "review_bundle": {
+    "format": 2,
+    "source_story": {
+      "path": "source-story.md",
+      "sha256": "a419a4980b5369574d78f4b08c378dca67bdc84d904fb6bd0aebde2a19b80f00"
+    },
+    "definition": {
+      "format": 1,
+      "reviewer": "Codex feature-story agent",
+      "source_sha256": "0c55c663eadfffa985b01fda7f1a9778f22eb6fe9254f1c08f051a638b93aad6",
+      "plan_sha256": "9d204ce8608ed8eb229529b4fc0fa73fac29b39b2dd9e450b5b4a9f3f9fd55d7",
+      "story_sha256": "a419a4980b5369574d78f4b08c378dca67bdc84d904fb6bd0aebde2a19b80f00"
+    },
+    "plugin": "heinzel-github",
+    "core_version": "0.9.18",
+    "inputs_sha256": "332ffc4a251d426fc1e01dc6295a91357db2114443b33d63d63fe1b6936f9fe9",
+    "screenshots": [
+      {
+        "path": "docs/assets/screenshots/workflow-collection.png",
+        "surface": "ui",
+        "caption": "Explore the fictional weekly code review in the local workflow collection"
+      },
+      {
+        "path": "docs/assets/screenshots/workflow-context.png",
+        "surface": "ui",
+        "caption": "Fictional weekly review declares merged-work and issue inputs; no report was generated"
+      },
+      {
+        "path": "docs/assets/screenshots/merged-work.png",
+        "surface": "ui",
+        "caption": "Fictional merged pull requests in the app terminal, using a fixture-only requester and the real adapter"
+      },
+      {
+        "path": "docs/assets/screenshots/issue-changes.png",
+        "surface": "ui",
+        "caption": "Fictional issue changes, owners and states in the app terminal, using a fixture-only requester"
+      },
+      {
+        "path": "docs/assets/screenshots/merged-cli.png",
+        "surface": "cli",
+        "caption": "Read fictional merged work in the shell with a fixture-only requester and the real adapter"
+      },
+      {
+        "path": "docs/assets/screenshots/issues-json.png",
+        "surface": "cli",
+        "caption": "Fictional issue results as JSON for scripts and agents, using a fixture-only requester"
+      }
+    ],
+    "images": {
+      "workflow-collection.png": "9a2115fd574e4b823feb72bede3c0cc747b9402990a7a3f67294a68767adc474",
+      "workflow-context.png": "82139ef90338ac3320a0983c79d6132c24d1888a556182af06adde5fec5f217b",
+      "merged-work.png": "8ff2207ebeaaae52e02d3718867d056fa8b2de5410e3ca885598c568ab0af79e",
+      "issue-changes.png": "5e5cd61862c5982db2102d6d691e80161462915ff0d985438bb8b2550ee286e0",
+      "merged-cli.png": "787d4a4a73a860dbf4b33fd849f9737e0a58e5495e3e94ea1104a0e60bdf7233",
+      "issues-json.png": "ba32601ae9d5cbf3c0925b64388c8786141602e603d5343e8e03efd6365d52bd"
+    },
+    "transcripts": {
+      "workflow-collection.txt": "0efdfa3a76168448e34c421f4183c3bc0f15f206ddd9f62e3dd732af4f490fd8",
+      "workflow-context.txt": "221dca27393be2e21cb9892f6d7e5a5bae1328a29fb72356e0f81017a8df7e6a",
+      "merged-work.txt": "ab950558a095b4ab4b79af69bc5fef6f5f675f8cc4ae84dfb62ca92a6085f086",
+      "issue-changes.txt": "dda7473ff6231e045f48ede7a639ca463a9a32d6e81bcef860718fd1e52a19cc",
+      "merged-cli.txt": "e4df52085e704c49ba37bd75f62656de48cd879405856220a53bcebb7efdebb4",
+      "issues-json.txt": "0478f05c2513c3aec957a26c792f41ff2893fb1eddea11b4f9b472e93b9ac0a4"
+    },
+    "bundle_sha256": "7365f2acd21fc3e1059991cb07196b4ddce6002e38c0722ab51ad29b517d08fe"
+  },
+  "privacy_review": {
+    "format": 1,
+    "bundle_sha256": "7365f2acd21fc3e1059991cb07196b4ddce6002e38c0722ab51ad29b517d08fe",
+    "reviewer": "Codex privacy agent",
+    "decision": "approve",
+    "checked_images": [
+      "workflow-collection.png",
+      "workflow-context.png",
+      "merged-work.png",
+      "issue-changes.png",
+      "merged-cli.png",
+      "issues-json.png"
+    ],
+    "checks": {
+      "tokens_absent": true,
+      "personal_data_absent": true,
+      "feature_relevant": true,
+      "multiple_ui_scenes": true,
+      "captions_accurate": true
+    },
+    "findings": []
+  }
+}

heinzel_github-0.9.2/docs/assets/screenshots/index.html

@@ -0,0 +1 @@
+<!doctype html><html lang="en"><meta charset="utf-8"><meta name="viewport" content="width=device-width"><title>heinzel-github screenshots</title><style>body{font:16px/1.6 system-ui;margin:2rem;background:#faf8f3;color:#263b32}main{display:grid;grid-template-columns:repeat(auto-fit,minmax(min(100%,420px),1fr));gap:1rem}figure{margin:0;padding:1rem;background:white;border:1px solid #d8ddd3;border-radius:12px}img{width:100%;height:auto}figcaption{margin-top:.75rem}a:focus-visible{outline:3px solid #a64028}</style><h1>heinzel-github</h1><p>Isolated demonstration profile · Core 0.9.18 · Review these captures before committing. Click an image to inspect it at full size.</p><main><figure><a href="workflow-collection.png"><img src="workflow-collection.png" alt="Explore the fictional weekly code review in the local workflow collection"></a><figcaption>UI · Explore the fictional weekly code review in the local workflow collection</figcaption></figure><figure><a href="workflow-context.png"><img src="workflow-context.png" alt="Fictional weekly review declares merged-work and issue inputs; no report was generated"></a><figcaption>UI · Fictional weekly review declares merged-work and issue inputs; no report was generated</figcaption></figure><figure><a href="merged-work.png"><img src="merged-work.png" alt="Fictional merged pull requests in the app terminal, using a fixture-only requester and the real adapter"></a><figcaption>UI · Fictional merged pull requests in the app terminal, using a fixture-only requester and the real adapter</figcaption></figure><figure><a href="issue-changes.png"><img src="issue-changes.png" alt="Fictional issue changes, owners and states in the app terminal, using a fixture-only requester"></a><figcaption>UI · Fictional issue changes, owners and states in the app terminal, using a fixture-only requester</figcaption></figure><figure><a href="merged-cli.png"><img src="merged-cli.png" alt="Read fictional merged work in the shell with a fixture-only requester and the real adapter"></a><figcaption>CLI · Read fictional merged work in the shell with a fixture-only requester and the real adapter</figcaption></figure><figure><a href="issues-json.png"><img src="issues-json.png" alt="Fictional issue results as JSON for scripts and agents, using a fixture-only requester"></a><figcaption>CLI · Fictional issue results as JSON for scripts and agents, using a fixture-only requester</figcaption></figure></main></html>

heinzel_github-0.9.2/docs/assets/screenshots/issue-changes.txt

@@ -0,0 +1,37 @@
+Skip to content
+Heinzelmännchen
+Heinzelmännchen
+Contracts
+Team graph
+Weekly code review
+Organisation
+Team roster
+M
+Mira
+· EM
+Today
+Today
+Doctor: 3 checks need attention
+
+ai.access ai access, system.doctor installation, system.runner claude-code
+
+Open
+Ask about it
+v0.9.18
+Plugins changed, warning
+Updates, off
+0
+System health, warning
+Calendar unavailable
+Daemon not installed, off
+Chat
+Terminal
+Demo complete
+$ hz showcase issues acme/widgets; printf '\033]0;Demo complete\007'
+┏━━━━━━━━━━━━━━━━┳━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┳━━━━━━━━┳━━━━━━━┓
+┃ Issue          ┃ Title                        ┃ State  ┃ Owner ┃
+┡━━━━━━━━━━━━━━━━╇━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━╇━━━━━━━━╇━━━━━━━┩
+│ acme/widgets#3 │ Widgets wobble at high speed │ open   │ grace │
+│ acme/widgets#4 │ Document the widget API      │ closed │ ada   │
+└────────────────┴──────────────────────────────┴────────┴───────┘
+$

heinzel_github-0.9.2/docs/assets/screenshots/issues-json.txt

@@ -0,0 +1,24 @@
+[
+  {
+    "key": "acme/widgets#3",
+    "title": "Widgets wobble at high speed",
+    "url": "https://github.com/acme/widgets/issues/3",
+    "state": "open",
+    "updated_at": "2026-10-05T10:00:00Z",
+    "assignee": "grace",
+    "labels": [
+      "bug"
+    ]
+  },
+  {
+    "key": "acme/widgets#4",
+    "title": "Document the widget API",
+    "url": "https://github.com/acme/widgets/issues/4",
+    "state": "closed",
+    "updated_at": "2026-10-22T09:00:00Z",
+    "assignee": "ada",
+    "labels": [
+      "docs"
+    ]
+  }
+]

heinzel_github-0.9.2/docs/assets/screenshots/merged-cli.txt

@@ -0,0 +1,7 @@
+┏━━━━━━━━┳━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┳━━━━━━━━┓
+┃ Merged ┃ Pull request                                ┃ Author ┃
+┡━━━━━━━━╇━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━╇━━━━━━━━┩
+│ 20 Oct │ #7 Render widgets in dark mode              │ ada    │
+│ 22 Oct │ #8 Keep the last row when exporting widgets │ mira   │
+│ 23 Oct │ #9 Add release readiness checks             │ jonas  │
+└────────┴─────────────────────────────────────────────┴────────┘

heinzel_github-0.9.2/docs/assets/screenshots/merged-work.txt

@@ -0,0 +1,38 @@
+Skip to content
+Heinzelmännchen
+Heinzelmännchen
+Contracts
+Team graph
+Weekly code review
+Organisation
+Team roster
+M
+Mira
+· EM
+Today
+Today
+Doctor: 3 checks need attention
+
+ai.access ai access, system.doctor installation, system.runner claude-code
+
+Open
+Ask about it
+v0.9.18
+Plugins changed, warning
+Updates, off
+0
+System health, warning
+Calendar unavailable
+Daemon not installed, off
+Chat
+Terminal
+Demo complete
+$ hz showcase merged acme/widgets; printf '\033]0;Demo complete\007'
+┏━━━━━━━━┳━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┳━━━━━━━━┓
+┃ Merged ┃ Pull request                                ┃ Author ┃
+┡━━━━━━━━╇━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━╇━━━━━━━━┩
+│ 20 Oct │ #7 Render widgets in dark mode              │ ada    │
+│ 22 Oct │ #8 Keep the last row when exporting widgets │ mira   │
+│ 23 Oct │ #9 Add release readiness checks             │ jonas  │
+└────────┴─────────────────────────────────────────────┴────────┘
+$

heinzel_github-0.9.2/docs/assets/screenshots/source-story.md

@@ -0,0 +1,40 @@
+## Audience and outcome
+
+A developer or team lead considering a GitHub connector should see how a local workflow can declare both merged pull requests and updated issues as inputs, and what those reads return. The story should make clear that the example is fictional, the workflow is only declared, and no review report has been generated.
+
+## Scenes
+
+1. **Workflow collection, light:** Find the fictional Weekly code review alongside local workflows. This establishes where the example is discovered.
+2. **Workflow context, dark:** Inspect the same workflow’s distinct detail state: its two capability inputs, repository, and intended output. It is a declaration, not a completed review.
+3. **Merged work, app terminal:** Show the fictional merged pull requests returned by the real adapter through the fixture-only requester.
+4. **Issue changes, app terminal:** Show fictional issue titles, states, and owners; the adapter excludes pull requests from issue results.
+5. **Merged work, CLI:** Show the same useful read in a native terminal, identifying the requester as demonstration-only.
+6. **Issues as JSON, CLI:** Show a different capability and output format for scripts, with fictional data.
+
+The first two are Core feature UI scenes with different purposes; the app-terminal scenes are terminal results within the app, not feature UI. The existing plan already expresses this story and is preserved below. Its routes and rendered results still require capture-time verification.
+
+## Fictional fixtures
+
+`docs/screenshot_fixture.py` creates the local Weekly code review contract in isolated state, binds both capabilities to GitHub, and supplies `DemoGh` responses for `acme/widgets`. Its `showcase.merged` and `showcase.issues` operations use the real adapter with October 2026 fixture responses. The names, repository, accounts, PRs, issues, and links are example data; they are not evidence of a real GitHub connection. The fixture’s fixed window and `browser_time` make the story coherent. Some raw fixture records reuse an API URL or ID despite differing displayed numbers; do not present those raw fields as consistent production records.
+
+## Source-bound UI surface inventory
+
+- `pyproject.toml` declares both `heinzel.modules` and `heinzel.connected_sources` entrypoints as `github = "heinzel_github"`. Their target, `src/heinzel_github/__init__.py`, configures the module, settings, services, skill, two read capability providers, `info` operation, system-info contribution, and offline and live health contributions. The connected-source entrypoint points to that same package; the supplied source does not independently establish a separate connector screen or its exact rendering.
+- `src/heinzel_github/_module.py` declares the GitHub module. `src/heinzel_github/_adapter.py` implements merged pull-request and updated-issue reads. No plugin-specific Page, View, navigation, channel, approval, setup, or footer declaration appears in the supplied plugin source. That absence alone does not rule out Core-rendered UI.
+- `README.md` explicitly describes Core Settings → Connectors, connector list/test, system capability list, system info, and doctor. `src/heinzel_github/__init__.py` and `_service.py` provide the info and health data those generic surfaces may render; exact routes and visual controls are not established by these sources. The live test contacts GitHub when explicitly run, so it is outside this offline fixture story.
+- `docs/screenshot_fixture.py` contributes the fictional workflow and two fixture-only operations. `docs/screenshots.toml` declares `/contracts` and `/contracts/weekly-code-review` for collection and detail captures. These are Core workflow surfaces, not GitHub-owned screens; the provided plan is evidence of the intended detail route, not proof that it currently renders. If capture cannot verify it, do not substitute invented HTML or an assumed route.
+- `src/heinzel_github/__init__.py` conditionally registers `GithubReleaseFeeds` from `src/heinzel_github/_release_feed.py`; `README.md` describes its draft-workflow release-feed use. The supplied fixture does not demonstrate that flow or establish its UI, so no release-feed screenshot is claimed.
+- GitHub and `gh auth login` are external provider tools. The app-terminal and native CLI outputs are terminal surfaces. The `review-pull-request` skill declared in `src/heinzel_github/skills/review-pull-request/SKILL.md` is agent guidance, not an evidenced product screen. The existence of the `info` CLI operation does not prove it is terminal-only.
+
+## Privacy pitfalls
+
+Normal presentation fictionalization is limited to these explicit mappings: verified owning-interpreter paths become `/demo-profile/.venv`, and only the verified whole hostname detail in the genuine Doctor row becomes `demo-host`. These mappings change no SDK health status or remaining detail and establish no privacy acceptance. Unknown identities still fail, and an independent reviewer must inspect every image and transcript. Review account names, paths, hostnames, URLs, environment-derived details, tokens, logs, browser chrome, and unrelated background content; fixture labels alone do not establish privacy. Do not run the live connector test during this offline story.
+
+## Acceptance criteria
+
+- Capture the two genuine Core workflow states in applied light and dark appearances, plus the distinct app-terminal and native CLI results. Verify actual routes, headings, and data during capture; do not treat this source review as a successful capture.
+- The collection and detail must show meaningfully different states. Reject duplicate images, caption-only changes, terminal output represented as feature UI, and forged HTML.
+- Verify the merged results and issue results against the fixture and adapter, including exclusion of the PR-shaped issue; show JSON only if it is the actual CLI output. Clearly label the fixture-only requester and fictional data.
+- Do not imply that the declared workflow ran, that a report exists, or that the fixture proves a live GitHub login or production health.
+- Inspect every image and transcript independently for privacy and truthful presentation before publication. Only the narrowly specified path and Doctor-host mappings are permitted; unknown identities fail review.
+- The TOML below was checked against the requested structure by inspection only. No parser, fixture, application, capture, network call, or source code was executed, so runtime route, theme, and output validation remains outstanding.

heinzel_github-0.9.2/docs/assets/screenshots/workflow-collection.txt

@@ -0,0 +1,70 @@
+Skip to content
+Heinzelmännchen
+Heinzelmännchen
+Contracts
+Team graph
+Weekly code review
+Organisation
+Team roster
+M
+Mira
+· EM
+Workflow
+Contracts
+
+What hz knows of your workflow: the systems you connected, the artifacts playbooks keep and discovery finds, your contracts and the ones playbooks suggest, and what they maintain. Select a node for its details and its command.
+
+Discover
+merged
+issues
+ai-access
+claude-code
+, System
+code-host
+github
+, System
+directory
+one-on-ones
+, System
+team-graph
+hz-graph
+, System
+tracker
+github
+, System
+Weekly code review
+, Contract
+team-graph-keeper
+graph
+suggested
+, Suggested contract
+notes
+me:weekly-code-review
+, Output
+team-graph-keeper
+team-graph-keeper
+, Output
+Legend
+System
+Artifact type
+Discovered artifact
+Contract
+Suggested contract
+Output
+All contracts
+Weekly code review
+me:weekly-code-review
+by hand only
+v0.9.18
+Updates, off
+0
+System health, warning
+Calendar unavailable
+Daemon not installed, off
+Chat
+New chat
+Your message
+Default
+
+Up to $0.25 per message · this chat $0.00
+Runs your agent runner and may cost money: at most $0.25 per message, $2.00 per chat; this chat has cost $0.00. It reads with hz and asks you before it changes anything.

heinzel_github-0.9.2/docs/assets/screenshots/workflow-context.txt

@@ -0,0 +1,52 @@
+Skip to content
+Heinzelmännchen
+Heinzelmännchen
+Contracts
+Team graph
+Weekly code review
+Organisation
+Team roster
+M
+Mira
+· EM
+weekly-code-review
+Weekly code review
+
+Review merged work and issue changes, with owners and source links.
+
+ready
+Schedule: by hand only
+0 drafts so far
+/demo-profile/state_dir/demonstration-contracts/weekly-code-review.prose.md
+
+it has no schedule: add `schedule: "0 7 * * MON"` under `hz:` in /demo-profile/state_dir/demonstration-contracts/weekly-code-review.prose.md, or run it by hand: hz heinzel wake me:weekly-code-review
+
+Requirements
+code-host:read github
+tracker:read github
+agent-runner:read claude-code
+Inputs
+merged: code-host.merged_pull_requests
+issues: tracker.issues_updated
+Outputs
+notes: markdown
+Next steps
+hz heinzel wake me:weekly-code-review --dry-run
+Run in terminal
+the packet the agent gets; nothing is spent
+hz heinzel wake me:weekly-code-review
+Run in terminal
+draft it now, at most 0.5 USD; the draft is saved under /demo-profile/data_dir/workflow/drafts/me-weekly-code-review
+v0.9.18
+Updates, off
+0
+System health, warning
+Calendar unavailable
+Daemon not installed, off
+Chat
+New chat
+Your message
+Default
+
+Up to $0.25 per message · this chat $0.00
+Runs your agent runner and may cost money: at most $0.25 per message, $2.00 per chat; this chat has cost $0.00. It reads with hz and asks you before it changes anything.

heinzel_github-0.9.2/docs/screenshot-definition.json

@@ -0,0 +1,7 @@
+{
+  "format": 1,
+  "reviewer": "Codex feature-story agent",
+  "source_sha256": "0c55c663eadfffa985b01fda7f1a9778f22eb6fe9254f1c08f051a638b93aad6",
+  "plan_sha256": "9d204ce8608ed8eb229529b4fc0fa73fac29b39b2dd9e450b5b4a9f3f9fd55d7",
+  "story_sha256": "a419a4980b5369574d78f4b08c378dca67bdc84d904fb6bd0aebde2a19b80f00"
+}