feat(browser): iris browser check <url> — render-verify a page from the command line - #72
Merged
Merged
Conversation
… the command line
The render check shipped as a skill plus a script, so an agent could run it and a person could
not. This is the same capability with no model in the loop — what CI, a pre-publish gate, or
someone on a terminal actually reaches for:
iris browser check https://heyiris.io/p/fleet-layer --viewports tablet:768x900
iris browser check <url> --json # the raw result
iris browser doctor # can this machine drive a browser at all
ONE IMPLEMENTATION. It execs render-check.sh from the IRIS bridge — the same file the V6
`hiveBrowserUse` tool runs on a Hive node and the browser-use skill runs by hand. A copy here
would be a third behaviour to keep in agreement.
THE EXIT CODE IS THE PRODUCT, and there are three, not two: 0 clean · 1 findings (listed) ·
2 COULD NOT MEASURE. Verified all three, plus --json, plus a machine with the script absent
(exit 2 naming the missing piece, never a false pass).
Note for whoever adds the next product: build-capabilities.ts indexes name, aliases, describe
and options — it does NOT read productCommand's `keywords`, which are documented as the leverage
that makes new recipes findable. So the words people search for are in the purpose line here,
and `iris find screenshot` reaches this command. Filed separately.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_018EozxzAioSnD4afkYcw8Zm
mayoalexander
added a commit
that referenced
this pull request
Sep 19, 2026
…+ iris browser check (PRs #80, #72) Brings in `iris reachr scrape` (public pages, Instagram, LinkedIn; --write adds leads), `iris reachr inbox` (+ --log-comms), `iris reachr audit-replies`, reachr-core with 57 tests, and its base branch feat/iris-browser-command (`iris browser check <url>`). Verified on the merged tree before pushing: - typecheck (tsgo --noEmit): 0 errors - reachr-core.test.ts: 57/57 - full suite: 3268 pass / 231 fail — the same 231 as the PR's CI run. Grouped by file, every failing file is outside this branch (provider, snapshot, config, agent, …). The three that still fail in isolation (platform-commands 13, bug-regressions 7, provider 9) fail IDENTICALLY on main 51c3cb9 — pre-existing, whole-suite leak tracked in #185847. - only conflict: capabilities.json (generated) — regenerated from the merged source. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0121oCnNCeZBewSyiQSQ8bin
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
1 participant
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.
The render check shipped as a skill + script, so an agent could run it and a person could not. This adds the same capability with no model in the loop:
One implementation. It execs
render-check.shfrom the IRIS bridge — the same file the V6hiveBrowserUsetool runs on a Hive node and thebrowser-useskill runs by hand. A copy here would be a third behaviour to keep in agreement.Three exit codes, not two:
0clean ·1findings (listed) ·2could not measure. All three verified, plus--json, plus a machine with the script missing (exit 2 naming the missing piece, never a false pass).Verified by running it, not by reading it:
check https://heyiris.iocheck /p/fleet-layer --viewports tablet:768x900check http://127.0.0.1:1/xdoctorwith the script absentbrowser --helpNote for the next product command:
build-capabilities.tsindexes name/aliases/describe/options and never readsproductCommand'skeywords, which the helper documents as the leverage for discoverability. Search terms are in the purpose line here soiris find screenshotreaches it; filing the generator gap separately.🤖 Generated with Claude Code
https://claude.ai/code/session_018EozxzAioSnD4afkYcw8Zm