dev-tools-setup-note: Dev tools setup note #2
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "task/dev-tools-setup-note"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Assigned idea
Benchmark authoring specification.
Summary: Author a deterministic documentation change for Hunch It that clarifies how contributors enable deterministic local testing with dev tools and verify the TypeScript check.
Task intent: Improve CONTRIBUTING.md so upstream contributors can clearly understand that deterministic local testing requires setting ENABLE_DEV_TOOLS=true in the root .env before using /dev-tools, and that pnpm typecheck is one of the expected pre-share checks.
Benchmark plan: Construct a regular documentation-change package against the pinned repository commit. The solver-facing prompt should ask for a focused update to CONTRIBUTING.md only, preserving the existing setup and development basics structure while making the deterministic local testing note and pnpm typecheck requirement clearer. Do not ask for unrelated code changes.
Environment plan: The repo environment should install dependencies with pnpm on Node.js >= 20 if available, matching the contributor prerequisites. The task environment does not need a database or container runtime because the expected change is documentation-only; separate this from the full repo environment described in CONTRIBUTING.md for pnpm dev, pnpm start, and pnpm db:push.
Verifier plan: Create test_outputs.py to inspect CONTRIBUTING.md. It should assert that the file still mentions pnpm typecheck, ENABLE_DEV_TOOLS=true, /dev-tools, and the root .env. It should also assert that the change is confined to CONTRIBUTING.md by checking git diff --name-only. Optionally run pnpm typecheck only if dependencies are already installed; the required deterministic verifier is the file-content and diff-scope check.
Oracle plan: The oracle solution should edit CONTRIBUTING.md near Setup or Development Basics to add a concise note such as: for deterministic local testing, set ENABLE_DEV_TOOLS=true in the root .env before starting the app, then sign in and open /dev-tools; before sharing changes, run pnpm typecheck from the repository root. No application code changes are needed.
Difficulty plan: Current coding systems may overreach by modifying startup scripts, adding tests, or touching environment files instead of making the small documentation clarification. They may also miss the requirement that the check command is pnpm typecheck or place the note somewhere that disrupts the existing contributor guide.
Repo patch scope: Expected edits are limited to CONTRIBUTING.md.
Anti-leakage notes: Solver-facing text must not mention benchmark, harness, Snorkel, Harbor, std-ts, agent, stage, attempt, retry, generated task, or evaluation context.
Approach: Use the existing CONTRIBUTING.md wording as the source of truth, then make a minimal contributor-guide clarification without changing project behavior.
Verification: Run python test_outputs.py. The verifier should check CONTRIBUTING.md content and ensure git diff --name-only reports only CONTRIBUTING.md.
Risk: Low risk because the package is documentation-only; the main risk is an overly broad or speculative edit that changes setup semantics not supported by the repository evidence.
Path rules: task package is tasks/; mutable upstream checkout is tasks//environment/repo; benchmark package files are under tasks//task; verifier/container environment belongs under tasks//task/environment; regular and UI verifier logic belongs in task/tests/test_outputs.py and test.sh only runs that file through pytest.
Agent context
Task slug: dev-tools-setup-note
Branch: task/dev-tools-setup-note
View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.Merge
Merge the changes and update on Forgejo.Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.