[policy-only] Propagate reviewed legacy branch rules with publication guards

agent commented

2026-10-13 23:46:00 +03:00

Collaborator

Propagate the reviewed canonical agent rules to the supported legacy main branch while preserving its existing face contracts. The complete target-to-candidate diff changes 16 reviewed policy/document/design paths plus the main push workflow; it imports no runtime feature.

The workflow ignores exactly the reviewed policy paths, keeps its own YAML eligible for future validation, and preserves its original job condition with an additional head-message [policy-only] guard. This initial policy and guard merge must use a controlled marker-bearing merge commit message so no build or publication runs. Future unmarked workflow/source pushes retain their existing eligibility.

Independent medium review: CLEAN for full candidate 46743d7e1f, tree 674f344e5c, against main a439c8541f. Complete patch SHA256 ae701698ffced2ee96dbdbf0078b1e556facc29c6841ceeb1b37bed427954352. Static YAML preservation, exact path coverage, parent bytes and diff whitespace checks passed. Actual server event and skipped jobs remain to be verified after the normal protected merge.

Archive 653a identity ca35a924a4636c16b1795c8b60d4ba71b2437b9d7e8fe678eb78a2b9a4ba6ff3: five linked governance documents match exactly; three linked policies intentionally preserve reviewed legacy applicability/domain/release details. AGENTS retains RTK and legacy applicability.

Merge through ordinary protection only, with required independent server approval. Do not override protection or introduce source changes. Recheck exact base/head/result tree before merge; reserved marker is broad and head-only. Recovery changing guard behavior requires separately authorized review of restored publication effects.

Propagate the reviewed canonical agent rules to the supported legacy main branch while preserving its existing face contracts. The complete target-to-candidate diff changes 16 reviewed policy/document/design paths plus the main push workflow; it imports no runtime feature. The workflow ignores exactly the reviewed policy paths, keeps its own YAML eligible for future validation, and preserves its original job condition with an additional head-message [policy-only] guard. This initial policy and guard merge must use a controlled marker-bearing merge commit message so no build or publication runs. Future unmarked workflow/source pushes retain their existing eligibility. Independent medium review: CLEAN for full candidate 46743d7e1f913e03f49df797dc74ed4b5bd45a26, tree 674f344e5c3d349dc8bac4f52c1e8376fda9643d, against main a439c8541f3a7905fd29f3ce9ec7cc466bb40488. Complete patch SHA256 ae701698ffced2ee96dbdbf0078b1e556facc29c6841ceeb1b37bed427954352. Static YAML preservation, exact path coverage, parent bytes and diff whitespace checks passed. Actual server event and skipped jobs remain to be verified after the normal protected merge. Archive 653a identity ca35a924a4636c16b1795c8b60d4ba71b2437b9d7e8fe678eb78a2b9a4ba6ff3: five linked governance documents match exactly; three linked policies intentionally preserve reviewed legacy applicability/domain/release details. AGENTS retains RTK and legacy applicability. Merge through ordinary protection only, with required independent server approval. Do not override protection or introduce source changes. Recheck exact base/head/result tree before merge; reserved marker is broad and head-only. Recovery changing guard behavior requires separately authorized review of restored publication effects.

agent added 6 commits

2026-10-13 23:46:00 +03:00