Repository navigation
docs: bring the 1.0 README refresh to main (#3741) - #3772
Merged
Merged
Conversation
Copies the README, hero images and 1.0 screenshots from dev so the GitHub landing page carries the 1.0 positioning ahead of the release cut. The manifest entries for Inbox and Projects screenshots point at the portal component directory rather than the dev-only component files (the screenshot guard requires every source path to exist on this branch); the dev manifest's more precise paths win when dev merges into main. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
vybe
approved these changes
Oct 16, 2026
vybe
left a comment
vybe
left a comment
Contributor
There was a problem hiding this comment.
Docs-only: README identical to dev, assets added, screenshot guard passes on main's tree.
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
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
mainso the GitHub landing page shows the 1.0 positioning now, ahead of the release cut.docs/assets/trinity-hero-{dark,light}.webp) and the eight 1.0 screenshots the README embeds, plus theirMANIFEST.yamlentries.README.mdis byte-identical to dev. The manifest's Inbox/Projects entries point atsrc/frontend/src/components/portal(exists on main) instead of the dev-only component files; dev's more precise paths win at the next dev → main merge.Verification
Fails on the unpatched dev manifest against main's tree (6 stale source paths), passes after the patch.
Docs-only, docs + binary assets, no code change.
🤖 Generated with Claude Code