A downstream resync surfaced a broken link in the byte-locked Governance section.\n\nEvidence:\n- GOVERNANCE.md under Running the Linters Locally links to ./docs/reusable-workflows.md.\n- Downstream fleet repositories do not carry docs/reusable-workflows.md.\n- The carried section must remain byte-identical to the hub, so downstream repositories cannot safely rewrite the link locally.\n- Copilot identified the broken downstream link during ptr727/ESPHome-Config#100.\n\nExpected:\nThe canonical carried prose should use a destination that remains navigable in downstream repositories, or the referenced documentation should be part of the declared carried baseline.\n\nAcceptance:\n- Choose and document the canonical cross-repo link strategy.\n- Update the hub source and generated/carried artifacts as required.\n- Add coverage preventing a hub-valid relative link from becoming broken after carry.
A downstream resync surfaced a broken link in the byte-locked Governance section.\n\nEvidence:\n- GOVERNANCE.md under Running the Linters Locally links to ./docs/reusable-workflows.md.\n- Downstream fleet repositories do not carry docs/reusable-workflows.md.\n- The carried section must remain byte-identical to the hub, so downstream repositories cannot safely rewrite the link locally.\n- Copilot identified the broken downstream link during ptr727/ESPHome-Config#100.\n\nExpected:\nThe canonical carried prose should use a destination that remains navigable in downstream repositories, or the referenced documentation should be part of the declared carried baseline.\n\nAcceptance:\n- Choose and document the canonical cross-repo link strategy.\n- Update the hub source and generated/carried artifacts as required.\n- Add coverage preventing a hub-valid relative link from becoming broken after carry.