playrote.play.v1

hhimanshu-jha/play-smoke-testv0.2.0Public

Play smoke test

A smoke test for a Play: does it actually run? Static scoring cannot answer that.

Read the full description

By default this inspects only and withholds execution, because a self-declared effect-read-only tag is not proof of safety. Set allow_effects=true to authorize one bounded run with a credential-free HOME and environment. Inspection fingerprints every regular file in the complete bounded play package—including dependency/runtime manifests, helpers, resources and fixtures, regardless of directory name—with relative paths, modes and contents, while rejecting every symlink and partial over-limit bundle. Before execution it verifies the same digest, copies that exact package into an isolated snapshot, verifies the snapshot again, and runs the snapshot, so later source mutation cannot change what executes. The run captures at most 64 KiB per stream, never returns child output, and terminates the whole process group. It reports exit status, duration, and step counts, not whether the target answer is correct. The authorized target may s

  • Published 4 Sep 2026
  • Downloads 2
  • Needs rote 0.62.0+
  • License MIT
  • Digest sha256:779eeff0419f…
  • Reference himanshu-jha/play-smoke-test@0.2.0

Before you run it2 local tools

Everything here is checked on your machine when rote inspects the play. This page never learns what you have installed or which credentials you hold.

  • ○
    python3local tool

    Requires >=3.8. Run rote play inspect to check your host; unverified versions remain unknown.

  • ○
    rotelocal tool

    Must be on your PATH when used. minimum version undeclared.

Inputs3, all optional

rote asks for these before running and shows the defaults it will use.

  • Playplay

    The play to review: a local play name, a play directory, or its main.ts. Steps run in the play run workspace rather than your shell, so a relative path resolves somewhere you did not mean.

    optionalstringdefault build-environment-trapsexample /Users/me/.rote/flows/my-playcustom value allowed
  • Ownerowner

    Your registry org slug, passed through to play-quality-doctor so it can derive the source_url fix instead of reporting it underivable.

    optionalstringexample himanshu-jhacustom value allowed
  • Allow effectsallow_effects

    Set true to explicitly authorize executing the target. Off by default for every target because an effect-read-only tag is only a claim, not a sandbox.

    optionalstringdefault falseexample truecustom value allowed

What it changes

No write operations are declared in this version's manifest.

Credentials remain in the recipient's local rote vault; this page and the publisher never receive them.

Runtime details
  • rote CLIversion 0.62.0 or newer
  • Servicesnone declared
  • Digestsha256:779eeff0419ff03c65936d1a926353cd0cb53d361f06b5d6b3442626fe2554c5
  • Archive size10780 bytes
  • Published2026-09-04T15:14:29.011354+00:00
  • Published withrote 0.79.0

Credential values and current readiness remain local. Opening this page never prompts for a credential, opens an authorization browser, or calls a service this play uses.

A play is a published, versioned automation package that runs on your own machine through rote, a free command-line tool. Opening this page installs nothing and runs nothing.