This repository (.github) is the settings-as-code source of truth for the codeo1io account: common-settings.yaml, the daily sync scripts, workflow templates, and community health files. It is intentionally public (reusable workflows must be reachable from other repositories).

Open a private security advisory on this repository (Security → Report a vulnerability) or email the account owner directly. Please do not open a public issue for anything secret- or credential-related.

• Never commit secrets. All credentials live in the environment of the machines that run the sync (~/.hermes/.env on the ops host; see the secrets rule in AGENTS.md), never in this repository.
• Automated scanning. The private-leak-sentinel reusable workflow runs gitleaks via SHA-pinned gitleaks-action with the fleet gitleaks.toml checked out at a pinned ref. This repository self-scans on pushes to main and on pull requests (new commits only), and weekly (full history) via leak-sentinel-self, using the exact config each pushed commit ships; magic-hermes calls the same reusable workflow on its own pushes and PRs. Other fleet repos have no sentinel yet — adoption is tracked as roadmap rm-016/rm-038.
• Report-only posture sync. scripts/sync_repo_settings.py reports GitHub-native security posture (secret scanning, push protection, Dependabot security updates) drift on public repos but never changes it automatically — posture changes are explicit owner decisions.
• Host-key pinning. scripts/check_known_hosts.py verifies the full pinned SSH key set for github.com and [ssh.github.com]:443 against GitHub's published fingerprints and fails closed on any deviation.

This repository is public — and so are main and the data branch the daily mirror pushes to. The data branch carries a bounded tail of operational state: cron schedule inventory, runner names, conductor tracks, kanban OWNERS canon references, the corrections ledger, and the last 5,000 lines of watchdog alerts (scripts/sync_data_branch.py, executed daily at 08:40 UTC by the deployed cron wrapper; single-flight flock, branch restore on failure, bounded subprocess timeouts). Schedules, names, and alert summaries only — no scripts, tokens, or credential material are mirrored, by design. Because the mirror is world-readable, anything fleet-internal that must not be public belongs nowhere under control-plane/ in the first place (legacy public-main exposure of frozen control-plane copies is tracked as roadmap rm-015).