rig 3.19.0

A lesson loop at close: rig-learn offers the catalogue's check field and its prose (#173)

A lesson loop at close: rig-learn offers the catalogue's check field and its prose

Tickets: #172

Direction

A lesson review is a gate recorded on the work, like the ticket decision, not a prompt inside rig close. AGENTS.md already explains why: no rig command waits for a human, and close deletes the worktrees a repo lesson would have to be committed in.

• rig-learn skill, shipped in skills/ beside rig and rig-handoff. It reads the whole story (context.md, handoff.md, PR review threads, CI failures and re-runs, the commit log) and offers each lesson a home:
  1. the catalogue: a check command when a machine can verify it, else prose;
  2. an attached repo: a test or CI step first, else its docs, landing in the work's last PR, or a small follow-up PR;
  3. rig itself: an issue in rig's tracker when the lesson is about the tool.
• Order of preference is /harness-learn's: a machine check over prose, and never a new rule.
• Prefer correcting a wrong sentence to appending a new one; check the entry first.
• Route each lesson to the data root its reader can see; preferences about how the user works go to agent memory, not the catalogue.
• Scale by reach: a one-repo, one-PR work gets one question; a staged, multi-repo work gets the full walk.
• The gate: rig save --learned records it, including a review that found nothing worth keeping. It may be passed after the close and is refused on an abandoned work. rig next offers the skill once a PR is open, above the close offer; rig close names an unreviewed work and never refuses.

Not chosen: a prompt inside rig close (it tears the worktrees down and exits).

Context doc: https://github.com/hugoforte/rig-data/blob/main/work/rig-learn/context.md

Fixes #172

Full changelog: v3.18.0...v3.19.0