Skip to content

fix(connect): the generated face's prose names no business-line word - #127

Merged
antoinetoussaint-byte merged 1 commit into
mainfrom
fix/connect-face-neutral-prose
Oct 30, 2026
Merged

antoinetoussaint-byte merged 1 commit into
mainfrom
fix/connect-face-neutral-prose

Conversation

@antoinetoussaint-byte

Copy link
Copy Markdown
Contributor

Fixes #126.

The generated Connect face's docstring said a SETTINGS frame is scanned "holding one entry". holding is a business-line word module repositories refuse in every file they carry, and sync writes this file into the service's tree, so a module that turns connect-endpoint on fails its own boundary gate on output it may not edit (obin-ai/module-evaluation, scorer Connect face). "keeping" says the same thing. Same class as service-go-grpc 0.1.65.

Classification: fix at the owner (the template is the source of the generated file).

Verified: go test -count=1 -run Connect . green.

🤖 Generated with Claude Code

The face's docstring said a SETTINGS frame is scanned "holding one entry".
"holding" is a business-line word that module repositories' boundary gates
refuse in every file they carry, and the face is written into the service's
tree by sync, so a module that turns connect-endpoint on fails its own gate
on generated output it may not edit. "keeping" says the same thing.

Same class as service-go-grpc 0.1.65 (connect_gen.go).

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
@antoinetoussaint-byte
antoinetoussaint-byte merged commit c7603d1 into main Oct 30, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Generated connect_gen.py names a business-line word, so a module that turns connect-endpoint on fails its boundary gate

1 participant