add-app: flag no-outbound-email constraint in first-run bootstrap - #41
Open
ClaydeCode wants to merge 1 commit into
Open
add-app: flag no-outbound-email constraint in first-run bootstrap#41ClaydeCode wants to merge 1 commit into
ClaydeCode wants to merge 1 commit into
Conversation
Shards have no outbound SMTP, so any signup/login flow requiring an emailed verification link is a dead end. Document this in the first-run bootstrap check (phase 03) so packaged apps either disable email verification or seed the initial user via env vars. Surfaced by a support case: a custom-packaged rybbit app was unreachable at registration; even past the immediate crash, its email-verified signup would never complete on a shard. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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.
What
Adds an explicit constraint to the
add-appskill's first-run bootstrap check (phases/03-proposal.mdstep 2a): shards have no outbound SMTP, so any signup/login flow that requires an emailed verification link can never complete. The initial user must be creatable without email — either self-registration with email verification disabled, or seeded via env vars.Also tightens resolution option 1 (was: "leave self-registration ENABLED" — which silently assumed email-gated signup works) and adds option 1a (seed the first user via env vars, no email/UI needed).
Why
Surfaced by a support case: a user's custom-packaged rybbit app 502'd at registration. The immediate cause was a ClickHouse DB-init bug, but even once fixed, rybbit's email-verified signup would never complete on a shard — there's no way to send the verification mail. The skill already handles the shell-access bootstrap gap (exit-criterion j) but had nothing on the email gap, and its recommended path even assumed enabled registration just works.
Scope
Single-file doc edit to the
add-appskill. No app changes.🤖 Generated with Claude Code