MINI-ROOK / BUILD LOG 022
The Raven Meets GitHub
Read-only release discovery through an installed GitHub App
TECHNICAL CHECKPOINT
What this build actually records.
- Stack and method
- GitHub App · short-lived installation authorization · selected repositories · read-only release cards
- Recorded progress
- Operator lists two installed repositories and retrieves four existing release records in Growth; syntax/deduplication pass.
- Still open at this checkpoint
- Unattended polling, event notifications and release-to-draft integration not verified at this checkpoint.
Software development on an existing workstation. This entry does not establish a new robot, custom hardware build or autonomous publishing capability.
TEST STATUS / SEPARATE FROM THE ORIGINAL RECORD
What later checks established.
The operator authenticated to two selected repositories and observed four existing ForgeCare/CharacterForge release records in Growth. Python/JavaScript syntax and isolated deduplication checks passed. The discovery count describes records newly seen in the local inbox, not new publication dates.
Still open: This checkpoint does not verify unattended GitHub polling, event notifications or release-to-draft integration; see Log 023 for later draft-save evidence. The GitHub App has read-only contents/metadata permissions. Private keys, installation credentials and integration tools are not exposed by this website.
01 / BUILD LOG 022
The original development record
Mini-Rook now connects to GitHub Releases through a registered GitHub App, Rookweld Release Companion. The app was transferred to the Rookweld organization and installed on two explicitly selected repositories: Rookweld/ForgeCare and Rookweld/CharacterForge, with read-only contents and metadata permissions.
The Fury-side integration signs a GitHub App JWT using a locally supplied private key, requests a short-lived installation token and uses that authorization to query releases. The private key is not embedded in the project files or shown in the interface. Releases appear as read-only cards in Mini-Rook's Growth UI. They are not automatically published as social posts or converted into marketing claims.
Human acceptance: the operator successfully listed the two installed repositories with a local authenticated test, then used the Growth interface to retrieve four existing release records: ForgeCare v1.0.0 and v1.1.0-beta.1, and CharacterForge v1.0.0 and v1.0.0-commercial-rc1. The initial discovery count measures records newly seen by the local inbox, not new GitHub publication dates. Python and JavaScript syntax checks and isolated deduplication tests also passed. This does not yet verify unattended GitHub polling, event-driven notifications, or release-to-draft integration.
Status: READY TO PUBLISH — authenticated GitHub release retrieval verified by human UI test. Chapter VII — The Raven Takes Initiative.
KEEP FOLLOWING THE BIRD