Earlier downstream carries drifted from the current repo-config and merge-bot reference

Noticed while sourcing the Vantage-Config carry (Vantage-Config #9) from the current hub reference; the next adoptee copying from a sibling instead of the hub would clone stale shapes:

PlexCleaner, LanguageTags, Utilities: repo-config uses the old ruleset-develop.json / ruleset-main.json naming (current reference: develop.json / main.json; audit.py letter-checks the new paths).
MediaTools: repo-config carry is partial (develop.json + main.json only; no README.md, configure.sh, settings.json).
MediaTools: merge-bot uses gh pr merge --auto --delete-branch and older comment wording; the current reference dropped --delete-branch.

Per the "fix systemic drift in the hub" rule this is one drift class across several repos - flagging here rather than patching each.

One more drift instance in the same class: carried AGENTS.md files can URL-link the hub registry (Vantage-Config's did: "see the fleet workflowModel" linked https://github.com/ptr727/ProjectTemplate/blob/main/registry/repos.json), violating the plain-text-hub-mentions carry rule - the link 404s without hub access. Fixed locally in Vantage-Config (4bf7c4d); other carries likely share it, and the hub's AGENTS.md template may want a carry-safe plain-text form.

Vantage adoption follow-ups: every-tier bots wording, registry, carry…

Swept: all four repos are now on the current repo-config and merge-bot reference, each via a Copilot-reviewed PR to develop (squash-merged, signed, CI green, all review threads resolved):

PlexCleaner Promote Copilot Skill Link Fix #854: ruleset-*.json renamed to develop.json/main.json, README/configure.sh/settings.json refreshed, merge-bot synced (had --delete-branch too), self-audit carry added (AUDIT.md + spec/secrets.json, docker-hub + codecov).
LanguageTags docs: restructure codecov snippet comments to the summarized style #278: same rename/refresh, merge-bot synced keeping the codegen job, self-audit carry added (nuget-oidc + codecov); follow-up commit reconciled its repo-specific WORKFLOW.md (5D and section 6 now point at the AUDIT.md self-audit instead of the removed configure.sh check/apply; NUGET_USERNAME documented both-stores).
Utilities Gate the Docker push on all builds; require validate-release (#414 Q4) #417: same rename/refresh + merge-bot sync + self-audit carry (nuget-oidc + codecov).
MediaTools Mediatools #19: partial carry completed (README/configure.sh/settings.json added; develop.json/main.json were already byte-identical to the reference), merge-bot --delete-branch dropped, self-audit carry added (nuget-oidc + codecov).

Two findings beyond this issue's list, confirmed during the sweep:

ALL four repos' merge-bots carried --delete-branch, not just MediaTools; all synced.
Live rulesets, settings, and secret names were verified in sync with the reference payloads on all four repos before the sweep (normalized diffs), so the sweep was committed-files-only - no live configuration was touched.

The self-audit carries adapt the blessed Vantage-Config reference per #331/#333; the fleet audit's new AUDIT.md + spec/secrets.json letter-checks now pass on these four. Reference-hardening nits raised by the downstream Copilot reviews are bundled into #332 rather than filed singly.

configure.sh model inference on carries; harden ruleset snippets (#334)

Navigation Menu

Repository navigation

Earlier downstream carries drifted from the current repo-config and merge-bot reference #330

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

Earlier downstream carries drifted from the current repo-config and merge-bot reference #330

Description

Activity

ptr727 commented on Jul 16, 2026

ptr727 commented on Jul 16, 2026

Metadata

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

Issue actions