From ca30c327545e7611f758ccc23650093d7a4f772a Mon Sep 17 00:00:00 2001 From: Aaron Stainback Date: Fri, 1 May 2026 00:38:39 -0400 Subject: [PATCH 1/2] =?UTF-8?q?hygiene(tick-history):=20shard=200440Z=20?= =?UTF-8?q?=E2=80=94=20follow-up=20drain=20on=20#1006=20+=20#1010=20merged?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Two new findings on #1006 after prior drain: residual GOVERNANCE inclusion in bullet 4 (Codex P1) + §47 gap (Copilot). Both fixed; both resolved. #1010 merged — first PR from this session window to land. Class-level lesson: when fixing a scope/vocabulary inconsistency, grep the WHOLE file for the inconsistent term, not just the section that triggered the finding. Co-Authored-By: Claude Opus 4.7 --- docs/hygiene-history/ticks/2026/05/01/0440Z.md | 1 + 1 file changed, 1 insertion(+) create mode 100644 docs/hygiene-history/ticks/2026/05/01/0440Z.md diff --git a/docs/hygiene-history/ticks/2026/05/01/0440Z.md b/docs/hygiene-history/ticks/2026/05/01/0440Z.md new file mode 100644 index 000000000..db2cc6f6b --- /dev/null +++ b/docs/hygiene-history/ticks/2026/05/01/0440Z.md @@ -0,0 +1 @@ +| 2026-05-01T04:40:00Z | opus-4-7 / autonomous-loop tick | (this commit) | Follow-up drain on PR #1006 — 2 new threads after the prior tick's drain push: (1) Codex P1 — residual "memory or GOVERNANCE" phrasing in bullet 4 of How-to-apply reintroduced the policy ambiguity Why-2 excluded; fixed by scoping bullet 4 to memory + CURRENT-aaron only and explicitly restating GOVERNANCE-exclusion (mirrored in CURRENT-aaron §46). (2) Copilot — §45→§46→§48 gap (no §47); fixed by adding an HTML comment between §46 and §48 that explicitly notes the gap is reserved for #1008's §47, sibling-branch, do-not-renumber. Both threads resolved via GraphQL. PR #1010 (Roney→Rodney typo fix) MERGED — first PR from this session window to land. Cron 98fc7424 healthy. | [PR #1006: 2→0 unresolved (post-drain re-review)] / [PR #1010 MERGED] | The Codex P1 catch is interesting because I missed it in the prior drain — the residual "or GOVERNANCE" was in a different section (bullet 4 of How-to-apply, not bullet 3 of the Why list which I had fixed). Class-level lesson: when fixing a vocabulary or scope inconsistency, grep the WHOLE file for the inconsistent term, not just the section that triggered the finding. The HTML-comment-noting-gap pattern for §47 is the same shape as the chunk-N path-pointer fix — both turn a dangling reference into a self-explanatory documentation artifact. | From f1863c6c70d8052aabbe86ef6cbe5507c34ed851 Mon Sep 17 00:00:00 2001 From: Aaron Stainback Date: Fri, 1 May 2026 00:40:02 -0400 Subject: [PATCH 2/2] =?UTF-8?q?hygiene(tick-history):=20fix=20col3=20cron-?= =?UTF-8?q?sentinel=20=E2=80=94=20replace=20placeholder=20with=2098fc7424?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Per Codex P0/P1 finding: shard schema expects col3 to be the 8-character CronList job ID, not '(this commit)'. The cron sentinel column carries the liveness linkage between shard rows and CronList fires. Co-Authored-By: Claude Opus 4.7 --- docs/hygiene-history/ticks/2026/05/01/0440Z.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/hygiene-history/ticks/2026/05/01/0440Z.md b/docs/hygiene-history/ticks/2026/05/01/0440Z.md index db2cc6f6b..4e32afc99 100644 --- a/docs/hygiene-history/ticks/2026/05/01/0440Z.md +++ b/docs/hygiene-history/ticks/2026/05/01/0440Z.md @@ -1 +1 @@ -| 2026-05-01T04:40:00Z | opus-4-7 / autonomous-loop tick | (this commit) | Follow-up drain on PR #1006 — 2 new threads after the prior tick's drain push: (1) Codex P1 — residual "memory or GOVERNANCE" phrasing in bullet 4 of How-to-apply reintroduced the policy ambiguity Why-2 excluded; fixed by scoping bullet 4 to memory + CURRENT-aaron only and explicitly restating GOVERNANCE-exclusion (mirrored in CURRENT-aaron §46). (2) Copilot — §45→§46→§48 gap (no §47); fixed by adding an HTML comment between §46 and §48 that explicitly notes the gap is reserved for #1008's §47, sibling-branch, do-not-renumber. Both threads resolved via GraphQL. PR #1010 (Roney→Rodney typo fix) MERGED — first PR from this session window to land. Cron 98fc7424 healthy. | [PR #1006: 2→0 unresolved (post-drain re-review)] / [PR #1010 MERGED] | The Codex P1 catch is interesting because I missed it in the prior drain — the residual "or GOVERNANCE" was in a different section (bullet 4 of How-to-apply, not bullet 3 of the Why list which I had fixed). Class-level lesson: when fixing a vocabulary or scope inconsistency, grep the WHOLE file for the inconsistent term, not just the section that triggered the finding. The HTML-comment-noting-gap pattern for §47 is the same shape as the chunk-N path-pointer fix — both turn a dangling reference into a self-explanatory documentation artifact. | +| 2026-05-01T04:40:00Z | opus-4-7 / autonomous-loop tick | 98fc7424 | Follow-up drain on PR #1006 — 2 new threads after the prior tick's drain push: (1) Codex P1 — residual "memory or GOVERNANCE" phrasing in bullet 4 of How-to-apply reintroduced the policy ambiguity Why-2 excluded; fixed by scoping bullet 4 to memory + CURRENT-aaron only and explicitly restating GOVERNANCE-exclusion (mirrored in CURRENT-aaron §46). (2) Copilot — §45→§46→§48 gap (no §47); fixed by adding an HTML comment between §46 and §48 that explicitly notes the gap is reserved for #1008's §47, sibling-branch, do-not-renumber. Both threads resolved via GraphQL. PR #1010 (Roney→Rodney typo fix) MERGED — first PR from this session window to land. Cron 98fc7424 healthy. | [PR #1006: 2→0 unresolved (post-drain re-review)] / [PR #1010 MERGED] | The Codex P1 catch is interesting because I missed it in the prior drain — the residual "or GOVERNANCE" was in a different section (bullet 4 of How-to-apply, not bullet 3 of the Why list which I had fixed). Class-level lesson: when fixing a vocabulary or scope inconsistency, grep the WHOLE file for the inconsistent term, not just the section that triggered the finding. The HTML-comment-noting-gap pattern for §47 is the same shape as the chunk-N path-pointer fix — both turn a dangling reference into a self-explanatory documentation artifact. |