Project cards now support cover art, project pages show a larger image, and journal entries can include captioned galleries. Every image is labeled as concept art, a project art asset or an actual screenshot, with alternative text and responsive sizes.
The first cover is an AI-generated illustration of an open workshop. It is a visual identity for this journal, rather than evidence of a finished game or a real workspace.
The image pipeline removes embedded metadata and creates smaller WebP copies. Automated checks cover image privacy, metadata removal, cross-project attachment rejection, approval controls, broken-image deployment checks and rollback. Original files stay private.
Individual image review is the default. A project can explicitly enable automatic art publication, while screenshots continue to require individual approval. The bot can show a private image preview before approval.
Concept art · AI-generated An imagined open workshop, created for Project Studio. This illustration is not a screenshot.
Next: Use cover art and milestone galleries as projects develop; enable automatic art only for the projects intended for public sharing.
The dashboard, project page, journal and daily ledger are now published. A separate network fetched the dashboard over HTTPS and its content hash matched the deployed release. The former demonstration pages have been removed from the public site.
All 36 automated tests passed, including a mocked coding turn through the bot harness, persisted session recovery, duplicate handling, private-data filtering, failed-deployment rollback and the three notification modes. A headless mobile-browser screenshot was also inspected. These checks establish the tested behavior; they do not substitute for the first owner interaction after activation.
The existing bot must finish its current reply before restarting safely. Integration activation is queued behind that turn. New project publication remains opt-in, and editorial drafts remain subject to owner review.
Next: After activation, try the Studio commands in the existing Telegram bot and select the next project to track.
The goal is a readable view of development work with fewer interruptions. This first build adds a project dashboard, durable project history, an editorial journal and a compact daily task ledger.
A 34-test Python suite passed, covering existing bot behavior alongside duplicate events, publication safety, restart persistence, rollback after a failed deployment, and notification modes. Failed results remain failures; simulated checks are labeled.
Unknown projects stay private. Public stories require reviewed summaries, while raw conversations and command logs stay out of the site. The default notification volume is preserved; quiet mode is available by choice.
These are automated local checks. Live activation and external website checks are the next acceptance steps. No mobile-device verification is claimed.
Next: Activate the bot integration and verify the published pages from a separate network.
Runtime activity
Process activity does not establish development progress. An old start without an end is unknown, not proof work is advancing.
