Reproduce the kitchen input
BENCHMARK CANDIDATE INPUT / V2
This is the exact candidate prompt for the separately prepared kitchen harness. It is not a general Lintel installation prompt or authorization to start a benchmark. Use only a fresh, correctly prepared candidate with the identical approved brief, runtime, fixtures and starter.
Exact shared prompt
Implement the complete Service House website from the approved BRIEF.md and RUNTIME.md, using fixture.json and selectors.json. The product requirements are already decided: make an implementation plan, then build and verify the application; do not stop after planning or repeat a requirements interview. Use the workflow configured in this repository and preserve its required independent reviews. Implement with vanilla HTML, CSS and JavaScript modules. A controller-owned local server serves public/ and /fixture.json at the URL in BENCHMARK-RUNTIME.json; do not start another server or change the infrastructure, fixtures or requirements. Work incrementally with small edits: keep every tool request below 4096 UTF-8 bytes, and never delete a working file before its replacement is safely written. Respect all normal host permissions; report unexpected permission-transport failures rather than bypassing them. Use only headless browser verification; Playwright is pinned in package.json and can be installed with npm ci --offline if needed. Do not read other workspaces, previous sessions/results, coordinating transcripts, graders or reference implementations. Do not install agent workflows or publish remotely. When all work and required reviews are finished, run node BENCHMARK-SUBMIT.mjs once and then stop. If blocked, report the actual blocker without submitting a ready marker. Do not ask product follow-up questions; make reasonable implementation decisions within the approved specification.
Download exact prompt · Product brief · Runtime contract
Read the brief with runtime v2. The controller owns the server; the candidate submits through BENCHMARK-SUBMIT. The older brief’s server-start paragraph is superseded.
Product requirements are fixed. The configured workflow supplies the treatment; required independent reviews remain part of the work. Fresh sessions alone do not establish isolation from user-global instructions.