docs(engine): document the Rent-a-Loop pipeline modules

[davion-knight]

Closes #5813.

Adds a ## Rent-a-Loop pipeline section to packages/loopover-engine/README.md documenting the three pure customer-facing modules that had zero README coverage — idea-intake.ts (#4779), loop-progress.ts (#4800), results-payload.ts (#4801) — in the same per-module style as the rest of the package README (explanation + key exported types + a runnable snippet each).

Docs-only — a single .md file, no code changed. Per codecov.yml, coverage is only collected over src/** / packages/loopover-engine/src/** / packages/loopover-miner/lib/**, so no Codecov gate fires (expected).

Deliverable

One umbrella section (idea → running loop → delivered result) with three subsections:

• idea-intake — validateIdeaSubmission → buildTaskGraph → scoreTaskGraph → buildClaimPlan; documents IdeaSubmission, TaskGraph, TaskGraphScore, ClaimPlan, and the text-cap constants.
• loop-progress — buildProgressSnapshot + progressChanged; documents LoopPhase, LoopRunStatus, ProgressSnapshot, MAX_PROGRESS_ACTIVITY.
• results-payload — buildResultsPayload; documents IterationResult, ResultsPayload, MAX_DIFF_PREVIEW_FILES.

It states explicitly that all three are pure/side-effect-free (no IO, network, wall-clock, or random reads), per the issue.

Validation

• All exported type/field names cross-checked against the three source files (incl. the IdeaValidationResult discriminated union and ClaimPlan disposition buckets).
• Every snippet was executed against the real module source (via tsx) — the commented outputs (scoreTaskGraph verdict, ClaimPlan buckets, the ProgressSnapshot incl. percentComplete: 40, and the ResultsPayload summary/totals) are the actual returned values, not hand-written.

[superagent-security]

Superagent didn't find any vulnerabilities or security issues in this PR.

[loopover-orb]

Tip

🟩🟩🟩🟩🟩🟩🟩🟩🟩🟩🟩🟩

✅ LoopOver review result - approve/merge recommended

_{Review updated: 2026-07-14 20:31:51 UTC}

1 file · 1 AI reviewer · no blockers · readiness 100/100 · CI green · clean

✅ Suggested Action - Approve/Merge

• safe to merge

Review summary
This is a pure documentation addition to packages/loopover-engine/README.md, adding a new 'Rent-a-Loop pipeline' section that documents three previously-undocumented pure modules (idea-intake, loop-progress, results-payload) in the same explanation+types+snippet style as the rest of the README. I cross-checked the results-payload snippet against the actual buildResultsPayload source and existing test suite (summary format, diffPreview truncation, totals roll-up) and the shown output values are correct. No code changes, so no functional risk; the PR closes issue #5813 as claimed.

Nits — 5 non-blocking

• The README is now roughly 840 lines per the size-smell scan; consider whether per-module doc sections should eventually move to separate docs files, though this is consistent with the existing file's style.
• The `idea-intake.ts` snippet doesn't show the `errors` branch of `IdeaValidationResult` (only the `ok: true` path), so a reader doesn't see what a rejected submission looks like.
• Consider a one-line cross-reference from this new section to the existing 'intake bridge (Idea-intake API/MCP tool #4798)' code comment context, since the README text mentions it implicitly but doesn't link it.
• For `loop-progress.ts`, a short example of `progressChanged(prev, next)` returning `false` for a no-op update would round out the pure-function contract shown.
• Diff looks like trivial or whitespace-only churn — Reduce whitespace-only or formatting-only churn and keep the diff focused on substantive changes.

Signal	Result	Evidence
Code review	✅ No blockers	1 reviewer
Linked issue	✅ Linked	#5813
Related work	✅ No active overlap found	No same-issue or scoped active PR overlap found.
Change scope	✅ 20/20	Low review scope from cached public metadata (1 linked issue).
Validation posture	✅ 25/25	PR body includes validation/test evidence.
Contributor workload	✅ 10/10	Author activity: 121 registered-repo PR(s), 86 merged, 0 issue(s).
Contributor context	✅ Confirmed Gittensor contributor	davion-knight; Gittensor profile; 121 PR(s), 0 issue(s).
Gate result	✅ Passing	No configured blocker found.
Improvement	⚠️ ℹ️ Insufficient signal	risk: low · value: insufficient-signal — Nothing measurable for the structural-improvement analyzers on this PR (e.g. no code files changed). LLM value judgment: moderate — This closes a documented gap (issue #5813) for three previously-undocumented pure modules with verified, executable snippets in the existing README style, which is a genuine and well-scoped (if modest) improvement to contributor-facing docs.

Linked issue satisfaction

Addressed
The PR adds a single 'Rent-a-Loop pipeline' section with three subsections covering idea-intake, loop-progress, and results-payload, each with a short explanation, key exported types, and a runnable usage snippet, matching the style of existing sections and explicitly noting the modules' pure/side-effect-free nature as requested.

Review context

• Author: davion-knight
• Role context: outside_contributor
• Public audience mode: oss maintainer
• Lane context: Repository is configured for direct PR review.
• Public profile languages: not available
• Official Gittensor activity: 121 PR(s), 0 issue(s).
• PR-specific overlap: none found.

Contributor next steps

• Keep the PR focused and include validation evidence before maintainer review.

Signal definitions

• Related work = same linked issue, overlapping active PRs, or title/path similarity.
• Change scope = cached public metadata such as size labels, draft state, and review-burden hints.
• Validation posture = whether the PR provides enough public validation/test evidence for maintainer review.
• Contributor workload = public contributor activity and cleanup pressure, not a repo-wide quality failure.
• Contributor context = public GitHub/Gittensor identity context; non-Gittensor status is not a blocker.

[BETA] Chat with Gittensory

Ask Gittensory a question about this PR directly in a comment — grounded only in the same cached, public-safe facts shown above, never a new claim.

• @gittensory ask <question> answers contribution-quality Q&A with source citations and freshness.
• @gittensory chat <question> answers in natural prose from cached decision-pack facts via local inference (maintainer/collaborator; read-only).
• A plain-language @gittensory mention with a real question is routed to the closest matching read-only command automatically -- no exact syntax required.

Full command reference: https://gittensory.aethereal.dev/docs/gittensory-commands

_{🟩 Safe / merged · 🟦 Advisory · 🟨 Held for review · 🟥 Blocked / closed}

---

💰 Earn for open-source contributions like this. Gittensor lets GitHub contributors earn for the work they already do — register to start earning →.

Checked by LoopOver, a quiet PR intelligence layer for OSS maintainers.

• Re-run LoopOver review

[loopover-orb]

Gittensory approves — the gate is satisfied and CI is green.