docs(config): document shipped review.effort_score and changed_files_summary toggles

[luciferlive112116]

Closes #2069

Summary

• Replace the stale "Planned display toggle" placeholder for review.effort_score with shipped documentation in gittensory.full.yml and keep .gittensory.yml.example in sync.
• Document review.changed_files_summary alongside effort_score as unified-comment display toggles (Changed-files summary table in the unified review comment #1957 / Deterministic review-effort / complexity score + review-time ROI signal #1955).

Validation

• npx vitest run test/unit/config-templates.test.ts

UI Evidence

N/A

[superagent-security]

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

[loopover-orb]

Warning

🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨

⏸️ Gittensory review result - manual review recommended

_{Review updated: 2026-07-06 05:52:51 UTC}

3 files · 1 AI reviewer · no blockers · readiness 62/100 · CI green · clean

⏸️ Suggested Action - Manual Review

Review summary
This is a pure documentation change: it replaces the stale 'Planned display toggle (#2069)' placeholder with docs for the shipped `changed_files_summary` and `effort_score` unified-comment toggles, kept identical across `.gittensory.yml.example` and `config/examples/gittensory.full.yml`, plus a new test asserting both field markers are documented and the placeholder text is gone. The change is self-consistent, low-risk, and the added test (`config-templates.test.ts:59-65`) directly validates the doc content via regex against the actual file, with CI green. No logic, schema, or migration surface is touched.

Nits — 6 non-blocking

• The test only asserts the field markers exist as comments in `gittensory.full.yml`; it doesn't assert the two example files stay byte-identical for these lines, so future edits could let `.gittensory.yml.example` and `gittensory.full.yml` drift apart undetected.
• The PR description asserts these toggles are 'shipped' but the diff contains no pointer (code file/PR link) to the implementation — worth linking the implementing PR/commit for `effort_score` and `changed_files_summary` so reviewers can confirm the docs match actual behavior.
• Both edited example config files are now at/over the 400-line long-file threshold (401 and 414 lines) — not a blocker for a docs PR, but worth keeping in mind if the file keeps growing with every new toggle.
• Add a small equality check between the `review:` block text of `.gittensory.yml.example` and `gittensory.full.yml` (or generate one from the other) to guarantee they can't silently diverge going forward.
• Since feat(review): add review.effort_score toggle + "review effort: N/5 (~M min)" line in the unified comment #2069's coverage is only 'partial' per linked history, consider explicitly confirming in the PR description that the runtime toggle behavior was verified working before merging pure docs that assert it is 'shipped'.
• Readiness score is below the configured threshold — Use the readiness panel as advisory maintainer context; the score does not block this PR.

Signal	Result	Evidence
Code review	✅ No blockers	1 reviewer
Linked issue	✅ Linked	#2069
Related work	⚠️ 3 scoped overlaps	Top overlaps are listed below; lower-confidence bulk is hidden.
Change scope	❌ 8/20	High review scope from cached public metadata (1 linked issue).
Validation posture	❌ 5/25	Preflight is holding this PR: the review lane is unavailable, so it is not ready for automated review.
Contributor workload	✅ 10/10	Author activity: 180 registered-repo PR(s), 94 merged, 18 issue(s).
Contributor context	✅ Confirmed Gittensor contributor	luciferlive112116; Gittensor profile; 180 PR(s), 18 issue(s).
Gate result	✅ Passing	No configured blocker found.

Review context

• Author: luciferlive112116
• Role context: outside_contributor
• Public audience mode: oss maintainer
• Lane context: Repository registration is not available in the local Gittensory cache.
• Public profile languages: JavaScript, MDX, Python, Rust, TypeScript
• Official Gittensor activity: 180 PR(s), 18 issue(s).
• Related work: Titles/paths share 6 meaningful terms. (issue #2189, issue #2156)
• Related work: Titles/paths share 6 meaningful terms. (issue #2156, issue #2152)
• Related work: Titles/paths share 6 meaningful terms. (issue #2156, issue #2184)

Contributor next steps

• Review top overlaps.
• Add a concise scope and risk note.
• Await review-lane availability.
• Refresh registry data or choose a registered active repo.
• Check active issues and PRs before submitting.

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.

_{🟩 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 Gittensory, a quiet PR intelligence layer for OSS maintainers.

• Re-run Gittensory review

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 93.36%. Comparing base (762a569) to head (9f7d9d5).

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #3714   +/-   ##
=======================================
  Coverage   93.36%   93.36%           
=======================================
  Files         315      315           
  Lines       32204    32204           
  Branches    11812    11812           
=======================================
  Hits        30066    30066           
  Misses       1507     1507           
  Partials      631      631           

🚀 New features to boost your workflow:

• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[loopover-orb]

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