Table of contents
LS workbench
Personal tooling of one contributor, public repository. Not an official or endorsed Longshot service.
LS workbench is a Linux test bench for contributors and coding agents. It supplies run wrappers, resource gates, scripted play, evidence readers, regression tools and nightly tooling. It includes no game, saves or built game. You need your own legally obtained game and build.
Get started
- Read the README and agent brief. Review the scripts before using them. The brief describes one contributor's environment, not requirements for every developer.
- Follow the README's Using it on another machine section. Adapt its example paths and resource limits to your own machine. The relocation helper rewrites checkout text, not installed files or live configuration. The gates assume Linux; the window helper is specific to Hyprland.
- Make your own owned build and disposable run directories. Keep player installations and original saves separate. Start with ls-workbench, which describes building, windowless runs and checks. A wrapper returning successfully does not prove the game succeeded: read the game's exit receipt.
- Choose from the thirteen skills: build/run, PR evidence, performance comparison, performance monitoring, scripted play, issue triage, team updates, regression hunting, nightly testing, PR follow-up, function lookup, skill upkeep and field data. They are Markdown instructions; people can read them too.
- Before investigating lifted code, use the function-map guide and ls-function-map. Entries distinguish tested facts, code-reading conclusions and guesses. Keep generated code and game-derived files private; do not copy map rows into the wiki.
- Add the optional workbench MCP server only after its operator configuration is understood.
Know the limits
harness/ runs and records; gates/ controls shared resources; play/ drives inputs; regress/ tests suspected regressions; perf/ reads sampled context; nightly/ retains repeated-check evidence. Ordinary runs and sampled readings are not speed proof. Use the performance-comparison skill for controlled comparisons.
The published names are ls-*, ls-workbench, ls-wb and LS_WB_*. Older helper filenames remain intentional. A rename does not migrate a live installation or make GitHub-backed CI and request tools understand Forgejo. The nightly guide lists which scenario families remain unvalidated; its presence is not an always-on test-service promise.