chore(standards): align the capture script's comment with main, byte for byte - #297
Merged
Merged
Conversation
…for byte COMMENTS ONLY. No logic changes, and the diff is 3 insertions / 7 deletions in a single comment block. The sticky-date fix was written twice — once on main (#295) and once here (#296) — with the same logic and DIFFERENT prose, because the develop copy added where the bug had been found. That left `capture-native-evaluability-snapshot.mjs` conflicting between the branches over ten lines of comment, after the whole point of the exercise had been to stop this file needing a decision at merge time. Taking main's text verbatim, so the file is byte-identical on both branches and drops out of the develop -> main conflict set entirely. Where the bug was found is recorded in #296's commit message and PR, which is the right place for it: a comment that differs per branch is a merge conflict pretending to be context. Verified that behaviour is untouched: `--check` passes, the replay is byte-identical, and the derived-artifact chain reports 5 links current and at a fixed point. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
📊 Bilingual Coverage ImpactPR Changes
Repository Coverage
To create skeletons: node .harness/scripts/generate-es-skeleton.mjs <file.md>Generated by GitHub Actions |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Comments only — 3 insertions / 7 deletions in a single block, no logic change.
The sticky-date fix was written twice, once on
main(#295) and once here (#296), with the same logic and different prose: the develop copy added where the bug had been found. That leftcapture-native-evaluability-snapshot.mjsconflicting between the branches over ten lines of comment — after the whole point of the exercise had been to stop this file needing a decision at merge time.Taking main's text verbatim, so the file is byte-identical on both branches and drops out of the
develop→mainconflict set. Where the bug was found stays in #296's commit message and PR, which is the right place for it: a comment that differs per branch is a merge conflict pretending to be context.Verified behaviour is untouched:
--checkpasses, the replay is byte-identical, the derived-artifact chain reports 5 links current and at a fixed point.Evolith Core Quality Gates
Linked ADRs / Issues
Conventional Commits
🤖 Generated with Claude Code