Repository navigation
docs(send-to-guide): enhance turns are free; render is the paid step - #2827
Conversation
The shipped pricing model is import + enhance turns free, only the final render charged (a monthly free-render credit, then per-minute). The guide labeled enhance as 'the paid step', which misstates the model to the authoring agent. Move the paid label to Render.
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
miguel-heygen
left a comment
miguel-heygen
left a comment
There was a problem hiding this comment.
Blocking — the corrected billing sentence is still not the shipped contract. The current server-side source of truth distinguishes tiers: FREE users receive 3 renders per month and are blocked when that allotment is exhausted; paid tiers have no monthly free-render step and are billed 20 credits/minute at render completion (magic_edit/logic/usage_limits.py). “A monthly free-render credit, then charged” reads as one universal free render followed by charging, so Claude would still be taught the wrong boundary. Please state the tiered contract explicitly (for example: “Free accounts receive 3 renders per month; paid plans are charged 20 credits per rendered minute”).
Blocking — pin this new LLM-facing invariant in the existing semantic contract test. packages/cli/src/commands/claude-design/sendToGuideContract.test.ts exists specifically because wording regressions in this guide silently steer Claude incorrectly. Add a concept-level assertion that the guide identifies Enhance as free and Render as the paid/billed step, plus a negative assertion that the retired “Enhance … paid step” wording cannot return. This keeps the correction from becoming stale again while avoiding an exact-sentence snapshot.
Everything else is clean at exact head bca07d576e: one guide-only 2+/2- delta, signed commit, docs validation and all applicable checks green.
…t in the guide test Address review: the pricing line must teach Claude the real tiered contract, not a single universal free render. Per heygen-server usage_limits.py: FREE accounts get 3 renders/month (then blocked, not billed); paid plans are charged 20 credits per rendered minute at completion. Enhance turns are free. Also pin the invariant in sendToGuideContract.test.ts: assert Enhance=free / Render=paid + the tiered figures, and a negative assertion blocking the retired 'Enhance ... paid step' wording from returning.
|
Both addressed in Tiered contract. Reworded to: "Render is the paid step: free accounts get 3 renders per month; paid plans are charged 20 credits per rendered minute." Confirmed against Test pin. Added to |
miguel-heygen
left a comment
miguel-heygen
left a comment
There was a problem hiding this comment.
Re-review at exact head 80eeb2f26c8dff1677c7f6d115fb970b446d2cc4 — both blockers are resolved.
The guide now states the shipped tiered contract precisely: Enhance turns are free; Render is the paid step; free accounts receive 3 renders/month; paid plans are charged 20 credits/rendered minute. The existing LLM-facing semantic contract test now pins those concepts independently and rejects the retired Enhance-as-paid wording without coupling to the full sentence. The two-file delta is clean and scoped; docs validation, build, lint, typecheck, format, producer/SDK/runtime-contract lanes are green, with only unrelated broad/Windows smoke lanes still settling and no failures.
Verdict: APPROVE
Reasoning: The pricing boundary and regression contract now match the source of truth and close both requested changes without widening scope.
— Magi
…eygen-com#2827) * docs(send-to-guide): enhance turns are free; render is the paid step The shipped pricing model is import + enhance turns free, only the final render charged (a monthly free-render credit, then per-minute). The guide labeled enhance as 'the paid step', which misstates the model to the authoring agent. Move the paid label to Render. * docs(send-to-guide): state the tiered render billing contract + pin it in the guide test Address review: the pricing line must teach Claude the real tiered contract, not a single universal free render. Per heygen-server usage_limits.py: FREE accounts get 3 renders/month (then blocked, not billed); paid plans are charged 20 credits per rendered minute at completion. Enhance turns are free. Also pin the invariant in sendToGuideContract.test.ts: assert Enhance=free / Render=paid + the tiered figures, and a negative assertion blocking the retired 'Enhance ... paid step' wording from returning.
What
One-line correction to the Send-to authoring guide's pricing summary. The guide labeled Enhance as "the paid step"; the shipped model is that import and enhance turns are free, and only the final render is charged (a monthly free-render credit, then per-minute after).
Before / after
becomes
Why
Claude Design fetches this guide (via the get-guide tool) to author Send-to compositions, so the pricing framing it reads should match reality. This aligns the guide with the same fix applied across the internal Send-to docs.