Latest Pack Fetch and Runtime Delivery
Runtime delivery follows the active project release, not draft editing state. The browser runtime resolves the active pointer, fetches the artifact for that version, verifies the signature, and then registers only the tools that are eligible for exposure.
Start from the active pointer
The runtime does not guess which release to load. It resolves against the active version for the project, which is why publish and activation state matter operationally.
This keeps runtime delivery aligned with the project release model instead of mixing draft state and live state together.
Fetch the artifact for that active version
After the active pointer resolves, runtime delivery fetches the concrete artifact file for that version. This is the materialized signed JSON output of the published pack.
That is the right place to use artifact language in docs, because the runtime is working with the actual file rather than the higher-level release concept.
Verify the signature before registration
Signature verification is part of the runtime delivery flow. Docs can say this confidently because the current product truth explicitly supports the active-pointer, artifact-fetch, and verify sequence.
This is also the boundary where docs should stay precise: verification here is about artifact delivery and integrity, not a blanket claim about every possible execution-time correctness guarantee.
Register tools selectively
- Eligible tools are registered into the runtime after the artifact is loaded and verified.
- Selective WebMCP registration is the right docs phrase because not every defined tool is automatically exposed.
- Teams should treat registration as an eligibility-driven runtime step, not as a guaranteed side effect of merely defining a tool in the project.
Do not imply blanket exposure
A project can define more tools than the runtime ultimately exposes. Docs should keep the selective-registration rule explicit so runtime behavior is not overstated.
Where runtime delivery issues usually show up
- Active-version state does not point where the team expects.
- Artifact delivery fails or returns the wrong release material.
- Signature verification rejects the fetched artifact.
- Tool eligibility prevents a defined tool from being registered or exposed.