Skip to content

docs(e2e): manual kitty verification procedure + demo inter-frame pause (K4) - #56

Merged
rsenna merged 2 commits into
mainfrom
e2e-k4-manual-doc
Oct 11, 2026
Merged

rsenna merged 2 commits into
mainfrom
e2e-k4-manual-doc

Conversation

@owkwo-bot

@owkwo-bot owkwo-bot commented Oct 11, 2026 •

Copy link
Copy Markdown
Collaborator

Summary by Sourcery

Improve Kitty rendering verification by documenting a manual real-terminal check and making the demo pause between frames.

Enhancements:

  • Add a manual verification procedure for confirming Kitty rendering, sprite movement, and background restoration in a real kitty-compatible terminal.

Documentation:

  • Document prerequisites, expected visuals, platform limitations, and the relationship between manual and automated Kitty verification.

Chores:

  • Pause the demo after its first frame so the initial render can be inspected before the second frame is displayed.

Summary by cubic

Adds a manual, by-eye verification procedure for kitty rendering and pauses the demo between frames so a human can observe the first frame and the sprite's move separately.

The planned automated Linux-only E2E test (shipped via a companion PR) only proves kitty accepts the escape sequence; it cannot verify pixels render correctly, and macOS and BSD have no Xvfb equivalent.

Changes

  • docs/manual-kitty-verification.md is a step-by-step procedure for real kitty-compatible terminals, including the expected output table and platform notes (BSD ships only the kitten CLI).
  • examples/src/bin/demo.rs now waits for Enter between the two present() calls so the first frame and the background restoration around the moved sprite are each observable — a single present() after an in-memory move proves neither.

Written for commit 5cf2900. Summary will update on new commits.

View guided diff Turn on auto-fix

…se (K4)

- docs/manual-kitty-verification.md: step-by-step, by-eye verification of
  present()'s rendered output in a real kitty terminal, covering macOS and
  BSD (the platforms with no Xvfb equivalent), and cross-referencing
  tasks/plan.md T1/T4.
- examples/src/bin/demo.rs: pause on a keypress between the two present()
  calls so a human can observe the first frame and the sprite's movement +
  background preservation separately, instead of only the final state.
@sourcery-ai

sourcery-ai Bot commented Oct 11, 2026 •

Copy link
Copy Markdown

Reviewer's Guide

Adds a manual kitty-terminal verification guide and updates the demo to pause after its first frame, enabling visual confirmation of rendering, sprite movement, and background preservation alongside the automated E2E protocol check.

Sequence diagram for the paused two-frame kitty demo

sequenceDiagram
    participant User
    participant Demo
    participant KittyBackend
    participant Terminal as KittyTerminal

    User->>Demo: run demo
    Demo->>KittyBackend: present(canvas)
    KittyBackend->>Terminal: render first frame
    Terminal-->>User: display full scene
    Demo-->>User: eprintln First frame rendered
    Demo->>User: read_line()
    User-->>Demo: press Enter
    Demo->>KittyBackend: present(canvas)
    KittyBackend->>Terminal: render second frame
    Terminal-->>User: display sprite at new position
    User->>User: verify background has no trail
Loading

File-Level Changes

Change Details Files
Adds a manual visual verification procedure for kitty rendering and documents how it complements the automated protocol-level E2E test.
  • Documents prerequisites, demo steps, expected rendered elements, failure indicators, and platform limitations.
  • Explains the distinction between kitty accepting escape sequences and pixels rendering correctly.
docs/manual-kitty-verification.md
Introduces an interactive pause between the demo's two rendered frames so sprite movement and background restoration can be visually inspected.
  • Waits for Enter after the first successful present().
  • Retains the second-frame sprite move and present() flow for comparison.
examples/src/bin/demo.rs

Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

@coderabbitai

coderabbitai Bot commented Oct 11, 2026 •

Copy link
Copy Markdown

Warning

Review limit reached

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

Next included review available in 44 minutes.

Check out review usage here.

View limit details

Limit details: You’ve used the included review currently available.

Learn how review limits work.

Review configuration:

⚙️ Run configuration
  • Configuration used: defaults
  • Review profile: CHILL
  • Plan: Advanced
  • Run ID: 8fdb7c36-59f6-4b8e-9dd1-35b002c2302b

📥 Commits

Reviewing files that changed from the base of the PR and between d556997 and 5cf2900.


📒 Files selected for processing (2)
  • docs/manual-kitty-verification.md
  • examples/src/bin/demo.rs

  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@codacy-production

Copy link
Copy Markdown

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

🟢 Metrics 0 complexity · 0 duplication

Metric Results
Complexity 0
Duplication 0

View in Codacy

NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.

@cubic-dev-ai cubic-dev-ai Bot left a comment •

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

All reported issues were addressed across 2 files

Reply with feedback, questions, or to request a fix.

View guided diff | Turn on auto-fix | Re-trigger cubic

Comment thread docs/manual-kitty-verification.md Outdated

@sourcery-ai sourcery-ai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey - I've reviewed your changes and they look great!

Sourcery assessment

Approved.


Sourcery is free for open source - if you like our reviews please consider sharing them ✨

The intro presented the automated Xvfb-backed E2E test as present, but it is
added by a companion PR; reword to 'planned' so the manual doc does not claim
an artifact that does not exist in this PR.
@rsenna
rsenna merged commit 84ab200 into main Oct 11, 2026
4 checks passed
@rsenna
rsenna deleted the e2e-k4-manual-doc branch October 11, 2026 16:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants