The landing page's story shows the Row-Bot 5.0 React app - #382
Merged
Merged
Conversation
The four story stills and clips (Research, Create, Automate, Ship) were recorded in the retired NiceGUI interface. They are now scripted captures of the real 5.0.0 React client, on an isolated temporary profile seeded with a fictional neighbourhood solar co-op: no real user data, accounts or model calls, and nothing is sent. - Research: a local qwen3:8b conversation with its source trace, then the Knowledge graph (103 memories, 170 links) settling. - Create: GPT-5.6 Sol (display-only) in the model picker beside an editable landing page in the Design panel. - Automate: workflow delivery kept in the app, the local model saved, then the retained run history. - Ship: an email to the co-op board waiting for approval, then Approve (answered by the harness), on the page's 2.25 s Buddy cue. scripts/docs/capture_landing_media.py seeds the profile, drives the app with Playwright and encodes with ffmpeg from imageio-ffmpeg (uv run --with; not a project dependency). The manifest and recording receipt carry the new hashes and say how the media was made; the manifest is pending_review until the owner approves it. The landing page bumps the clip cache keys and describes the new stills. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…ph labels stand clear Automate is captured again on top of the workflow profile fix, so the Workflows list names the agent profile "Default", as the run drawer does. Research is captured again with a knowledge graph whose labels no longer overlap: the seeded relations now have fixed ids as well as the memories (the graph reads its edges in id order, which steered the layout and made it differ between captures), and the id seed was chosen by measuring label overlaps across seeded profiles. The manifest and recording receipt carry the new hashes; the manifest stays pending_review. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…s media are approved The display-only local runtime in the landing capture now lists qwen3.8:27b, the local model the owner runs, in place of the docs capture's demo models (overridden in the landing script, so docs screenshots are unchanged). Every local conversation, the workflows and the Create picker's Ollama Local group show it. All four scenes were captured again from the current client build with the same layout seed, timings and Buddy-safe framing; the Research and Create stills come out byte-identical, as they show no local model. The owner reviewed and approved the footage: the manifest records review_status "approved" with its review time (capture_landing_media.py --records --approve), and the receipt names the model it shows. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The landing page's four story scenes (Research, Create, Automate, Ship) showed the retired NiceGUI app. They now show the Row-Bot 5.0 React app, reviewed and approved by the owner.
docs/media/landing-story/screenshots/{research,create,automate,ship}.webp: 1440×810 WebP, 62–70 KB.clips/*.webm(VP9) and*.mp4(H.264, faststart): 1440×810, 30 fps, no audio. Research 9.4 s, Create 9.4 s, Automate 8.8 s, Ship 2.9 s (the page turns Buddy to success 2.25 s in).manifest.jsonandrecording-receipt.json: new hashes, durations and alt texts, aproductionblock that says how the footage was made, andreview_status: approved.docs/index.html: clip cache keys and alt texts only; the "Real app capture · Recorded in-product" framing is kept, as the owner chose.scripts/docs/capture_landing_media.py(new) reproduces the footage. It reuses the docs capture's launcher and display-only local runtime. It runs the real app and its React client in Edge on an isolated profile seeded with fictional data (a neighbourhood solar co-op). No model runs; the frontier model shows as connected only because the harness says so, and the harness answers Ship's Approve itself, so nothing is sent. Stable relation ids make the graph layout deterministic.Type of change
Risk area
Testing
uv run python scripts/run_test_matrix.py docs: 109 passed (landing story hashes, sizes, durations, frame rate, runtime behaviour, approved manifest)Release notes
Checklist
main🤖 Generated with Claude Code