feat(build-plan): customer_portal goal asks for connections + reservation deep-link - #8
Merged
Merged
Conversation
…tion deep-link The customer_portal goal was a generic "create a portal and embed it", so the integration agent never built the two flows the reference example demonstrates. Enrich it to request both explicitly: (1) an embedded connections-and-mapping page (connect + organize + manage), and (2) opening the portal directly to a reservation via pushData + landing_page/deep_link. Points the agent at the Customer Portal example app for structure. Keeps existing behavior: still names the framework, still ignores build-block selections (customer_portal has no hint lines). All build-plan tests pass.
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.
Summary
When testing the wizard against a Next.js PMS in Customer Portal mode, the integration agent produced only a generic embedded portal — never the connections/mapping and reservation-deep-link flows that the
next-app-router-customer-portalreference app (seam-ai#99/#100) now demonstrates.Root cause:
composeGoal()'scustomer_portalbranch is a fixed generic prompt ("create a Customer Portal, embed it, regenerate per visit"). It never asks for those capabilities, and customer_portal mode ignores the build-block selections. The richer example is only a structural reference — the goal defines what gets built, so the two flows could never appear.This enriches the customer_portal goal to request both explicitly:
is_embedded: true) withconnect+organize+manageso the customer connects device accounts and maps devices onto their spaces.customers.pushData) and create a portal deep-linked to it (landing_page/deep_link) that a reservation page links to.It also nudges the agent to model the structure on the Customer Portal example app.
Behavior preserved
…'s conventions).-hint lines) — the existing test asserts this.Testing
tsctypecheck cleanbuild-plan.test.ts— all 16 pass (incl. "describes the Customer Portal", "ignores selections", "names the framework for customer_portal too")Security & Compliance