From 152cb7b36e38cbe4c784cb29daf2251fd6aa291f Mon Sep 17 00:00:00 2001 From: DreamCoder08 Date: Wed, 30 Sep 2026 02:16:54 -0500 Subject: [PATCH] docs(odd): record the decision on projects that set strict mode themselves The earlier count of 31 was wrong: 72 checkouts of 15 repositories track STRICT_MODE=true, so it is committed project policy. The decision is to leave them alone and use --no-verify during a Codex outage. --- odd/tasks/gga-pin-and-matugen-hardening.md | 14 +++++++++++--- 1 file changed, 11 insertions(+), 3 deletions(-) diff --git a/odd/tasks/gga-pin-and-matugen-hardening.md b/odd/tasks/gga-pin-and-matugen-hardening.md index d77ad071..a0c774d1 100644 --- a/odd/tasks/gga-pin-and-matugen-hardening.md +++ b/odd/tasks/gga-pin-and-matugen-hardening.md @@ -65,8 +65,16 @@ grew, so the tasks and evidence below are reconstructed from the merged PRs. in suites that run with the real HOME (a leak once broke the live wallpaper runner); a test that cannot fail is worse than none (a vacuous injection test was removed). +## Decision (2026-09-30) + +An earlier count of "~31" project `.gga` files with `STRICT_MODE="true"` was wrong: a full scan +finds 72 checkouts of 15 repositories (50 of them worktrees of one `arkelythex` organisation +repository), all tracked by git, so the value is committed project policy rather than a personal +preference. The user chose **not to touch them**: during a Codex outage those repositories keep +blocking commits, and `git commit --no-verify` is the escape hatch (documented in +`docs/configuration/gga.md`). Changing them would mean editing tracked files in other +repositories, so it needs a per-repository decision by their owners. + ## Next step -Feature complete. Open decision for the user: ~31 project `.gga` files set -`STRICT_MODE="true"`, which overrides the global value and still blocks commits during a -Codex outage; they were deliberately not edited. +Feature complete; nothing pending.