Ship branch rulesets as versioned JSON in the re-sync / drift loop by ptr727 · Pull Request #212 · ptr727/ProjectTemplate

ptr727 · 2026-06-26T16:52:21Z

Problem

Closes#211. Branch rulesets are live GitHub config applied once at repo creation, so they sit outside the file-based re-sync loop (AGENTS.md "Staying in Sync"). Two consequences: a corrected template ruleset never propagates to existing derived repos, and downstream ruleset drift is invisible. This bit ptr727/PlexCleaner — its synced docs said strict=false while its live rulesets stayed strict=true on both develop and main (the exact #82 failure mode), fixed locally only after it broke auto-merge and blocked a promotion.

Change

Canonical rulesets as committed files, maintained in this template only..github/rulesets/develop.json and .github/rulesets/main.json hold the re-importable writable subset ({name, target, enforcement, bypass_actors, conditions, rules}), strict_required_status_checks_policy: false on both. They port verbatim with no placeholders — conditions key on refs/heads/{develop,main}, bypass_actors uses the global Admin role actor_id: 5, the required check binds by name.
README "Rules / Rulesets" repoints the source of truth to these committed files: setup imports from them; the live export becomes the regenerate recipe run in the template when the maintainer changes the live rulesets.
AGENTS.md documents that the rulesets are deliberately not in the verbatim-carry set and are not carried/re-synced downstream as a per-repo copy — they are live config, not a file a derived repo consumes. They ride the re-sync loop from the hub: diff each derived repo's live rulesets against the template's committed JSON and correct drift via a full-payload PUT. The drift command normalizes rules[]/bypass_actors[] order so a reordered-but-equivalent ruleset doesn't read as drift.
Also folds in pending spell-dict / workspace-extension additions (and mirrors the two new general extensions into both devcontainers).

Verification

jq -S round-trip stable for both files; order-normalized drift diff against the template's own live rulesets reports develop: in sync / main: in sync.
Ran the drift check across all 8 derived repos (read-only): 6 in sync, Utilities has real live drift, homeassistant-purpleair has no rulesets configured — both surfaced to the maintainer (issues filed), not auto-applied.
markdownlint-cli2 clean on README.md and AGENTS.md (0 errors).

🤖 Generated with Claude Code

Closes the gap from #211: branch rulesets were live GitHub config applied once at repo creation, so they sat outside the file-based re-sync loop - a corrected template ruleset never propagated to derived repos, and downstream drift was invisible (PlexCleaner's docs said strict=false while live config stayed strict=true on both branches). - Commit the canonical writable subset as .github/rulesets/{develop,main}.json (strict_required_status_checks_policy false on both - the #82 value this exists to keep propagated). They port verbatim: conditions key on refs/heads/{develop,main}, bypass_actors uses global Admin role actor_id 5, the required check binds by name. - README "Rules / Rulesets": repoint the source of truth to the committed files - import from them at setup; the live export becomes the regenerate recipe run when the maintainer changes the template's live rulesets. - AGENTS.md: add the rulesets to the verbatim-carry set and document the live-vs-committed drift check (full-payload PUT to correct) in Staying in Sync. Note that carrying the file only syncs the source of truth; live config changes only on import/PUT. Also folds in pending spell-dictionary / workspace-extension additions and three deferred-item bullets that were already staged. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Copilot

Pull request overview

This PR brings branch rulesets into the repo-based re-sync/drift workflow by committing canonical develop/main ruleset JSON and updating documentation to treat those files as the versioned source of truth, plus minor editor/workspace hygiene updates.

Changes:

Add committed GitHub ruleset definitions for develop and main under .github/rulesets/.
Update README.md and AGENTS.md to import/sync rulesets from committed JSON and document how to detect/correct drift against live GitHub config.
Reformat and extend ProjectTemplate.code-workspace (spellings + recommended extensions).

Reviewed changes

Copilot reviewed 5 out of 5 changed files in this pull request and generated 1 comment.

Show a summary per file

File	Description
README.md	Updates ruleset setup docs to import from committed JSON; adds deferred-pattern notes.
ProjectTemplate.code-workspace	Normalizes formatting; adds cSpell words and extension recommendations.
AGENTS.md	Adds ruleset JSON to verbatim-carry list and documents drift-check procedure.
.github/rulesets/main.json	Introduces canonical `main` branch ruleset JSON (importable subset).
.github/rulesets/develop.json	Introduces canonical `develop` branch ruleset JSON (importable subset).

GitHub returns a ruleset's rules[] (and bypass_actors[]) in arbitrary order, so the plain diff false-positived on a reordered-but-equivalent ruleset (PlexCleaner's develop/main read as DRIFT when only the rule order differed). Sort both arrays before diffing so only real differences surface. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

The versioned rulesets are live GitHub config, not a file a derived repo consumes, so copying them into every downstream repo only adds noise and divergence. Drop them from the verbatim-carry set; document that they live only in the template as the source of truth and ride the re-sync loop from the hub - diffing each derived repo's live config against the template's committed JSON and correcting drift via full-payload PUT. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Copilot

Pull request overview

Copilot reviewed 5 out of 5 changed files in this pull request and generated 4 comments.

Two of the pre-staged Deferred Patterns are no longer deferred: - "Factor cleanup-artifacts into a reusable workflow" is moot - #214 removes the blanket cleanup job entirely (surgical consume-then-delete instead), so there is nothing left to factor. - "Generalize the input-validation step into a reusable pattern" is realized - #213 codifies the validate-input/state-at-entry pattern in AGENTS.md. Keep the publish-docker-readme "Validate inputs step" downstream-resync entry; that concrete downstream action is still pending. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

- Reword "never copied into derived repos" (README + AGENTS.md): the JSON is maintained in the template as the source of truth and reconciled against a repo's live config; it is not carried/re-synced as a per-repo copy. Avoids the inaccurate absolute (a template-instantiated repo does receive the files). - Mirror the two new general extensions (actionlint, shellcheck) into both devcontainers and fix the stale `*.code-workspace` reference (the per-language workspaces were consolidated into ProjectTemplate.code-workspace in #210). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

…s-versioned-json

Copilot

Pull request overview

Copilot reviewed 7 out of 7 changed files in this pull request and generated 4 comments.

 "customizations": {
 "vscode": {
- // Mirror of `recommendations` in Python.code-workspace.
+ // Mirror of `recommendations` in ProjectTemplate.code-workspace.


 "customizations": {
 "vscode": {
- // Mirror of `recommendations` in DotNet.code-workspace.
+ // Mirror of `recommendations` in ProjectTemplate.code-workspace.


+The branch rulesets ([`.github/rulesets/{develop,main}.json`](./.github/rulesets/)) are deliberately **not** in this carry set: they are live GitHub config, not a file a derived repo consumes, so carrying and re-syncing them downstream only adds noise. They are maintained **in this template** as the source of truth and are reconciled against each repo's *live* config during porting/re-sync - see [Staying in Sync](#staying-in-sync-and-reporting-drift-upstream).
+


 for name in develop main; do
 id=$(gh api repos/ptr727/ProjectTemplate/rulesets --jq ".[] | select(.name==\"$name\") | .id")
 gh api "repos/ptr727/ProjectTemplate/rulesets/$id" \
- --jq '{name, target, enforcement, bypass_actors, conditions, rules}' > "$name-ruleset.json"
+ --jq '{name, target, enforcement, bypass_actors, conditions, rules}' \
+ | jq -S '.' > ".github/rulesets/$name.json"


Promote the accumulated `develop` work to `main`. Twelve changes since the last promotion: - Add `WORKFLOW.md`: workflow style, architecture, behavioral contract, test methodology (#223) - Use NBGV `IGNORE_GITHUB_REF` instead of the ineffective `GITHUB_REF` override (#222) - Skip validate-release on smoke builds (#220) - Gate asset delete on the release create/refresh condition (#218) - Ship branch rulesets as versioned JSON in the re-sync / drift loop (#212) - Clean up transfer artifacts surgically at consumption, not blanket-delete (#216) - Version each publish leg against its own branch; validate at entry (#215) - Consolidate workspace configurations into a unified ProjectTemplate workspace (#210) - Template convergence barrier: absorb pins, generic release + docker-readme, carry-whole-file (#207) - Key merge-bot concurrency on PR number, not `github.ref` (#206) - Codify orchestrated re-sync personas and full-replacement rule (#205) - Lead action pins; affirm pattern-based artifact handoff (#204) 🤖 Generated with [Claude Code](https://claude.com/claude-code)

ptr727 · 2026-06-26T16:52:21Z

Problem

Closes#211. Branch rulesets are live GitHub config applied once at repo creation, so they sit outside the file-based re-sync loop (AGENTS.md "Staying in Sync"). Two consequences: a corrected template ruleset never propagates to existing derived repos, and downstream ruleset drift is invisible. This bit ptr727/PlexCleaner — its synced docs said strict=false while its live rulesets stayed strict=true on both develop and main (the exact #82 failure mode), fixed locally only after it broke auto-merge and blocked a promotion.

Change

Canonical rulesets as committed files, maintained in this template only..github/rulesets/develop.json and .github/rulesets/main.json hold the re-importable writable subset ({name, target, enforcement, bypass_actors, conditions, rules}), strict_required_status_checks_policy: false on both. They port verbatim with no placeholders — conditions key on refs/heads/{develop,main}, bypass_actors uses the global Admin role actor_id: 5, the required check binds by name.
README "Rules / Rulesets" repoints the source of truth to these committed files: setup imports from them; the live export becomes the regenerate recipe run in the template when the maintainer changes the live rulesets.
AGENTS.md documents that the rulesets are deliberately not in the verbatim-carry set and are not carried/re-synced downstream as a per-repo copy — they are live config, not a file a derived repo consumes. They ride the re-sync loop from the hub: diff each derived repo's live rulesets against the template's committed JSON and correct drift via a full-payload PUT. The drift command normalizes rules[]/bypass_actors[] order so a reordered-but-equivalent ruleset doesn't read as drift.
Also folds in pending spell-dict / workspace-extension additions (and mirrors the two new general extensions into both devcontainers).

Verification

jq -S round-trip stable for both files; order-normalized drift diff against the template's own live rulesets reports develop: in sync / main: in sync.
Ran the drift check across all 8 derived repos (read-only): 6 in sync, Utilities has real live drift, homeassistant-purpleair has no rulesets configured — both surfaced to the maintainer (issues filed), not auto-applied.
markdownlint-cli2 clean on README.md and AGENTS.md (0 errors).

🤖 Generated with Claude Code

Closes the gap from #211: branch rulesets were live GitHub config applied once at repo creation, so they sat outside the file-based re-sync loop - a corrected template ruleset never propagated to derived repos, and downstream drift was invisible (PlexCleaner's docs said strict=false while live config stayed strict=true on both branches). - Commit the canonical writable subset as .github/rulesets/{develop,main}.json (strict_required_status_checks_policy false on both - the #82 value this exists to keep propagated). They port verbatim: conditions key on refs/heads/{develop,main}, bypass_actors uses global Admin role actor_id 5, the required check binds by name. - README "Rules / Rulesets": repoint the source of truth to the committed files - import from them at setup; the live export becomes the regenerate recipe run when the maintainer changes the template's live rulesets. - AGENTS.md: add the rulesets to the verbatim-carry set and document the live-vs-committed drift check (full-payload PUT to correct) in Staying in Sync. Note that carrying the file only syncs the source of truth; live config changes only on import/PUT. Also folds in pending spell-dictionary / workspace-extension additions and three deferred-item bullets that were already staged. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Copilot

Pull request overview

This PR brings branch rulesets into the repo-based re-sync/drift workflow by committing canonical develop/main ruleset JSON and updating documentation to treat those files as the versioned source of truth, plus minor editor/workspace hygiene updates.

Changes:

Add committed GitHub ruleset definitions for develop and main under .github/rulesets/.
Update README.md and AGENTS.md to import/sync rulesets from committed JSON and document how to detect/correct drift against live GitHub config.
Reformat and extend ProjectTemplate.code-workspace (spellings + recommended extensions).

Reviewed changes

Copilot reviewed 5 out of 5 changed files in this pull request and generated 1 comment.

Show a summary per file

File	Description
README.md	Updates ruleset setup docs to import from committed JSON; adds deferred-pattern notes.
ProjectTemplate.code-workspace	Normalizes formatting; adds cSpell words and extension recommendations.
AGENTS.md	Adds ruleset JSON to verbatim-carry list and documents drift-check procedure.
.github/rulesets/main.json	Introduces canonical `main` branch ruleset JSON (importable subset).
.github/rulesets/develop.json	Introduces canonical `develop` branch ruleset JSON (importable subset).

GitHub returns a ruleset's rules[] (and bypass_actors[]) in arbitrary order, so the plain diff false-positived on a reordered-but-equivalent ruleset (PlexCleaner's develop/main read as DRIFT when only the rule order differed). Sort both arrays before diffing so only real differences surface. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

The versioned rulesets are live GitHub config, not a file a derived repo consumes, so copying them into every downstream repo only adds noise and divergence. Drop them from the verbatim-carry set; document that they live only in the template as the source of truth and ride the re-sync loop from the hub - diffing each derived repo's live config against the template's committed JSON and correcting drift via full-payload PUT. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Copilot

Pull request overview

Copilot reviewed 5 out of 5 changed files in this pull request and generated 4 comments.

Two of the pre-staged Deferred Patterns are no longer deferred: - "Factor cleanup-artifacts into a reusable workflow" is moot - #214 removes the blanket cleanup job entirely (surgical consume-then-delete instead), so there is nothing left to factor. - "Generalize the input-validation step into a reusable pattern" is realized - #213 codifies the validate-input/state-at-entry pattern in AGENTS.md. Keep the publish-docker-readme "Validate inputs step" downstream-resync entry; that concrete downstream action is still pending. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

- Reword "never copied into derived repos" (README + AGENTS.md): the JSON is maintained in the template as the source of truth and reconciled against a repo's live config; it is not carried/re-synced as a per-repo copy. Avoids the inaccurate absolute (a template-instantiated repo does receive the files). - Mirror the two new general extensions (actionlint, shellcheck) into both devcontainers and fix the stale `*.code-workspace` reference (the per-language workspaces were consolidated into ProjectTemplate.code-workspace in #210). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

…s-versioned-json

Copilot

Pull request overview

Copilot reviewed 7 out of 7 changed files in this pull request and generated 4 comments.

 "customizations": {
 "vscode": {
- // Mirror of `recommendations` in Python.code-workspace.
+ // Mirror of `recommendations` in ProjectTemplate.code-workspace.


 "customizations": {
 "vscode": {
- // Mirror of `recommendations` in DotNet.code-workspace.
+ // Mirror of `recommendations` in ProjectTemplate.code-workspace.


+The branch rulesets ([`.github/rulesets/{develop,main}.json`](./.github/rulesets/)) are deliberately **not** in this carry set: they are live GitHub config, not a file a derived repo consumes, so carrying and re-syncing them downstream only adds noise. They are maintained **in this template** as the source of truth and are reconciled against each repo's *live* config during porting/re-sync - see [Staying in Sync](#staying-in-sync-and-reporting-drift-upstream).
+


 for name in develop main; do
 id=$(gh api repos/ptr727/ProjectTemplate/rulesets --jq ".[] | select(.name==\"$name\") | .id")
 gh api "repos/ptr727/ProjectTemplate/rulesets/$id" \
- --jq '{name, target, enforcement, bypass_actors, conditions, rules}' > "$name-ruleset.json"
+ --jq '{name, target, enforcement, bypass_actors, conditions, rules}' \
+ | jq -S '.' > ".github/rulesets/$name.json"


Promote the accumulated `develop` work to `main`. Twelve changes since the last promotion: - Add `WORKFLOW.md`: workflow style, architecture, behavioral contract, test methodology (#223) - Use NBGV `IGNORE_GITHUB_REF` instead of the ineffective `GITHUB_REF` override (#222) - Skip validate-release on smoke builds (#220) - Gate asset delete on the release create/refresh condition (#218) - Ship branch rulesets as versioned JSON in the re-sync / drift loop (#212) - Clean up transfer artifacts surgically at consumption, not blanket-delete (#216) - Version each publish leg against its own branch; validate at entry (#215) - Consolidate workspace configurations into a unified ProjectTemplate workspace (#210) - Template convergence barrier: absorb pins, generic release + docker-readme, carry-whole-file (#207) - Key merge-bot concurrency on PR number, not `github.ref` (#206) - Codify orchestrated re-sync personas and full-replacement rule (#205) - Lead action pins; affirm pattern-based artifact handoff (#204) 🤖 Generated with [Claude Code](https://claude.com/claude-code)

ptr727 · 2026-06-26T16:52:21Z

Problem

Closes#211. Branch rulesets are live GitHub config applied once at repo creation, so they sit outside the file-based re-sync loop (AGENTS.md "Staying in Sync"). Two consequences: a corrected template ruleset never propagates to existing derived repos, and downstream ruleset drift is invisible. This bit ptr727/PlexCleaner — its synced docs said strict=false while its live rulesets stayed strict=true on both develop and main (the exact #82 failure mode), fixed locally only after it broke auto-merge and blocked a promotion.

Change

Canonical rulesets as committed files, maintained in this template only..github/rulesets/develop.json and .github/rulesets/main.json hold the re-importable writable subset ({name, target, enforcement, bypass_actors, conditions, rules}), strict_required_status_checks_policy: false on both. They port verbatim with no placeholders — conditions key on refs/heads/{develop,main}, bypass_actors uses the global Admin role actor_id: 5, the required check binds by name.
README "Rules / Rulesets" repoints the source of truth to these committed files: setup imports from them; the live export becomes the regenerate recipe run in the template when the maintainer changes the live rulesets.
AGENTS.md documents that the rulesets are deliberately not in the verbatim-carry set and are not carried/re-synced downstream as a per-repo copy — they are live config, not a file a derived repo consumes. They ride the re-sync loop from the hub: diff each derived repo's live rulesets against the template's committed JSON and correct drift via a full-payload PUT. The drift command normalizes rules[]/bypass_actors[] order so a reordered-but-equivalent ruleset doesn't read as drift.
Also folds in pending spell-dict / workspace-extension additions (and mirrors the two new general extensions into both devcontainers).

Verification

jq -S round-trip stable for both files; order-normalized drift diff against the template's own live rulesets reports develop: in sync / main: in sync.
Ran the drift check across all 8 derived repos (read-only): 6 in sync, Utilities has real live drift, homeassistant-purpleair has no rulesets configured — both surfaced to the maintainer (issues filed), not auto-applied.
markdownlint-cli2 clean on README.md and AGENTS.md (0 errors).

🤖 Generated with Claude Code

Closes the gap from #211: branch rulesets were live GitHub config applied once at repo creation, so they sat outside the file-based re-sync loop - a corrected template ruleset never propagated to derived repos, and downstream drift was invisible (PlexCleaner's docs said strict=false while live config stayed strict=true on both branches). - Commit the canonical writable subset as .github/rulesets/{develop,main}.json (strict_required_status_checks_policy false on both - the #82 value this exists to keep propagated). They port verbatim: conditions key on refs/heads/{develop,main}, bypass_actors uses global Admin role actor_id 5, the required check binds by name. - README "Rules / Rulesets": repoint the source of truth to the committed files - import from them at setup; the live export becomes the regenerate recipe run when the maintainer changes the template's live rulesets. - AGENTS.md: add the rulesets to the verbatim-carry set and document the live-vs-committed drift check (full-payload PUT to correct) in Staying in Sync. Note that carrying the file only syncs the source of truth; live config changes only on import/PUT. Also folds in pending spell-dictionary / workspace-extension additions and three deferred-item bullets that were already staged. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Copilot

Pull request overview

This PR brings branch rulesets into the repo-based re-sync/drift workflow by committing canonical develop/main ruleset JSON and updating documentation to treat those files as the versioned source of truth, plus minor editor/workspace hygiene updates.

Changes:

Add committed GitHub ruleset definitions for develop and main under .github/rulesets/.
Update README.md and AGENTS.md to import/sync rulesets from committed JSON and document how to detect/correct drift against live GitHub config.
Reformat and extend ProjectTemplate.code-workspace (spellings + recommended extensions).

Reviewed changes

Copilot reviewed 5 out of 5 changed files in this pull request and generated 1 comment.

Show a summary per file

File	Description
README.md	Updates ruleset setup docs to import from committed JSON; adds deferred-pattern notes.
ProjectTemplate.code-workspace	Normalizes formatting; adds cSpell words and extension recommendations.
AGENTS.md	Adds ruleset JSON to verbatim-carry list and documents drift-check procedure.
.github/rulesets/main.json	Introduces canonical `main` branch ruleset JSON (importable subset).
.github/rulesets/develop.json	Introduces canonical `develop` branch ruleset JSON (importable subset).

GitHub returns a ruleset's rules[] (and bypass_actors[]) in arbitrary order, so the plain diff false-positived on a reordered-but-equivalent ruleset (PlexCleaner's develop/main read as DRIFT when only the rule order differed). Sort both arrays before diffing so only real differences surface. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

The versioned rulesets are live GitHub config, not a file a derived repo consumes, so copying them into every downstream repo only adds noise and divergence. Drop them from the verbatim-carry set; document that they live only in the template as the source of truth and ride the re-sync loop from the hub - diffing each derived repo's live config against the template's committed JSON and correcting drift via full-payload PUT. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Copilot

Pull request overview

Copilot reviewed 5 out of 5 changed files in this pull request and generated 4 comments.

Two of the pre-staged Deferred Patterns are no longer deferred: - "Factor cleanup-artifacts into a reusable workflow" is moot - #214 removes the blanket cleanup job entirely (surgical consume-then-delete instead), so there is nothing left to factor. - "Generalize the input-validation step into a reusable pattern" is realized - #213 codifies the validate-input/state-at-entry pattern in AGENTS.md. Keep the publish-docker-readme "Validate inputs step" downstream-resync entry; that concrete downstream action is still pending. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

- Reword "never copied into derived repos" (README + AGENTS.md): the JSON is maintained in the template as the source of truth and reconciled against a repo's live config; it is not carried/re-synced as a per-repo copy. Avoids the inaccurate absolute (a template-instantiated repo does receive the files). - Mirror the two new general extensions (actionlint, shellcheck) into both devcontainers and fix the stale `*.code-workspace` reference (the per-language workspaces were consolidated into ProjectTemplate.code-workspace in #210). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

…s-versioned-json

Copilot

Pull request overview

Copilot reviewed 7 out of 7 changed files in this pull request and generated 4 comments.

 "customizations": {
 "vscode": {
- // Mirror of `recommendations` in Python.code-workspace.
+ // Mirror of `recommendations` in ProjectTemplate.code-workspace.


 "customizations": {
 "vscode": {
- // Mirror of `recommendations` in DotNet.code-workspace.
+ // Mirror of `recommendations` in ProjectTemplate.code-workspace.


+The branch rulesets ([`.github/rulesets/{develop,main}.json`](./.github/rulesets/)) are deliberately **not** in this carry set: they are live GitHub config, not a file a derived repo consumes, so carrying and re-syncing them downstream only adds noise. They are maintained **in this template** as the source of truth and are reconciled against each repo's *live* config during porting/re-sync - see [Staying in Sync](#staying-in-sync-and-reporting-drift-upstream).
+


 for name in develop main; do
 id=$(gh api repos/ptr727/ProjectTemplate/rulesets --jq ".[] | select(.name==\"$name\") | .id")
 gh api "repos/ptr727/ProjectTemplate/rulesets/$id" \
- --jq '{name, target, enforcement, bypass_actors, conditions, rules}' > "$name-ruleset.json"
+ --jq '{name, target, enforcement, bypass_actors, conditions, rules}' \
+ | jq -S '.' > ".github/rulesets/$name.json"


Promote the accumulated `develop` work to `main`. Twelve changes since the last promotion: - Add `WORKFLOW.md`: workflow style, architecture, behavioral contract, test methodology (#223) - Use NBGV `IGNORE_GITHUB_REF` instead of the ineffective `GITHUB_REF` override (#222) - Skip validate-release on smoke builds (#220) - Gate asset delete on the release create/refresh condition (#218) - Ship branch rulesets as versioned JSON in the re-sync / drift loop (#212) - Clean up transfer artifacts surgically at consumption, not blanket-delete (#216) - Version each publish leg against its own branch; validate at entry (#215) - Consolidate workspace configurations into a unified ProjectTemplate workspace (#210) - Template convergence barrier: absorb pins, generic release + docker-readme, carry-whole-file (#207) - Key merge-bot concurrency on PR number, not `github.ref` (#206) - Codify orchestrated re-sync personas and full-replacement rule (#205) - Lead action pins; affirm pattern-based artifact handoff (#204) 🤖 Generated with [Claude Code](https://claude.com/claude-code)

ptr727 · 2026-06-26T16:52:21Z

Problem

Closes#211. Branch rulesets are live GitHub config applied once at repo creation, so they sit outside the file-based re-sync loop (AGENTS.md "Staying in Sync"). Two consequences: a corrected template ruleset never propagates to existing derived repos, and downstream ruleset drift is invisible. This bit ptr727/PlexCleaner — its synced docs said strict=false while its live rulesets stayed strict=true on both develop and main (the exact #82 failure mode), fixed locally only after it broke auto-merge and blocked a promotion.

Change

Canonical rulesets as committed files, maintained in this template only..github/rulesets/develop.json and .github/rulesets/main.json hold the re-importable writable subset ({name, target, enforcement, bypass_actors, conditions, rules}), strict_required_status_checks_policy: false on both. They port verbatim with no placeholders — conditions key on refs/heads/{develop,main}, bypass_actors uses the global Admin role actor_id: 5, the required check binds by name.
README "Rules / Rulesets" repoints the source of truth to these committed files: setup imports from them; the live export becomes the regenerate recipe run in the template when the maintainer changes the live rulesets.
AGENTS.md documents that the rulesets are deliberately not in the verbatim-carry set and are not carried/re-synced downstream as a per-repo copy — they are live config, not a file a derived repo consumes. They ride the re-sync loop from the hub: diff each derived repo's live rulesets against the template's committed JSON and correct drift via a full-payload PUT. The drift command normalizes rules[]/bypass_actors[] order so a reordered-but-equivalent ruleset doesn't read as drift.
Also folds in pending spell-dict / workspace-extension additions (and mirrors the two new general extensions into both devcontainers).

Verification

jq -S round-trip stable for both files; order-normalized drift diff against the template's own live rulesets reports develop: in sync / main: in sync.
Ran the drift check across all 8 derived repos (read-only): 6 in sync, Utilities has real live drift, homeassistant-purpleair has no rulesets configured — both surfaced to the maintainer (issues filed), not auto-applied.
markdownlint-cli2 clean on README.md and AGENTS.md (0 errors).

🤖 Generated with Claude Code

Closes the gap from #211: branch rulesets were live GitHub config applied once at repo creation, so they sat outside the file-based re-sync loop - a corrected template ruleset never propagated to derived repos, and downstream drift was invisible (PlexCleaner's docs said strict=false while live config stayed strict=true on both branches). - Commit the canonical writable subset as .github/rulesets/{develop,main}.json (strict_required_status_checks_policy false on both - the #82 value this exists to keep propagated). They port verbatim: conditions key on refs/heads/{develop,main}, bypass_actors uses global Admin role actor_id 5, the required check binds by name. - README "Rules / Rulesets": repoint the source of truth to the committed files - import from them at setup; the live export becomes the regenerate recipe run when the maintainer changes the template's live rulesets. - AGENTS.md: add the rulesets to the verbatim-carry set and document the live-vs-committed drift check (full-payload PUT to correct) in Staying in Sync. Note that carrying the file only syncs the source of truth; live config changes only on import/PUT. Also folds in pending spell-dictionary / workspace-extension additions and three deferred-item bullets that were already staged. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Copilot

Pull request overview

This PR brings branch rulesets into the repo-based re-sync/drift workflow by committing canonical develop/main ruleset JSON and updating documentation to treat those files as the versioned source of truth, plus minor editor/workspace hygiene updates.

Changes:

Add committed GitHub ruleset definitions for develop and main under .github/rulesets/.
Update README.md and AGENTS.md to import/sync rulesets from committed JSON and document how to detect/correct drift against live GitHub config.
Reformat and extend ProjectTemplate.code-workspace (spellings + recommended extensions).

Reviewed changes

Copilot reviewed 5 out of 5 changed files in this pull request and generated 1 comment.

Show a summary per file

File	Description
README.md	Updates ruleset setup docs to import from committed JSON; adds deferred-pattern notes.
ProjectTemplate.code-workspace	Normalizes formatting; adds cSpell words and extension recommendations.
AGENTS.md	Adds ruleset JSON to verbatim-carry list and documents drift-check procedure.
.github/rulesets/main.json	Introduces canonical `main` branch ruleset JSON (importable subset).
.github/rulesets/develop.json	Introduces canonical `develop` branch ruleset JSON (importable subset).

GitHub returns a ruleset's rules[] (and bypass_actors[]) in arbitrary order, so the plain diff false-positived on a reordered-but-equivalent ruleset (PlexCleaner's develop/main read as DRIFT when only the rule order differed). Sort both arrays before diffing so only real differences surface. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

The versioned rulesets are live GitHub config, not a file a derived repo consumes, so copying them into every downstream repo only adds noise and divergence. Drop them from the verbatim-carry set; document that they live only in the template as the source of truth and ride the re-sync loop from the hub - diffing each derived repo's live config against the template's committed JSON and correcting drift via full-payload PUT. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Copilot

Pull request overview

Copilot reviewed 5 out of 5 changed files in this pull request and generated 4 comments.

Two of the pre-staged Deferred Patterns are no longer deferred: - "Factor cleanup-artifacts into a reusable workflow" is moot - #214 removes the blanket cleanup job entirely (surgical consume-then-delete instead), so there is nothing left to factor. - "Generalize the input-validation step into a reusable pattern" is realized - #213 codifies the validate-input/state-at-entry pattern in AGENTS.md. Keep the publish-docker-readme "Validate inputs step" downstream-resync entry; that concrete downstream action is still pending. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

- Reword "never copied into derived repos" (README + AGENTS.md): the JSON is maintained in the template as the source of truth and reconciled against a repo's live config; it is not carried/re-synced as a per-repo copy. Avoids the inaccurate absolute (a template-instantiated repo does receive the files). - Mirror the two new general extensions (actionlint, shellcheck) into both devcontainers and fix the stale `*.code-workspace` reference (the per-language workspaces were consolidated into ProjectTemplate.code-workspace in #210). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

…s-versioned-json

Copilot

Pull request overview

Copilot reviewed 7 out of 7 changed files in this pull request and generated 4 comments.

 "customizations": {
 "vscode": {
- // Mirror of `recommendations` in Python.code-workspace.
+ // Mirror of `recommendations` in ProjectTemplate.code-workspace.


 "customizations": {
 "vscode": {
- // Mirror of `recommendations` in DotNet.code-workspace.
+ // Mirror of `recommendations` in ProjectTemplate.code-workspace.


+The branch rulesets ([`.github/rulesets/{develop,main}.json`](./.github/rulesets/)) are deliberately **not** in this carry set: they are live GitHub config, not a file a derived repo consumes, so carrying and re-syncing them downstream only adds noise. They are maintained **in this template** as the source of truth and are reconciled against each repo's *live* config during porting/re-sync - see [Staying in Sync](#staying-in-sync-and-reporting-drift-upstream).
+


 for name in develop main; do
 id=$(gh api repos/ptr727/ProjectTemplate/rulesets --jq ".[] | select(.name==\"$name\") | .id")
 gh api "repos/ptr727/ProjectTemplate/rulesets/$id" \
- --jq '{name, target, enforcement, bypass_actors, conditions, rules}' > "$name-ruleset.json"
+ --jq '{name, target, enforcement, bypass_actors, conditions, rules}' \
+ | jq -S '.' > ".github/rulesets/$name.json"


Promote the accumulated `develop` work to `main`. Twelve changes since the last promotion: - Add `WORKFLOW.md`: workflow style, architecture, behavioral contract, test methodology (#223) - Use NBGV `IGNORE_GITHUB_REF` instead of the ineffective `GITHUB_REF` override (#222) - Skip validate-release on smoke builds (#220) - Gate asset delete on the release create/refresh condition (#218) - Ship branch rulesets as versioned JSON in the re-sync / drift loop (#212) - Clean up transfer artifacts surgically at consumption, not blanket-delete (#216) - Version each publish leg against its own branch; validate at entry (#215) - Consolidate workspace configurations into a unified ProjectTemplate workspace (#210) - Template convergence barrier: absorb pins, generic release + docker-readme, carry-whole-file (#207) - Key merge-bot concurrency on PR number, not `github.ref` (#206) - Codify orchestrated re-sync personas and full-replacement rule (#205) - Lead action pins; affirm pattern-based artifact handoff (#204) 🤖 Generated with [Claude Code](https://claude.com/claude-code)

ptr727 · 2026-06-26T16:52:21Z

Problem

Closes#211. Branch rulesets are live GitHub config applied once at repo creation, so they sit outside the file-based re-sync loop (AGENTS.md "Staying in Sync"). Two consequences: a corrected template ruleset never propagates to existing derived repos, and downstream ruleset drift is invisible. This bit ptr727/PlexCleaner — its synced docs said strict=false while its live rulesets stayed strict=true on both develop and main (the exact #82 failure mode), fixed locally only after it broke auto-merge and blocked a promotion.

Change

Canonical rulesets as committed files, maintained in this template only..github/rulesets/develop.json and .github/rulesets/main.json hold the re-importable writable subset ({name, target, enforcement, bypass_actors, conditions, rules}), strict_required_status_checks_policy: false on both. They port verbatim with no placeholders — conditions key on refs/heads/{develop,main}, bypass_actors uses the global Admin role actor_id: 5, the required check binds by name.
README "Rules / Rulesets" repoints the source of truth to these committed files: setup imports from them; the live export becomes the regenerate recipe run in the template when the maintainer changes the live rulesets.
AGENTS.md documents that the rulesets are deliberately not in the verbatim-carry set and are not carried/re-synced downstream as a per-repo copy — they are live config, not a file a derived repo consumes. They ride the re-sync loop from the hub: diff each derived repo's live rulesets against the template's committed JSON and correct drift via a full-payload PUT. The drift command normalizes rules[]/bypass_actors[] order so a reordered-but-equivalent ruleset doesn't read as drift.
Also folds in pending spell-dict / workspace-extension additions (and mirrors the two new general extensions into both devcontainers).

Verification

jq -S round-trip stable for both files; order-normalized drift diff against the template's own live rulesets reports develop: in sync / main: in sync.
Ran the drift check across all 8 derived repos (read-only): 6 in sync, Utilities has real live drift, homeassistant-purpleair has no rulesets configured — both surfaced to the maintainer (issues filed), not auto-applied.
markdownlint-cli2 clean on README.md and AGENTS.md (0 errors).

🤖 Generated with Claude Code

Closes the gap from #211: branch rulesets were live GitHub config applied once at repo creation, so they sat outside the file-based re-sync loop - a corrected template ruleset never propagated to derived repos, and downstream drift was invisible (PlexCleaner's docs said strict=false while live config stayed strict=true on both branches). - Commit the canonical writable subset as .github/rulesets/{develop,main}.json (strict_required_status_checks_policy false on both - the #82 value this exists to keep propagated). They port verbatim: conditions key on refs/heads/{develop,main}, bypass_actors uses global Admin role actor_id 5, the required check binds by name. - README "Rules / Rulesets": repoint the source of truth to the committed files - import from them at setup; the live export becomes the regenerate recipe run when the maintainer changes the template's live rulesets. - AGENTS.md: add the rulesets to the verbatim-carry set and document the live-vs-committed drift check (full-payload PUT to correct) in Staying in Sync. Note that carrying the file only syncs the source of truth; live config changes only on import/PUT. Also folds in pending spell-dictionary / workspace-extension additions and three deferred-item bullets that were already staged. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Copilot

Pull request overview

This PR brings branch rulesets into the repo-based re-sync/drift workflow by committing canonical develop/main ruleset JSON and updating documentation to treat those files as the versioned source of truth, plus minor editor/workspace hygiene updates.

Changes:

Add committed GitHub ruleset definitions for develop and main under .github/rulesets/.
Update README.md and AGENTS.md to import/sync rulesets from committed JSON and document how to detect/correct drift against live GitHub config.
Reformat and extend ProjectTemplate.code-workspace (spellings + recommended extensions).

Reviewed changes

Copilot reviewed 5 out of 5 changed files in this pull request and generated 1 comment.

Show a summary per file

File	Description
README.md	Updates ruleset setup docs to import from committed JSON; adds deferred-pattern notes.
ProjectTemplate.code-workspace	Normalizes formatting; adds cSpell words and extension recommendations.
AGENTS.md	Adds ruleset JSON to verbatim-carry list and documents drift-check procedure.
.github/rulesets/main.json	Introduces canonical `main` branch ruleset JSON (importable subset).
.github/rulesets/develop.json	Introduces canonical `develop` branch ruleset JSON (importable subset).

GitHub returns a ruleset's rules[] (and bypass_actors[]) in arbitrary order, so the plain diff false-positived on a reordered-but-equivalent ruleset (PlexCleaner's develop/main read as DRIFT when only the rule order differed). Sort both arrays before diffing so only real differences surface. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

The versioned rulesets are live GitHub config, not a file a derived repo consumes, so copying them into every downstream repo only adds noise and divergence. Drop them from the verbatim-carry set; document that they live only in the template as the source of truth and ride the re-sync loop from the hub - diffing each derived repo's live config against the template's committed JSON and correcting drift via full-payload PUT. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Copilot

Pull request overview

Copilot reviewed 5 out of 5 changed files in this pull request and generated 4 comments.

Two of the pre-staged Deferred Patterns are no longer deferred: - "Factor cleanup-artifacts into a reusable workflow" is moot - #214 removes the blanket cleanup job entirely (surgical consume-then-delete instead), so there is nothing left to factor. - "Generalize the input-validation step into a reusable pattern" is realized - #213 codifies the validate-input/state-at-entry pattern in AGENTS.md. Keep the publish-docker-readme "Validate inputs step" downstream-resync entry; that concrete downstream action is still pending. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

- Reword "never copied into derived repos" (README + AGENTS.md): the JSON is maintained in the template as the source of truth and reconciled against a repo's live config; it is not carried/re-synced as a per-repo copy. Avoids the inaccurate absolute (a template-instantiated repo does receive the files). - Mirror the two new general extensions (actionlint, shellcheck) into both devcontainers and fix the stale `*.code-workspace` reference (the per-language workspaces were consolidated into ProjectTemplate.code-workspace in #210). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

…s-versioned-json

Copilot

Pull request overview

Copilot reviewed 7 out of 7 changed files in this pull request and generated 4 comments.

 "customizations": {
 "vscode": {
- // Mirror of `recommendations` in Python.code-workspace.
+ // Mirror of `recommendations` in ProjectTemplate.code-workspace.


 "customizations": {
 "vscode": {
- // Mirror of `recommendations` in DotNet.code-workspace.
+ // Mirror of `recommendations` in ProjectTemplate.code-workspace.


+The branch rulesets ([`.github/rulesets/{develop,main}.json`](./.github/rulesets/)) are deliberately **not** in this carry set: they are live GitHub config, not a file a derived repo consumes, so carrying and re-syncing them downstream only adds noise. They are maintained **in this template** as the source of truth and are reconciled against each repo's *live* config during porting/re-sync - see [Staying in Sync](#staying-in-sync-and-reporting-drift-upstream).
+


 for name in develop main; do
 id=$(gh api repos/ptr727/ProjectTemplate/rulesets --jq ".[] | select(.name==\"$name\") | .id")
 gh api "repos/ptr727/ProjectTemplate/rulesets/$id" \
- --jq '{name, target, enforcement, bypass_actors, conditions, rules}' > "$name-ruleset.json"
+ --jq '{name, target, enforcement, bypass_actors, conditions, rules}' \
+ | jq -S '.' > ".github/rulesets/$name.json"


Promote the accumulated `develop` work to `main`. Twelve changes since the last promotion: - Add `WORKFLOW.md`: workflow style, architecture, behavioral contract, test methodology (#223) - Use NBGV `IGNORE_GITHUB_REF` instead of the ineffective `GITHUB_REF` override (#222) - Skip validate-release on smoke builds (#220) - Gate asset delete on the release create/refresh condition (#218) - Ship branch rulesets as versioned JSON in the re-sync / drift loop (#212) - Clean up transfer artifacts surgically at consumption, not blanket-delete (#216) - Version each publish leg against its own branch; validate at entry (#215) - Consolidate workspace configurations into a unified ProjectTemplate workspace (#210) - Template convergence barrier: absorb pins, generic release + docker-readme, carry-whole-file (#207) - Key merge-bot concurrency on PR number, not `github.ref` (#206) - Codify orchestrated re-sync personas and full-replacement rule (#205) - Lead action pins; affirm pattern-based artifact handoff (#204) 🤖 Generated with [Claude Code](https://claude.com/claude-code)

ptr727 · 2026-06-26T16:52:21Z

Problem

Closes#211. Branch rulesets are live GitHub config applied once at repo creation, so they sit outside the file-based re-sync loop (AGENTS.md "Staying in Sync"). Two consequences: a corrected template ruleset never propagates to existing derived repos, and downstream ruleset drift is invisible. This bit ptr727/PlexCleaner — its synced docs said strict=false while its live rulesets stayed strict=true on both develop and main (the exact #82 failure mode), fixed locally only after it broke auto-merge and blocked a promotion.

Change

Canonical rulesets as committed files, maintained in this template only..github/rulesets/develop.json and .github/rulesets/main.json hold the re-importable writable subset ({name, target, enforcement, bypass_actors, conditions, rules}), strict_required_status_checks_policy: false on both. They port verbatim with no placeholders — conditions key on refs/heads/{develop,main}, bypass_actors uses the global Admin role actor_id: 5, the required check binds by name.
README "Rules / Rulesets" repoints the source of truth to these committed files: setup imports from them; the live export becomes the regenerate recipe run in the template when the maintainer changes the live rulesets.
AGENTS.md documents that the rulesets are deliberately not in the verbatim-carry set and are not carried/re-synced downstream as a per-repo copy — they are live config, not a file a derived repo consumes. They ride the re-sync loop from the hub: diff each derived repo's live rulesets against the template's committed JSON and correct drift via a full-payload PUT. The drift command normalizes rules[]/bypass_actors[] order so a reordered-but-equivalent ruleset doesn't read as drift.
Also folds in pending spell-dict / workspace-extension additions (and mirrors the two new general extensions into both devcontainers).

Verification

jq -S round-trip stable for both files; order-normalized drift diff against the template's own live rulesets reports develop: in sync / main: in sync.
Ran the drift check across all 8 derived repos (read-only): 6 in sync, Utilities has real live drift, homeassistant-purpleair has no rulesets configured — both surfaced to the maintainer (issues filed), not auto-applied.
markdownlint-cli2 clean on README.md and AGENTS.md (0 errors).

🤖 Generated with Claude Code

Closes the gap from #211: branch rulesets were live GitHub config applied once at repo creation, so they sat outside the file-based re-sync loop - a corrected template ruleset never propagated to derived repos, and downstream drift was invisible (PlexCleaner's docs said strict=false while live config stayed strict=true on both branches). - Commit the canonical writable subset as .github/rulesets/{develop,main}.json (strict_required_status_checks_policy false on both - the #82 value this exists to keep propagated). They port verbatim: conditions key on refs/heads/{develop,main}, bypass_actors uses global Admin role actor_id 5, the required check binds by name. - README "Rules / Rulesets": repoint the source of truth to the committed files - import from them at setup; the live export becomes the regenerate recipe run when the maintainer changes the template's live rulesets. - AGENTS.md: add the rulesets to the verbatim-carry set and document the live-vs-committed drift check (full-payload PUT to correct) in Staying in Sync. Note that carrying the file only syncs the source of truth; live config changes only on import/PUT. Also folds in pending spell-dictionary / workspace-extension additions and three deferred-item bullets that were already staged. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Copilot

Pull request overview

This PR brings branch rulesets into the repo-based re-sync/drift workflow by committing canonical develop/main ruleset JSON and updating documentation to treat those files as the versioned source of truth, plus minor editor/workspace hygiene updates.

Changes:

Add committed GitHub ruleset definitions for develop and main under .github/rulesets/.
Update README.md and AGENTS.md to import/sync rulesets from committed JSON and document how to detect/correct drift against live GitHub config.
Reformat and extend ProjectTemplate.code-workspace (spellings + recommended extensions).

Reviewed changes

Copilot reviewed 5 out of 5 changed files in this pull request and generated 1 comment.

Show a summary per file

File	Description
README.md	Updates ruleset setup docs to import from committed JSON; adds deferred-pattern notes.
ProjectTemplate.code-workspace	Normalizes formatting; adds cSpell words and extension recommendations.
AGENTS.md	Adds ruleset JSON to verbatim-carry list and documents drift-check procedure.
.github/rulesets/main.json	Introduces canonical `main` branch ruleset JSON (importable subset).
.github/rulesets/develop.json	Introduces canonical `develop` branch ruleset JSON (importable subset).

GitHub returns a ruleset's rules[] (and bypass_actors[]) in arbitrary order, so the plain diff false-positived on a reordered-but-equivalent ruleset (PlexCleaner's develop/main read as DRIFT when only the rule order differed). Sort both arrays before diffing so only real differences surface. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

The versioned rulesets are live GitHub config, not a file a derived repo consumes, so copying them into every downstream repo only adds noise and divergence. Drop them from the verbatim-carry set; document that they live only in the template as the source of truth and ride the re-sync loop from the hub - diffing each derived repo's live config against the template's committed JSON and correcting drift via full-payload PUT. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Copilot

Pull request overview

Copilot reviewed 5 out of 5 changed files in this pull request and generated 4 comments.

Two of the pre-staged Deferred Patterns are no longer deferred: - "Factor cleanup-artifacts into a reusable workflow" is moot - #214 removes the blanket cleanup job entirely (surgical consume-then-delete instead), so there is nothing left to factor. - "Generalize the input-validation step into a reusable pattern" is realized - #213 codifies the validate-input/state-at-entry pattern in AGENTS.md. Keep the publish-docker-readme "Validate inputs step" downstream-resync entry; that concrete downstream action is still pending. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

- Reword "never copied into derived repos" (README + AGENTS.md): the JSON is maintained in the template as the source of truth and reconciled against a repo's live config; it is not carried/re-synced as a per-repo copy. Avoids the inaccurate absolute (a template-instantiated repo does receive the files). - Mirror the two new general extensions (actionlint, shellcheck) into both devcontainers and fix the stale `*.code-workspace` reference (the per-language workspaces were consolidated into ProjectTemplate.code-workspace in #210). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

…s-versioned-json

Copilot

Pull request overview

Copilot reviewed 7 out of 7 changed files in this pull request and generated 4 comments.

 "customizations": {
 "vscode": {
- // Mirror of `recommendations` in Python.code-workspace.
+ // Mirror of `recommendations` in ProjectTemplate.code-workspace.


 "customizations": {
 "vscode": {
- // Mirror of `recommendations` in DotNet.code-workspace.
+ // Mirror of `recommendations` in ProjectTemplate.code-workspace.


+The branch rulesets ([`.github/rulesets/{develop,main}.json`](./.github/rulesets/)) are deliberately **not** in this carry set: they are live GitHub config, not a file a derived repo consumes, so carrying and re-syncing them downstream only adds noise. They are maintained **in this template** as the source of truth and are reconciled against each repo's *live* config during porting/re-sync - see [Staying in Sync](#staying-in-sync-and-reporting-drift-upstream).
+


 for name in develop main; do
 id=$(gh api repos/ptr727/ProjectTemplate/rulesets --jq ".[] | select(.name==\"$name\") | .id")
 gh api "repos/ptr727/ProjectTemplate/rulesets/$id" \
- --jq '{name, target, enforcement, bypass_actors, conditions, rules}' > "$name-ruleset.json"
+ --jq '{name, target, enforcement, bypass_actors, conditions, rules}' \
+ | jq -S '.' > ".github/rulesets/$name.json"


Promote the accumulated `develop` work to `main`. Twelve changes since the last promotion: - Add `WORKFLOW.md`: workflow style, architecture, behavioral contract, test methodology (#223) - Use NBGV `IGNORE_GITHUB_REF` instead of the ineffective `GITHUB_REF` override (#222) - Skip validate-release on smoke builds (#220) - Gate asset delete on the release create/refresh condition (#218) - Ship branch rulesets as versioned JSON in the re-sync / drift loop (#212) - Clean up transfer artifacts surgically at consumption, not blanket-delete (#216) - Version each publish leg against its own branch; validate at entry (#215) - Consolidate workspace configurations into a unified ProjectTemplate workspace (#210) - Template convergence barrier: absorb pins, generic release + docker-readme, carry-whole-file (#207) - Key merge-bot concurrency on PR number, not `github.ref` (#206) - Codify orchestrated re-sync personas and full-replacement rule (#205) - Lead action pins; affirm pattern-based artifact handoff (#204) 🤖 Generated with [Claude Code](https://claude.com/claude-code)

ptr727 · 2026-06-26T16:52:21Z

Problem

Closes#211. Branch rulesets are live GitHub config applied once at repo creation, so they sit outside the file-based re-sync loop (AGENTS.md "Staying in Sync"). Two consequences: a corrected template ruleset never propagates to existing derived repos, and downstream ruleset drift is invisible. This bit ptr727/PlexCleaner — its synced docs said strict=false while its live rulesets stayed strict=true on both develop and main (the exact #82 failure mode), fixed locally only after it broke auto-merge and blocked a promotion.

Change

Canonical rulesets as committed files, maintained in this template only..github/rulesets/develop.json and .github/rulesets/main.json hold the re-importable writable subset ({name, target, enforcement, bypass_actors, conditions, rules}), strict_required_status_checks_policy: false on both. They port verbatim with no placeholders — conditions key on refs/heads/{develop,main}, bypass_actors uses the global Admin role actor_id: 5, the required check binds by name.
README "Rules / Rulesets" repoints the source of truth to these committed files: setup imports from them; the live export becomes the regenerate recipe run in the template when the maintainer changes the live rulesets.
AGENTS.md documents that the rulesets are deliberately not in the verbatim-carry set and are not carried/re-synced downstream as a per-repo copy — they are live config, not a file a derived repo consumes. They ride the re-sync loop from the hub: diff each derived repo's live rulesets against the template's committed JSON and correct drift via a full-payload PUT. The drift command normalizes rules[]/bypass_actors[] order so a reordered-but-equivalent ruleset doesn't read as drift.
Also folds in pending spell-dict / workspace-extension additions (and mirrors the two new general extensions into both devcontainers).

Verification

jq -S round-trip stable for both files; order-normalized drift diff against the template's own live rulesets reports develop: in sync / main: in sync.
Ran the drift check across all 8 derived repos (read-only): 6 in sync, Utilities has real live drift, homeassistant-purpleair has no rulesets configured — both surfaced to the maintainer (issues filed), not auto-applied.
markdownlint-cli2 clean on README.md and AGENTS.md (0 errors).

🤖 Generated with Claude Code

Closes the gap from #211: branch rulesets were live GitHub config applied once at repo creation, so they sat outside the file-based re-sync loop - a corrected template ruleset never propagated to derived repos, and downstream drift was invisible (PlexCleaner's docs said strict=false while live config stayed strict=true on both branches). - Commit the canonical writable subset as .github/rulesets/{develop,main}.json (strict_required_status_checks_policy false on both - the #82 value this exists to keep propagated). They port verbatim: conditions key on refs/heads/{develop,main}, bypass_actors uses global Admin role actor_id 5, the required check binds by name. - README "Rules / Rulesets": repoint the source of truth to the committed files - import from them at setup; the live export becomes the regenerate recipe run when the maintainer changes the template's live rulesets. - AGENTS.md: add the rulesets to the verbatim-carry set and document the live-vs-committed drift check (full-payload PUT to correct) in Staying in Sync. Note that carrying the file only syncs the source of truth; live config changes only on import/PUT. Also folds in pending spell-dictionary / workspace-extension additions and three deferred-item bullets that were already staged. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Copilot

Pull request overview

This PR brings branch rulesets into the repo-based re-sync/drift workflow by committing canonical develop/main ruleset JSON and updating documentation to treat those files as the versioned source of truth, plus minor editor/workspace hygiene updates.

Changes:

Add committed GitHub ruleset definitions for develop and main under .github/rulesets/.
Update README.md and AGENTS.md to import/sync rulesets from committed JSON and document how to detect/correct drift against live GitHub config.
Reformat and extend ProjectTemplate.code-workspace (spellings + recommended extensions).

Reviewed changes

Copilot reviewed 5 out of 5 changed files in this pull request and generated 1 comment.

Show a summary per file

File	Description
README.md	Updates ruleset setup docs to import from committed JSON; adds deferred-pattern notes.
ProjectTemplate.code-workspace	Normalizes formatting; adds cSpell words and extension recommendations.
AGENTS.md	Adds ruleset JSON to verbatim-carry list and documents drift-check procedure.
.github/rulesets/main.json	Introduces canonical `main` branch ruleset JSON (importable subset).
.github/rulesets/develop.json	Introduces canonical `develop` branch ruleset JSON (importable subset).

GitHub returns a ruleset's rules[] (and bypass_actors[]) in arbitrary order, so the plain diff false-positived on a reordered-but-equivalent ruleset (PlexCleaner's develop/main read as DRIFT when only the rule order differed). Sort both arrays before diffing so only real differences surface. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

The versioned rulesets are live GitHub config, not a file a derived repo consumes, so copying them into every downstream repo only adds noise and divergence. Drop them from the verbatim-carry set; document that they live only in the template as the source of truth and ride the re-sync loop from the hub - diffing each derived repo's live config against the template's committed JSON and correcting drift via full-payload PUT. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Copilot

Pull request overview

Copilot reviewed 5 out of 5 changed files in this pull request and generated 4 comments.

Two of the pre-staged Deferred Patterns are no longer deferred: - "Factor cleanup-artifacts into a reusable workflow" is moot - #214 removes the blanket cleanup job entirely (surgical consume-then-delete instead), so there is nothing left to factor. - "Generalize the input-validation step into a reusable pattern" is realized - #213 codifies the validate-input/state-at-entry pattern in AGENTS.md. Keep the publish-docker-readme "Validate inputs step" downstream-resync entry; that concrete downstream action is still pending. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

- Reword "never copied into derived repos" (README + AGENTS.md): the JSON is maintained in the template as the source of truth and reconciled against a repo's live config; it is not carried/re-synced as a per-repo copy. Avoids the inaccurate absolute (a template-instantiated repo does receive the files). - Mirror the two new general extensions (actionlint, shellcheck) into both devcontainers and fix the stale `*.code-workspace` reference (the per-language workspaces were consolidated into ProjectTemplate.code-workspace in #210). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

…s-versioned-json

Copilot

Pull request overview

Copilot reviewed 7 out of 7 changed files in this pull request and generated 4 comments.

 "customizations": {
 "vscode": {
- // Mirror of `recommendations` in Python.code-workspace.
+ // Mirror of `recommendations` in ProjectTemplate.code-workspace.


 "customizations": {
 "vscode": {
- // Mirror of `recommendations` in DotNet.code-workspace.
+ // Mirror of `recommendations` in ProjectTemplate.code-workspace.


+The branch rulesets ([`.github/rulesets/{develop,main}.json`](./.github/rulesets/)) are deliberately **not** in this carry set: they are live GitHub config, not a file a derived repo consumes, so carrying and re-syncing them downstream only adds noise. They are maintained **in this template** as the source of truth and are reconciled against each repo's *live* config during porting/re-sync - see [Staying in Sync](#staying-in-sync-and-reporting-drift-upstream).
+


 for name in develop main; do
 id=$(gh api repos/ptr727/ProjectTemplate/rulesets --jq ".[] | select(.name==\"$name\") | .id")
 gh api "repos/ptr727/ProjectTemplate/rulesets/$id" \
- --jq '{name, target, enforcement, bypass_actors, conditions, rules}' > "$name-ruleset.json"
+ --jq '{name, target, enforcement, bypass_actors, conditions, rules}' \
+ | jq -S '.' > ".github/rulesets/$name.json"


Promote the accumulated `develop` work to `main`. Twelve changes since the last promotion: - Add `WORKFLOW.md`: workflow style, architecture, behavioral contract, test methodology (#223) - Use NBGV `IGNORE_GITHUB_REF` instead of the ineffective `GITHUB_REF` override (#222) - Skip validate-release on smoke builds (#220) - Gate asset delete on the release create/refresh condition (#218) - Ship branch rulesets as versioned JSON in the re-sync / drift loop (#212) - Clean up transfer artifacts surgically at consumption, not blanket-delete (#216) - Version each publish leg against its own branch; validate at entry (#215) - Consolidate workspace configurations into a unified ProjectTemplate workspace (#210) - Template convergence barrier: absorb pins, generic release + docker-readme, carry-whole-file (#207) - Key merge-bot concurrency on PR number, not `github.ref` (#206) - Codify orchestrated re-sync personas and full-replacement rule (#205) - Lead action pins; affirm pattern-based artifact handoff (#204) 🤖 Generated with [Claude Code](https://claude.com/claude-code)

ptr727 · 2026-06-26T16:52:21Z

Problem

Closes#211. Branch rulesets are live GitHub config applied once at repo creation, so they sit outside the file-based re-sync loop (AGENTS.md "Staying in Sync"). Two consequences: a corrected template ruleset never propagates to existing derived repos, and downstream ruleset drift is invisible. This bit ptr727/PlexCleaner — its synced docs said strict=false while its live rulesets stayed strict=true on both develop and main (the exact #82 failure mode), fixed locally only after it broke auto-merge and blocked a promotion.

Change

Canonical rulesets as committed files, maintained in this template only..github/rulesets/develop.json and .github/rulesets/main.json hold the re-importable writable subset ({name, target, enforcement, bypass_actors, conditions, rules}), strict_required_status_checks_policy: false on both. They port verbatim with no placeholders — conditions key on refs/heads/{develop,main}, bypass_actors uses the global Admin role actor_id: 5, the required check binds by name.
README "Rules / Rulesets" repoints the source of truth to these committed files: setup imports from them; the live export becomes the regenerate recipe run in the template when the maintainer changes the live rulesets.
AGENTS.md documents that the rulesets are deliberately not in the verbatim-carry set and are not carried/re-synced downstream as a per-repo copy — they are live config, not a file a derived repo consumes. They ride the re-sync loop from the hub: diff each derived repo's live rulesets against the template's committed JSON and correct drift via a full-payload PUT. The drift command normalizes rules[]/bypass_actors[] order so a reordered-but-equivalent ruleset doesn't read as drift.
Also folds in pending spell-dict / workspace-extension additions (and mirrors the two new general extensions into both devcontainers).

Verification

jq -S round-trip stable for both files; order-normalized drift diff against the template's own live rulesets reports develop: in sync / main: in sync.
Ran the drift check across all 8 derived repos (read-only): 6 in sync, Utilities has real live drift, homeassistant-purpleair has no rulesets configured — both surfaced to the maintainer (issues filed), not auto-applied.
markdownlint-cli2 clean on README.md and AGENTS.md (0 errors).

🤖 Generated with Claude Code

Closes the gap from #211: branch rulesets were live GitHub config applied once at repo creation, so they sat outside the file-based re-sync loop - a corrected template ruleset never propagated to derived repos, and downstream drift was invisible (PlexCleaner's docs said strict=false while live config stayed strict=true on both branches). - Commit the canonical writable subset as .github/rulesets/{develop,main}.json (strict_required_status_checks_policy false on both - the #82 value this exists to keep propagated). They port verbatim: conditions key on refs/heads/{develop,main}, bypass_actors uses global Admin role actor_id 5, the required check binds by name. - README "Rules / Rulesets": repoint the source of truth to the committed files - import from them at setup; the live export becomes the regenerate recipe run when the maintainer changes the template's live rulesets. - AGENTS.md: add the rulesets to the verbatim-carry set and document the live-vs-committed drift check (full-payload PUT to correct) in Staying in Sync. Note that carrying the file only syncs the source of truth; live config changes only on import/PUT. Also folds in pending spell-dictionary / workspace-extension additions and three deferred-item bullets that were already staged. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Copilot

Pull request overview

This PR brings branch rulesets into the repo-based re-sync/drift workflow by committing canonical develop/main ruleset JSON and updating documentation to treat those files as the versioned source of truth, plus minor editor/workspace hygiene updates.

Changes:

Add committed GitHub ruleset definitions for develop and main under .github/rulesets/.
Update README.md and AGENTS.md to import/sync rulesets from committed JSON and document how to detect/correct drift against live GitHub config.
Reformat and extend ProjectTemplate.code-workspace (spellings + recommended extensions).

Reviewed changes

Copilot reviewed 5 out of 5 changed files in this pull request and generated 1 comment.

Show a summary per file

File	Description
README.md	Updates ruleset setup docs to import from committed JSON; adds deferred-pattern notes.
ProjectTemplate.code-workspace	Normalizes formatting; adds cSpell words and extension recommendations.
AGENTS.md	Adds ruleset JSON to verbatim-carry list and documents drift-check procedure.
.github/rulesets/main.json	Introduces canonical `main` branch ruleset JSON (importable subset).
.github/rulesets/develop.json	Introduces canonical `develop` branch ruleset JSON (importable subset).

GitHub returns a ruleset's rules[] (and bypass_actors[]) in arbitrary order, so the plain diff false-positived on a reordered-but-equivalent ruleset (PlexCleaner's develop/main read as DRIFT when only the rule order differed). Sort both arrays before diffing so only real differences surface. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

The versioned rulesets are live GitHub config, not a file a derived repo consumes, so copying them into every downstream repo only adds noise and divergence. Drop them from the verbatim-carry set; document that they live only in the template as the source of truth and ride the re-sync loop from the hub - diffing each derived repo's live config against the template's committed JSON and correcting drift via full-payload PUT. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Copilot

Pull request overview

Copilot reviewed 5 out of 5 changed files in this pull request and generated 4 comments.

Two of the pre-staged Deferred Patterns are no longer deferred: - "Factor cleanup-artifacts into a reusable workflow" is moot - #214 removes the blanket cleanup job entirely (surgical consume-then-delete instead), so there is nothing left to factor. - "Generalize the input-validation step into a reusable pattern" is realized - #213 codifies the validate-input/state-at-entry pattern in AGENTS.md. Keep the publish-docker-readme "Validate inputs step" downstream-resync entry; that concrete downstream action is still pending. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

- Reword "never copied into derived repos" (README + AGENTS.md): the JSON is maintained in the template as the source of truth and reconciled against a repo's live config; it is not carried/re-synced as a per-repo copy. Avoids the inaccurate absolute (a template-instantiated repo does receive the files). - Mirror the two new general extensions (actionlint, shellcheck) into both devcontainers and fix the stale `*.code-workspace` reference (the per-language workspaces were consolidated into ProjectTemplate.code-workspace in #210). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

…s-versioned-json

Copilot

Pull request overview

Copilot reviewed 7 out of 7 changed files in this pull request and generated 4 comments.

 "customizations": {
 "vscode": {
- // Mirror of `recommendations` in Python.code-workspace.
+ // Mirror of `recommendations` in ProjectTemplate.code-workspace.


 "customizations": {
 "vscode": {
- // Mirror of `recommendations` in DotNet.code-workspace.
+ // Mirror of `recommendations` in ProjectTemplate.code-workspace.


+The branch rulesets ([`.github/rulesets/{develop,main}.json`](./.github/rulesets/)) are deliberately **not** in this carry set: they are live GitHub config, not a file a derived repo consumes, so carrying and re-syncing them downstream only adds noise. They are maintained **in this template** as the source of truth and are reconciled against each repo's *live* config during porting/re-sync - see [Staying in Sync](#staying-in-sync-and-reporting-drift-upstream).
+


 for name in develop main; do
 id=$(gh api repos/ptr727/ProjectTemplate/rulesets --jq ".[] | select(.name==\"$name\") | .id")
 gh api "repos/ptr727/ProjectTemplate/rulesets/$id" \
- --jq '{name, target, enforcement, bypass_actors, conditions, rules}' > "$name-ruleset.json"
+ --jq '{name, target, enforcement, bypass_actors, conditions, rules}' \
+ | jq -S '.' > ".github/rulesets/$name.json"


Promote the accumulated `develop` work to `main`. Twelve changes since the last promotion: - Add `WORKFLOW.md`: workflow style, architecture, behavioral contract, test methodology (#223) - Use NBGV `IGNORE_GITHUB_REF` instead of the ineffective `GITHUB_REF` override (#222) - Skip validate-release on smoke builds (#220) - Gate asset delete on the release create/refresh condition (#218) - Ship branch rulesets as versioned JSON in the re-sync / drift loop (#212) - Clean up transfer artifacts surgically at consumption, not blanket-delete (#216) - Version each publish leg against its own branch; validate at entry (#215) - Consolidate workspace configurations into a unified ProjectTemplate workspace (#210) - Template convergence barrier: absorb pins, generic release + docker-readme, carry-whole-file (#207) - Key merge-bot concurrency on PR number, not `github.ref` (#206) - Codify orchestrated re-sync personas and full-replacement rule (#205) - Lead action pins; affirm pattern-based artifact handoff (#204) 🤖 Generated with [Claude Code](https://claude.com/claude-code)

CopilotAI review requested due to automatic review settings June 26, 2026 16:52

Copilotstarted reviewing on behalf of ptr727 June 26, 2026 16:52 View session

CopilotAI reviewed Jun 26, 2026
View reviewed changes

Comment threadREADME.md Outdated

ptr727and others added 2 commits June 26, 2026 09:56

CopilotAI review requested due to automatic review settings June 26, 2026 17:00

Copilotstarted reviewing on behalf of ptr727 June 26, 2026 17:01 View session

CopilotAI reviewed Jun 26, 2026
View reviewed changes

Comment threadREADME.md Outdated
Comment threadREADME.md Outdated
Comment threadProjectTemplate.code-workspace
Comment threadAGENTS.md Outdated

ptr727and others added 3 commits June 26, 2026 10:52

Merge remote-tracking branch 'origin/develop' into feature/rulesets-a…
af0131e
…s-versioned-json

CopilotAI review requested due to automatic review settings June 26, 2026 18:17

Copilotstarted reviewing on behalf of ptr727 June 26, 2026 18:18 View session

ptr727 merged commit 59e0e91 into developJun 26, 2026
9 checks passed

ptr727 deleted the feature/rulesets-as-versioned-json branch June 26, 2026 18:19

CopilotAI reviewed Jun 26, 2026
View reviewed changes

This was referenced Jun 26, 2026
Ship branch rulesets as versioned JSON and add them to the re-sync / drift-check loop #211
Closed
Re-sync template #213/#214 workflow fixes (single-target adaptation) ptr727/LanguageTags#195
Closed

ptr727 mentioned this pull request Jul 4, 2026
Release: promote develop to main #225
Merged

CopilotAI review requested due to automatic review settings June 26, 2026 16:52

Copilotstarted reviewing on behalf of ptr727 June 26, 2026 16:52 View session

CopilotAI reviewed Jun 26, 2026
View reviewed changes

Comment threadREADME.md Outdated

ptr727and others added 2 commits June 26, 2026 09:56

CopilotAI review requested due to automatic review settings June 26, 2026 17:00

Copilotstarted reviewing on behalf of ptr727 June 26, 2026 17:01 View session

CopilotAI reviewed Jun 26, 2026
View reviewed changes

Comment threadREADME.md Outdated
Comment threadREADME.md Outdated
Comment threadProjectTemplate.code-workspace
Comment threadAGENTS.md Outdated

ptr727and others added 3 commits June 26, 2026 10:52

Merge remote-tracking branch 'origin/develop' into feature/rulesets-a…
af0131e
…s-versioned-json

CopilotAI review requested due to automatic review settings June 26, 2026 18:17

Copilotstarted reviewing on behalf of ptr727 June 26, 2026 18:18 View session

ptr727 merged commit 59e0e91 into developJun 26, 2026
9 checks passed

ptr727 deleted the feature/rulesets-as-versioned-json branch June 26, 2026 18:19

CopilotAI reviewed Jun 26, 2026
View reviewed changes

This was referenced Jun 26, 2026
Ship branch rulesets as versioned JSON and add them to the re-sync / drift-check loop #211
Closed
Re-sync template #213/#214 workflow fixes (single-target adaptation) ptr727/LanguageTags#195
Closed

ptr727 mentioned this pull request Jul 4, 2026
Release: promote develop to main #225
Merged

CopilotAI review requested due to automatic review settings June 26, 2026 16:52

Copilotstarted reviewing on behalf of ptr727 June 26, 2026 16:52 View session

CopilotAI reviewed Jun 26, 2026
View reviewed changes

Comment threadREADME.md Outdated

ptr727and others added 2 commits June 26, 2026 09:56

CopilotAI review requested due to automatic review settings June 26, 2026 17:00

Copilotstarted reviewing on behalf of ptr727 June 26, 2026 17:01 View session

CopilotAI reviewed Jun 26, 2026
View reviewed changes

Comment threadREADME.md Outdated
Comment threadREADME.md Outdated
Comment threadProjectTemplate.code-workspace
Comment threadAGENTS.md Outdated

ptr727and others added 3 commits June 26, 2026 10:52

Merge remote-tracking branch 'origin/develop' into feature/rulesets-a…
af0131e
…s-versioned-json

CopilotAI review requested due to automatic review settings June 26, 2026 18:17

Copilotstarted reviewing on behalf of ptr727 June 26, 2026 18:18 View session

ptr727 merged commit 59e0e91 into developJun 26, 2026
9 checks passed

ptr727 deleted the feature/rulesets-as-versioned-json branch June 26, 2026 18:19

CopilotAI reviewed Jun 26, 2026
View reviewed changes

This was referenced Jun 26, 2026
Ship branch rulesets as versioned JSON and add them to the re-sync / drift-check loop #211
Closed
Re-sync template #213/#214 workflow fixes (single-target adaptation) ptr727/LanguageTags#195
Closed

ptr727 mentioned this pull request Jul 4, 2026
Release: promote develop to main #225
Merged

CopilotAI review requested due to automatic review settings June 26, 2026 16:52

Copilotstarted reviewing on behalf of ptr727 June 26, 2026 16:52 View session

CopilotAI reviewed Jun 26, 2026
View reviewed changes

Comment threadREADME.md Outdated

ptr727and others added 2 commits June 26, 2026 09:56

CopilotAI review requested due to automatic review settings June 26, 2026 17:00

Copilotstarted reviewing on behalf of ptr727 June 26, 2026 17:01 View session

CopilotAI reviewed Jun 26, 2026
View reviewed changes

Comment threadREADME.md Outdated
Comment threadREADME.md Outdated
Comment threadProjectTemplate.code-workspace
Comment threadAGENTS.md Outdated

ptr727and others added 3 commits June 26, 2026 10:52

Merge remote-tracking branch 'origin/develop' into feature/rulesets-a…
af0131e
…s-versioned-json

CopilotAI review requested due to automatic review settings June 26, 2026 18:17

Copilotstarted reviewing on behalf of ptr727 June 26, 2026 18:18 View session

ptr727 merged commit 59e0e91 into developJun 26, 2026
9 checks passed

ptr727 deleted the feature/rulesets-as-versioned-json branch June 26, 2026 18:19

CopilotAI reviewed Jun 26, 2026
View reviewed changes

This was referenced Jun 26, 2026
Ship branch rulesets as versioned JSON and add them to the re-sync / drift-check loop #211
Closed
Re-sync template #213/#214 workflow fixes (single-target adaptation) ptr727/LanguageTags#195
Closed

ptr727 mentioned this pull request Jul 4, 2026
Release: promote develop to main #225
Merged

CopilotAI review requested due to automatic review settings June 26, 2026 16:52

Copilotstarted reviewing on behalf of ptr727 June 26, 2026 16:52 View session

CopilotAI reviewed Jun 26, 2026
View reviewed changes

Comment threadREADME.md Outdated

ptr727and others added 2 commits June 26, 2026 09:56

CopilotAI review requested due to automatic review settings June 26, 2026 17:00

Copilotstarted reviewing on behalf of ptr727 June 26, 2026 17:01 View session

CopilotAI reviewed Jun 26, 2026
View reviewed changes

Comment threadREADME.md Outdated
Comment threadREADME.md Outdated
Comment threadProjectTemplate.code-workspace
Comment threadAGENTS.md Outdated

ptr727and others added 3 commits June 26, 2026 10:52

Merge remote-tracking branch 'origin/develop' into feature/rulesets-a…
af0131e
…s-versioned-json

CopilotAI review requested due to automatic review settings June 26, 2026 18:17

Copilotstarted reviewing on behalf of ptr727 June 26, 2026 18:18 View session

ptr727 merged commit 59e0e91 into developJun 26, 2026
9 checks passed

ptr727 deleted the feature/rulesets-as-versioned-json branch June 26, 2026 18:19

CopilotAI reviewed Jun 26, 2026
View reviewed changes

This was referenced Jun 26, 2026
Ship branch rulesets as versioned JSON and add them to the re-sync / drift-check loop #211
Closed
Re-sync template #213/#214 workflow fixes (single-target adaptation) ptr727/LanguageTags#195
Closed

ptr727 mentioned this pull request Jul 4, 2026
Release: promote develop to main #225
Merged

CopilotAI review requested due to automatic review settings June 26, 2026 16:52

Copilotstarted reviewing on behalf of ptr727 June 26, 2026 16:52 View session

CopilotAI reviewed Jun 26, 2026
View reviewed changes

Comment threadREADME.md Outdated

ptr727and others added 2 commits June 26, 2026 09:56

CopilotAI review requested due to automatic review settings June 26, 2026 17:00

Copilotstarted reviewing on behalf of ptr727 June 26, 2026 17:01 View session

CopilotAI reviewed Jun 26, 2026
View reviewed changes

Comment threadREADME.md Outdated
Comment threadREADME.md Outdated
Comment threadProjectTemplate.code-workspace
Comment threadAGENTS.md Outdated

ptr727and others added 3 commits June 26, 2026 10:52

Merge remote-tracking branch 'origin/develop' into feature/rulesets-a…
af0131e
…s-versioned-json

CopilotAI review requested due to automatic review settings June 26, 2026 18:17

Copilotstarted reviewing on behalf of ptr727 June 26, 2026 18:18 View session

ptr727 merged commit 59e0e91 into developJun 26, 2026
9 checks passed

ptr727 deleted the feature/rulesets-as-versioned-json branch June 26, 2026 18:19

CopilotAI reviewed Jun 26, 2026
View reviewed changes

This was referenced Jun 26, 2026
Ship branch rulesets as versioned JSON and add them to the re-sync / drift-check loop #211
Closed
Re-sync template #213/#214 workflow fixes (single-target adaptation) ptr727/LanguageTags#195
Closed

ptr727 mentioned this pull request Jul 4, 2026
Release: promote develop to main #225
Merged

CopilotAI review requested due to automatic review settings June 26, 2026 16:52

Copilotstarted reviewing on behalf of ptr727 June 26, 2026 16:52 View session

CopilotAI reviewed Jun 26, 2026
View reviewed changes

Comment threadREADME.md Outdated

ptr727and others added 2 commits June 26, 2026 09:56

CopilotAI review requested due to automatic review settings June 26, 2026 17:00

Copilotstarted reviewing on behalf of ptr727 June 26, 2026 17:01 View session

CopilotAI reviewed Jun 26, 2026
View reviewed changes

Comment threadREADME.md Outdated
Comment threadREADME.md Outdated
Comment threadProjectTemplate.code-workspace
Comment threadAGENTS.md Outdated

ptr727and others added 3 commits June 26, 2026 10:52

Merge remote-tracking branch 'origin/develop' into feature/rulesets-a…
af0131e
…s-versioned-json

CopilotAI review requested due to automatic review settings June 26, 2026 18:17

Copilotstarted reviewing on behalf of ptr727 June 26, 2026 18:18 View session

ptr727 merged commit 59e0e91 into developJun 26, 2026
9 checks passed

ptr727 deleted the feature/rulesets-as-versioned-json branch June 26, 2026 18:19

CopilotAI reviewed Jun 26, 2026
View reviewed changes

This was referenced Jun 26, 2026
Ship branch rulesets as versioned JSON and add them to the re-sync / drift-check loop #211
Closed
Re-sync template #213/#214 workflow fixes (single-target adaptation) ptr727/LanguageTags#195
Closed

ptr727 mentioned this pull request Jul 4, 2026
Release: promote develop to main #225
Merged

CopilotAI review requested due to automatic review settings June 26, 2026 16:52

Copilotstarted reviewing on behalf of ptr727 June 26, 2026 16:52 View session

CopilotAI reviewed Jun 26, 2026
View reviewed changes

Comment threadREADME.md Outdated

ptr727and others added 2 commits June 26, 2026 09:56

CopilotAI review requested due to automatic review settings June 26, 2026 17:00

Copilotstarted reviewing on behalf of ptr727 June 26, 2026 17:01 View session

CopilotAI reviewed Jun 26, 2026
View reviewed changes

Comment threadREADME.md Outdated
Comment threadREADME.md Outdated
Comment threadProjectTemplate.code-workspace
Comment threadAGENTS.md Outdated

ptr727and others added 3 commits June 26, 2026 10:52

Merge remote-tracking branch 'origin/develop' into feature/rulesets-a…
af0131e
…s-versioned-json

CopilotAI review requested due to automatic review settings June 26, 2026 18:17

Copilotstarted reviewing on behalf of ptr727 June 26, 2026 18:18 View session

ptr727 merged commit 59e0e91 into developJun 26, 2026
9 checks passed

ptr727 deleted the feature/rulesets-as-versioned-json branch June 26, 2026 18:19

CopilotAI reviewed Jun 26, 2026
View reviewed changes

This was referenced Jun 26, 2026
Ship branch rulesets as versioned JSON and add them to the re-sync / drift-check loop #211
Closed
Re-sync template #213/#214 workflow fixes (single-target adaptation) ptr727/LanguageTags#195
Closed

ptr727 mentioned this pull request Jul 4, 2026
Release: promote develop to main #225
Merged

		The branch rulesets ([`.github/rulesets/{develop,main}.json`](./.github/rulesets/)) are deliberately not in this carry set: they are live GitHub config, not a file a derived repo consumes, so carrying and re-syncing them downstream only adds noise. They are maintained in this template as the source of truth and are reconciled against each repo's live config during porting/re-sync - see [Staying in Sync](#staying-in-sync-and-reporting-drift-upstream).

Conversation

ptr727 commented Jun 26, 2026• edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Problem

Change

Verification

Uh oh!

CopilotAI left a comment

Choose a reason for hiding this comment

Pull request overview

Reviewed changes

Uh oh!

Uh oh!

CopilotAI left a comment

Choose a reason for hiding this comment

Pull request overview

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

CopilotAI left a comment

Choose a reason for hiding this comment

Pull request overview

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Conversation

ptr727 commented Jun 26, 2026• edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Problem

Change

Verification

Uh oh!

CopilotAI left a comment

Choose a reason for hiding this comment

Pull request overview

Reviewed changes

Uh oh!

Uh oh!

CopilotAI left a comment

Choose a reason for hiding this comment

Pull request overview

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

CopilotAI left a comment

Choose a reason for hiding this comment

Pull request overview

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Conversation

ptr727 commented Jun 26, 2026• edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Problem

Change

Verification

Uh oh!

CopilotAI left a comment

Choose a reason for hiding this comment

Pull request overview

Reviewed changes

Uh oh!

ptr727 commented Jun 26, 2026•
edited
Loading

ptr727 commented Jun 26, 2026•
edited
Loading

ptr727 commented Jun 26, 2026•
edited
Loading

ptr727 commented Jun 26, 2026•
edited
Loading