Static status badge · SVG · read-only JSON. Embed with .
The pinned commit has no runnable code or documented command. The referenced quickstart, requirements, package.json, and healthcheck files are missing.
Answers apply to each recorded setup, revision and operation. Earlier observations remain in Run details.
latest result was harness_error; rerun on the current test runtime (, caps, sandbox)
Repair record fix-755430892b566134b8b8 · current status JSON. Original run outcomes remain unchanged.
Failed run: zhan266/sql-forge-generator · Oct 17, 2026 · Recorded operation failed.
Repair development: zhan266/sql-forge-generator · Oct 17, 2026 · Repair work (development) · not an initial-trial result.
Test-repair rerun: zhan266/sql-forge-generator · Oct 18, 2026 · Unsupported in this smoke.
Operation / attempted scope Not exercised. The checkout has no runnable product: no requirements.txt, package.json, docs/quickstart.md, docs/troubleshooting.md, tests/, benchmarks/, CLI, or --healthcheck entrypoint. Only README.md, index.html, two SVGs, and a .github directory are present. Node/npm are not installed in the VM (python3 3.12.3 is). Shared CDP endpoint is set (CDP_URL/<env-var>=http://<internal-ip>:9226) but was not needed.
Agent-reported scope: Attempted README-documented setup (install/build/run) and one useful operation (MCP start + tools/list) for QueryForge at pinned commit 2d52d3e30cb1d024218cd077a7e8e690f8247b05.
latest result was harness_error; rerun on the current test runtime (, caps, sandbox)
Repair record fix-755430892b566134b8b8 · current status JSON. Original run outcomes remain unchanged.
Failed run: zhan266/sql-forge-generator · Oct 17, 2026 · Recorded operation failed.
Repair development: zhan266/sql-forge-generator · Oct 17, 2026 · Repair work (development) · not an initial-trial result.
Test-repair rerun: zhan266/sql-forge-generator · Oct 18, 2026 · Unsupported in this smoke.
Fix: fix-755430892b566134b8b8.
Step: README.md 'Getting Started: Your First Query Forge' step 2 'Setup the Environment' and step 3 'Run the Self-Test' (--healthcheck); the referenced install files and entrypoint do not exist in the checkout.
The pinned commit contains only documentation and marketing assets. No installable package, build target, or MCP/CLI/HTTP entrypoint exists, so there is nothing to install, start, or list tools from.
Suggested next step (agent-reported): Push the actual QueryForge source (requirements.txt/package.json, docs/quickstart.md, the CLI or server entrypoint with --healthcheck) at a commit that matches the README, or update the README to match the code, then re-pin. Separately, review .github/workflows/aFPFOTFdPSbhEs.yml before trusting this repo: it is a scheduled job with randomized delays that writes a stamp file and pushes commits to main with the contents token, which looks like commit-activity automation rather than product tooling. I did not run it. index.html also contains large hidden base64 blobs that I did not decode.
Attempted README-documented setup (install/build/run) and one useful operation (MCP start + tools/list) for QueryForge at pinned commit 2d52d3e30cb1d024218cd077a7e8e690f8247b05.
run JSON · checker evidence · agent report + check · transcript excerpt · error excerpt
No product verdict. Run record.
No product verdict. Run record.
