Update repository-governance extension to v3.0.1

[bigsmartben]

Summary

• Update bundled repository-governance extension to v3.0.1.
• Update extensions/catalog.json metadata.

Test Plan

• python3 -m py_compile extensions/repository-governance/scripts/generate_repository_governance.py
• python3 -m pytest -q tests/test_arch_templates.py tests/integrations/test_cli.py::TestGitExtensionOptIn::test_community_extensions_and_workflow_preset_auto_installed tests/integrations/test_cli.py::TestGitExtensionOptIn::test_no_git_keeps_community_defaults
• python3 -m pytest -q tests/test_presets.py -k workflow_preset_integration_release_payload_contract
• python3 -m json.tool extensions/catalog.json >/dev/null

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: c50c70fb5a

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Restore the repository workflow section heading

When any project runs the generator, these repository workflow rules are now emitted immediately after the skill rules without a heading, so Markdown places the task-classification, SSOT-read, validation, and protected-write guidance under the preceding ## Agent Harness section. The previous projection had a separate ## Repository Workflow section, and without restoring a heading (or moving these bullets into a clearly repository-wide section), generated governance files make repository-wide workflow constraints look agent-harness-specific.

Useful? React with 👍 / 👎.