Runbook Library — forking and live updates

The Runbook Library (Marketplace → Runbook Library tab) is where you'll find public runbooks published by Turtini and partner orgs — fully validated lab guides you can fork into your own org and customize for your customers.

Browsing the library:
1. Go to Marketplace and click "Runbook Library"
2. Each card shows the runbook title, summary, author org, and step count
3. Click "View" to see the full runbook before forking, or "Fork" to copy it into your org

Forking a runbook:
• A copy is created in your org's runbooks list
• You become the owner of the copy and can edit any step, validation rule, or expected output
• The original runbook in the author's org is unaffected

Live inheritance from template runbooks:
Some public runbooks are published as **templates**. When you fork from a template, "Inherit updates" is turned on by default. When the author publishes a new version of the template runbook, your fork receives the update automatically:
• Existing steps from the template are refreshed
• Steps the author added are added to your fork
• Steps the author removed are removed from your fork

To stop receiving updates: open your fork → toggle "Inherit updates" off. Your fork is detached from the source and stays as it is now.

When to keep inheritance on vs. off:
• On — you're using a vendor-maintained playbook (e.g. Turtini-authored OpenShift install) and want bug fixes and version bumps automatically
• Off — you've heavily customized the runbook for a specific customer and need it frozen

Forks NOT created from a template are independent copies — there's no inheritance toggle, and they never auto-update.