Repository navigation
docs(rook): 0.1.11 polish, real-run captures (Attack intent, Coverage gaps, OWASP table), skill 0.1.11 - #3694
Merged
Conversation
- CLI Reference lists every command that writes one JSON document with --json (adds scenarios list, project --workspace, mcp, ask); CI/CD links to it. - Installation: npm upgrade uses `npm install -g @testmuai/rook@latest`, matching PowerShell and the CLI's own fallback; drop stale 0.1.7 notes; Next Step moves to the end of the page. - Quickstart: PowerShell install is unpinned like the other install lines. - Client skill-copy recipes pin the 0.1.11 skill commit (439480f2) instead of the September commit (f199cb99). - dateModified -> 2026-10-13 on pages changed for 0.1.11; quickstart step 2 heading case; remove the web UI "coming soon" search note. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
From a signed-in 0.1.11 run of the Quickstart's triage-service sample: - get-started screenshot is now the signed-in session with the project chooser (captions and sizes updated on Overview, Quickstart, Install); - local viewer captures of the Attack intent panel (Scenarios) and the Coverage gaps panel (Web UI); - an excerpt of the report's OWASP coverage table, with what each column counts (Results and Evidence). Corrections found in that run: - skip_reason prefixes come only from Rook's own validation; the checker writes plain sentences (Scenarios, Troubleshooting); - a plain generate can plan no attacks; ask with --class adversarial. Also folds in LambdaTest#3693: the skill package is now 0.1.11 (Coding Agents). Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
…ings - Replay the Quickstart as written on Rook 0.1.11 and recapture its 15 walkthrough images, plus all 26 /help screens and /doctor. - Quickstart: document reviewing generated call checks; a called_with check with empty arguments reports Unable to Verify. - Scenarios: full on-disk path under projects/<project-id>/; link the OWASP Top 10 for Agentic Applications. - CLI Reference: /docs opens the documentation site, not the repository. - Update captions and alt texts for the new captures. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
This was referenced Oct 14, 2026
surishubham
pushed a commit
that referenced
this pull request
Oct 14, 2026
… QA fixes Applies the #3694 changes (merged to stage as d77b1de) unchanged: recaptured TUI walkthrough, /help and /doctor screenshots on Rook 0.1.11, Attack intent and Coverage gaps captures, the OWASP coverage table, skill 0.1.11, and the QA fixes (scenario path, /docs, OWASP Agentic link, Quickstart calls arguments). Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
surishubham
added a commit
that referenced
this pull request
Oct 14, 2026
…estmucom docs(rook): promote #3694 to testmuCom — 0.1.11 screenshots and QA fixes
surishubham
pushed a commit
that referenced
this pull request
Oct 14, 2026
… QA fixes Applies the #3694 changes (merged to stage as d77b1de) unchanged: recaptured TUI walkthrough, /help and /doctor screenshots on Rook 0.1.11, Attack intent and Coverage gaps captures, the OWASP coverage table, skill 0.1.11, and the QA fixes (scenario path, /docs, OWASP Agentic link, Quickstart calls arguments). Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
surishubham
added a commit
that referenced
this pull request
Oct 14, 2026
…t-docs docs(rook): promote #3694 to lt-docs — 0.1.11 screenshots and QA fixes
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
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.
Third commit (
22cd7575): screenshots recaptured on 0.1.11, QA findingsFrom Mayur's QA pass:
/help <command>screens and the/doctorscreen were recaptured too. Local paths are shortened to~/rook-samples/…and~/.testmuai/rook/…, and the account name is replaced. Image sizes, captions and alt texts are updated to match, for exampleSC-001instead ofSC-002, and the triage profile instead of the old CommerceCare demo..testmuai/rook/projects/<project-id>/agents/<agent-id>/scenarios/, with a link to the Workspace Files tree./docs(CLI Reference): the page said/docsopens the public repository. In 0.1.11 (and 0.1.7) it opens the documentation site, so the docs are what changed, not the command.Found in the replay:
expect: called_withwith emptyarguments: {}for every tool call. A run then reported the T-1043 scenario as Unable to Verify, even though all four criteria passed. The Quickstart now says to review thecallslist and fill in the expected arguments; with that change the scenario passes. This is a product bug and will be filed in Jira.Docs test: 44/44. Static-md fences: 0 errors.
Second commit (
260ab763): real 0.1.11 run, plus #3693This PR now also replaces #3693. One promotion covers both.
Captured from a signed-in run of the published
@testmuai/rook@0.1.11against production, using the Quickstart'striage-servicesample:Corrections found in that run:
skip_reasonstarts withcoverage gap:,invalid scenario:orinvalid red-team scenario:only when Rook's own validation wrote it. The scenario checker writes plain sentences (for example, a precondition the profile can't establish).generate: a plaingeneratecan plan no attacks for a small agent; this run planned 9 functional scenarios and no attacks. The page now says to ask with--class adversarialand to check the coverage gaps.Docs test: 44/44. Static-md fences: 0 errors.
Summary
Follow-up polish after #3675/#3690. No new features are documented.
--json. Previously only plan, status, run and report were listed; this addsscenarios list,project --workspace,mcpandask, checked against the 0.1.11 CLI. CI/CD links to that list.npm install -g @testmuai/rook@latest. It used to benpm update -g; the new command matches the PowerShell section and the CLI's own update fallback.439480f2, the commit published as@testmuai/rook-skill@0.1.11(Describe rook 0.1.11 in the agent skill rook#52). They pinnedf199cb99, from September 14, and 7 skill files have changed since.dateModified→ 2026-10-13 on the 13 pages changed for 0.1.11;Left as is:
Verification
node --test scripts/rook-docs.test.cjs: 44/44. The quickstart PowerShell pin assertion moved to the installation page.generate-static-md+check-static-md-fences: 0 errors. Generatedstatic/docsis not included.🤖 Generated with Claude Code