Context
The 2026-05-21 docs-noob-tester report (discussion #33700) flagged a critical, blocking issue at step zero:
The server was not running when I started the task. I had to manually start it using the lifecycle management instructions.
Impact: Complete blocker — cannot test documentation without a running server.
The instructions say "the documentation server is already running at ..." — but it isn't. Every new-user pass spends turns getting unstuck before they can even evaluate docs quality.
Quick-win task
- Add an explicit
Start docs server step at the top of docs-noob-tester.md (and any peer that consumes the local docs site) that runs the project's make docs-serve (or equivalent) in the background.
- Add a wait-for-port readiness probe before the agent step kicks off.
- Update the agent prompt so the assumption ("server is running") matches reality.
Success criteria
- Next docs-noob-tester run reports no "docs server not running" critical issue.
- The agent's narrative starts with content evaluation, not infra recovery.
References
Generated by 🔬 DeepReport - Intelligence Gathering Agent · ● 17.9M · ◷
Context
The 2026-05-21 docs-noob-tester report (discussion #33700) flagged a critical, blocking issue at step zero:
The instructions say "the documentation server is already running at ..." — but it isn't. Every new-user pass spends turns getting unstuck before they can even evaluate docs quality.
Quick-win task
Start docs serverstep at the top ofdocs-noob-tester.md(and any peer that consumes the local docs site) that runs the project'smake docs-serve(or equivalent) in the background.Success criteria
References