Skip to content

docs: update Rook guide for public 0.1.0 - #3420

Open
4DvAnCeBoY wants to merge 1 commit into
LambdaTest:stagefrom
4DvAnCeBoY:docs/rook-public-release
Open

docs: update Rook guide for public 0.1.0#3420
4DvAnCeBoY wants to merge 1 commit into
LambdaTest:stagefrom
4DvAnCeBoY:docs/rook-public-release

Conversation

@4DvAnCeBoY

Copy link
Copy Markdown
Member

Summary

  • replaces the former private-repository install flow with the public npm, checksummed shell, and Homebrew methods
  • documents platform/runtime behavior and the tested Windows, pipe-installer, Homebrew dependency, and controller limitations
  • separates headless and interactive doctor behavior and adds a release-accurate installation screenshot
  • adds a real expense-policy scenario while explicitly marking session-scoped tool evidence as Unable to Verify in 0.1.0
  • dates live-service observations so later service changes do not make the guide silently misleading

Release validation

  • @testmuai/rook 0.1.0 installed and launched from an isolated npm prefix
  • shell archive installed from a downloaded script, checksum verified, and bundled runtime launched without system Node
  • Homebrew bottle installed, tested, uninstalled, and the prior local Rook link restored
  • public release assets, install.sh flags, formula behavior, changelog, and gated release pipeline checked
  • realistic refund, triage, and expense agents exercised through missing-input, boundary, repeat-state, multimodal-output, and audit-evidence cases

Documentation validation

  • HOST=localhost API=local-build-placeholder pnpm build
  • all seven changed routes returned HTTP 200 from the production build
  • installation and use-case pages inspected in headless Chrome
  • git diff --check
  • adversarial review completed with both Codex and Claude; findings were corrected before push

The build reports the existing repository-wide duplicate-route and broken-anchor warnings. No warning references a Rook page or the preserved continuous-regression anchor.

Documents installer and runtime behavior verified against the public release, including dated controller availability, Windows and shell-installer gaps, and evidence limitations.\n\nAssumption: time-sensitive service observations remain explicitly dated August 17, 2026 and should be replaced when a later release restores the end-to-end journey.
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