Ritoko 0.2.0

Ritoko 0.2.0

Ritoko 0.2.0 adds destination checks before creating an item, read-only reconciliation of an uncertain write, installation diagnostics and a runnable first try.

• ensure confirms an existing scoped record without submitting and permits creation only after a positive absence check.
• run_reconcile / reconcile use the original frozen lookup, parameters and input to check an uncertain item without replaying the submission. An inconclusive check leaves it for review.
• Lookups support direct HTTP GET and trusted MCP tools explicitly marked read-only. Browser, host and agent-managed lookups are outside this release's support.
• doctor checks runtime, installation, journal and browser configuration. Dedicated browser shutdown is bounded and never launches a new browser to close it.
• The local first try creates ten fake CSV customers, verifies each with a separate readback and checks that rerunning creates nothing further. No account or Chrome is required for this example.
• Claude Code and Codex Git plugin manifests, npm and MCP Registry metadata are aligned at 0.2.0. The local MCP server exposes 20 tools. MCPB generation and extracted-bundle checks are now reproducible from committed scripts.

Upgrade: manual resolution now requires an evidence note and --confirm-checked, and is recorded as an unverified human decision. Adoption requires fresh verification. Update automation clients using these calls before upgrading. Reconciliation needs a lookup already present in the original run snapshot; adding a lookup to a saved workflow does not retrofit an older run.

Requires Node.js 24+. Browser workflows additionally need Chrome and an authorized debugging connection or explicitly selected dedicated profile. API-only workflows do not need Chrome. Host browser replay needs a client permitting page-script execution; current Codex computer-use read-only evaluation does not provide it.

Local validation: 206 unit tests, 37 E2E tests and 36-page site preflight pass on Windows, Node 24.19.0. Publication also requires green CI on the exact commit across Windows, macOS and Linux. The MCPB extracted test verifies 20 tools and two API rows followed by two skips; desktop-client runtime compatibility remains to be tested.

Install the executable release with npm install ritoko@0.2.0, or configure npx -y ritoko@0.2.0 mcp in a local stdio MCP client. Follow the update policies, test a small batch, and restart an existing MCP process after upgrading.

Source: c333b04. CI: https://github.com/Swih/ritoko/actions/runs/37921407496.

The npm tarball, MCPB bundle and SHA256SUMS are attached. Bundle validation covers Windows Node 24.19.0; desktop client compatibility is not established by that test.

Ritoko 0.1.1

Align the MCP namespace with the case-sensitive GitHub owner (io.github.Swih/ritoko) so the official registry can authenticate publication. Plugin manifests and MCP protocol metadata now report 0.1.1; release checks catch namespace and installed-server version mismatches.

Validation: 142 unit tests and 36 end-to-end tests pass in CI on Windows, Linux and macOS. The public npm package also passes an isolated stdio smoke test: 18 tools, two verified API rows and two skipped rows on the second run, without Chrome.

Requires Node.js 24 or newer. Chrome is needed for browser workflows; API-only workflows run without it. Runs and journals stay local. This release provides a local stdio server.

Assets include the published npm tarball and an MCPB bundle with production dependencies. The bundle passes official MCPB validation and an extracted-bundle stdio/API smoke test on Windows with Node 24.19.0; its client must provide Node 24 or newer.

The release guide explains distribution updates and pinned versus latest client versions.

Ritoko 0.1.0

Turn a browser task into a deterministic procedure for new CSV or Excel data. Ritoko journals each item, verifies its business result and resumes interrupted batches while holding uncertain writes for review.

• Local stdio MCP server and skills for Claude Code and Codex CLI.
• Direct Chrome workflows and journaled HTTP/MCP steps; API-only workflows need no browser.
• Host batches with up to four lanes in clients that permit page-script execution.
• Indexed host scheduling, compact cursor state and isolation of invalid download receipts.
• Compiled npm distribution, installed-package smoke tests and process-kill recovery tests.

Requires Node 24+. Start the MCP server with npx -y ritoko@0.1.0 mcp. The GitHub plugin installation instructions are in the README.

Validation: 142 unit tests and 36 end-to-end tests, including real Chrome and the installed npm tarball, passed in CI on Windows, Linux and macOS. Production dependency audit reported no known vulnerabilities at release time.

Current host limitations include setup/teardown, keyboard, extraction and iframes. Codex's read-only computer-use evaluate cannot execute host browser programs. Direct MCP connections use the legacy v1 protocol versions through 2025-11-25. Controlled fixtures do not establish reliability on every third-party site; see the release and validation roadmap.