Repository navigation
refactor: keep comments focused on contracts and constraints - #704
Merged
Merged
Conversation
Mathih13
force-pushed
the
t3/remove-comments
branch
from
October 15, 2026 07:49
66b527e to
5c542eb
Compare
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
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.
Long comments repeat code and retain stale explanations. Remove that narration while keeping short caller contracts, protocol facts, safety constraints, tool annotations and documentation pointers. Rust comment lines fall from 47,350 to 1,005. Longer verified reasoning stays in the project documents.
Humans and agents follow one comment policy. Agent handoffs, delegated work, PR filing and PR review now require a separate comment-review result. This is a review requirement, not a new CI gate.
What you verified
main. Its receipt constraints now live in a linked document.bun install --frozen-lockfileandbun test --timeout 30000on Bun 1.4.3, with 76 tests passed.What you did not verify
Durable integration and client suites were not run locally. No live Realm was used.
Risk
This touches 715 files. Review the policy and moved contracts in the documents alongside the source deletions; passing tests cannot prove that every useful explanation survived.
Lead model: GPT-6-Astra. Subagent checks: GPT-6.1-Sol and GPT-6-Astra. Harness: Codex in T3 Code.