The harvest loop

harvest-game and harvest-full-game build a game to expose engine gaps. This skill drops the game: the carrier is whatever task you were handed. The task still ships — but a harvest run is never just the task. You do the task and you make the engine better as much as you can while you're in there, because doing real work is the best gap-finder there is.

Two deliverables, both required: the task done, and the engine improved. A run that only does the task and leaves no engine trace missed the point; a run that improves the engine but drops the task failed the user. Hit both.

Take the invocation argument and resolve the work:

• A concrete task named (fix, feature, refactor, question, doc pass, investigation) → that's the carrier. Do it.
• A link (issue, PR, file, error) → read it for what's actually being asked, then do that. A [FEATURE] gap issue is a natural carrier — close the gap is the task.
• Nothing / "find something" → pull from the standing gap list: open [FEATURE] issues on this repo (search_issues), plus any TODO/doc-drift you already know about. Pick one whose fix teaches the most about the engine surface.

Then run the loop in this session: