Context
jsonbored__gittensory.gittensory.yml:137 and jsonbored__metagraphed.gittensory.yml:157 both set gate.linkedIssue: block with no comment; jsonbored__awesome-claude.gittensory.yml:127 sets gate.linkedIssue: advisory, also with no comment — while the sibling manifestPolicy: advisory deviation two lines below it (136-142) gets a 7-line justification. This is a real, currently-live functional difference (advisory never hard-blocks for a missing linked issue). Note: awesome-claude's value actually just matches the deployment-wide default (global.gittensory.yml:8) — it's gittensory/metagraphed that positively override up to block, and neither of those lines is commented either, so this isn't a unique outlier, just the most conspicuous gap in the most heavily-annotated of the three files.
Worth fixing anyway: linkedIssuePolicy and gate.linkedIssue are independent knobs with real prior-bug history (#4618: a mismatch between them once silently no-op'd) — worth calling the pairing out explicitly even though today's values are coherent (optional-issue, content-submission repo → advisory gate).
Requirements
- Direct edit to the private dedicated-server config, not a GitHub PR.
Deliverables
Expected Outcome
A future editor of this file understands why linkedIssue is advisory here and not block, and the #4618 pairing risk is on record.
Links & Resources
- Evidence:
jsonbored__awesome-claude.gittensory.yml:127 vs :136-142; jsonbored__gittensory.gittensory.yml:137; jsonbored__metagraphed.gittensory.yml:157
Part of #5270 (roadmap epic).
Context
jsonbored__gittensory.gittensory.yml:137andjsonbored__metagraphed.gittensory.yml:157both setgate.linkedIssue: blockwith no comment;jsonbored__awesome-claude.gittensory.yml:127setsgate.linkedIssue: advisory, also with no comment — while the siblingmanifestPolicy: advisorydeviation two lines below it (136-142) gets a 7-line justification. This is a real, currently-live functional difference (advisory never hard-blocks for a missing linked issue). Note: awesome-claude's value actually just matches the deployment-wide default (global.gittensory.yml:8) — it's gittensory/metagraphed that positively override up toblock, and neither of those lines is commented either, so this isn't a unique outlier, just the most conspicuous gap in the most heavily-annotated of the three files.Worth fixing anyway:
linkedIssuePolicyandgate.linkedIssueare independent knobs with real prior-bug history (#4618: a mismatch between them once silently no-op'd) — worth calling the pairing out explicitly even though today's values are coherent (optional-issue, content-submission repo → advisory gate).Requirements
Deliverables
linkedIssue: advisoryinjsonbored__awesome-claude.gittensory.ymltying it explicitly tolinkedIssuePolicy: optional(line 115) and noting the Reduce redundant config surface: linked-issue knob, gateCheckMode, label fields #4618 prior-bug context.Expected Outcome
A future editor of this file understands why
linkedIssueisadvisoryhere and notblock, and the #4618 pairing risk is on record.Links & Resources
jsonbored__awesome-claude.gittensory.yml:127vs:136-142;jsonbored__gittensory.gittensory.yml:137;jsonbored__metagraphed.gittensory.yml:157Part of #5270 (roadmap epic).