MINI-ROOK / BUILD LOG 023
From Releases to Stories
An authenticated release becomes a checked local draft
TECHNICAL CHECKPOINT
What this build actually records.
- Stack and method
- Authenticated release recheck · bounded metadata · tag/link/prerelease checks · one repair attempt
- Recorded progress
- Focused safeguards pass; creator confirms sourced CharacterForge RC1 story saved in Growth Draft Queue.
- Still open at this checkpoint
- Offline, activation, cost and feature claims require separate editorial fact checks; no automatic publishing.
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.
Syntax and focused source-link, recency and prerelease safeguards passed. The creator observed an Ollama CharacterForge RC1 story with its exact tag, official release URL and separate Quest Forge licensing reference, then confirmed Story saved for review and persistence in Growth Draft Queue. This is a human-observed release-to-draft workflow result.
Still open: Offline capability, activation requirements, costs and other feature assertions still need manual fact review. Rule checks do not guarantee release-note support for every claim. One repair attempt is allowed; successful outputs remain local drafts for human review, not automatically published stories.
01 / BUILD LOG 023
The original development record
Mini-Rook's GitHub Release Companion now exposes a Draft release story action for a selected release. Before drafting, it confirms that the requested release was previously discovered, that the repository belongs to the allowlisted Rookweld projects and is still granted to the installed GitHub App, and that the release still exists in GitHub's authenticated response.
The AI receives bounded release metadata, published tag and URL, prerelease status, listed asset names and an excerpt from release notes. The existing editorial Quality Gate and evidence checks run on the generated text. Additional checks require the exact release link and tag, flag unsupported "released today" claims, and insist that prerelease status be communicated. One repair attempt is allowed, after which an unsuccessful draft is blocked. A successful draft is saved locally for human review, not published.
Verification: Python and JavaScript syntax PASS; focused safeguards test PASS for missing source link, unsupported recency and omitted prerelease status, while a correctly sourced prerelease sentence passes. The creator subsequently provided a successful live Ollama-generated CharacterForge RC1 release story containing the correct tag, official GitHub release URL, and separate Quest Forge licensing reference. This confirms successful human-observed generation and output; the creator confirmed the interface displayed Story saved for review and the generated entry persisted in Growth Draft Queue. Some statements about offline capability, activation requirements and cost remain subject to separate manual fact-checking. These rule-based checks cannot guarantee that every feature claim is factually supported by the release notes.
Status: READY TO PUBLISH — human acceptance PASS for the complete draft-save workflow; editorial fact review is still required. Chapter VII — The Raven Takes Initiative.
KEEP FOLLOWING THE BIRD