Skip to content

docs(docs): complete showcase dogfood screenshots#333

Merged
w7-mgfcode merged 2 commits into
devfrom
docs/showcase-dogfood-screenshots
May 31, 2026
Merged

docs(docs): complete showcase dogfood screenshots#333
w7-mgfcode merged 2 commits into
devfrom
docs/showcase-dogfood-screenshots

Conversation

@w7-mgfcode
Copy link
Copy Markdown
Owner

@w7-mgfcode w7-mgfcode commented May 31, 2026

Summary

Completes the PRP-42 PR2 walkthrough by capturing the five remaining /showcase screenshots from a live, green showcase_rich dogfood run and wiring them into docs/user-guide/showcase-walkthrough.md. Docs-only — no app, frontend, alembic, or dependency changes.

The dogfood ran the full end-to-end pipeline from the browser and reached "Pipeline complete" (winner prophet_like, ~16 s): 24 steps, 18/18 batch items, RAG knowledge phase real against the docs/user-guide/ corpus (ollama qwen3-embedding:4b, 37 chunks), agent phase on Gemini, scenario plans persisted, ops snapshot computed.

Screenshots added (docs/user-guide/img/)

  • kpi-strip.png — KPI strip (runs 1 · aliases 1 · batch 18 · plans 2 · RAG chunks 37)
  • inspect-artifacts-panel.png — the 10-card deep-link Inspect-Artifacts grid
  • run-history-strip.png — Recent-runs strip (showcase_rich PASS 16s + Replay)
  • ops-snapshot-tiles.png — Ops-snapshot step card + five-tile KPI grid
  • agent-hitl-approve.png — Agents (HITL) step card

Notes

  • DB Reset + Re-seed first were used for a clean reviewer-grade run.
  • The HITL screenshot shows the documented skip state, not an Approve button: the agent answered without calling save_scenario (the gated tool), so agent_hitl_flow skipped by design and the one-click Approve button did not render. This matches the "visible or documented if skipped" criterion; the alt text reflects it.
  • A separate frontend bug was found during the dogfood and tracked independently in fix(ui): avoid crypto.randomUUID crash on LAN HTTP showcase #332: /showcase white-screens at completion over LAN HTTP (crypto.randomUUID is not a function — LAN-IP origin is not a secure context). The backend completes fine; screenshots were captured via localhost (a secure context). Out of scope for this docs PR.

Validation

  • grep -c "<!-- screenshot:" docs/user-guide/showcase-walkthrough.md0
  • 5 image links present (lines 159/171/201/202/203); 5 PNGs on disk
  • git diff --stat → only showcase-walkthrough.md + the new images
  • No app/ / frontend/ / alembic/ / uv.lock / env changes; no secrets in filenames or markdown

Closes #331

Summary by Sourcery

Documentation:

  • Embed five /showcase walkthrough screenshots into the user guide with detailed, accessible alt text describing each UI element.

@sourcery-ai
Copy link
Copy Markdown
Contributor

sourcery-ai Bot commented May 31, 2026

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Replaces placeholder HTML comments in the showcase walkthrough docs with actual screenshot markdown links and descriptive alt text, wiring five new dogfood-generated PNGs into the user guide without touching any application or infrastructure code.

Flow diagram for wiring showcase screenshots into docs

flowchart LR
  ShowcaseWalkthroughMD[showcase-walkthrough.md]
  KPIStrip[kpi-strip.png]
  InspectArtifacts[inspect-artifacts-panel.png]
  RunHistory[run-history-strip.png]
  OpsSnapshot[ops-snapshot-tiles.png]
  AgentHITL[agent-hitl-approve.png]

  ShowcaseWalkthroughMD -- markdown_image_link --> KPIStrip
  ShowcaseWalkthroughMD -- markdown_image_link --> InspectArtifacts
  ShowcaseWalkthroughMD -- markdown_image_link --> RunHistory
  ShowcaseWalkthroughMD -- markdown_image_link --> OpsSnapshot
  ShowcaseWalkthroughMD -- markdown_image_link --> AgentHITL
Loading

File-Level Changes

Change Details Files
Wire the Agents HITL and Ops snapshot screenshots into the showcase walkthrough with detailed, behavior-accurate alt text.
  • Replace the commented-out agent HITL screenshot marker with a markdown image link pointing to agent-hitl-approve.png and explanatory alt text describing the skip state and approval behavior.
  • Replace the commented-out ops snapshot screenshot marker with a markdown image link to ops-snapshot-tiles.png and alt text explaining the five-tile KPI grid after a green showcase run.
docs/user-guide/showcase-walkthrough.md
docs/user-guide/img/agent-hitl-approve.png
docs/user-guide/img/ops-snapshot-tiles.png
Complete the chrome-level showcase UI documentation by embedding remaining KPI, Inspect-Artifacts, and run-history screenshots.
  • Replace the placeholder comment for the KPI strip with a markdown image referencing kpi-strip.png and alt text summarizing the five KPI tiles populated after a completed run.
  • Replace the placeholder comment for the Inspect-Artifacts panel with a markdown image pointing to inspect-artifacts-panel.png and alt text describing the deep-link grid into dashboard pages populated by the run.
  • Replace the placeholder comment for the run-history strip with a markdown image for run-history-strip.png and alt text describing recent runs, status, timing, and Replay.
docs/user-guide/showcase-walkthrough.md
docs/user-guide/img/kpi-strip.png
docs/user-guide/img/inspect-artifacts-panel.png
docs/user-guide/img/run-history-strip.png

Possibly linked issues


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
Copy link
Copy Markdown

coderabbitai Bot commented May 31, 2026

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 417f8112-ca3a-45ca-acc2-b1c78c52c068

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch docs/showcase-dogfood-screenshots

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 and usage tips.

Copy link
Copy Markdown
Contributor

@sourcery-ai sourcery-ai Bot left a comment

Choose a reason for hiding this comment

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

Hey - I've found 1 issue, and left some high level feedback:

  • Some of the new alt texts are quite long and include implementation details (e.g., save_scenario behavior); consider shortening them to focus on what’s visually on screen and move explanatory context into the surrounding paragraph for better readability and accessibility.
  • Tool and flow names like agent_hitl_flow and save_scenario are referenced inline in prose; consider wrapping these in backticks for consistency with the rest of the docs’ code/identifier styling.
Prompt for AI Agents
Please address the comments from this code review:

## Overall Comments
- Some of the new alt texts are quite long and include implementation details (e.g., `save_scenario` behavior); consider shortening them to focus on what’s visually on screen and move explanatory context into the surrounding paragraph for better readability and accessibility.
- Tool and flow names like `agent_hitl_flow` and `save_scenario` are referenced inline in prose; consider wrapping these in backticks for consistency with the rest of the docs’ code/identifier styling.

## Individual Comments

### Comment 1
<location path="docs/user-guide/showcase-walkthrough.md" line_range="159" />
<code_context>
 [Agents and RAG Guide](./agents-and-rag-guide.md) for the approval gate.

-<!-- screenshot: agent-hitl-approve.png -->
+![Agents (HITL) phase — the agent_hitl_flow step card. In this local run the agent answered without calling save_scenario, so the step skipped by design; the one-click Approve button renders only when the agent triggers the gated save_scenario tool.](./img/agent-hitl-approve.png)

 ### Phase: Ops snapshot
</code_context>
<issue_to_address>
**suggestion (typo):** Consider adding a missing auxiliary verb in "so the step skipped by design".

This reads slightly ungrammatically; consider "so the step is skipped by design" (or "was skipped," depending on tense).

```suggestion
![Agents (HITL) phase — the agent_hitl_flow step card. In this local run the agent answered without calling save_scenario, so the step is skipped by design; the one-click Approve button renders only when the agent triggers the gated save_scenario tool.](./img/agent-hitl-approve.png)
```
</issue_to_address>

Sourcery is free for open source - if you like our reviews please consider sharing them ✨
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.

Comment thread docs/user-guide/showcase-walkthrough.md Outdated
Co-authored-by: sourcery-ai[bot] <58596630+sourcery-ai[bot]@users.noreply.github.com>
@w7-mgfcode w7-mgfcode merged commit c47aa02 into dev May 31, 2026
8 checks passed
@w7-mgfcode w7-mgfcode deleted the docs/showcase-dogfood-screenshots branch May 31, 2026 22:05
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.

1 participant