governance: add .gitignore housekeeping and regular audits; implement audit script and CI step; update templates, proposal, and docs
Some checks failed
ci / test (push) Has been cancelled

This commit is contained in:
2025-09-17 11:17:12 -05:00
parent bae62d94dc
commit 1eaa2f7997
14 changed files with 177 additions and 4 deletions

View File

@@ -30,6 +30,9 @@
-- Clean Roots --
- Keep repo root minimal; store assets under `docs/`, `templates/`, `collab/`, `prompts/`, `modes/`, `scripts/`, `meta/`. Avoid ad-hoc root files.
-- .gitignore --
- Require `.gitignore` with `runs/` and common OS ignores; keep updated as artifacts evolve.
-- CI/Containers (Gitea + Docker) --
- CI uses Gitea Actions in `.gitea/workflows/` with local parity via Docker Compose.
- Do work inside containers; host only for git/tea and Docker orchestration.
@@ -37,3 +40,6 @@
- Use explicit container/network names; remove orphans; clean networks/volumes.
- Mount host config (e.g., codex) when needed.
- Keep local/remote in sync; no dangling files or empty directories.
-- Audits --
- Run regular audits and prompt user before release tags. Record results in `docs/audits/`; summarize in DevLog.

View File

@@ -95,6 +95,10 @@ You are a coding agent running in the Codex CLI (terminal-based). Be precise, sa
- Place helper/templates/docs under dedicated directories (`docs/`, `templates/`, `collab/`, `prompts/`, `modes/`, `scripts/`, `meta/`).
- Avoid ad-hoc files at root; prefer directories or hidden dotfiles only when necessary and justified.
## .gitignore Housekeeping
- Every repo and generated project must include a `.gitignore` with at least `runs/` and common OS artifacts.
- Keep `.gitignore` current as new generated or runtime artifacts are introduced.
## CI and Containers (Gitea + Docker)
- CI: Use Gitea Actions exclusively. Store workflows under `.gitea/workflows/`.
- Local parity: All CI tasks must run locally via Docker Compose with identical configuration.
@@ -104,6 +108,11 @@ You are a coding agent running in the Codex CLI (terminal-based). Be precise, sa
- Config: Where host auth/config is required (e.g., codex), mount the necessary config dirs into the container securely.
- Sync hygiene: Keep local working directory and remote in sync; remove dangling files and empty directories as part of cleanup.
## Audits (Regular and PreRelease)
- Perform regular audits to verify governance compliance (TDD, zero-debt, clean root, CI parity, .gitignore coverage, structure).
- Prompt the user for an audit prior to cutting any release/tag.
- Maintain concise audit reports in `docs/audits/` and log summaries in DevLogs.
## Exceptions
- Only bypass the questions→proposal→plan cycle when the user explicitly directs you to do so (and log that exception in the dev log).