docs(screenshots): refresh landing + README captures to current UI#39
Conversation
Re-captured 6 surfaces against the current frontend on a clean English demo corpus (no private project names): Time Machine stack, Lens, Mix & Match, Predict, Replay, and the (English) Dashboard. Replaces the stale older-corpus captures. - assets/screenshots/*.png — root landing (index.html) - docs/img/*.png — README topology.png is intentionally left unchanged this pass. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
Important Review skippedReview was skipped due to path filters ⛔ Files ignored due to path filters (11)
CodeRabbit blocks several paths by default. You can override this behavior by explicitly including those paths in the path filters. For example, including ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
Note Gemini is unable to generate a review for this pull request due to the file types involved not being currently supported. |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
memex/assets/screenshots/stack.png
Line 1 in 411b7b5
Replace the duplicated Time Machine screenshot
This refreshed stack capture is byte-for-byte identical to assets/screenshots/predict.png (and the README copy docs/img/stack.png is also identical to docs/img/predict.png). Since index.html maps the Time Machine surface to assets/screenshots/stack.png and the README grid uses docs/img/stack.png for Time Machine, both docs now show the Predict next-action panel where the Time Machine card stack should appear.
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
The first pass captured stack.png on the same auto-selected card as predict.png, making the two images byte-identical. Re-shoot the stack on a different deck card so it shows the layered card cascade distinctly. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
@codex 좋은 지적입니다 — 이미 다음 커밋 첫 패스에서 현재 head(
이제 Time Machine 서피스는 카드 스택을, Predict는 next-action 패널을 각각 올바르게 보여줍니다. @codex review |
|
Codex Review: Didn't find any major issues. More of your lovely PRs please. ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
If Codex has suggestions, it will comment; otherwise it will react with 👍. Codex can also answer questions or update the PR. Try commenting "@codex address that feedback". |
1 participant
Refreshes the product screenshots on the root landing (
index.html) and the README (docs/img/) — the previous captures were from an older corpus + older UI.Re-captured against the current frontend on a clean English demo corpus (no private project names):
topology.pngintentionally left unchanged this pass.Images only — no code changes.
🤖 Generated with Claude Code