[Partner Nodes] Fix Recraft pricing placeholder and add missing Runway FirstLastFrame node

[lin-bot23]

Recraft — Replace the placeholder 0.21/run with 14 accurate rows covering all Recraft nodes with price_badge in nodes_recraft.py:

• Create Style, Text to Image, Image to Image, Inpainting (0.04 USD = 8.44 credits)
• Text to Vector (0.08 = 16.88)
• Vectorize Image, Remove Background (0.01 = 2.11)
• Replace Background (0.04 = 8.44)
• Crisp Upscale (0.004 = 0.84), Creative Upscale (0.25 = 52.75)
• V4 Text to Image (recraftv4: 0.04 = 8.44, recraftv4_pro: 0.25 = 52.75)
• V4 Text to Vector (recraftv4: 0.08 = 16.88, recraftv4_pro: 0.30 = 63.30)

Runway — Add the missing First & Last Frame Generation Product node (RunwayFirstLastFrameNode in nodes_runway.py, price_badge: 0.0715/sec = 15.09 credits/sec).

Languages: EN / ZH / JA
Files: 4 changed (3 pricing + .gitignore)

[coderabbitai]

📝 Walkthrough

Walkthrough

This PR updates pricing documentation for Recraft and Runway partner nodes across three language versions while also excluding a build directory from version control. The Recraft pricing table expands from a single row to multiple granular product/operation entries, and Runway pricing is refined with unit adjustments and a new product offering.

Changes

Documentation and Build Configuration Updates

Layer / File(s)	Summary
Build configuration .gitignore	.work/ directory is added to the ignore list to exclude temporary build artifacts.
Recraft pricing expansion across language versions tutorials/partner-nodes/pricing.mdx, ja/tutorials/partner-nodes/pricing.mdx, zh/tutorials/partner-nodes/pricing.mdx	Recraft pricing table transitions from a single catch-all row to a detailed breakdown with operation-specific entries (style creation, text-to-image, image-to-image, inpainting, vectorization, background operations, upscaling, and V4/V4 Pro variants) maintained consistently across English, Japanese, and Chinese documentation.
Runway pricing table refinement across language versions tutorials/partner-nodes/pricing.mdx, ja/tutorials/partner-nodes/pricing.mdx, zh/tutorials/partner-nodes/pricing.mdx	RunwayML image generation pricing unit is adjusted for consistency, and a new Runway First & Last Frame Generation product row is added with per-second video pricing across all language versions—quite the pricing frame of mind!

🚥 Pre-merge checks | ✅ 2

✅ Passed checks (2 passed)

Check name	Status	Explanation
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

✨ Simplify code

• Create PR with simplified code

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@ja/tutorials/partner-nodes/pricing.mdx`:
- Line 740: Several pricing rows in the MDX use inconsistent Japanese
translations for the "/ run" unit ("実行" vs "回"); pick one term (e.g., "回" or
"実行") and standardize every occurrence in the pricing tables across this
document so all product rows (including entries like the RunwayML "model:
gen4_image" row and BFL rows) use the same unit term; search the file for both
"実行" and "回" in pricing contexts and replace to the chosen term, and if unsure
of semantic nuance, confirm with a native reviewer before bulk replacing.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: 0fef9004-6aeb-4e90-bc7f-2babef8e9c7c

📥 Commits

Reviewing files that changed from the base of the PR and between fd21771 and 07f22bf.

📒 Files selected for processing (4)

• .gitignore
• ja/tutorials/partner-nodes/pricing.mdx
• tutorials/partner-nodes/pricing.mdx
• zh/tutorials/partner-nodes/pricing.mdx

[coderabbitai]

🧹 Nitpick | 🔵 Trivial | 💤 Low value

Translation terminology inconsistency worth noting (a unit pun, if you will).

The JA file uses both "実行" and "回" to translate the English "/ run" unit throughout the document. Line 740 changes from "実行" to "回", but this doesn't resolve the broader inconsistency (e.g., BFL section at line 27 uses "実行" while line 34 uses "回" for similar per-run pricing).

While this doesn't affect functionality, consider standardizing the terminology across the entire pricing table in a follow-up if there's no semantic distinction intended between these terms.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@ja/tutorials/partner-nodes/pricing.mdx` at line 740, Several pricing rows in
the MDX use inconsistent Japanese translations for the "/ run" unit ("実行" vs
"回"); pick one term (e.g., "回" or "実行") and standardize every occurrence in the
pricing tables across this document so all product rows (including entries like
the RunwayML "model: gen4_image" row and BFL rows) use the same unit term;
search the file for both "実行" and "回" in pricing contexts and replace to the
chosen term, and if unsure of semantic nuance, confirm with a native reviewer
before bulk replacing.