Skip to content

Relocate misplaced hardGuardrailGlobs rationale comment in gittensory's config (VPS) #5278

Description

@JSONbored

Context

gittensory's private hardGuardrailGlobs was cut from global's 38 entries to 8 (workflows/actions/wrangler only), dropping every lockfile glob — unlike metagraphed (38+6) and awesome-claude (exact 38). A rationale comment for this shrink ("Lightened 20260708 (per-user directive)... Lockfiles... now go through normal review... pipeline") exists but sits directly above the unrelated linkedIssueLabelPropagation: block, while hardGuardrailGlobs: itself has no comment at all. A reader would misattribute the rationale to label propagation and find the actual 38→8 glob cut silently undocumented.

Requirements

  • Direct edit to the private dedicated-server config, not a GitHub PR.
  • Comment relocation only — no config-value change.

Deliverables

  • Move the "Lightened 20260708" comment block down to sit directly above hardGuardrailGlobs: in jsonbored__gittensory.gittensory.yml (currently at line 81), and restore a blank line before linkedIssueLabelPropagation:.

Expected Outcome

The rationale for gittensory's narrower guardrail-glob set is attached to the actual key it explains.

Links & Resources

  • Evidence: jsonbored__gittensory.gittensory.yml:60-65 (comment ends before linkedIssueLabelPropagation:) vs :81-89 (the actual, uncommented glob cut); contrast jsonbored__metagraphed.gittensory.yml:91-137 (correctly-placed comment at 131-132)

Part of #5270 (roadmap epic).

Metadata

Metadata

Assignees

Labels

maintainer-onlyOwner-only work — yields no Gittensor points.

Projects

Status
Done

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions