Frontend Snippet
The primary integration entrypoint for MergeSafe is a frontend script snippet. Teams install that snippet into the product surface that should load the project runtime, rather than hand-building the runtime boot sequence from scratch each time.
The primary runtime entrypoint
Docs should present the frontend snippet as the normal installation surface for product teams. It is the clear handoff between project configuration in MergeSafe and runtime behavior inside the website or app.
That matters because the snippet is not a marketing embed. It is the operational entrypoint that loads the project bootstrap and runtime path.
What the snippet conceptually does
- It identifies which project runtime should be loaded into the page.
- It starts the bootstrap path that resolves runtime assets and SDK setup.
- It creates the browser-side bridge that can later load the active pack and register eligible tools.
How it connects to bootstrap and runtime delivery
The snippet should be documented as the first step in a longer runtime flow. After installation, the project bootstrap route can load runtime JavaScript, initialize the SDK, and trigger pack loading for the active version.
This lets docs explain the runtime clearly without turning the snippet into something magical. It starts the flow, but it does not replace bootstrap, SDK initialization, or artifact delivery.
How to keep snippet docs clear
- Describe the snippet as a generated install surface, not as a hand-authored integration pattern.
- Keep the explanation product-doc clear rather than diving into low-level loader mechanics unless the page is explicitly implementation focused.
- Avoid implying that the snippet alone makes every defined tool callable; runtime loading and eligibility rules still matter.