[codex] Structure relay install confirmation conflicts - #3365

Files reviewed

• apps/web/src/cloud/relayClientInstallDialog.ts
• apps/web/src/cloud/relayClientInstallDialog.test.ts

Findings

The PR replaces a generic new Error("A relay client installation is already in progress.") with a structured RelayClientInstallConfirmationConflictError. This aligns well with the conventions:

• Imports: import * as Schema from "effect/Schema" uses the correct namespace subpath import. The named imports (RelayClientInstallProgressStageSchema, RelayClientInstallProgressEvent, RelayClientInstallProgressStage) come from the whole package @t3tools/contracts, which is explicitly exempt from the namespace rule. Verified these names are exported by the package.
• Error modeling: The failure is defined with Schema.TaggedErrorClass and carries structured, serializable attributes (requestedVersion, activeVersion, activeDialogStatus, optional activeInstallStage).
• Message: Derived exclusively from stable structural attributes, never from a cause.
• Cause: This is a pure domain/validation conflict (concurrent confirmation rejected) created without an underlying failure, so the absence of a cause field is correct and consistent with the conventions. The test explicitly asserts no cause property, which is appropriate.
• Discriminator: activeDialogStatus is a multi-value literal used both structurally and in the message, not a redundant single-value discriminator paired with the tag, so it does not violate the duplicate-distinction rule.
• Tests: Backend behavior changed (new typed error with structured fields/message), and a focused test was added to cover it — consistent with the change-discipline guidance.

No violations to report.

Tool Calls

Agent Credits: 36 credits