-
Notifications
You must be signed in to change notification settings - Fork 1
hygiene(tick-history): shard 0440Z — #1006 follow-up drain + #1010 merged #1023
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1 @@ | ||
| | 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. | | ||
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.