Skip to content
Roku Codex Toolkit

v0.1.0 release boundary

v0.1.0 is the first stable public preview of two project-neutral Codex plugins: five documented skills and the 13-tool roku-device MCP server already present in this repository.

Included

Section titled “Included”
  • ECP queries, launch, remote keys, and non-secret text entry.
  • Developer-mode screenshot, console capture, and confirmed sideload operations.
  • JSON flow preflight and execution with private evidence artifacts.
  • Runtime-log triage, accessibility review guidance, and release validation guidance.
  • Node-based marketplace installation and a portable Python launcher.
  • Host-side automated tests on current macOS, Ubuntu, and Windows runners.

Acceptance criteria

Section titled “Acceptance criteria”
  • npm run validate passes on Node 18, 20, and 22 where supported by CI and Python 3.9 through 3.13 matrix representatives.
  • No developer password appears in argv, normal output, reports, or repository configuration.
  • Network and subprocess operations are bounded and cancellable at the MCP boundary.
  • Developer-mode credentials are sent only to private, link-local, or loopback targets.
  • Explicit artifact destinations are resolved into an existing requested directory, protected from symlink swaps at commit, and written with user-only permissions where POSIX permissions apply.
  • Concurrent mutations to the same resolved device are serialized.
  • Dry runs never claim verification. Successful device commands never prove UI correctness. Screenshots remain pending_visual_review until reviewed.
  • Documentation distinguishes host CI evidence from physical-device evidence.
  • The physical-device matrix in hardware-validation.md is completed with sanitized evidence references.
  • Installation, contribution, security reporting, examples, and release steps are documented.

Deferred

Section titled “Deferred”
  • Public package registries, a hosted documentation portal, website, telemetry, auto-update, and release publishing.
  • Product-specific authentication, entitlement, playback policy, deployment, or service integrations.
  • A graphical IDE, BrightScript language server, general-purpose debugger, or replacement for Roku developer services.
  • Hardware certification across host operating systems and Roku model/firmware combinations.

Breaking adjustments are possible during the 0.x series, but tool names, schemas, report semantics, and configuration paths should be treated as compatibility surfaces and changed deliberately.