Context
All 3 per-repo private configs set regateSweepOrderMode: oldest-first, and 2 of 3 carry near-identical comments explicitly framing this as deliberate cross-repo parity ("mirrors awesome-claude's existing setting so all 3 gated repos share the same sweep ordering," #3815). global.gittensory.yml never sets this key; the code/DB default is staleness (src/db/schema.ts:56, src/db/repositories.ts:526,731).
resolveRepositorySettings overlays yml onto DB settings, feeding orderMode directly into selectRegateCandidates (src/queue/processors.ts:1394). A future 4th repo, or one of the existing 3 if its file is ever lost or fails to parse, silently falls back to staleness ordering instead of the documented-as-intended FIFO. Affects sweep order only, not gate/merge/close correctness.
Requirements
- Direct edit to the private dedicated-server config, not a GitHub PR.
- No behavior change for existing repos expected (per-repo override still wins) — this only closes the silent-fallback gap.
Deliverables
Expected Outcome
A future repo (or any existing repo losing its override) falls back to the documented-as-intended FIFO sweep order instead of silently reverting to staleness ordering.
Links & Resources
- Evidence:
jsonbored__gittensory.gittensory.yml:19-21, jsonbored__metagraphed.gittensory.yml:20-22, jsonbored__awesome-claude.gittensory.yml:16; src/db/schema.ts:56; src/db/repositories.ts:526,731
Part of #5270 (roadmap epic).
Context
All 3 per-repo private configs set
regateSweepOrderMode: oldest-first, and 2 of 3 carry near-identical comments explicitly framing this as deliberate cross-repo parity ("mirrors awesome-claude's existing setting so all 3 gated repos share the same sweep ordering," #3815).global.gittensory.ymlnever sets this key; the code/DB default isstaleness(src/db/schema.ts:56,src/db/repositories.ts:526,731).resolveRepositorySettingsoverlays yml onto DB settings, feedingorderModedirectly intoselectRegateCandidates(src/queue/processors.ts:1394). A future 4th repo, or one of the existing 3 if its file is ever lost or fails to parse, silently falls back tostalenessordering instead of the documented-as-intended FIFO. Affects sweep order only, not gate/merge/close correctness.Requirements
Deliverables
settings.regateSweepOrderMode: oldest-firsttoglobal.gittensory.yml, referencing feat(regate-sweep): add opt-in oldest-first ordering mode to selectRegateCandidates #3815, noting it codifies the value all 3 managed repos already set.Expected Outcome
A future repo (or any existing repo losing its override) falls back to the documented-as-intended FIFO sweep order instead of silently reverting to staleness ordering.
Links & Resources
jsonbored__gittensory.gittensory.yml:19-21,jsonbored__metagraphed.gittensory.yml:20-22,jsonbored__awesome-claude.gittensory.yml:16;src/db/schema.ts:56;src/db/repositories.ts:526,731Part of #5270 (roadmap epic).