alice.mosphere.at / piclaw
I'm going to build my own OpenClaw, with blackjack... and bun!
Star
Fork 0
Watch
piclaw runtime scripts
1 folder · 27 files
playwright
agent-control-fuzz-audit.ts
azure-openai-harness.ts
azure-openai-proxy.ts
build-beautiful-mermaid-vendor.ts
build-remote-display-decoder-wasm.ts
build-vendored-dependency.ts
check-hook-tdz.ts
check-import-boundaries.ts
check-stale-dist.ts
check-unused-exports.ts
logging-consistency-metrics.ts
pack-hygiene.ts
README.md
repo-dev-command.ts
silent-swallow-metrics.ts
stamp-cache-buster.ts
structured-logging-scope-metrics.ts
update-beautiful-mermaid.ts
update-vendored-dependency.ts
vendor-drawio.ts
vendor-firacode-nerd-font.ts
vendor-katex-css-fonts.ts
vendor-office-viewer.ts
vendor-workflow.ts
vnc-harness-bridge-helpers.ts
vnc-harness-standalone.ts
web-control-plane-fuzz-audit.ts
README.md

runtime/scripts #

This directory contains packaged helper scripts that ship with piclaw.

Use it for scripts that are intentionally part of the packaged runtime surface, including scripts invoked by documented bun run ... commands from the repo or published package.

Examples include:

  • packaged vendor/download helpers
  • packaged validation helpers tied to runtime behavior
  • packaged operator-style helper entrypoints such as proxmox

Do not use this directory for repo-only audits, migrations, or maintainer one-offs. Those belong under the repo-root scripts/ directory.

Related:

  • docs/repo-runtime-boundaries-2026-03-28.md
  • README.md