[prestoncabe]

Connected CRM hosts receive optional structured nextSteps with successful result messages. Screen, print, and CRM content share a projection of the saved screener copy, so application instructions and failed-check names stay consistent.

Closes #559. Sixth PR for #552, following #578.

This is an additive extension to protocol version 1, supported in object and JSON message modes. Only decided benefits are exported. Eligible entries include validated application/help links, a contact number, and Markdown instructions; ineligible entries include named unmet requirements and a Markdown note. No visible component omits the extension; whenComplete sends an empty object until every benefit is decided. Each new snapshot replaces previous instructions. A malformed optional extension is dropped without losing the decisions.

Print and CRM choose the first component whose own and ancestor conditions show it, using form-js's current expression context. Selection covers repeated scopes and dynamic lists with repetition disabled, and remains available during re-imports. Standalone screeners skip CRM projection. Existing stale-response and disconnection protections remain in force.

The browser and Salesforce examples save on the explicit Save action, render Markdown as text, omit empty sections, validate saved links with a shared adapter helper, and read older snapshots. Salesforce saves decisions without next steps when the optional instructions exceed its configured field size, and reports that omission. CRM example tests now run through devbox run test -- examples and in CI.

Validation:

• All 314 frontend tests passed locally, including non-repeating group selection, visibility changes, projection consistency, and adapter compatibility.
• Production frontend build passed.
• All 12 public Playwright tests passed locally: iframe/popup, object/JSON messages, persistence, hidden-content clearing, absent components, display settings, and printing.
• All 10 example tests passed through the shared runner.
• All six CI checks passed on the rebased, reviewed commit: frontend, builder API, library API, examples, documentation, and end-to-end (25 browser tests).
• git diff --check passed.