[codeforester]

Summary

Closes #280.

• Add a pinned CodeQL workflow for Python on pushes, pull requests, and a weekly schedule.
• Add Dependabot configuration for pip and GitHub Actions updates.
• Document repository-level controls and their relationship to the runtime threat model and existing Bandit/pip-audit gates.
• Enable the repository's Dependabot security updates, secret scanning, and push protection settings through the GitHub API.

GitHub currently reports non-provider secret patterns and validity checks as plan-limited/disabled; the documentation records that these settings require readback and compensating controls.

Validation

• UV_CACHE_DIR=/private/tmp/base-cli-uv-cache uv run --extra dev --extra typer --extra quality ./tests/full_validate.sh --gate contracts
• UV_CACHE_DIR=/private/tmp/base-cli-uv-cache uv run --extra quality ./tests/full_validate.sh --gate style
• Parsed .github/workflows/codeql.yml and .github/dependabot.yml with PyYAML.
• git diff --check

GitHub settings readback

Dependabot security updates, secret scanning, and push protection are enabled on basefoundry/base-cli. CodeQL will report its first analysis after this workflow is merged.

[github-advanced-security]

You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool.

What Enabling Code Scanning Means:

• The 'Security' tab will display more code scanning analysis results (e.g., for the default branch).
• Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results.
• You will be able to see the analysis results for the pull request's branch on this overview once the scans have completed and the checks have passed.

For more information about GitHub Code Scanning, check out the documentation.