Skip to content

[wix-manage] - #DOM2-8382 - rewrite domain search and purchase reference, add connect-domain path - #983

Open
maximzabuti wants to merge 4 commits into
mainfrom
maximz-domain-search-connect-rewrite
Open

[wix-manage] - #DOM2-8382 - rewrite domain search and purchase reference, add connect-domain path#983
maximzabuti wants to merge 4 commits into
mainfrom
maximz-domain-search-connect-rewrite

Conversation

@maximzabuti

Copy link
Copy Markdown

Summary

  • Restructures domain-search-and-purchase.md into four parts with letter-prefixed section numbers: A (entry & routing), P (purchase), C (connect), R (reference).
  • Adds a new path for connecting a domain the user already owns — ownership lookup and binding the domain to a site — alongside the existing buy flow.
  • Consolidates site resolution, ownership lookup, and error handling into Part R so both the purchase and connect paths share one reference instead of duplicating it.

Markdown-only change; no build or test impact.

🤖 Generated with Claude Code

…ect-domain path

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@maximzabuti

Copy link
Copy Markdown
Author

#allow_unsafe_merge_with_disabled_targets

@maximzabuti

Copy link
Copy Markdown
Author

#skipreview

@maximzabuti
maximzabuti force-pushed the maximz-domain-search-connect-rewrite branch from 8fff25e to 0b800b7 Compare August 12, 2026 14:50
@wix wix deleted a comment from github-actions Bot Aug 12, 2026
@maximzabuti

Copy link
Copy Markdown
Author

#skipreview

The YAML gate requires every changed doc under skills/wix-manage/ to be named by
a tool-call assertion in a scenario under yaml/wix-manage-evals/. The rewritten
domain-search-and-purchase reference had none, so the gate blocked on missing
coverage.

One scenario per path the doc now routes to. domain-buy-flow asserts the Part A
availability answer is stated plainly and that the turn continues into Part P
rather than ending there. domain-connect-owned asserts a user who already owns
the domain is read as a connect rather than a purchase, and that the outcome is
gated on the site's Premium plan per Part C. Both judges also fail any response
that narrates internal mechanics to the user, which is the recipe's standing UX
rule.

Neither scenario sets a top-level maxTokens. These are multi-step flows — the
measured runs came in at 142k and 588k tokens — so the 30k budget the
dashboard-navigation scenario uses does not transfer, and no budget in use
anywhere in the repo (highest is 150k) would fit the buy flow.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@maximzabuti
maximzabuti force-pushed the maximz-domain-search-connect-rewrite branch from 0b800b7 to 23320b8 Compare August 12, 2026 14:55
@maximzabuti maximzabuti reopened this Aug 12, 2026
@wix wix deleted a comment from github-actions Bot Aug 12, 2026
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.

1 participant