Product

QA for thin Runs

How grokbot.sh QA works: tagged jobs stamp immediately, then a follow-up pass fills in the thread and writes a public copyable prompt from the specific job; a daily cron still strengthens every published Run; the Owner can tag a weak page and revisit the source thread.

Owner can flag a thin run. A revisit agent re-reads the source thread and writes findings here.