Update repository-governance bundled extension

[bigsmartben]

Summary

• Sync bundled extensions/repository-governance/ with the latest source changes from bigsmartben/spec-kit-agent-governance.
• Add fixed directory-tree SSOT governance with poc/ exploration routing and validation-record requirements.
• Update extensions/catalog.community.json for repository-governance v3.0.2 and extend manifest/catalog parity coverage.

Validation

• uv run python -m py_compile extensions/repository-governance/scripts/generate_repository_governance.py
• uv run python -m json.tool extensions/catalog.community.json > $null
• uv run python -m json.tool extensions/catalog.json > $null
• uv run python -m pytest -q tests/test_extensions.py::TestExtensionManifest::test_bundled_default_catalogs_match_manifest
• uv run python -m pytest -q tests/integrations/test_cli.py::TestGitExtensionDefaultInstall::test_community_extensions_and_workflow_preset_auto_installed tests/integrations/test_cli.py::TestGitExtensionDefaultInstall::test_git_default_keeps_community_defaults
• uv run python -m pytest -q tests/test_presets.py -k workflow_preset_integration_release_payload_contract
• uv run python -m pytest -q tests/test_arch_templates.py

Notes

• This targets the bigsmartben/spec-kit integration fork only; it does not open or push anything to github/spec-kit.
• Existing untracked local directory sdd 实践 was left untouched.

[bigsmartben]

Posted on behalf of @bigsmartben by Codex (model: GPT-5).

Review round update:

• Adjusted integration lifecycle tests to rely on the default bundled git extension installed by specify init, instead of attempting a duplicate specify extension add git.
• This fixes the pytest matrix failures caused by Extension 'git' is already installed.

Commit: 943503a

Validation:

• .\.venv\Scripts\python.exe -m pytest -q tests/integrations/test_integration_subcommand.py
• .\.venv\Scripts\python.exe -m py_compile extensions/repository-governance/scripts/generate_repository_governance.py
• .\.venv\Scripts\python.exe -m json.tool extensions/catalog.community.json
• .\.venv\Scripts\python.exe -m json.tool extensions/catalog.json
• .\.venv\Scripts\python.exe -m pytest -q tests/test_extensions.py::TestExtensionManifest::test_bundled_default_catalogs_match_manifest
• .\.venv\Scripts\python.exe -m pytest -q tests/integrations/test_cli.py::TestGitExtensionDefaultInstall::test_community_extensions_and_workflow_preset_auto_installed tests/integrations/test_cli.py::TestGitExtensionDefaultInstall::test_git_default_keeps_community_defaults
• GitHub Actions is green on the updated head.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 943503a288

ℹ️ 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]

Keep nested dotfiles in evidence scans

In monorepos or nested projects, runtime/style dotfiles such as packages/app/.env.example or packages/app/.editorconfig are now skipped because this filter only allows dotted filenames at the repository root. Those files are part of the newly indexed engineering-runtime inputs, so the generated projection can report engineering-runtime as missing and fall back even though a bounded-depth matching config exists; keep the previous bounded-depth name match for these dotfiles or restrict only names that truly must be top-level.

Useful? React with 👍 / 👎.