Bug report - Copy error:

Bug Report: landingPageCreate tool intermittently fails to sync new/regenerated pages to board, causing 404 errors and silent content substitution

Summary
Multiple consecutive calls to the landingPageCreate tool, intended to update a single landing page (edits: remove sub-brand reference, change photo frame shape/size, adjust background color warmth, remove one image), resulted in two distinct failure modes across repeated attempts:

1. Newly created pages did not persist/sync to the board's connected artifacts, causing the returned URL to 404 for the user despite a successful-looking tool response.

2. On several calls, the tool ignored the exact HTML/htmlDescription payload provided and instead generated a completely unrelated generic template (dark navy/starfield theme, pricing tables, booking forms, testimonials, FAQ accordions) that contradicted explicit exclusion instructions in the prompt.

Steps to reproduce

1. Successfully create a landing page via landingPageCreate (mode: site) with a detailed htmlDescription and/or full html payload. Page connects correctly and is reachable (confirmed working: node landingPageNode-twilight-butterfly-B7dR3).

2. User requests a content/style edit to the existing page (no dedicated landingPageEdit tool was available in this session, only landingPageCreate).

3. Call landingPageCreate again, either with a full raw html string or with htmlDescription, explicitly targeting the same content and stating exclusions (e.g. "no pricing, no forms, no CTAs, no testimonials").

4. Observed results across ~5 consecutive attempts:

   • New nodeId generated each time (e.g. landingPageNode-fragrant-pond-3NUCe, landingPageNode-weathered-pond-8CgXj, landingPageNode-divine-grassland-kiU--, landingPageNode-little-waterfall-uV4vZ, landingPageNode-twilight-sky-reycr, landingPageNode-icy-brook-Y_Vwx).

   • Calling getConnectedArtifacts (no args) sometimes showed a different/older node still connected, sometimes showed the newest node, inconsistently.

   • Calling getConnectedArtifacts with the newest returned nodeId frequently returned {"found": false} immediately after a successful-looking landingPageCreate response.

   • Several responses returned HTML content bearing no resemblance to the submitted payload (unrelated dark-theme sales page with pricing/forms/testimonials), despite the tool call including exact matching HTML or a highly detailed, explicit htmlDescription with "ABSOLUTE EXCLUSIONS" instructions repeated at both the start and end of the prompt.

Expected behavior

• landingPageCreate should either update the existing connected page in place, or reliably attach the newly created page to the board so it is immediately reachable via getConnectedArtifacts and its live URL.

• When html is provided directly (not just htmlDescription), the tool should preserve that exact HTML rather than regenerating unrelated content.

• If no dedicated edit tool exists, this should be made explicit in tool discovery/schema so the agent doesn't attempt repeated blind landingPageCreate calls expecting in-place edits.

Actual behavior

• Page connection state was unreliable: newly generated nodes intermittently failed to attach to the board (404 on the user's end, found: false on getConnectedArtifacts).

• Content fidelity was unreliable: at least 2 of 6 attempts returned content unrelated to the submitted payload, including a full generic template with pricing, contact forms, testimonials, and FAQ sections that were explicitly excluded in the instructions.

• No landingPageEdit tool was discoverable via searchTools in this session (confirmed via direct lookup, returned "Unknown tool"), despite tool guidance text referencing "use landingPageEdit for any landing-page change." This mismatch between documented guidance and actual tool availability may be contributing to the retry pattern that triggered the sync issue.

Impact

• User (agency/business owner) was unable to reliably preview or share a client-facing deliverable for an extended period, requiring 6+ regeneration attempts across a single session.

• Repeated regeneration also means multiple orphaned/disconnected landingPageNode artifacts were created and left on the board (landingPageNode-blue-storm-9RZVo, landingPageNode-jolly-peninsula-gPBqH, landingPageNode-silent-cherry-FYH6v, landingPageNode-small-haze-sVL7i, landingPageNode-summer-plateau-SeJnH, landingPageNode-twilight-butterfly-B7dR3, plus the additional unattached nodes above), which may need manual cleanup.

Resolution in this session

• After multiple attempts, one landingPageCreate call using a highly detailed, explicit htmlDescription (rather than raw html) eventually produced a correctly synced, correctly styled page that connected properly to the board and was confirmed working by the user.

• Root cause of the intermittent success/failure was not identifiable from the agent side; behavior appeared non-deterministic across otherwise similar tool calls.

Suggested follow-up for engineering

• Investigate whether landingPageCreate write/attach-to-board is subject to a race condition or eventual-consistency delay that a synchronous getConnectedArtifacts check-immediately-after can outpace.

• Confirm whether a landingPageEdit tool is intended to exist for this integration tier; if so, investigate why it was not discoverable via searchTools in this session.

• Investigate why raw html payloads were sometimes discarded in favor of unrelated generated content; this suggests either a prompt-injection-like override happening server-side, a caching/template fallback bug, or model output not honoring the html field when both html and htmlDescription context exist.