Skip to content

docs(landing): add Jam bug hunt blog post#325

Merged
siisee11 merged 1 commit into
mainfrom
codex/blog-jam-bug-hunt
Jul 23, 2026
Merged

docs(landing): add Jam bug hunt blog post#325
siisee11 merged 1 commit into
mainfrom
codex/blog-jam-bug-hunt

Conversation

@siisee11

Copy link
Copy Markdown
Contributor

One-Line Summary

Adds a practical guide for turning autonomous browser QA findings into verified Jam evidence, bounded OneQuery diagnostics, and actionable Linear handoffs.

User-Facing Changes

  • Adds the new “Hunting web bugs with Jam and agents” post to the OneQuery blog.
  • Explains the reproduce-twice, duplicate-check, capture, Jam verification, and Linear Triage workflow used by the Jam bug-hunt agent skill.
  • Documents the boundary between Jam CLI publishing and OneQuery’s approved read-only Jam MCP operations.
  • Adds a thumbnail using the official OneQuery and Jam marks and a labeled workflow diagram following the landing brand guide.

Why This Changed

OneQuery supports Jam as a connected source, but the blog did not show how Jam evidence fits into an end-to-end agent QA workflow. Without that explanation, it was easy to conflate publishing a Jam with reading Jam diagnostics or to treat autonomous bug hunting as unverified screenshot collection.

How It Changed

  • Adds an English MDX post under the Usecase category with concrete safety, reproduction, evidence, deduplication, and failure-preservation guidance.
  • Names the currently approved Jam diagnostics exposed through OneQuery and explicitly notes that comments, updates, and screenshot binary retrieval remain unavailable.
  • Uses the existing 1254×1254 integration-thumbnail composition with the official hosted Jam logo.
  • Uses a 1774×887 monochrome technical diagram with directly labeled states, transitions, boundaries, and non-happy paths.
  • Updates image alt text so the diagram remains understandable alongside the nearby textual workflow summary.

Extra Context / Decisions (Optional)

  • The Jam logo is the official asset already referenced by the shared JamIcon; it was not redrawn by an image model.
  • The workflow visual is code-rendered to follow the diagram guide’s monochrome, labeled, grayscale-readable style.

Verification

  • bun run format
  • bun run --cwd apps/landing typecheck
  • bun run landing:build
  • git diff --check
  • Confirmed the generated article route: /blog/hunting-web-bugs-with-jam-and-agents/
  • Confirmed thumbnail dimensions: 1254×1254
  • Confirmed workflow diagram dimensions: 1774×887

Video / Screenshot (Optional)

Jam bug hunt blog thumbnail

Verified Jam bug hunt workflow

@siisee11
siisee11 enabled auto-merge (squash) July 23, 2026 16:02
@cloudflare-workers-and-pages

Copy link
Copy Markdown

Deploying with  Cloudflare Workers  Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status Name Latest Commit Preview URL Updated (UTC)
✅ Deployment successful!
View logs
onequery-landing 2d3a826 Commit Preview URL

Branch Preview URL
Jul 23 2026, 04:04 PM

@siisee11
siisee11 merged commit b825bbe into main Jul 23, 2026
9 checks passed
@siisee11
siisee11 deleted the codex/blog-jam-bug-hunt branch July 23, 2026 16: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