Add rationale comment to gittensory/metagraphed's aiReview.closeConfidence: 0.95 (VPS)

[JSONbored]

Context

src/rules/advisory.ts:912 hardcodes DEFAULT_AI_REVIEW_CLOSE_CONFIDENCE = 0.93. jsonbored__gittensory.gittensory.yml:152 and jsonbored__metagraphed.gittensory.yml:172 both silently raise this to 0.95 with zero comment; jsonbored__awesome-claude.gittensory.yml:149 sets 0.93 (a no-op restatement of the default). This is a genuine, deliberate per-repo override (confirmed not inherited — global sets no aiReview/closeConfidence key at all) that survived a recent "restored 2026-07-09" pass which carefully re-commented every other overridden field in the same block, but skipped this one. Bonus: gittensory's mode: block comment claims "matching metagraphed/awesome-claude" — which is actually untrue for closeConfidence (0.95 vs awesome-claude's 0.93), so the adjacent comment's implied full-parity claim is itself slightly misleading.

Requirements

• Direct edit to the private dedicated-server config, not a GitHub PR.
• If the 0.95 raise wasn't actually deliberate, reverting to the implicit 0.93 default is an acceptable alternative outcome — use judgment, don't just paper over it with a comment if the value itself looks wrong.

Deliverables

• Add a dated rationale comment on both 0.95 lines (closeConfidence: 0.95 # <date>: intentionally stricter than the 0.93 default/awesome-claude — <reason>), OR revert to the implicit default if the raise wasn't deliberate.

Expected Outcome

The closeConfidence override (or lack thereof) on each of the 3 repos is deliberate and explained, matching the annotation quality of every sibling field in the same block.

Links & Resources

• Evidence: src/rules/advisory.ts:912; jsonbored__gittensory.gittensory.yml:152; jsonbored__metagraphed.gittensory.yml:172; jsonbored__awesome-claude.gittensory.yml:149

---

Part of #5270 (roadmap epic).

[linear-code]

JSO-3772

[JSONbored]

Applied directly to jsonbored__gittensory/.gittensory.yml and jsonbored__metagraphed/.gittensory.yml on the dedicated server, 2026-07-12 (same backup timestamp as #5275). Added a comment on both closeConfidence: 0.95 lines confirming it's a real, deliberate, non-default override — but honestly, the ORIGINAL reason for 0.95 over the 0.93 default couldn't be found anywhere, so the comment says that plainly rather than inventing a justification. Left the value as-is (0.95) since it's clearly deliberate, not accidental.